Sterling Schaefer
asked on
SBS 2011 Exchange Console WS-Management Does Not Support the Request / remote.hosname.com 401.0
I have been troubleshooting my SBS 2011 server for the past few weeks, and have been unsuccessful in resolving the few issues I am experiencing.
Here is where things stand now:
I have a domain registered, and set up in the DHCP server (for privacy purposes, I will call it server.hostname.com & server.hostname.local)
When going to remote.hostname.com, I get a 401.0 error
When I launch the Exchange Management Shell, I get The WS-Management service does not support the request
When I run the Exchange Management Troubleshooter, it gives the same error as the Shell, with the problem found of Path of:
The Path of the Powershell virtual directory has been modified. The PowerShell virtual directory must point to the "\Exchange Server\v14\ClientAccess\Po
When looking in the IIS Manger, Default Web Site / PowerShell has the following listed in Basic Setting:
Alias: PowerShell
Application pool: MSExchangePowerShellAppPoo
Physical path: c:\program files\microsoft\exchange server\v14\clientaccess\po
When selecting Test Connection, it fails with:
Invalid application path
The Application Pool for MSExchangePowerShellAppPoo
.NET Framework v2.0.50727
Managed pipeline mode: Integrated
Start application pool immediately is checked.
Going to http://www.hostname.com/PowerShell prompts for a user/password, but does not take admin user
Here is where things stand now:
I have a domain registered, and set up in the DHCP server (for privacy purposes, I will call it server.hostname.com & server.hostname.local)
When going to remote.hostname.com, I get a 401.0 error
When I launch the Exchange Management Shell, I get The WS-Management service does not support the request
When I run the Exchange Management Troubleshooter, it gives the same error as the Shell, with the problem found of Path of:
The Path of the Powershell virtual directory has been modified. The PowerShell virtual directory must point to the "\Exchange Server\v14\ClientAccess\Po
When looking in the IIS Manger, Default Web Site / PowerShell has the following listed in Basic Setting:
Alias: PowerShell
Application pool: MSExchangePowerShellAppPoo
Physical path: c:\program files\microsoft\exchange server\v14\clientaccess\po
When selecting Test Connection, it fails with:
Invalid application path
The Application Pool for MSExchangePowerShellAppPoo
.NET Framework v2.0.50727
Managed pipeline mode: Integrated
Start application pool immediately is checked.
Going to http://www.hostname.com/PowerShell prompts for a user/password, but does not take admin user
ASKER
My mistake, I meant DNS server, not DHCP server. This was added so that I could resolve the domain from within the network since the router used does not support loopback.
Server was installed about 2 years ago, and was working properly. When the server was initially set up, I did run the Connect to the internet wizard.
Server was installed about 2 years ago, and was working properly. When the server was initially set up, I did run the Connect to the internet wizard.
And how did you add this to the DNS server? Running the Setup my internet address wizard typically creates the split DNS setup for you. No manual entries required.
Is the end goal to resolve external rww address internally, or to resolve your www/public website internally?
Is the end goal to resolve external rww address internally, or to resolve your www/public website internally?
ASKER
I believe that this was added manually through he DNS control panel although maybe it was added by the wizard. The point does not really matter how it was added, but more that I am using a FQDN to access remote.hostname.com which resolves to the local server. This is the same for internal IPs and external IPs (although they go to different IPs since external goes through the router and internal is direct to the server)
The end goal is for me to be able to access the exchange shell or the exchange gui application. I would also like to access remote.hostname.com from both internal machines, and external IPs.
I believe that the 2 issues are related, since they started to fail around the same time (I do not normally need to manage the exchange server, so I do not know for 100% certanty when they both started) If it is the case that the 2 are not related, I can resolve the first issue, and then move to work on the 2nd issue later.
The end goal is for me to be able to access the exchange shell or the exchange gui application. I would also like to access remote.hostname.com from both internal machines, and external IPs.
I believe that the 2 issues are related, since they started to fail around the same time (I do not normally need to manage the exchange server, so I do not know for 100% certanty when they both started) If it is the case that the 2 are not related, I can resolve the first issue, and then move to work on the 2nd issue later.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you for the link. I am now able to get into my exchange console and exchange shell.
Did you initially run the Connect to the internet wizard ' and the Setup your internet address wizard '?
How long has your server been installed and did it ever work properly?