Network Browsing.

[J741]

I have just set up my first W2K Server on my LAN. My Windows 95, 98, and ME workstations can log in to my domain without issue. However, when these machines attempt to access "network neiborhood" the server is the only machine which does not show up. If I use the "Find Computer" function on these workstations, then I can locate the server by name, and browse through the available shared resources. But the server still does not show up in the "network neighborhood" of these workstations.

Both the TCP/IP and NetBEUI protocols are installed on all machines on the network.

How can I let the server be seen from "network neighborhood"?

- James.

 

[compnut24]

is your server's hard drive set as shared?

 

[J741]

There is a directory on the server's drive that is shared. It's permissions are "full access" for all users.

- James.

 

[tlcscousin]

does the server name end with $
Just wondering because if it does it is hidden unless you know to look for it.

 

[sixthsense]

have u installed active directory on the w2k server.
if so u can download a patch for the win9x clients
for the ADS(active directory services).check it out on the microsoft site.
"

http://www.microsoft.com/windows2000/downloads/tools/adclient/default.asp"

apply the patch on the win9x comp
i think it'll solve yr problem
kapil

 

[J741]

I'll look into that patch for 9x based machines, but I'm not so sure that is going to solve the issue, as the server does not even show up in it's own "my network places". It is not hidden, as it can be found when searched for by name.

- James.

 

[peterve]

why do you need them to show up in network neighborhood ?
as long as you can map drives, it should be fine

However, getting rid of Netbeui and implementing WINS could solve your problem... Peter Van Eeckhoutte
peter.ve@pandora.be

 

[panky]

J741

Try one more thing..

remove network adapter from device manager and reconfigure it in order to refresh network bindings and other properties and boot..then see.

I think even peters solution can be fruitful.



check your local security policies.

cheers
panky