Discussion Locked

IIS Error after Server Name Change

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Yesterday I changed one of our server names. This involved adding the new computer name to Server Manager and deleting the old one, changing the name in the Network properties, and updating the DNS with the new IP address. I really feel like I'm leaving something out here.

The reason is because when I try to open Internet Service Manager (IIS), I get the following error:

Error connecting to (old computername): the RPC server is unavailable.

Is there some reason why IIS would still try to connect to the old machine name instead of the new one? The strange thing is that only one of the web sites that we have on that machine works and the others don't. This is an internal machine, so we've been using host headers with the machine's IP address.

Sorry about the points, I don't have any more to give.

Any ideas?

7 replies

by ckern

I had the same thing occur when I loaded a new machine to replace an existing IIS server. IT didn't seem to cause a problem unless we had MTS installed on the same server. I spoke with MS at that time - they thought it was odd that I would change the name and I am glad to hear I am not the only one doing this!! The only way to correct it was to change the registry entries or to re-install IIS. There were a ton of references to the server name in the registry settings for IIS. GOOD LUCK!!

by gregory w. smith

You're using the Microsoft Management Console (MMC) which remembers it's prior settings. Simply change them (remove offending part; add a module that references the proper name) and save the console.

This discussion is closed to new replies.