Netbios name resolution problem

[Guest]

A multihomed PDC has had two of its four NICs disabled. The WINS database on that server has been updated and all of the outdated entries for those two NICs have been removed. Client machines still resolve Netbios names to those two nonexistant NIC IP addresses for some strange reason. Changing the node type from Hybrid to Peer ( to the updated WINS database server ) did not help either, nor did several reboots and flushing of the Nbtstat cache. There are no entries to the outdated/nonexistant addresses in either the lmhosts or hosts files of the clients. Other peer machines on that segment were also shut down to prevent possible Segment Master Browser issues, but to no avail ( that was a desperate guess ). Where is this outdated/nonexistant Netbios info coming from, and how does one disable/avoid that ? Is this a registry setting somewhere ? Some client machines even briefly reflected the new Netbios info, then reverted back to the old, nonexistant addresses again. TIA for any help on this one ...

 

[Larry Stotler]

Hello,

I am assuming that the clients are pointing ONLY to the WINS server you are
working on. If this is not true then look to any other coinfigured WINS
servers to see if the record exists there also.

Also if these are 2000 or XP clients, they will append thier Domain suffix
to the netbios name and look to DNS to resolve it. Look in your DNS
servers to see if the old entries are there.

I would suggest taking a Network trace to get the final answer on who it is
asking for name resolution and where the answer is coming from. You can
use Microsofts Network Monitor for this.

243270 HOW TO: Install Network Monitor in Windows 2000
http://support.microsoft.com/?id=243270

148942 How to Capture Network Traffic with Network Monitor
http://support.microsoft.com/?id=148942

Larry Stotler, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose