Recently I have two sites that have very simular issues that seem to be centered on networking and have been trouble shot down to the point of Win2K being the culprit. By this I mean all network hardware has been tested and or replaced on each PC and all routing and switching devices have been switched out to eliminate faulty equipment and configurations.
The issue is this...
It seems the network will grind to a halt and all PC's will lock up at the same time. Rebooting each of the PC's clears this issue and all is well for a few days and then it all begins again. We are running software that requires shared drive access, and data corruption has been noted at both sites. Both sites are running identical PC makes and models BUT they in no way communicate with each other (independent clients). BOTH sites are having the same issues which began at about the same time.
One notable difference is the third party software being run by both of these clients is from the same developer, but are different Versions - and has never caused these types of issues before.
When I take PC's from both locations and run sustained ping tests on them using a private network, I do note that Windows will continue to report in and out bound activity on the network cards for the entire test. Pings are reported as successful for the entire duration (have run them for over 72 hours without failing) and a linux box I have placed on the network with these machines has successfully ping BOTH of them for the entire 72 hours as they ping each other. No failures at all...
Is there an Update to Win2K that has somehow caused odd network behavior issues like what I have attempted to describe above for anyone else over the last couple of weeks?
I realize this is sketchy...but thanks for any input you can share on your expirences...
The issue is this...
It seems the network will grind to a halt and all PC's will lock up at the same time. Rebooting each of the PC's clears this issue and all is well for a few days and then it all begins again. We are running software that requires shared drive access, and data corruption has been noted at both sites. Both sites are running identical PC makes and models BUT they in no way communicate with each other (independent clients). BOTH sites are having the same issues which began at about the same time.
One notable difference is the third party software being run by both of these clients is from the same developer, but are different Versions - and has never caused these types of issues before.
When I take PC's from both locations and run sustained ping tests on them using a private network, I do note that Windows will continue to report in and out bound activity on the network cards for the entire test. Pings are reported as successful for the entire duration (have run them for over 72 hours without failing) and a linux box I have placed on the network with these machines has successfully ping BOTH of them for the entire 72 hours as they ping each other. No failures at all...
Is there an Update to Win2K that has somehow caused odd network behavior issues like what I have attempted to describe above for anyone else over the last couple of weeks?
I realize this is sketchy...but thanks for any input you can share on your expirences...