Windows Forum

Ask something
Discussion Locked

Missing Win2k Server

0 helpful
6 replies

by Member 24778686

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a small Microsoft Windows 2000 domain setup with a MS Win2k Server(SP3) and about 20 MS Win2k Professional workstations. We haven't had any problems with our network and then all of a sudden the server is not in the network place or can not be found by using the net commands. But here is the weird part all of the network drives that are mapped from the server still work. Also when I'm on the server I can see the entire network and the server is listed in the group, But from the workstation point the server is not listed in the group. The printers that were mapped from the server don't work. So I had to set them up on the machines locally. But does anyone have a solution to why my server drop off the radar. Help!!!

6 replies

by wallytcw

I would recommend checking over your DNS (and WINS, if you're using it) setup. First of all make sure that your 2000 Pros are set to use your 2000 Server as their DNS server. (If your Internet DNS is specified here, you'll have trouble. The workstations should look at the 2000 DNS server, which should forward the request on if it doesn't know the answer.) Next, verify that your DNS server is working (nslookup command) and that a query for the server name comes back with the correct reponse. Also make sure that the connection suffix on the clients matches the DNS domain name of the server. (If you're using DHCP, you'll want to use DHCP options to set all of the client settings. Use ipconfig /all to check your configuration.) If all that is working fine, you should check your WINS setup - or consider installing and setting up WINS if you're not using it. On small networks it does far more good than harm.

Hope this helps

by wallytcw

I would recommend checking over your DNS (and WINS, if you're using it) setup. First of all make sure that your 2000 Pros are set to use your 2000 Server as their DNS server. (If your Internet DNS is specified here, you'll have trouble. The workstations should look at the 2000 DNS server, which should forward the request on if it doesn't know the answer.) Next, verify that your DNS server is working (nslookup command) and that a query for the server name comes back with the correct reponse. Also make sure that the connection suffix on the clients matches the DNS domain name of the server. (If you're using DHCP, you'll want to use DHCP options to set all of the client settings. Use ipconfig /all to check your configuration.) If all that is working fine, you should check your WINS setup - or consider installing and setting up WINS if you're not using it. On small networks it does far more good than harm.

Hope this helps

This discussion is closed to new replies.