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

IP Adress Conflict alert when there is no conflict

Status
Not open for further replies.

goffron

Technical User
Joined
Aug 11, 2006
Messages
14
Location
US
For some reason I can't explain, one computer running windows XP (identical in settings to all others on the network) will get an IP Confict bubble pop up after being connected to the network for about 10 min. Connections are all fine and dandy then this thing pops up.

I'm pretty new, but I don't think this should be happening, since all computers work fine, and this one works on other, public networks.

I'm running win 2003 on the server with 2 nics (one to the isp, one to our switch. DHCP entabled on the server with automatic ip settings as the problem computer (as well as several other with out this problem) travel a lot.

Please help!
 
From the workstation go to a command prompt and type nbtstat -n.
It will give you the IP Address the machine is using and other list any devices that may be in conflict.

It's possible there is a device on the network (printer, etc.) that was assigned a static address, but the address wasn't excluded from the DHCP pool.
 
Tried the nbtstate -n. On the problematic computer. No conflicts.

The ironic thing is: Prior to entering the command prompt, the computer had just put up a bubble saying there was an IP conflict.
 
Now that I think about it, I think the command I gave you is for duplicate NAMES.

OK - try this. Do an Ipconfig on the workstation. Note the address. Then shutdown the workstation and remove the network cable. Then from a machine that is on the network, see if you can ping that ip address. If you get a reply, then someone definitely has that address.
 
Command I should have given earlier is nbtstat -A {ip address} where ip address is the address that is supposedly in conflict. Make sure it is a capital A. See what results that gives.
 
Ok, the nbtstat -A {ipaddress} yielded the following:
The "TECH" is the problem computer and "MORDOR" is the server.


Node IpAddress: [192.168.254.11] Scope Id: []

NetBIOS Remote Machine Name Table

Name Type Status
------------------------------------------
TECH <00> UNIQUE Registered
TECH <20> UNIQUE Registered
MORDOR <00> GROUP Registered
MORDOR <1E> GROUP Registered


When I do this on a working computer (ie Mine), I get:

Host not found.
 
Oh... the problem pc also gives this:

"MAC Address = 00-0B-DB-21-8D-CF
 
He is a possible solution, try signing it a static IP that isn't being used and then see what happens. If this works and you stay connected then you can hunt for the IP that is causing the conflict.
 
Also there is a program called Network View download the free trial and it will scan your network and tell you all the IP addresses and who they are assigned to.
 
THe NetworkView finally pinpointed the problem. The network copier/printer was assigned a static address by the copier people without telling me what it was... subseqently I couldn't exclude that from the DHCP addresses.

You guys ROCK thanks for all your help!
 
Had a feeling a printer would be the culprit. Glad you got it resolved. Dberg35, nice suggestion on the NetworkView program.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top