network cable unplugged

[kinzo]

windows 2003 domain.
trying to logon to domain from my xp client, i got "network cable unplugged" but it's NOT. So i couldn't sync with shares on the server nor logon to it.
I followed MS

http://support.microsoft.com/kb/910389,

but didn't help, tried to reinstall drivers, to remove my profile,
to disable-enable NIC but..nothing. Device manager showed no NIC errors at all. Pinging my IP addr or other IP addr on LAN gave hardware error, i could only ping loop interface. Net view showed the shares on the server (but obviously i could not connect). IPCONFIG -> no device. No way to connect to internet too (gateway). Some help? Tomorrow morning i'll be at work and i MUST find out a solution

I'm googlin' about it at the moment...without success...

 

[MrNick0483]

It sounds to me like a bad NIC or the other end of the cable is not hooked up right since you are sure your end it connected right.

 

[burtsbees]

Yes---layer 1 problem...don't over think it...

Burt

 

[kinzo]

Assuming a bad NIC (it's on the M/B), my pc isn't the only one with this problem on the LAN. So i'm a little baffled...furthermore the other PC showed this issue after the use of a pen drive linux system (usb booted)...do you think there could be something related to this issue?
Anyway i never used usb drive on my box at work...

 

[burtsbees]

It's a layer one problem, whether it be drivers, NIC, cable, server NIC, etc. You must find the one common denominator and troubleshoot from there---isolate it. Take a pc and crossover cable to the server, etc. You are not providing enough info---describe the topology, what works, what stops working and when, what has never worked, etc.
Pinging the loopback only means that the IP stack is intact---it can send and receive packets on the correct terminals on the MoBo using the TCP/IP protocols. The next test would be telnet/RDP---that will test all 7 layers...but you must first isolate the layer 1 problem.

Burt

 

[kinzo]

SOLVED!

I don't know if this could be of some help for someone, but all I did was reset BIOS to default settings.
After this some IP/DNS problems solved flushing DNS cache.
Thank you all for your quick replays.

scrAb_