• 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.

Getting an internal IP conflict???

A

Ace69

Senior member
Hey guys! I posted recently about my problem of connecting my two roomates cable modem and mine in this Ars thread. NetBEUI and being hooked up to their switch has worked for awhile now, but I have started to get IP conflicts from my 192.168.1.2 address and every other internal IP I put in, including the 10.x.x.x addresses! Whenever I unhook myself from their switch and just run off of my hub like normal, it works fine. I am getting the IP conflict somewhere out there from their cable modem. As far as I knew, the internal IPs were not routable so I don't know how I would be getting this IP conflict if no other computer was on our little LAN.
Any help is appreciated..
 
If you're getting a conflict on that IP, it's coming from inside, not outside. This usually happens when something has a static IP that's also included in the DHCP range. Not uncommon, and most cable routers don't have enough smarts to check an IP before handing it out.

Try to go into your router and adjust the range the it gives out for DHCP - Start it at .20 or something, instead of .2. That's kind of a cheap way to get around it, but should do the trick.

- G
 
The router is not doing DHCP. I have manually input that IP. I still have no idea how I am getting an IP conflict.
 
Plenty of ISPs use RFC1918 addresses internally. It is entirely possible for you to see those addresses if you are with a large ISP. They should be blocking the addresses from leaking to where they interfere with you, but it is possible.

However, I suspect your problem is a corrupt driver or failing hardware. Remove the card in Windows, shut down, remove the card from the system, reboot, shut down, put the card back in but in a different slot, reboot, reload drivers, see how that works.

RagManX
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top