2000 Server Can't Join 2000 Adv Svr Domain

[vz1518]

After installing a server and have it Join the domain during installation the server will not join the domain again after reboot. Each time I try to log on to the designated domain I get the following error message:

The system cannot log you on due to the following error: RPC Server is unavable. Please try again.

Help.

 

[ashpp]

Likely DNS issue...

What errors are in the Event Viewer?

What Service Packs are you running?

Is this a single domain network?

Have you set up DNS on the new server then tried again?

What happens when you try to do NSLOOKUP from this server?

Also Take a look at

http://support.microsoft.com/default.aspx?scid=kb;en-us;224370

 

[ashpp]

Likely DNS issue...

What errors are in the Event Viewer?

What Service Packs are you running?

Is this a single domain network?

Have you set up DNS on the new server then tried again? (set it up to look at the current server)

What happens when you try to do NSLOOKUP from this server?

Also Take a look at

http://support.microsoft.com/default.aspx?scid=kb;en-us;224370

 

[GlenJohnson]

AshleyPride is probably right. Try an ipconfig /all and see if anything is ammiss. Also, try leaving the domain and rejoin the domain. Check the event logs as per the earlier post, and see if the all services that are supposed to be automatic are started. The rpc is remote procedure call. I don't have a server in front of me, so I can't verify that this is a service, but it's worth checking. Good luck. Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
"Since we cannot know all that there is to be known about anything,
we ought to know a little about everything."
Blaise Pascal

 

[vz1518]

I am currently running Service Pac 3

This is a single domain but I have a DSL router that gives me acces to the Internet. So I have natted IPs for the local addresses.

I have not set up DNS on this server that is Failing. I have though set up DNS on the Domain Controler. And I must say that I have two other servers connecting to this domain without errors.

I am able to do NSLookup and name is resolved to IP and I am able to PING and get back a response. I am able to IPConfig and I get back all the configuration IP, etc.

The error messages that I am getting from the Event Viewer are:

1) The PrintQueue container could not be found because of the DNS Domain could not retreive the name.

Attempting to update HOST Services Principal Names (SPNs)
of the computer object in Active Directory failed. The Update values were "UNVALUABLE".... The following error occur, RPC not available.

 

[GlenJohnson]

Do you have a bad host or lmhost file? Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
"Since we cannot know all that there is to be known about anything,
we ought to know a little about everything."
Blaise Pascal

 

[ashpp]

1 - Does a NETDIAG on the current DC show everything is okay on the network?
Does the DNS server have the correct SRV records (_msdcs, _tcp, _udp, _sites) ?
In the DNS server is there a entry for this new server?

2 - Is DNS on the client OK?
Primary DNS suffix correcT?
Check Append primary and connection specific DNS suffixes.
Check Append parent suffixes of the primary DNS suffix check box.
Check Register this connection's addresses in DNS check box.

Ash.

 

[vz1518]

OK
I did some investigation on my PDC and found out that (eventhough it was not reporting a failed service) it had numerous failed services.

Failed services in the Event Viewer are as follows:

NetLogon with Event ID 5775
Deregistration of the DNS record 'domainName.com. 600 IN A 172.142.123.147' failed with wthe following error. DNS server unable to interpret format.

All the events are the same as above with the exception of what seems like the IP Address with the last Octel incrementing. Example, from above 172.142.123.147 changes to 172.167.85.134.

Any suggestions?

Thanks.

 

[ashpp]

The DNS zone you are in isn't accepting DNS registrations. Have you enabled dynamic updates?

Enable Dynamic Update on the Forward Lookup Zone
In DNS Manager, expand the DNS Server object. Expand the Forward Lookup Zones folder.
Right-click the zone you created, and then click Properties.
On the General tab, click to select the Allow Dynamic Update check box, and then click OK to accept the change.
DNS server configuration is finished. Proceed to the next step if you want to promote this DNS server to be the first domain controller in the enterprise. This is the recommended path.
If you decide to use a different computer as your first domain controller, the configuration instructions in the "DNS Setup for Replica and Child Domain Controllers" section apply to that domain controller after you have installed Windows 2000.

 

[ashpp]

Also check that the DNS servers are all authorised for the zones they are running.