As above, my brothers computer has been playing up, tried repairing it, resetting the modem, etc. to no effect. I think its windows (XP64) having issues again Any ideas?

Mine works great on the same router, although Im using wifi and my brothers laptop has no problem either line or radio so it isnt the router.

Got a firewall installed?

Have you tried uninstalling the network card from the device driver and then doing a scan for new hardware?

If you have checked both of these then just nuke it from orbit, only way to be sure ::

open up a command window and type :: "netsh int ip reset resetlog.txt"  The file name can be anything you actually want.  

you getting 0.0.0.0?

Quote from: BeakerGot a firewall installed?

Have you tried uninstalling the network card from the device driver and then doing a scan for new hardware?

If you have checked both of these then just nuke it from orbit, only way to be sure ::

open up a command window and type :: "netsh int ip reset resetlog.txt"  The file name can be anything you actually want.  

Hes using the indows one ATM

Yes, it reinstalls no problem but the smae thing happens again

Thought about the nuking from orbit but he says he needs it to work.

sdp: comes up with 196.254.146.115

have you tried manually specifying an IP? If this doesnt work then reinstall. If that doesnt work, somethings f**ked.

Quote from: Serious

Quote from: BeakerGot a firewall installed?

Have you tried uninstalling the network card from the device driver and then doing a scan for new hardware?

If you have checked both of these then just nuke it from orbit, only way to be sure ::

open up a command window and type :: "netsh int ip reset resetlog.txt"  The file name can be anything you actually want.  

Hes using the indows one ATM

Yes, it reinstalls no problem but the smae thing happens again

Thought about the nuking from orbit but he says he needs it to work.

sdp: comes up with 196.254.146.115

that command line code resets the TCP/IP stack.  Its a favourite problem with Windows atm.  I think one of the recent updates hosed it for loads of people.

Edit :: That is an external IP addy.  Hes not got the router set is bridging mode has he?

It only came up after I reset the TCP/IP stack, dont have one from before.

My old compy had a bridge going for months when something went wrong, without being an issue.

looks like an apipa address to me.

apipa addresses fall within 169.254.0.0/16

thats a routable IP there

Assuming its not a typing error

It should be coming up with 192.168.0.x Mine is using 192.168.0.5 at the moment.

Im pretty sure its his windaz install screwing up rather than a hardware problem.

check to see if the DHCP client is running in the system management console?