NIC shows as Connected to LAN but can't Ping either way

[Seanwho]

Hi guys,

I have a Domain/network of 15 Dell gx200 workstations running win2k Pro & 512MB Ram. they are connect via 2 Dell Poweredge 2800 Servers using static IP's and DNS on two sites. They have all been behaving well until recently when one Workstation on the remote site lost connection to the Network even though the Indicator showed that it was still connected, opening a cmd prompt and pinging showed it wasn't and cannot be seen by the server anymore. We replaced this machine with a duplicate and everything see,ed to be ok. Yesterday another machine this time on the local site displayed the same symptoms. Both NICs seem to be in good working order and the originally changed one is still functioning correctly on a test rig. Any ideas anyone heard of a win 2k problems?

thanks for listening......

Sean

<b>The mountain always looks bigger when you can't see all of it</B>

 

[bcastner]

1. Ports on switches do go bad.
2. Winsock service stack corruption is also common. To repair, use this simple tool:

http://members.shaw.ca/techcd/VB_Projects/WinsockFix.zip

 

[Seanwho]

Bcastner

thanks for the info will give it a go.

Sean

 

[Seanwho]

Hi Bcastner,

have tried the tool on a laptop and it rebuilds registry keys amongst other things but since then Iinfra red has been disabled and several other network components have been affected. the machine now runs slower and I am loathed to try this tool on an 'Active' machine. The problem as you suggest does appear to be caused by a Winsock service stack corruption any other suggestions or do you know anymore about the tool you pointed me to?

many thanks

Sean

 

[bcastner]

It follows exactly the MS prescription for repairing damage to the Winsock service:

http://support.microsoft.com/default.aspx?scid=kb;en-us;817571

It then uses a nets in reset to correct routing errors.

It finally checks that your HOSTS file has a valid localhost pointer.

Re-enabling your IR port is trivial. When you say it is slower, how did you measure this? The solution for any slowness would be to look at your NIC driver and re-examine the priority of the protocols being used. If you are using multiple protocols use your Network Connection Properties sheet and examine the binding order as they may have changed.

 

[bcastner]

Typo:

&quot;It then uses a nets in reset to correct routing errors&quot;

Should be:

It then uses a netsh int reset to correct routing errors.