[alferret]

Originally Posted by Halcyon

Has this PC you are trying to connect up been on the net before using that particular ethernet port ?
Could be faulty ethernet socket. You could pick up a cheap card for £5 and try that.

The PC connects to the net from his mates house without problem in that ethernet port.

Im hoping to be back at work tomorrow if I am then he is going to bring the PC in so I can take it home and have a look see.

---------- Post added at 09:43 ---------- Previous post was at 09:42 ----------

Originally Posted by Aragorn

A 169 IP address indicates it tried to get an automatic (DHCP) address from the UBR, but failed for some reason.
Has the modem been power cycled since the eng tried it? It could be the cable - can he borrow one from his mate (the one that works)? Is this mate using a router?
The 169 address probably verifies the Lan card is working OK.

Modem has been power cycled and AFAIK he was popping to a neighbours house to borrow another lead, havnt heard back from him yet

---------- Post added at 09:44 ---------- Previous post was at 09:43 ----------

Originally Posted by whydoIneedatech

This 169 IP address results from a built in feature of windows called automatic private IP address(APIPA). When your computer is unable to find a DHCP server the APIPA service will assign itself a 169.x.x.x IP address.

According to Microsoft, the APIPA service checks for a DHCP server every five minutes.

Your PC will asign an IP address even when not connected to the internet.

So if it cant find a DHCP server could this look to being a madem fault?