Windows 2000 client cannot browse network

Windows 2000 client cannot browse network

Post by epaetz4 » Fri, 01 Aug 2003 22:38:12


Is there a difference between how Windows 2000 and Windows 98 browse a
network?

I have two machines in a remote office, one a w2k and the other a w98.
The w98 can browse and map to drives on a (remote) server but the w2k
machine cannot.

The w2k machine can ping the server both by IP and by computer name. I
can map a drive on the server with the w2k box, and if I mis-type the
mapped directory, the w2k box recognizes the mistake. But when I do a
dir command or double-click on the mapped drive, it fails.

Netbios over tcp/ip is enabled, and so is NetBeui. I've tried a number
of things with no affect. I'm wondering if the router is the culprit.

Thanks,
Eric
 
 
 

Windows 2000 client cannot browse network

Post by G » Sat, 02 Aug 2003 03:56:40

There are several layers to a network, and at the tcp/ip level there is no
difference. Once you get down to the o/s, and file system, there are big
differences. Is it a domain or peer2peer? What o/s is running on the
server that these machines are trying to access and how are they
authenticating to it? Oh, and why on earth are you using Netbeui?

 
 
 

Windows 2000 client cannot browse network

Post by Marina Roo » Sat, 02 Aug 2003 07:25:35

He was talking about a remote server.
Eric, have you got WINS installed on that server? W9x needs it.

Marina

"G" < XXXX@XXXXX.COM > schreef in bericht
 
 
 

Windows 2000 client cannot browse network

Post by G » Sun, 03 Aug 2003 00:54:51

...and he said the Win9x box was not having a problem, it is the W2K box
that is the problem.




no
big
 
 
 

Windows 2000 client cannot browse network

Post by Marina Roo » Mon, 04 Aug 2003 03:46:24

Yeah, you're right about that. Let's wait untill Eric responses.

Marina

"G" < XXXX@XXXXX.COM > schreef in bericht




is


a
w98.
w2k
I
the
a
number
culprit.