Hi again.
Master browsers have nothing to do with name resolution, they only collect and
distribute the browse list which is nothing more than a gui for users to see what
computers/shares are available on the network. Once a user tries to access a
resource, then the name resolution process begins. Now a computer that is a master
browse could also be a dns or wins server in which case they could be used in the
name resolution process but a computer that is a separate process from browsing.
When you ping a computer by name, then the computer returning the IP address must be
a wins [possibly wins proxy] or dns server. That is where I would look to see why
that computer is returning a bad IP by looking in the dns zone or wins database on
that computer, and also hosts, lmhosts files. When you cleared the wins database you
should tombstone entries instead of deleting them or old entries can reappear if you
deleted them on the wins server that was not the owner that originally registered the
record. A dns server can also use wins lookup if it can not find the name in the dns
zone if configured for wins lookups so it can be trick to track the problem down.
Below is a paste from Ethereal to show how the name resolution process works on a
domain computer. I pinged a non existent computer named "server33" from computer with
IP address of 192.168.1.22 and you can see that first dns name resolution was tried,
followed by wins server, and finally three broadcasts as shown by address of
192.168.1.255 which did not find the non existent computer. --- Steve
source destination
4 192.168.1.22 192.168.1.105 DNS Standard query A
server33.umbach1.com
5 192.168.1.105 192.168.1.22 DNS Standard query response, No
such name
6 192.168.1.22 192.168.1.105 NBNS Name query NB SERVER33<00>
7 192.168.1.105 192.168.1.22 NBNS Name query response
8 192.168.1.22 192.168.1.255 NBNS Name query NB SERVER33<00>
9 192.168.1.22 192.168.1.255 NBNS Name query NB SERVER33<00>
10 192.168.1.22 192.168.1.255 NBNS Name query NB SERVER33<00>
E-Double said:
How do the segment/domain master browser machines play into the name resolution
scheme of things ? We have been having ongoing problems with Netbios name resolution
on our Win2K Svr PDC. After making a change and disabling a few of its nics so that
it would no longer be multihomed, the Netbios name resolution still resolves its
name/path ( e.g. \\servername ) to the disabled IP addresses on the now-remote
subnets. The WINS and DDNS databases are updated to only reflect the PDC's current
IP address, and there are no entries in the lmhosts or hosts files on the clients.
The clients are configured for Hybrid Netbios resolution, but Peer was also tried.
After clearing the DNS, ARP, and NBTStat caches and running a network trace from a
client, when ping'ing the PDC it appears that another client machine ( segment master
browser ? ) is answering a NS query w/ the outdated IP address info for the PDC. Can
this happen ? And, if so, how does one fix this problem ? We have tried to disable
the Computer Browser Service on the clients ( to hopefully 'force' it to use WINS
directly ) but this did not help. Is it just a matter of shutting-off every client
PC on the entire lan, rebooting the server, and then trying again if it is in fact a
Browser Service problem ? Or is there some way to 'flush' the master browser entries
? TIA for any help as it would be greatly appreciated ...
