Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Lone Windows 98 Computer on LAN Cannot Communicate With WAN

Status
Not open for further replies.

Arsynic

MIS
Jun 17, 2003
141
In short the Win98 machine can log into the network, it can access the Internet and it can ping any computer on the LAN as well as websites. However, it can't ping or connect to any of the Terminal Servers in the WAN. I scoured the net and I came across some Microsoft fix, but I have to call Microsoft support, however I'm not sure that's the problem. Everything points to vserver.vxd. It's a strange problem. I've uninstalled and reinstalled network drivers, protocols and clients to no avail.

Also, when I go to the server and look up all of the computers in the active directory, I don't see this one machine listed. However, it can connect to the Terminal Server on the LAN. Strange. I stayed for three hours after work trying to figure the problem out and still no headway. The only course of action now is a complete reformat and reinstall which I always try to avoid. This is a nasty and elusive problem that I've seen once before on older hardware. I don't know if it's a hardware problem or what.
 
One guess: the Netbios names exceed 12 characters in length. Win9x has issues resolving such names.
 
Well, the other Windows 98 computers don't have that problem, so I think I can eliminate that. Is NetBIOS a protocol that has to be installed??? I went to Net Neighborhood and I checked the list of clients and protocols and NetBIOS wasn't on there.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top