2 IPs , 2 Hostsnames, 1 Server

I have a server die on us, I have moved the files from that server to a temp server. The temp server already has a hostname and IP (as you would expect) but what I want to do is add the IP of the old server to the current NIC and then share the folders exactly the same as they where on the old server. This will then allow all users to use the same mapped drives etc.

eg

Old server

Hostname - old_server IP 172.1.1.2

Temp Server

Hostname - temp_server IP 172.1.1.1

I want to be able to point the old server name to the temp server but it simply will not work. ping resolves no problem, rdns works no problem as does nslookup old_server, but \\old_server will not work, I get "The network path was not found" Any ideas?

Not sure how old this setup is, but... if needs be, is old_server registered in WINS?

yes, but the IP is correct

Hmm... What does netstat -a tell you the host resolves to?

Can't you delete the A record for the old dead server from DNS then create a CNAME record with the same old server's hostname pointing at the temp server?

I've seen this before, I think it's down to the lanmanserver service only listening against the original server name. Can you view the shares if you look at by its IP addresses?

The way I fixed it was to add a registry key - HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters\DisableStrictNameChecking. Add it as a DWORD with a decimal value of 1.

I have had issues making my DC come fileserver accept file sharing requests on more than one IP. Do you have any clients that are going to try and access the share by IP Address? If not then it will be much less hassle to put a CNAME (or an extra A record) in DNS. If you can't do that then you could check the bindings for the network services. Start -> Control Panel -> Network Connections. Then choose Advanced Settings from the Advanced menu. I don't have 2 addresses on any of my NIC's so I don't know if there are any useful options for you in there or not.

Quote:

---

Originally Posted by burble

I've seen this before, I think it's down to the lanmanserver service only listening against the original server name. Can you view the shares if you look at by its IP addresses?

The way I fixed it was to add a registry key - HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters\DisableStrictNameChecking. Add it as a DWORD with a decimal value of 1.

---

^^^^^^This

Quote:

---

Originally Posted by burble

I've seen this before, I think it's down to the lanmanserver service only listening against the original server name. Can you view the shares if you look at by its IP addresses?

The way I fixed it was to add a registry key - HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters\DisableStrictNameChecking. Add it as a DWORD with a decimal value of 1.

---

and this was on on the server that the CNAME points to?

all sorted with the reg key... once again Hexus community shows its brilliance.

thanks everyone.

Good stuff :)

nice one ! I can never remember the reg key for that one.