Solved IP Address Conflict on Network

December 17, 2012 at 10:41:44
Specs: Windows 7, Core i3
I keep getting an IP Address Conflict notification from Windows. We have a Netgear R6300 Wireless router, set to DHCP, and 6 Computers in the office, all wireless, all set to DHCP. Yet 2 computers keep saying there is an IP Address Conflict. What gives?

See More: IP Address Conflict on Network

Report •


✔ Best Answer
January 15, 2013 at 11:19:36
Sorry Curt, lol. I got wrapped up in Troll lashing. It turns out that several of the systems on the network, while being configured for DHCP, were actually named the same thing. So I changed all the names to unique ones, and reset everything and Voila!! Thanks a lot for the helpful guidance and assistance!!!!


#1
December 17, 2012 at 12:30:51
Is it the same two computers all the time?

If so, and you're 100% sure they're both set to DHCP, then it would seem the DHCP server is confused and trying to give them both the same IP. Now since this is coming from a SOHO router I can't see there's a whole lot you can do.

If your router's DHCP server service is capable of doing so, you could reserve an IP for both. Then the DHCP server would only try to give each unit the IP assigned to it.

If your router isn't capable of doing that, I would consider giving one, or both, a statically assigned IP address.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#2
December 17, 2012 at 12:35:59
If you only have 6 computers, use static IPs.

How do you know when a politician is lying? His mouth is moving.


Report •

#3
December 18, 2012 at 00:40:25
I would advice you check the PCs name on the network and login to the Router and see numbers on system(PCs) allowed in there. If all these are correct I think there should be no problem.

Report •

Related Solutions

#4
December 18, 2012 at 01:09:55
Make sure the PCs names are not the same on the network and check numbers of PC allowed in the Router configuration(By logging in to the router).


Thanks.


Report •

#5
January 14, 2013 at 22:03:00
So well put Truetrue. After getting about 30 differing answers from different sites where people had similar but not the EXACT same issue I was, I decided rather than to hobble a potential solution together from a bunch of no-identical situations, I would ask an intelligent group about my SPECIFIC problem. But thanks for being an ass. Hope that works out for you. Troll.

Report •

#6
January 14, 2013 at 22:49:00
@ xfile102 , thanks for the update.

Stay connected.


Report •

#7
January 15, 2013 at 07:19:57
azedas101

Did you read the OP's last post? He wasn't posting an update. He was bashing someone for posting a useless response.

xfile102

I'd love to know what the issue was and how it was resolved though....hint hint.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#8
January 15, 2013 at 11:19:36
✔ Best Answer
Sorry Curt, lol. I got wrapped up in Troll lashing. It turns out that several of the systems on the network, while being configured for DHCP, were actually named the same thing. So I changed all the names to unique ones, and reset everything and Voila!! Thanks a lot for the helpful guidance and assistance!!!!

Report •

#9
January 15, 2013 at 11:29:01
Then it was not a ip conflict but a netbios name conflict. FYI

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#10
January 15, 2013 at 11:49:25
Awesome....thanks for getting back to us xfile102 With a bit of luck, your last response will help somebody else with a similar problem.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •


Ask Question