Problem with IP address - Ping and map network drive results different

[Randy K]

My agency just with week moved from one NAS (Network Attached Storage)
to another. Each device keep its original IP address. When we
installed the first NAS years ago we didn't have a domain name server
so we hardcoded the IP address in each User's HOSTS file.

When we did the switch over last weekend we removed the host name
entry in all HOSTS files (old IP address) and put a hostname entry in
the DNS server for the first time. So we removed the line
198.222.177.30 dnrolympia
from all hosts files. The Network administrator then added
198.222.177.55 dnrolympia
to the DNS resolver. Problem is some PC that had an L: drive mapped
to dnrolympia are still getting the .30 and not the .55. A ping
displays the new IP address but a Map network drive goes to the old.
In both cases using the host name dnrolympia

Any idea what might be causing this?

 

[Lanwench [MVP - Exchange]]

In

My agency just with week moved from one NAS (Network Attached Storage)
to another. Each device keep its original IP address. When we
installed the first NAS years ago we didn't have a domain name server
so we hardcoded the IP address in each User's HOSTS file.

When we did the switch over last weekend we removed the host name
entry in all HOSTS files (old IP address) and put a hostname entry in
the DNS server for the first time. So we removed the line
198.222.177.30 dnrolympia
from all hosts files. The Network administrator then added
198.222.177.55 dnrolympia
to the DNS resolver. Problem is some PC that had an L: drive mapped
to dnrolympia are still getting the .30 and not the .55. A ping
displays the new IP address but a Map network drive goes to the old.
In both cases using the host name dnrolympia

Any idea what might be causing this?

Is dnrolympia showing up in your internal DNS properly? Everyone pointing at
the right DNS server? Do you use WINS?

Did you check for both HOSTS and LMHOSTS in the clients?