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\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
Sterling SchaeferAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cris HannaCommented:
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
Sterling SchaeferAuthor Commented:
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
Cris HannaCommented:
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
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

Sterling SchaeferAuthor Commented:
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
Cris HannaCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Sterling SchaeferAuthor Commented:
Thank you for the link.  I am now able to get into my exchange console and exchange shell.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.