NetBIOS problem ??

  • Thread starter Thread starter Willard
  • Start date Start date
W

Willard

Winnt\system32\nbtstat -n

NetBIOS Local Name Table

Name Type Status
--------------------------------------
GX3 <00> Unique Registered
GX3 <20> Unique Registered
WorkGroup <00> Group Registered
WorkGroup <1E> Group Registered
GX3 <03> Unique Registered
Administrator <03> Unique Registered
WorkGroup <1D> Unique Registered
..__MsBrowse__ <01> Group Registered

Should there be so many duplicates of
my Computer "GX3" & "WorkGroup"??

If not how can I get rid of the offenders??

Willard
 
Willard said:
Winnt\system32\nbtstat -n

NetBIOS Local Name Table

Name Type Status
--------------------------------------
GX3 <00> Unique Registered
GX3 <20> Unique Registered
WorkGroup <00> Group Registered
WorkGroup <1E> Group Registered
GX3 <03> Unique Registered
Administrator <03> Unique Registered
WorkGroup <1D> Unique Registered
.__MsBrowse__ <01> Group Registered

Should there be so many duplicates of
my Computer "GX3" & "WorkGroup"??

If not how can I get rid of the offenders??

Willard
Click to expand...

Yes that's normal. Each of those codes in the "type" column is giving info
your computer and its services (used by other computers on your network as
part of the standard MS networking protocols...)

You can look up the documentation here if interested...
http://www.microsoft.com/windows200...r/help/sag_WINS_add_NetbiosNamesReference.htm
 
Colin said:
Yes that's normal. Each of those codes in the "type" column is giving info
your computer and its services (used by other computers on your network as
part of the standard MS networking protocols...)

You can look up the documentation here if interested...
http://www.microsoft.com/windows200...r/help/sag_WINS_add_NetbiosNamesReference.htm
Click to expand...

Thanks for the information..
I have not been able to network my desktop and laptop since reinstalling
Win2k; so I thought something extra may have been left in the CMOS..

My Event Viewer shows: Event 4319, Source NBT
A duplicate name has been detected on the TCP network. The IP address
of the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.

Willard
 
Back
Top