Discussion Locked

Windows Server 2003: Can't see it on the network

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have just setup WIndows Server 2003, but I cannot see it on the LAN. I put the sever in the same workgroup as the rest of the computers, but it is still not showing up. Anyone know what's wrong?

10 replies

by ccollins

Is this an IP workgroup? If so try the ping routine - ping the loop-back, the IP address, the gateway/router, another machine's IP and then the name for name res. Check for typos and the correct subnet mask. Check for lights on the NIC and make sure your cable and connections are working.

by pb_valiant

if ur using a smart switch try resetting it

Power off / power on, wait 10 secs in between, sometimes if u connect hardware to a smart switch it wont recognise it until you reset the switch.

by cogtek

If this is your first 2003 server on this LAN, then the problem is probably related to your DNS settings.
Although DNS is for "Domain" naming, it is crucial for 2003 to have a good DNS structure in place for the LAN to operate.
Something to do with Netbios going away and DNS replacing it to help Microsoft implement .NET infrastructures.
I don't know the Technical details, but I have experienced the same thing.

Or could be your IP is incorrect.
Or could be the NIC isn't plugged in.
Or you could have a VLAN on your switch.

Start with basic troubleshooting.
Always check the plug first.

by rene

Go to your command prompt and type IPCONFIG and then enter. You should see the server's ip address, gateway, DNS, etc. That's your first step. If you can't do that then you need to check the Local Area Connection Settings.
Also use the MANAGE YOUR SERVER application within Windows as there are many wizzards in there that can help you setup properly

by adrianfoot

Check that you have Netbeui and IPX/Spx etc running on the computers in the work group. That should fix it.
Go to view network connections, their properties, and add a protocol Microsoft protocols add NetBeui and Ipx/Spx and you should be able to see all the computers by exploring the network once you have rebooted to make sure.
Obviously you must be able to ping the computers and make sure that the interfaces are all working.

by scifi

No IPX and No NETBEUI. They are not necessary and do nothing except fill your network with broadcasts. You should probably elaborate on what you mean by not appearing on the LAN. If you mean the network browse list (aka network neighborhood), then make sure you enabled netbios in the tcp/ip properties for the ethernet adapter and make sure the computer browser service is running.

by Former member

Double Check the Workgroup - Make sure it's spelled the same as all the other computers on the Network.
Make sure they are on the same Sub-Net (ie. 255.0.0.0, 255.255.0.0, 255.255.255.0)
Make sure you on the same IP Network.
Install the utility tools from the W2K3 CD. Run Netdiag /fix.

by dritten2002

Sounds like a Netbios issue, if you want to see it in your workgroup, try enabling "netbios over tcp/ip" or "using netbios through the dhcp server", you may also want to deploy a WINS server. You probably already know, WINS is not needed to run a Windows 2003 network, only TCP/IP, however it has a few perks!

by stevehazen

As added security the default settings do not allow the server to be visible. To make it visible you need to use the Microsoft Management Console on the server (or remote desktop) and use the security settings snap in. The server is probably working fine. To make network shares you just have to know the name of the server.

by kdoanconsulting

Where in MMC Security do you set the server to be visable?

I removed DNS from the server, rebooted, and reinstalled DNS and my server showed in "Entire Network" for about two weeks. Now it has "disappeared" (it doesn't show) when browsing in Entire Network.

So you are saying this done deliberately to have it and then not have it?

Please provide more detail on your post. Thanks.

This discussion is closed to new replies.