2nd NetBIOS transport for a singlehomed server? WTF?

[beer]

We're having problems with our 2K server maintaining an accurate browse list. It is configured as a master browser because it is the primary domain controller. Using browstat and browmon, we've located the problem: apperantly Win2K server thinks there is a 2nd netbios transport. Windows has this a browslist for this 2nd netbios transport that is coming up when users are requesting the network neighborhood listing for the other netBIOS transport. The incorrect browse list only contains 3 computers, whereas the browse list for the netBIOS transport - the one for the real adapter - has 43 or so. I've been scouring the MS knowledge base and it seems 2K has some issues with netbios and multihomed systems and this is why we believe this is the case.

Now, this is a Dell Poweredge that came with two network adapters. There is one remaining adapter that is bound to TCP/IP. I can't disable netBT over it because we still resolve about half our names using WINS.

Why is this 2nd netbios transport remaining and how can I get rid of it? There is only ONE adapter and this shouldn't have two netbios transports, should it?


Browmon is showing that this second transport has an unknown master browser and only 3 servers. The primary transport has our Win2K server as the master browser and 43 servers. How can I eliminate that second transport with the unknown master browser? Windows only sees one adapter.