Error connecting to…
 
Notifications
Clear all

Error connecting to remote server

5 Posts
4 Users
0 Reactions
5,560 Views
0
Topic starter

Still trying to get through the initial settings. Once I save the settings and then return to Exchange section and hit refresh on the databases field, I get the following error:

Error! Connecting to remote server XXXXXXXX failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.

I have spun my wheels on this for a bit now to no avail. Any ideas?

5 Answers
0

It sounds like the application pool you are running CloudPanel under (in IIS) is not set to a domain user with rights. Please make sure the application pool CloudPanel is using is a domain administrator (should match what you have in the settings page of CloudPanel).

Also make sure Basic Authentication is enabled in Cloudpanel settings for Exchange and enabled on the /powershell virtual directory for Exchange.

0

Did you ever get yours fixed? I have the same problem, however my APP pool is set to a domain admin account with proper rights, etc.

0

Aaron,

You also need to enable Basic Authentication on the Exchange server powershell virtual directory. You can do this with EAC.

0

I was having the exact same issue with a server in my test lab.

I can confirm that:

  • the app pool is running with an domain admin account
  • the powershell virtual directory has basic auth enabled in iis
  • the powershell virtual directory in EAC has basic auth enabled
  • my username and password is correct and is in the form DOMAINadminusername

None of the above settings worked.

After digging around for some time I noticed that the powershell virtual directory was set to

“C:Program FilesMicrosoftExchange ServerV15FrontEndHttpProxyPowerShell”

so as a test I changed it to

“C:Program FilesMicrosoftExchange ServerV15ClientAccessPowerShell”

then tested again and it worked it seems that from Exchange 2013 CU3 the installer/updates change the powershell folder for some reason.

So far everything I am doing seems to work after changing the powershell physical path in IIS

 

0

I remember that being an issue in the early CU’s with Exchange… Keep in mind each CU is only supported for two months so you really should get to an updated CU… especially since Pre-SP1 there were TONS of issues

Share: