Network Stops Responding

[Adam Selene]

I've got a Win2K Pro SP4 workstation that's experiencing network
stalls.

PC originally used on-motherboard 3Com 905C type NIC but I've replaced
it with an Intel Pro/100+ PCI card and disabled the on-board NIC.

I've replaced the network cable.

I've swapped ports on the network switch.

I've stared at event logs 'till I'm bug-eyed and found nothing.

Recovery is USUALLY possible by disabling the LAN connection, then
enabling it. Otherwise, a cold-boot works.

Network is hosted by Win2k3 SBS Server but this workstation is not yet
joined to the domain.

I'm stumped!

HELP!

Adam

 

[Phillip Windell]

Check for Spyware on the machine using Spybot S&D or whatever favorite one
you might have. Some spyware fouls up Winsock.

 

[Adam Selene]

Check for Spyware on the machine using Spybot S&D or whatever favorite one
you might have. Some spyware fouls up Winsock.

Now joined to domain. Still loses Domain Controller connection
occasionally. Usually manifests by event logs showing failed to send
DNS update or failed to find Domain Controller. Same recovery method.

Only one patch cable and one in-the-wall cable left to check and then
it's probably gonna be re-load city. ( I really dread that. )

Adam

 

[Phillip Windell]

Did you disable the "power saver" features of the Nics themselves? This has
nothing to do with the power save features in the Display settings.

 

[Adam Selene]

Did you disable the "power saver" features of the Nics themselves? This has
nothing to do with the power save features in the Display settings.

Yes. I can't see anything useful about powering down a NIC when the
desktops stay on overnight.

 

[Adam Selene]

Did you disable the "power saver" features of the Nics themselves? This has
nothing to do with the power save features in the Display settings.

Out of desperation it just occurred to me that I might uninstall
TCP/IP, then re-install it.

Any thoughts about that? Is it a foolish idea or might it work?

What I'm seeing in event logs is that PC loses contact with DC and
promptly tries to become a Master Browser. DC hears and slaps PC down
with an election but this comes and goes in cycles.

I'm seriously starting to believe it's not hardware -- at least not on
the PC itself.

Adam

 

[Phillip Windell]

Out of desperation it just occurred to me that I might uninstall
TCP/IP, then re-install it.

Any thoughts about that? Is it a foolish idea or might it work?

No, I don't think that is needed.

What I'm seeing in event logs is that PC loses contact with DC and
promptly tries to become a Master Browser. DC hears and slaps PC down
with an election but this comes and goes in cycles.

That is normal behavor when it can't find the DC (also the Master Browser).
So that doesn't really help to troubleshoot.

I'm seriously starting to believe it's not hardware -- at least not on
the PC itself.

I'm still thinking it could be hardware,..or maybe the Nic driver. Anyway,
when the machine is having one of its "fits" and can't find the DC, can it
still ping its own IP#?...can it ping other LAN IP#s? (forget names). What
is the "IPCONFIG /All" output of both the troublesome machine and also from
the DC? Can other workstations still see the DC just fine during the "fits"
of this machine?

 

[Adam Selene]

No, I don't think that is needed.


That is normal behavor when it can't find the DC (also the Master Browser).
So that doesn't really help to troubleshoot.


I'm still thinking it could be hardware,..or maybe the Nic driver.

That'd be two totally dis-similar drivers -- i.e., 3COM and INTEL.

Anyway, when the machine is having one of its "fits" and can't find the DC, can it
still ping its own IP#?...can it ping other LAN IP#s? (forget names). What
is the "IPCONFIG /All" output of both the troublesome machine and also from
the DC?

I'll have to get back on when it happens to answer these definitely.
It's been restored by disable/enable sequence on the connection.

Can other workstations still see the DC just fine during the "fits"
of this machine?

Yes.