Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NBTSTAT

Status
Not open for further replies.

Igaduma

Technical User
Nov 23, 2001
322
BE
Hi all,

I'm administrating several NT4 workstations on a subnet of a corporate LAN.

I configured each machine with a static IP adress & correct routing information, ...
But, for some reason I get following error in the event viewer from time to time:
The machine still talks to the DNS & Wins server. Only dynamic-static IP has been changed.

This is the message in the event viewer:

...Another machine has sent a name release message to this machine probably because a duplicate name has been detected on the TCP network. The IP address of the node that sent the message is in the data.
Use nbtstat -n in a command window to see which name is in the Conflict state.

And when I check the HEX value of the data, the IP adress turns out to our BDC,WINS & DHCP server.

There are no duplicate IP adress or duplicate hostnames.


Anybody an idea ?

Thanks.
Iga-Duma
 
Are these machines multi-homed? Having more than a single NIC can cause these issues. See Q315259.

-gbiello
 
Hi Gbiello,

Nop, 1 nic in each machine.

Still looking for the reason...very strange.
 
Hmmm. If you "configured each machine with a static IP adress", why do you need DHCP? Does the range in your DHCP scope overlap some of the static IP's? If yes, you should either redo your scope, or add reservations.

Also, in WINS Manager, you can "Initiate Scavenging" to clean up the database. There's also something similar you can do for DNS and DHCP. This may help.

-gbiello
 
Hi Gbiello,

No, i'm not using DHCP, i've got a Class C all to myself, but company wide DHCP is the method used.
I think the overlapping might be the problem, this subnet wasn't known to the SMS server (which caused 8Gb log files on all machines...), so I take it it isn't configured in the DHCP also.
Good idea.

Sad thing is i'm not the admin on those servers, otherwise I think it would have been solved by now!
But apparently I rely too much on people reading their log files and solving the problems they see in their instead of waiting for someone to raise the issue.

Iga-Duma




 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top