Discussion Locked

Server not regestering in Server Manager

0 helpful
17 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
One of my (stand alone but member, not a pdc or bdc) servers in my domain does not want to regester correctly in server manager for domains. When you go into server manager the name of the server is grayed out and server manager only recgonizes it as a nt server or workstation. It also does not show up in network neighborhood even though it has shared files. I can acces it through the command line (\\servername\c$) and it is regestering correctly in the WINS. Any ideas on why it is not regestering in network neighborhood and server manager?

17 replies

by aekland

The server manager uses information from the browse masters (network neighborhood) to show what the machine type is. Why it isn't showing up I don't know. The server service does the registering with the browse master so you should look at that. Also there are settings that can tell the system not to brodcast or be a browse master. It could also be a network issue where the broadcast annoucment is not getting to a browse master. From the server manager can you double click on the server and manage it? If not there may be a trust issue with the server.

by lbischofs

check to see if it is hidden...
From DOS run (on the machine is question)
Net config server

by doncurtis1

make sure the RPC service is running on the server in question. on a command prompt type
NET USE \\machinename\IPC$ where machine name is the name of the machine thats grayed out. this should give RPC service in server manager a kick in the pants.

by gahlad

The server lost its secure channel to the PDC,
To get this server back on the domain
1 Remove the computer account from the PDC server manager and manually synchronize with the BDC if you have one.
2 on the member server change it from the domain to workgroup and reboot
3 when the server comes backup in Workgroup mode, You can now rejoin the domain you can create a computer account from the member server or create it on the PDC before joining the Member server to the domain.

P.S. All Domain controller?s and member servers use the Secure Channel. Member servers are easy to reestablish the Secure Channel as you can see from above. Primary and backup Domain controller the above won?t work because you can?t put a PDC or BDC in workgroup mode. In order to restore the channel on Domain Controllers you need NETDOM off the NT Resource Kit the help file will give instruction on use.

I hope this helps
George-

NETDOM /Domain:mydomain /User:mydomain\AUser /Password:apassword BDC mybdc /ADD
NETDOM /Domain:mydomain BDC mybdc /ADD
NETDOM /Domain:mydomain BDC mybdc /DELETE
NETDOM BDC mybdc /QUERY
NETDOM BDC mybdc /RESET <------- this one works well for BDC

Netdom Help vers. ? copyright Microsoft Corporation 1996-1997

by ktimm

None of the solutions offered here fixed the problem. I had to resort to completely reinstalling (not just a repair or overlay) NT. Now it seems to be working correctly.

This discussion is closed to new replies.