Hey Hey,

*shakes his head at parts of this thread and gets down to business*

Ghost_25inf: Pinging localhost and the IP Addres assigned to the NIC interface are two different things... localhost = 127.0.0.1 = loopback = seperate interface handled in software... a way of testing your network stack... no response from localhost is definately _NOT_ indicitive of a bad NIC... it demonstrates a problem with the Network Stack on the OS (commonly reset with netsh interface ip reset reset.log or by deleting TCP/IP from your networking (both windows fixes))

Duck: If you run ipconfig on the PC is an IP Address listed for the interface? the DHCP Table of the router says it's assigned an address but does the PC itself indicate an actual address?

If it works direct to the modem (I'm assuming you checkd your ip address and it was valid and that you could route traffic to various public websites)... Then you have an odd problem going on..

If ipconfig doesn't reveal an actual IP Address run ipconfig /release and ipconfig /renew, however run Ethereal while doing it... ensure that the proper DHCP request is occuring..

DHCP Discover, DHCP Offer, DHCP Request, DHCP Ack...

If you see a Discover than your PC is sending a request..
If you see an Offer than the Routers DHCP Server is offering back an address
Request means that the PC is accepting that address and asking for permission to use it
Ack Means go ahead and use it

If you see all of that and you still don't have connectivity then provide the following here

ipconfig /all results
route print results
arp -a results

Peace,
HT