Discussion Locked

W2K Pros can't see each other

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have recently began rolling out W2K pro workstations in our NT domain. Love it except on ocassion the W2K machines can't browse each other. They appear in the browse list, and can be pinged, but when we try to connect to them, we receive an error message stating, "\\(machine name) is not accessible. The specified network path is no longer available."

5 replies

by inthemix88

Using "\\computername" invokes a netbios name. If you want to be able to do this, you need to install the WINS service on one of the DCs or other Win 2K servers in your domain. you can then configure DHCP options to assign the IP address of the WINSserver to the workstations. If you dont want to use WINS, You can try using the FQ DNS name for the workstation. That should resolve your name resolution issue. Hope that helps,
Martin Reyes

by jlmoak

We currently have WINS running on our NT PDC, without DHCP. The W2K machines can browse other W2K machines, but only Intermittently.

by oridjinn

There is a known problem with Win2K and network connections, you can most likely fix this with Service Pack 1. You can also play with Wins and DNS, but it sounds to me like you already have those in place correctly, otherwise you wouldn't see each other at all.

by stillatit

This may be a longshot, but some NIC cards intermittently lose data with W2K. In particular, 3com 3c509 in legacy mode does this (I was bit by this one). In that particular case, you need to move it to PNP mode.

Good luck.

This discussion is closed to new replies.