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

DHCP problem

Arcex

Senior member
OK, I know exactly what is happening, but I cannot find out why. I've checked all the common reasons but most of them don't apply, here is the situation.

Every once in a while I connect a PC or laptop to a standard, basic Linksys switch (EZXS55W to be exact) and sometimes it gives me the "limited or no connectivity" message.

What's happening is DHCP (which is working fine in every case) will simply not supply the PC with the IP address and of course causes Windows to spit out an Automatic Private Address. There is no reason for DHCP not to give out the IP, I've released / renewed, checked the DHCP service, checked Winsock, checked the NIC, checked the switch, checked the cord, checked everything and there is nothing wrong.

The switch isn't tapped out on handing out the IP's either, this will sometimes happen with 1 thing plugged into the switch and sometimes with all 5 slots being used, but it will only happen on 1 PC / laptop, never on all of the items running off it. If I plug the cord in elsewhere or reset the switch nothing happens. It is very intermittent and if I play around with the cords and settings long enough it will just start working.

So, does anyone know why this happens? It's mostly just annoying but it wastes too much of my time when it happens and should be something simple enough to fix that it bugs the crap out of me. Thanks in advance.
 
i have a similar problem with my home wifi network. it is in ad hoc mode (Peer to peer) and shared internet is shared through ICS

sometimes my laptop fails to obtain the ip from DHCP and then it goes to limited connectivity. this is usually fixed by repairing the connection/ renewing the ip manually. i changed it to static and set the appropriate dns and gateway settings as a temporary fix (works perfectly)
 
You're right about the switch, sorry, had a brain fart, but I doubt it's a network issue. It's at my work, T1 line, the IT people looked into it and couldn't find anything wrong network-wise.

Release/renew doesn't work.
 
Originally posted by: Arcex
You're right about the switch, sorry, had a brain fart, but I doubt it's a network issue. It's at my work, T1 line, the IT people looked into it and couldn't find anything wrong network-wise.

Release/renew doesn't work.

If you can't release/renew, either:

1) your connection is not working right (bad cable/NIC/whatever), or

2) your DHCP server is not working right.

There isn't a whole lot else to it. If you're on a T1, talk to your ISP.
 
Back
Top