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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

A duplicate name has been detected on the tCP network 2

Status
Not open for further replies.

RBP

Programmer
May 5, 2001
88
GB
Can anyone help fix/remove this error?

I have a network of 3 pcs through a BT router.
2xPC's are win 2 K PRo, 1 is Win XP Pro
all have DHCP set no hard coded IPs for the pcs ( I did at one time)

checking one pc, FIDO, with compmgmt.msc shows me two error messages for FIDO each time I boot up see below.

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. Checking the IP shown in the error window = xxx.xxx.1.4 that is the IP of the XP machine, not FIDO, his IP is xxx.xxx.1.2 the other pic's IP is xxx.xxx.1.3
So 3 pc's, all different IPs where does the duplicate come in?

NBSTATS -N gives me

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
FIDO <00> UNIQUE Registered
FIDO <20> UNIQUE Registered
TESTING <00> GROUP Registered
TESTING <1E> GROUP Registered
FIDO <03> UNIQUE Registered
ADMINISTRATOR <03> UNIQUE Registered
INet~Services <1C> GROUP Registered
IS~FIDO........<00> UNIQUE Registered



Any ideas would really be appreciated, it is not killling me, but an error reported is still an error.

Thanks in advance.
RBP
 
Run nbtstat -n on the machine who's IP is .1.4. It is that XP machine that is reporting the conflict, not FIDO.

Remember you're looking for a duplicate name, not address.

"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 
Thanks Lawnboy, done that and all three PCs have different names, FIDO, CEDRIC, WULFIE

NBTSTAT - N on WULFIE gives.
Local Area Connection:
Node IpAddress: [192.168.1.4] Scope Id: []

NetBIOS Local Name Table

Name Type Status
--------------------------------------------
WULFIE <00> UNIQUE Registered
TESTING <00> GROUP Registered
WULFIE <20> UNIQUE Registered
TESTING <1E> GROUP Registered
TESTING <1D> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered

I am none the wiser on this.

NBTSTAT -N on CEDRIC below.

Wired Network:
Node IpAddress: [192.168.1.3] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
CEDRIC <00> UNIQUE Registered
TESTING <00> GROUP Registered
CEDRIC <20> UNIQUE Registered
TESTING <1E> GROUP Registered
INet~Services <1C> GROUP Registered
IS~CEDRIC......<00> UNIQUE Registered

Wireless Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

aNY MORE INFORMATION GRATEFULLY RECEIVED.
rbp


 
I'm no expert on WINS, but I notice that FIDO (and the pc I'm using) has three types registered: <00>, <20>, and <03>.
Whereas Wulfie and Cedric don't have type <03>.

You might have better luck asking in a Windows forum, this is really not a tcp/ip issue.

Wulfie?! By chance, did you used to play Painkeep?


"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 
No I didn't play painkeep, Wulfie is short for Wulfriyth, some early king (I think) Still got no clue as to why I'm getting this message, Microsoft site no help either. Will keep searching. Thanks.RBP
 
Have you tried releasing and renewing all the machines netBIOS info?

NBTSTAT -RR

This should clear out any duplicates that aren't showing (why they wouldn't show is unclear, but worth a try).
 
Hi tfg13, if I carry out a NBTSTAT -rr on all pcs, will it cure the problem? ( need to wait til tomorrow before booting up again) ta
 
Truthfully, I'm not sure. I haven't a lab to try and duplicate the problem, and really, I don't know if I could duplicate the problem. Sounds like one of the freaks of the computer world that come up and bites us every once in a while.
 
I've done some more fiddling, and I think it's tied into something using port 80, can't pin down what, when I go to IIS.msc and check the default web site, it says STOPPED, and whatever I do I cannot start it ( I can stop it using net stop w3svc, but it won't start again, I get the message address already in use. (could be barking up the wrong tree on this)
I get system messages about w3svc as well as the one that caused me to post this original query. Badly stuck on this one.
 
Have you used a sniffer yet? Something like wireshark to find what traffic is out there for what's going on? Is it possible that WINS is flaking out? Have you checked the WINS server (if there is one)?
 
I have not tried a sniffer (don't know a lot about them, nor WINS) I'm sure I'll get to the bottom eventually. Will post again if I find an answer. thanks.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top