Discussion Locked

Win98SE PCs losing connection w NT4 LAN

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a small network with an HP E8000 server loaded with NT4.0 sp6, connected to a 4 port 3COM ISDN LAN modem, (acts as dhcp server)and that's plugged into a 24 port 3COM superstack hub.

The workstations are all windows 98se, with various brands of nics. Some machines are original to the network from 97, while others are much newer.

Within the past month, we've started getting error messages on the workstations, primarily while using Access database programs, but that is simply what we use the most in our business. The error pops up: "Network error or Disk full". After the message is finally cleared, the user can then go to network neighborhood and still see the network. I advise them to open the program again, and they areprompted to run the repair utility within access. This seems harmless, but it happens several times a day, and impedes the progress of numerous other staff at this location.

I have replaced some nics, the 3com hub is new, replaced the nic in the server, replaced the patch cord on the server. I have about 25 users there, and would hate to change out everyone. I have virus protection on the server and workstations, and it's updated automatically and any problems are quaranteened. I haven't noticed much in the line of virus infestation at this place.

Does anyone have any better ideas?? I would surely appreciate any solution you have.

3 replies

by jayanth

Maybe as a starting point, why dont you try to sniff the packets between the workstations and the server running the access database. maybe if you are capturing the packets and one of the users get this error message, you can know the type of packetthat caused this error and this can help you in further troubleshooting the problem. check out http://www.snifferpro.co.uk

by bbennett

I found the culprit to be a nic in a workstation attempting to pull the same ip as the server. To do this, I shut down all but the server,and turned on the workstations one by one, checking the ip address and opening numerous applications as to force an error. As soon as I booted that machine, all havoc broke lose. I swapped out the nic, renewed the ip address, and all is working again.

Note: http://www.snifferpro.co.uk no longer offers a demo as a download, so it wouldn't have been a quick solution for me. But I truly appreciate your answer. I spent 2 days on this project as it was. Thanks again!

This discussion is closed to new replies.