Discussion Locked

Network Browse for 2003 server fails

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

I have recently upgraded the PDC in the network to a 2003 server from NT4. When I do a NET VIEW or try to browse the network the new server is not shown. If I call it by name (\\server) I can see the shares.
I had originally thought it may be part of 2003 security, but I have now installed a 2003 terminal server and it broadcasts OK.
I have checked all the obvious (Domain controller security policies, SMB signing, File & print sharing) and can not see why it wont show up.

Any suggestions?

13 replies

by techkid

check the network properties>TCP/IP>advanced>WINS>enable netbios over TCP

This setting should be ticked.

by scottsman

If you are still using NT in the network you should have a WINS server setup. This will resolve your issue.

Note that there is a recent security vulnerability with MS WINS:
http://www.internetnews.com/security/article.php/3442311

Note that the Domain model from 2000 and up uses DNS for name resolution. The big issue here is that MS Office still uses old netbios calls. This can cause wierd network and shared drive issues if using Office to get a file off of a share. Thus the need still exists to have WINS in your MS environment. Unless of course you are cutting edge and your people use open office (I do not know if OO uses netbios though...)

by scottsman

Worst case just add IP and host name to the host files. (not practical on a large network.)

by liame

It could be that you have connected 2 network cards as many of us would on a win2k server. The feature that used to be in win2k server standard is now only available in the higher versions of 2003 server.

Solution - disconnect a one of the cards.

by 4d_striker

I have this problem with W98 machines being unable to browse W3K server before and problem was solved after I installed DS Client on all W98 machines.

This discussion is closed to new replies.