Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

SBS 2011 Exchange Console WS-Management Does Not Support the Request / remote.hosname.com 401.0

Posted on 2014-10-09
6
Medium Priority
?
352 Views
Last Modified: 2014-10-11
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\PowerShell"
When looking in the IIS Manger, Default Web Site / PowerShell has the following listed in Basic Setting:
Alias:      PowerShell
Application pool:      MSExchangePowerShellAppPool
Physical path:      c:\program files\microsoft\exchange server\v14\clientaccess\powershell\
When selecting Test Connection, it fails with:
Invalid application path

The Application Pool for MSExchangePowerShellAppPool has:
.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
0
Comment
Question by:Sterling Schaefer
  • 3
  • 3
6 Comments
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 40372680
You say that you put server.domain.com in your DHCP server?  It does not belong there.
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?
0
 

Author Comment

by:Sterling Schaefer
ID: 40372913
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.
0
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 40373128
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?
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 

Author Comment

by:Sterling Schaefer
ID: 40373173
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.
0
 
LVL 35

Accepted Solution

by:
Cris Hanna earned 1500 total points
ID: 40373205
my first suggestion would be that you run the Fix my network wizard from the Network > Connectivity section of the SBS console.  Let it attempt to fix anything it finds (it's going to complain about ports on your router and that it can't fix that ....that's normal...you can even uncheck it as an item to let the wizard try to fix)

Then I would download the SBS BPA https://support.microsoft.com/kb/2673284?wa=wsignin1.0
Make sure you get it updated to 1.5 or the results are pretty useless.   And fix anything it finds as well, whether you think it's related.

Then we can see if the you can access the EMC.
0
 

Author Comment

by:Sterling Schaefer
ID: 40374874
Thank you for the link.  I am now able to get into my exchange console and exchange shell.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In the event you manage a Small Business Server 2003, and you are audited for PCI compliance, there are several changes you must make in order to pass the audit. I can take no credit for discovering any of these fixes or workarounds, but there is no…
I've often see, or have been asked, the question about the difference between the Exchange 2010 SP1 version, available as part of Small Business Server (SBS) 2011, and the “normal” Exchange 2010 SP1 Standard. The answer to the question is relativ…
Integration Management Part 2
In response to a need for security and privacy, and to continue fostering an environment members can turn to for support, solutions, and education, Experts Exchange has created anonymous question capabilities. This new feature is available to our Pr…

972 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question