Limited or no connectivity...

Dingleberry88 · 2 May 2007 at 23:17

So I came to use my PC earlier and my network connection is showing limited or no connectivity. It's got an IP address of 169.254.76.70, which I know is self assigned as it doesn't seem to be able to get one by DHCP.

My PC's directly connected to my router (Netgear DG834PN).

I've tried different cables, resetting my router and reinstalling the drivers for my ethernet port, but it's still not working.

I'm able to connect with my laptop no problem, both wired and wirelessly.

I've not made any changes to my system. Any ideas what's gone wrong? :confused:

BenST · 2 May 2007 at 23:29

Have you tried assigning the PC a static IP to see if it can still connect? Have you checked to make sure the DHCP service is running (under services.msc somewhere)?

Dingleberry88 · 2 May 2007 at 23:39

DHCP is started and automatic.

I assigned an IP of 192.168.0.5, now I'm not getting the connectivity message, but I still can't connect to the internet.

BenST · 3 May 2007 at 00:04

Have you put the gateway (router IP) in the DNS address field? Can you access the router direct from the PC with a manually assigned IP?

Dingleberry88 · 3 May 2007 at 00:10

Yes I put the gateway in.

No I can't access the router from the PC.

BenST · 3 May 2007 at 00:24

How totally odd. Tried connecting to another PC/Laptop via x-over lead and pinging it?

Dingleberry88 · 3 May 2007 at 00:28

Don't have any crossover cables. I'll pick one up from work tomorrow.

Anything else I can try in the meantime?

BenST · 3 May 2007 at 01:02

Sounds like a definate problem with your PC but couldn't be sure if it's hardware or software what with you reinstalling drivers etc. Try rolling it back to a restore point maybe?

Dingleberry88 · 3 May 2007 at 01:26

Don't use SysRestore...

RaiderX · 3 May 2007 at 01:32

can you try wireless on your PC, see if it works throug that?

it might be a fault in the ethernet card

tolien · 3 May 2007 at 01:52

Linux LiveCD, e.g. Ubuntu?

Dingleberry88 · 3 May 2007 at 09:16

Crisis averted.

I turned on my PC this morning and I'm connecting no problem.

Thanks for the help, but looks like it somehow sorted itself... :confused:

Edit: Despite being on a dynamic IP, I've had the same one since I signed up a few months ago. Though as of today I have a new IP. Whether that's got anything to do with what happened I don't know...

ArmoVanBuuren · 3 May 2007 at 09:34

I solved a similar problem yesterday, every so often I would get the default 169 IP address and wouldnt be able to access the internet. Turns out I had accidently turned on DHCP server on my NAS so with my router I had two DHCP servers on my network which was giving the computers contrasting IP information. Works excellent when I turned the DHCP off my NAS.