Exchange 2010 remote PowerShell breaks after add/remove/change of IP Address

by Nicolas Blank on 5 April 2011 · 3 comments

in Exchange,PowerShell,Tips & Tricks

Something that occurs in a lab situation quite frequently and less in real life is changing IP addresses on your Exchange server. Some of my lab servers frequently undergo a scenario change where I’ll add or remove them from specific Hyper-V networks or subnets.

 

Then one day everything broke. EMS reported :

Connecting to remote server failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooting Help topic.

image

 

EMC reported a slightly different error:

The attempt to connect using “Kerberos” authentication failed, etc, etc however the message points to the fact that the WinRM URL isn’t where it’s expected to be.

image

 

Bearing in mind that we know that the machines IP addresses have changed a little, it makes sense to have a look at the IIS configuration.

Looking at the bindings of the default web site I can see that something is amiss, since the IP address reflected is the new IPadress of the new subnet I connected to, as opposed to the expect machine address, or even All Unassigned on the Default Site as I would expect.

image

I changed the bindings back to All Unassigned, and restarted the web site

image

 

EMS and EMC are back in business.

image

Share this post:
  • Twitter
  • muti
  • laaik.it
  • Facebook
  • Posterous
  • del.icio.us
  • Digg
  • Live
  • LinkedIn
  • Slashdot
  • StumbleUpon
  • Suggest to Techmeme via Twitter
  • Fark
  • email

{ 3 comments }

Álvaro Vieira November 30, 2011 at 3:51 pm

Hi,

I have the same problem, when I change the IP address, the EPS doesn´t work, the message error is: permission denied.

How can I resolve this problem?

Regards,

Álvaro

roys April 17, 2012 at 7:44 am

check your clock. in my case the hyper-v host was off –> the VMs were off

problem resolved by setting time sync to work properly

prescription glasses transition progressive January 19, 2013 at 3:05 am

Thanks for sharing your info. I really appreciate your efforts and I am waiting
for your next post thanks once again.

Comments on this entry are closed.

Previous post:

Next post: