Comments on: Windows 2k Server http://itknowledgeexchange.techtarget.com/itanswers/windows-2k-server/ Sun, 26 May 2013 01:40:27 +0000 hourly 1 By: newsgazoo http://itknowledgeexchange.techtarget.com/itanswers/windows-2k-server/#comment-42950 newsgazoo Mon, 25 Oct 2004 16:22:05 +0000 #comment-42950 Is netbeui installed? If not it should fix the problem.

]]> By: noneil http://itknowledgeexchange.techtarget.com/itanswers/windows-2k-server/#comment-42952 noneil Fri, 08 Oct 2004 13:57:53 +0000 #comment-42952 this is probably because NETBIOS is disabled. netbios is what makes machines show up in network neighborhood.

]]> By: masterojnone http://itknowledgeexchange.techtarget.com/itanswers/windows-2k-server/#comment-42953 masterojnone Fri, 08 Oct 2004 13:49:46 +0000 #comment-42953 In network setting on the server, do you have File and Print Sharing for Microsoft enabled? This will cause you not to see your server in Network Neighborhood. See,if you can connect to server through your browser by typing servernamec$.

]]> By: 131313 http://itknowledgeexchange.techtarget.com/itanswers/windows-2k-server/#comment-42954 131313 Fri, 08 Oct 2004 13:44:34 +0000 #comment-42954 can you disable the Window Messenger service on the W2K server.

]]> By: isok2005 http://itknowledgeexchange.techtarget.com/itanswers/windows-2k-server/#comment-42955 isok2005 Fri, 08 Oct 2004 13:44:11 +0000 #comment-42955 Do you have a primary WINS and secondary WINS defined on your network? If so is one of them 2000 and one NT4? Also what protocols do you have installed on the PDC?

]]> By: yellowtuna http://itknowledgeexchange.techtarget.com/itanswers/windows-2k-server/#comment-42956 yellowtuna Fri, 08 Oct 2004 13:41:20 +0000 #comment-42956 One possibility is that the server service is stopped on the W2k server. If the server service is not running, no browser registration will take place and the server will not show up in network neighborhood.

Try going to Start, Run and type in ipaddress of the server. If that does not work check the status of the server service.

]]> By: tedrizzi http://itknowledgeexchange.techtarget.com/itanswers/windows-2k-server/#comment-42957 tedrizzi Fri, 08 Oct 2004 13:37:43 +0000 #comment-42957 In addition to the previous excellent suggestion. you should check to to make sure that you have netbios/tcp enabled in the network properties.. and that the wins server is listed there, as well as a the dns server and the dns server has an A record for the machine,, assuming that you have a dns server to resolve internal address. under nt4 that is not a requirement.NT4 primarily uses netbios to resolve names to ip.. where as win2k uses dns as the primary method to resolve names to IP. if your running a win2k dns server you can set it up to query your wins server for any addresses that it cannot resolve itself.
hope this helps

]]> By: netfox http://itknowledgeexchange.techtarget.com/itanswers/windows-2k-server/#comment-42958 netfox Fri, 08 Oct 2004 13:35:20 +0000 #comment-42958 From the new W2k server, can you browse the network at all? Did you install DNS or WINS on that server? It may be trying to dynamically register to itself, and never informs the NT box it exists.

]]> By: ctg023 http://itknowledgeexchange.techtarget.com/itanswers/windows-2k-server/#comment-42959 ctg023 Fri, 08 Oct 2004 13:34:50 +0000 #comment-42959 Another thing that came to mind is if you have any files shared on the new server.

]]> By: ctg023 http://itknowledgeexchange.techtarget.com/itanswers/windows-2k-server/#comment-42960 ctg023 Fri, 08 Oct 2004 13:32:55 +0000 #comment-42960 I had a similar problem with a server on my network and the problem was that the wins ip address was not added on the new server. But since you say that is properly configured then the only other thing I can think of to try to rejoin the domain.

]]>