Windows 2k Server
Hello,
I just set up a W2K server in a MS domain that has an NT box as the PDC. I am unable to see this machine on the network neighborhood nor can I navigate to it using the IP or DNS name. I can ping it and traceroute I just can't get to it. I get a path not found error. I saw it in the WINS cache on the PDC. I am able to see other machines on the net neighborhood on the 2K server and browse them. Any help is greatly appreciated.
Software/Hardware used:
Software/Hardware used:
ASKED:
October 8, 2004 10:23 AM
UPDATED:
October 25, 2004 4:22 PM
Answer Wiki:
Would like some clarification. When you ping and tracert, are you successful doing so by IP, name or both? Are you saying no computer in your domain can contact the Win2000 server? Is the Win 2000 server listed in Network Neighborhood and when you attempt to connect to it you get the error message?
You might want to look at the event logs on both the Win 2000 server and the PDC to get some more clues.
To see all answers submitted to the Answer Wiki: View Answer History.
I am able to ping and tracert using both the IP and name. The W2K server is not listed in the domain in the net neighborhood.
I would check:
1)gateway ip address
2)subnet mask
If any of these two are not correct you will not be able to ping the machine from a different LAN subnet.
I would check:
1)gateway ip address
2)subnet mask
If any of these two are not correct you will not be able to ping the machine from a different LAN subnet.
Did you add the wins and dns server ip address in network settings on the new server?
The IP sub mask and gateway are all set correctly. I can successfully ping it. I just can’t access it through net neighborhood nor can I navigate to it.
Have you tried removing the server from the domain and re-joining the domain again?
DNS and WINS are all correctly configured.
Have you tried removing the server from the domain and re-joining the domain again?
I have tried rejoining the domain and still no success.
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.
Another thing that came to mind is if you have any files shared on the new server.
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.
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
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.
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?
can you disable the Window Messenger service on the W2K server.
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$.
this is probably because NETBIOS is disabled. netbios is what makes machines show up in network neighborhood.
Is netbeui installed? If not it should fix the problem.