Discussion Locked

I can't my server on the Network...

0 helpful
19 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We just a added a file server on our NT network on our network. We are able to ping it by both name and IP but when we try to map a drive to it, it does not see it. We have both drives shared as c$ and D$ but still no avail. Help is definitely needed. The pc is running NT 4.0 workstation(not server). Also when browsing through network properties and in our domain we are unable to see. What changes are needed to be made on the domain controller to allow us to see it?

19 replies

by liquidcoolit

With Regard to what I said in my previous posting of the same question earlier.

Make sure you are logging on the Workstation as an administrator. Then you should be able to view the network properties. Make sure you have added the workstation to the domain. Place a tick where it askes you to add the computer to the domain, by placing in a Domain Admin's username and password. Otherwise just rename the workgroup to the same name as what the local domain is. Also make sure that the TCP/IP settings show a correct subnet mask and IP address (check another PC on the network to get the same subnet mask and IP range)

Nothing has to be done on the server.

Also make a directory on the PC and share that with rights for everyone to access it(or only certain users - for security). Then you can map to the shared folder.

As I said C$ and D$ are hidden shares for admin use.

Cheers ....

by ann777

I recommend that you just rename the shares as "Drive_C" and "Drive_D" ; the dollar sign at the end of your current shares is what makes them hidden.

by art23

The pc is on the domain already and it but it is not being seen out there by the network. The only way tha you could possibly see it is by pinging it.

by tejota

Can you map by IP address? Go to start\run\ and type \\xxx.xxx.xxx.xxx\d$ and click ok. If you are able to reach the server like that, then you have a WINS issue. Make sure you have the WINS IP address set in the TCPIP properties on the server. Make sure also that the workstation you're trying to map from is running WINS as well.

Hope this helps. TJ

by art23

That was the second thing that I tried. It failed as well when trying to map by IP address.

by dcadmin

Can you see the new workstation in server manager?
You can only map to c$ and d$ if you have administrative rights, no changing that. Make folders on the c and d drives and then share them. Users should not be mapping to the c$ and d$ shares. Example folder temp could be shared on server "testserver" and the mapping would be \\tempserver\test
If you can't do this we need to know more specifically what is wrong.
and like another person said, do check the wins database.

by rlevesque

Firstm is this server within the same domain, or did you add this server and put it into its own workgroup? Check under the network properties to verify you indeed placed it under the proper domain name.

Second, is that sometimes depending on your network and configuration, it may take time for the master browser list to be updated. Eventually it will appear if again, you entered it into the proper domain.

Third, have you gone under any of your servers and run Server manager and look and see if the workstation is listed within the domain?

Fourth, have you tried go use Start >> Find >> computers and see if it can find the computer.

Basically, the above is to verify the computer is located within the proper domain or workgroup.
Fifth is to create new shares. Anything with a $ at the end of a shared name, is a hidden share.

by brasslet

It sounds like your system isn't a member of the NT domain. Perhaps this is a bit too obvious, but did you add the system to the domain via Server Manger? If no, add it. If so, is the computer account showing up in Server Manager? If so, do you get any error messages when you try to log in to the server using a domain user account?

by qatest

Just a test of the email system by TechRepublic QA...sorry for the intrusion.

by curacao_dejavu

The change has to be made on the workstation.

The server service is not installed or not running. This allows the pc to be seen by other pc's and allows other pc's to connect to it.

properties of the network neighbourhood add server service orcheck in the control panel , service if the server service is running.

also just confirm if you can map from that workstation to another pc or to a server. Then you would know also that the problem is at the pc and not the server.

regards,

by art23

This was the solution the entire time. One re-installing the server service we had to re-install the service pack and now we are able to map drives to it. I wish you would have come along a lot sooner, it would have saved us some time.

This discussion is closed to new replies.