Windows Server 2003 Domain Controller is not viewable on Network
Does anyone know how to get a domain controller to show up when you try to view the network? In other words, when you browse the domain, it will list all of out workstations but it does not list the actual server in the list. I can access the server from a client by going through a command line. How can I get the server to show up in the domain? Thanks in advance!!
July 29th, 2008 8:30pm
For Windows Server 2008 I think you need to turn on the "Network Discovery" feature in network connection properties. Right click on network than click properties and look for Network Discovery. For Server 2003 I have never run into that problem unless the firewall is causing the problem.
Free Windows Admin Tool Kit Click here and download it now
July 29th, 2008 10:47pm
Hi,
Do you mean when you chick My Network places->Entire Network->Microsoft Windows network, you can browse other clients? If I misunderstood, please let me know.
This problem may be caused by several factors. Let's start from some basic ones. Firstly, I list the services and ports which browsing is dependent on. Please check them one by one to see if they are all well-prepared.
1. Required running services:
l Computer Browser Service
l Workstation Service
l Server Service
Please run 'services.msc' to check if the state of services above is 'Started'.
l Enable NetBIOS over TCP/IP
You can enable NetBIOS over TCP/IP for computers running Windows Server 2003 by opening Network Connections, right-clicking a connection, clicking the Internet Protocol (TCP/IP) component, clicking Properties, clicking Advanced, clicking the WINS tab, and clicking the 'Enable' option in NetBIOS setting.
2. Required TCP/UDP Protocol Ports
UDP 137
UDP 138
TCP 139
Please check if some 3rd party applications on the local machine, such as firewall, block these ports.
You can use portqry to check if these ports are listening .
For example:
The following command tries to resolve my server to an IP address and then queries the specified range of UDP ports (137-139) in sequential order on the corresponding host. This command also creates a log file (my_server.txt) that contains a log of its output.
portqry -n DC_server -p udp -r 137:139 -l my_server.txt
Below is an article about the PORTTQRY tool
http://support.microsoft.com/?kbid=310099
Below is a link to download the PORTQRY tool
http://www.microsoft.com/downloads/details.aspx?familyid=89811747-C74B-4638-A2D5-AC828BDC6983&displaylang=en
3. Network problems
Please test if this PC can access other clients using UNC path (\\servername).
If this issue still persists, please provide me the result of your verification of the above factors and the following information.
1. How is you attempting to browse to the computer?
2. Are all the computers in the browse list on the same local subnet as the client machine?
3. Does Browsing work using Safe Mode with Networking?
4. Does other server have the same problem in your network?
July 30th, 2008 12:59pm