Korean Job Discussion Forums

[The Lemon]

esetters21 is closest to what's going wrong. When you fire up your computer, it gets its IP address for the session from your internet provider's DHCP server. This address they assign you changes every few minutes/hours/days, depending on how they've got it set up.

But if their DHCP server goes on the blink, or your computer can't see it, your computer doesn't get assigned an address. That gets the "limited or no connectivity" error message. Specifically, it's telling you that there is an ethernet cable (or wireless connection) established with the wider network, but your computer hasn't been given the IP address it needs to do anything on it.

Forcing a static IP address by typing one in in your Network Properties *would* be a solution if your ISP lets (either technically, or "legally") you do it. My current one does not, and it's iffy whether yours would, either. I've lived in homes where the ISP did let me do this, but I don't think it's common on home DSL networks.

Short answer - if it keeps happening, bug them. It's probably their fault, unless you've got a home network that's not set up right or something like that.

[Hater Depot]

Hmm. It does partly seem to be a loose LAN card or something, as it will cut out if the cable gets bumped but will reconnect if I jigger it for a moment. Other times though, it cuts out for a few seconds for no apparent reason. Overall though, it's not like I'm working in the coal mines.