General discussion

Locked

W2K Network Lockup Troubleshooting

By Kevin at Alexander Group ·
I have been working on an issue with a Windows 2000 network with W98 clients. Periodically, all network adapters lose connectivity. They simply can't see any other IP addresses. This state stays in effect for each computer until it is rebooted (ie the clients can see each other once rebooted, but not any unrebooted machines.) We have worked with Microsoft to vet our server settings. We have switched out the routing hardware. We have replaced NICs. We have analyzed the network and found the only issues to be some crosstalk and return loss on some of the cabling. Running network monitor when the lockup returns yields no signs of increased traffic.
The server has not locked up the couple of times we have been working on it when the lockup occurs, but it does lock up completely when we are not on it.
Any thoughts or advice would be appreciated.

This conversation is currently closed to new comments.

12 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

W2K Network Lockup Troubleshooting

by Shanghai Sam In reply to W2K Network Lockup Troubl ...

You don't say what make of NIC you use but I have been having problems with 3com 3c905 cards. They are slow to start eg when you boot up you have to wait 20-30 secs after the logon prompt appears otherwise the profile loading fails with 'Path not found' and they will suddenly lose connection (haven't found a reason yet)that only a reboot will resolve, Yet other machines on the same hub\switch combination will not have a problem (Using Intel EtherExpress Pro 10\100 NIC).
We also came across a problem with Realtek NIC chip drivers Lots of NIC mfr's use these driver IC's and Win98 when using some DOS based packages caused by Opportunistic Locking on the server (NT4.0) and the version of the Virtual Redirector on the client machine.
Another thought is that if your machines drop out at the same time then start looking for a external problem or possibly power supply faults at the server\hubs\switch

Hope this adds something
Chris

Collapse -

W2K Network Lockup Troubleshooting

Poster rated this answer

Collapse -

W2K Network Lockup Troubleshooting

by cruncher_1 In reply to W2K Network Lockup Troubl ...

We have had a silmilar problem. The lockups were only the clients and were intermittent. There are some ME clients on the network that were not compatible with the virus software. You didn't mention ME, but my thought is that there might be some software incompatibility causing the problem. You have checked out the hardware. Have you checked the software compatibility? I assume that since Microsoft was assisting, the HCL was checked.

Hope this helps.

Collapse -

W2K Network Lockup Troubleshooting

Poster rated this answer

Collapse -

W2K Network Lockup Troubleshooting

by Shanghai Sam In reply to W2K Network Lockup Troubl ...

One area that you should also investigate is the NIC's settings. The Autonegotiation feature was a bit of an afterthought in the standards and as such it?s implementation in some manufacturers switches are flakey. Disable the Autonegotiation feature and set you NIC?s and switch ports to be the same speed and duplex. Ensure that all cabling is tested and passes at least a Cat5 test. This should eliminate the networking components (hardware wise).

For all of the cards to stop functioning together, it may be that they all share the same switch/hub and the unit is restarting, causing the server to loose the connection states with the clients. There may be a firmware upgrade available for the type of network unit that you have.

Hope this is of some use to you.

Kevin

Collapse -

W2K Network Lockup Troubleshooting

Poster rated this answer

Collapse -

W2K Network Lockup Troubleshooting

by JediMaster2003 In reply to W2K Network Lockup Troubl ...

With rebooting, that would reset all network connections, and with that in mind, here are some Things to check;
1. Can you isolate the issue to a Server, or network?(Server locks up as well?)
2. If server as well, then forget the network and work on the server.
3. if network, work with one pc and the server to test.
(Change the network cableing on one pc to the router, then router to server for testing see if this doesn't help any matters)(Start from the botton up)....

Collapse -

W2K Network Lockup Troubleshooting

by JediMaster2003 In reply to W2K Network Lockup Troubl ...

(would not hurt to run a virus scan of your network.)(Some virus are known to cause broadcast storms etc...)

Collapse -

W2K Network Lockup Troubleshooting

Isolating it to the server did help. We found the problem was actually limited to the server.

Collapse -

W2K Network Lockup Troubleshooting

by jereg In reply to W2K Network Lockup Troubl ...

All the answers have been good, but there may be a few other things to check if you already haven't. Could the server IP address be conflicting with another on the network? Could it be conflicting with your ISP? Is your Ip numbering system inline with the standards for private networks (i.e.192.168.x.x, etc.)? Did you replace the NIC in the server? Have you turned off all the other protocols? If so, have you tried turning on NETBEUI?
I knoe that these iintermitant problems are the worst. GoodLuck.

Back to Networks Forum
12 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums