You don't say what operating systems are involved so I am assuming W2K domain and W2K
and or XP Pro clients. If that is the case they will use dns name resolution first
even for netbios names by appending the domain name to the nebios name and then doing
a dns name lookup. If your domain is abc.com and you are trying to resolve the name
of computer server1 the client computer will do a dns lookup at it's preferred dns
server [which needs to be an AD domain controller running dns for the domain] for
server1.abc.com. Only if server1.abc.com is not found in the domain zone, then will
first wins lookup and then broadcasts be used for netbios name resolution [assuming
no hosts/lmhosts/or cache entries for dns or netbios] . Nslookup could be helpful in
determining if proper dns name resolution is happening. You could run nslookup and
then query for the PDC fsmo role holder domain controller to see what IP address is
returned. Keep in mind that if you have wins referral enabled for your dns zone that
bad IP mappings can be coming from the wins database. Ipconfig /displaydns will also
help determine if dns name resolution is being used as would nbtstat -r for netbios
name resolution.
http://support.microsoft.com/default.aspx?scid=kb;en-us;200525
It would also be a good idea to first run netdiag and then dcdiag on your newly
configured PDC looking for any failed tests or other errors/warnings that may help
pinpoint the problem and look in Event Viewer for clues. These tool are on the
install disk under support tools where you will need to run the setup program there.
First I would run netdiag /fix and the restart the netlogon service on that PDC. I
have also fount that a packet sniffer is real handy in resolving name resolution
problems. There is no Netmom built in on client operating systems but Ethereal is
free and a joy to use. If you want to try it, start it up just before you try to ping
the PDC and watch the name resolution process and what servers are queried for dns or
wins and their responses. --- Steve
http://www.ethereal.com/
E-Double said:
a site has a PDC that was multi-homed ( 4 nics ) that they are now trying to run on
one nic. after disconnecting three nics from their respective segments, configuring
a new router, and clearing the WINS, DNS, and DHCP scopes the client machines on the
three subnets that had their direct connections/nics to the PDC removed still resolve
the PDC Netbios name to the old PDC IP addresses ( this affects all mapped drives,
printer paths, folder access, etc... ). at first it was believed to be a lingering
entry in the DDNS database, but after using other DNS servers ( and checking the DDNS
database ) that proved not to be the case. in troubleshooting, all other machines
were brought down to prevent any clients acting as segment browsers to progogate any
false/outdated info and the arp, netbios, and dns caches were all flushed and the
machines rebooted several times. the lmhosts files and hosts files also don't have
any suspicious/old entries that might cause the problem. the client machines on the
three misbehaving segments seem to route all other IP traffic okay, can access the
PDC on the other subnet by IP address, and internet dns resolution works great. and
they can still get DHCP info from the PDC on the other segement as well. but
correcting the name resolution problem to the PDC on the other three segments has
proven to be a daunting task. any help would be greatly appreciated. TIA ...
