Discussion Locked

Win2K Network Failure

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

I installed win2K on a workstation of my company, & it soon get lost in the LAN. It worked fine as a win98 b/4 this, but as win2k, the networking started 2 fail (including internet). It is not a total failure tho, as the PC will be able to access the LAN & Internet after each reboot, but soon fails after a few mins.
Some corrective measure i've performed included the updating of drivers, changing of networking card, renaming of the PC to single 2-letter name. Is that any unforseen possibilityof conflict i missed out?

7 replies

by spunkmnky

What kind of Network card are you using? I've noticed that 3Com's have a tendancy to reset themselves when another computer on the network reboots, try setting the network card to a specific speed instead of auto detect. Just a thought. Later

Mike

by philando

Since this was a 98 machine before, I am assuming that the nic card was the same one being used on the lan. Win2k has issues with hardware that are not on it hardware compatibility list. They might work for ever, but sometimes you get irratic behavior like you're experiencing.
The good thing about NT is that it log just about everything, so look in the event log to see what services are not being loaded or failing. To check the event log go to the administrative tools in the control panel. Pay special attention to the Application and System logs.
Hopefully you're using DHCP for ip addressing, but make sure there are no duplicate addresses (Just a suggestion,you probably have that covered already)
Good Luck

by jack republic

you should preform a few tests :
1. ping 127.0.0.1 to check internal binding
if sucsses ping the machine ip address .
2. issue ipconfig /all command
3. issue nbtstat -a command
4. ping ip address of wins and dns .
you should preform this tests when the access to lan is unavalable.
i think you have a problem whith the protocol stack .and you might need to remove all protocols and reinstall them

This discussion is closed to new replies.