How to re-scan relationship between network computer names and ip addresses
(Originally asked on Microsoft Answers http://answers.microsoft.com/en-us/windows/forum/windows_xp-networking/how-to-re-scan-relationship-between-network/97fad8b2-742c-4c49-a7f9-c28f6d5a5b60 Basith M suggested I try here.) On my SBS 2003 network with six or so domain client PCs, and a few extra non-domain workgroup PCs (some XP, some Windows 7, all PCs in the 192.168.0.### range with 255.255.255.0 subnet), the computers can access each other using \\computername. When I change the normally-dhcp-assigned IP address of a computer on my network to a static IP address, sometimes the other PCs can no longer use \\computername, but now need to use \\ip-adress instead. Example: A computer can open the "\\mypc\shared" folder. I change the IP address on "mypc" to a static ip address, 192.168.0.220. Now the other computer needs to use \\192.168.0.220\shared" to get to that folder; "\\mypc\shared" returns an error that the specified computer can't be found (or something like that). I know that I can enter names and ip addresses in the Hosts file, but that's manual, and the computers did it automatically the first time. I have also learned that eventually the other PCs may find the PC with the changed IP address and be able to access by \\computername again. Eventually... How can I get the PCs to re-scan the computer names and IP addresses and link them up again (preferably right away)?
February 10th, 2012 10:44am

Hi, Regarding this issue, I suggest that you could try the following methods: 1. Use ipconfig /flushdns to refresh the DNS cache. 2. Check the Address record on the DNS on the SBS server 2003. Best regards, Della Li
Free Windows Admin Tool Kit Click here and download it now
February 13th, 2012 1:51am

Sounds like interesting ideas, folks! Thanks very much. ipconfig /flushdns and "nbtstat -RR" I'll try them soon as this problem happens again. Della, a question (since I'm really green on this stuff): Would the Address record on the server be under Administrative Tools -> DNS -> Forward Lookup Zones -> "our.domain"? Or is that record somewhere else? I did find there a list of all the ip addresses the server has handed out to client PCs over the years, but not any of the workgroup PCs.
February 15th, 2012 3:38pm

Sounds like interesting ideas, folks! Thanks very much. ipconfig /flushdns and "nbtstat -RR" I'll try them soon as this problem happens again. Della, a question (since I'm really green on this stuff): Would the Address record on the server be under Administrative Tools -> DNS -> Forward Lookup Zones -> "our.domain"? Or is that record somewhere else? I did find there a list of all the ip addresses the server has handed out to client PCs over the years, but not any of the workgroup PCs.
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2012 3:38pm

If you change the IP adress on a client you can also do a "ipconfig /registerdns" to register the new IP adress with the DNS record instantly. Then as the other guys pointed out, do a "ipconfig /flushdns" on the other clients so they receive the new update and don't use an obselete record :) This cache will be updated by itself eventually though, but this is just to speed up the process.Website: www.danielclasson.com | LinkedIn: Daniel Classon
February 15th, 2012 6:23pm

If you change the IP adress on a client you can also do a "ipconfig /registerdns" to register the new IP adress with the DNS record instantly. Then as the other guys pointed out, do a "ipconfig /flushdns" on the other clients so they receive the new update and don't use an obselete record :) This cache will be updated by itself eventually though, but this is just to speed up the process.Website: www.danielclasson.com | LinkedIn: Daniel Classon
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2012 6:23pm

If you change the IP adress on a client you can also do a "ipconfig /registerdns" to register the new IP adress with the DNS record instantly. Then as the other guys pointed out, do a "ipconfig /flushdns" on the other clients so they receive the new update and don't use an obselete record :) This cache will be updated by itself eventually though, but this is just to speed up the process.Website: www.danielclasson.com | LinkedIn: Daniel Classon
February 15th, 2012 6:23pm

Also in a command prompt type in nbtstat -RR this will purge the WINS cache and the PC will put out a new call to refresh and update WINS.
Free Windows Admin Tool Kit Click here and download it now
February 16th, 2012 7:15pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics