• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

I keep getting concflicting IP's with DHCP enabled...

joe4324

Senior member
Ok, Here is my current network setup


I have a Linksys BEFW11S4 Ver.2 (4 port 10/100 wireless cable/dsl router)
I have DHCP enabled on the router, and all client PC's (2k,xp) are set to autodetect settings for TCP/IP.

But all the time I get the IP conflict errors, and when I look at the DHCP clients table on the router it shows everyone as having a different IP. what gives?


I can provide alot more information on my network but I figure'd I try to see if I was stupid and missing something really easy 🙂

thanks in advance!
 
I should note, I've tried hard-reseting the router (clearing all changes) Having the entire network shut down, and restart peice by peice. clearing the DHCP table and having everyone reboot to get new ones.

Also! the internet works fine, and some games even run... and sometimes they dont...
 
I'll try to help.

What does "it shows everyone has a different IP" mean? All nodes on a network are supposed to have a different IP.

An IP address is like a street address. You live at 123 Jones Street. I live at 120 Jones Street. Two different houses on the same street cannot have the same address.

Do this. Physically disconnect all workstations from the router. Leave the modem plugged into the router.

On all workstations, ensure they are all set up to grab an IP AND DNS server automatically. Reboot them.

Go to the Command Prompt (Start/Run/type CMD) then type "ipconfig/release" (no quotes) Leave it alone for now.

Unplug the power wire from the router and count to 30. Plug it back in. Let it do the self test thing.

Plug in one workstation to the router. Go back to the command prompt and type "ipconfig/renew" and see what it says. Should say 192.168.0.x.

If not, go into the router's setup and make sure that it is set to do DHCP. Should work.

 
Yes the firmware has the latest version.

Well I wanted to avoid static ips because the client situation changes daily, it would be nice just to have everything automatically assigned its own ip. but alas I'll settle for static if there is no other resolution.
 
Could you define "all the time" and what machine you see the conflicts on? Is it the same machine always? or random machines? It sounds like you might be a part of another LAN, try changing your router to give addresses on the 192.168.55.x (55=any number) addresses and see if it still happens.
 
Are you absolutely sure there are no other dhcp servers running on the lan? Go into your linksys config and change the dhcp range to something different and very narrow and release/renew or reboot the clients and see if they all take one in that range. Maybe run a sniffer and watch for the dhcp traffic and see what you're getting.
 
Ok I changed the ip on the linksys DHCP server from 192.168.1.1 to 192.168.55.1, and changed the DHCP to serve ips from 192.168.55.200+ instead of 192.168.55.001+

It seems to have cleared up... do we have any explanations?! I live in a TINY town, I dont think anyone else even knows that they can get free internet from me hehe
 
Originally posted by: joe4324
Ok I changed the ip on the linksys DHCP server from 192.168.1.1 to 192.168.55.1, and changed the DHCP to serve ips from 192.168.55.200+ instead of 192.168.55.001+

It seems to have cleared up... do we have any explanations?! I live in a TINY town, I dont think anyone else even knows that they can get free internet from me hehe

Well, you could check your logs to see who has connected to you.
 
Originally posted by: joe4324
Ok I changed the ip on the linksys DHCP server from 192.168.1.1 to 192.168.55.1, and changed the DHCP to serve ips from 192.168.55.200+ instead of 192.168.55.001+

It seems to have cleared up... do we have any explanations?! I live in a TINY town, I dont think anyone else even knows that they can get free internet from me hehe

Explanation, no not withou setting it back and doing some rouge dhcp detection or sniffing. It could be your ISP has no clue what they are doing and gave you a 192.168.x.x address and you were trying to give them out also.
Just be aware that setting the DHCP pool to serve .200+ you area restricting yourself to 54 clients 🙂
 
Back
Top