How can I make a Windows 2008 R2 machine have more than 1 hostname?

Posted on

How can I make a Windows 2008 R2 machine have more than 1 hostname? – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.

But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about windows, networking, domain-name-system, , .

Have a small network of Windows XP machines set up where everyone’s files are on a machine named M99. Recently, I’ve built a Windows 2008 R2 machine, and would like to move the files to it, but…this server is named FMS. All the other computers have configuration pathnames that would have to change from \M99whatever to \FMSwhatever, and I don’t want to spend all day (or days) making this change. What I would like to do (for now), is just change the name of the M99 computer, and somehow make the FMS computer look like it’s M99. This fix will solve things nicely until the larger project of re-working everything into an AD domain is completed. How can I make FMS take on M99’s identity?

Solution :

Create your shares and move the files as you are planning, then do one of the following based on what your name resolution mechanism is:

1) create a DNS alias (CNAME) record. The name of the record would be M99 and the machine it points to would be FMS. Then M99 would resolve in DNS to FMS.

or

2) create host file entries on your workstations for M99 with the IP address of FMS.

Note both of these solutions assume that the FMS server is actually not available on the network as FMS anymore so you’ll either have to completely take it offline or rename it.

You will also have to disable strict name checking on the FMS server, otherwise connections to the alias will fail (ie- it’ll only accept connections using the FMS name and both).

Create a new DWORD and set the value to 1, then reboot the server to make it active.

HKLMSYSTEMCurrentControlSetServicesLanmanServerParametersDisableStrictNameChecking 

See this TechNet article for more info.

Leave a Reply

Your email address will not be published. Required fields are marked *