Networks

Ask something
Discussion Locked

Name Cache

0 helpful
2 replies

by netadmin 1 view

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

I administer a peer-to-peer workgroup. There is a Windows 2000 Server which stores all sensitive data, and about 14 Windows98 clients which make up the network.

The windows98 machines have shortcuts to server folders on their desktops. Often, they are unable to open them. the IP address of the server is 192.168.0.1, which I can ping from any machine on the network. However, when I ping server1 by name on the computers when they are unable to open the server folders, it tries to ping 192.168.0.43, which is not the server's IP Address. If I run the nbtstat -r command to flush the name cache, the clients will work fine for a day or two, then the next day they may do the same thing again... they can ping server1 by address, but not by name.

Any suggestions on how to fix this?

thanks

2 replies

by andrew cooke

This can be fixed. Firstly if you can answer.

What is 192.168.0.43 ? Is it another server or workstation ?

Do the Win2k server runs WINS (I don't expect so ?)

If 192.168.0.43 is another workstation, same as the other 14 computers, it must have had some additional information applied to it in the past. And it is answering NetBios name queries.

Try the name flush on that server.

Also see if you can work out who the master browser is by typing

nbtstat -c

Or even better copy the results of that command here

by mshavrov

First of all. There are 2 different "naming mechanisms" in Windows:

1. IP Name Resolution. It works with all legacy IP applications (Internet Explorer) and utilities (like ping, tracert, or telnet). System resolves names either through "hosts" file (stored in c:\windows\system32\drivers\etc), or through DNS (internal or external).

2. NetBIOS Names. This names are used for "Network Neighborhood Browsing", file and printers sharing, etc. (i.e. Microsoft Networking). NetBIOS Names can be resolved by 3 ways: WINS server (have to configure in TCP/IP properties), LMHOSTS file (stored in the same folder with HOSTS file), or by LAN broadcasts.

So, you can be able to resolve name in "ping" utility but be unable to share files with a server and viceversa.

You may ignore "ping" part of troubleshooting and look at NetBIOS part. First of all, check if you have anything configured in c:\windows\system32\drivers\etc\lmhosts file. If you have this file created, you may just add correct entries into this file and reboot your workstation. But this way is not scalable. Since you have Windows 2000 server, it would be easier to install and enable WINS server on that machine. It's very easy and strightforward. Then either modify your workstations' TCP/IP properties (WINS Tab), or modify your DHCP Scope.
And last thing, why you may have screw-up with 192.168.0.43 address - check all workstations names in your network. May be you have a workstaition with name "server1" and it may answer to broadcast request faster than real server.

If you have more questions, send me e-mail.

Michael Shavrov
CCNP, CCDP, MCSE W2K, Security+, ...

This discussion is closed to new replies.