rpc and netlogon issue

  • Thread starter Thread starter Andrew Bullock
  • Start date Start date
A

Andrew Bullock

Hi guys,
can someone suggest whats causing my win2k logon onto my 2k3 server to take
a while, producing this error?

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5788
Date: 29/12/2003
Time: 11:32:29
User: N/A
Computer: ANDREW
Description:
Attempt to update HOST Service Principal Names (SPNs) of the computer object
in Active Directory failed. The updated values were '<UNAVAILABLE>' and
'<UNAVAILABLE>'. The following error occurred:
The RPC server is unavailable.
Data:
0000: ba 06 00 00 º...



Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5789
Date: 29/12/2003
Time: 11:32:29
User: N/A
Computer: ANDREW
Description:
Attempt to update DNS Host Name of the computer object in Active Directory
failed. The updated value was 'andrew.trull.no-ip.com'. The following error
occurred:
The RPC server is unavailable.
Data:
0000: ba 06 00 00 º...



thanks in advance

Andrew
 
Make sure that the ipconfig/all from the clients shows that everything is
pointing to the server-IP. How many nics in the server? Make sure that DNS
on the servernic(s) *only* points to the server-IP.

Marina
 
I changed the server NIC to point to itsself for DNS

i relogged on, but it still took time, and gave this error:

Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11151
Date: 29/12/2003
Time: 13:44:03
User: N/A
Computer: ANDREW
Description:
The system failed to register network adapter with settings:
(.5 is the server, .4 is the client)

Adapter Name : {8E1E107A-CE72-46B1-98CB-D24C615CBBC4}
Host Name : andrew
Adapter-specific Domain Suffix : trull.no-ip.com
DNS server list :
192.168.0.5
Sent update to server : None
IP Address(es) :
192.168.0.4

The cause of this DNS registration failure was because of DNS server
failure. This may be due to a zone transfer that has locked the DNS server
for the applicable zone that your computer needs to register itself with.

(The applicable zone should typically correspond to the Adapter-specific
Domain Suffix that was indicated above.) You can manually retry registration
of the network adapter and its settings by typing "ipconfig /registerdns" at
the command prompt. If problems still persist, contact your network systems
administrator to verify network conditions.
Data:
0000: 2a 23 00 00 *#..


i rebooted and logged on again, and it gave the two errors i mentioned
before. :s

Cheers
Andrew Bullock
 
Can you post the ipconfig/all please?
Do you have options 003, 006 and 015 in DHCP-server, Scope options? Do you
have DNS-server set to allow dynamic updates?

Marina
 
Hi Marina

I dont have it set up as DHCP server, the Router deals with this.

I think its set up to allow dynamic updates, because it complained it didnt
have a static IP, and needed one. (However, it does have a fake static IP.
My router ALWAYS dynamically assigns it with the same IP)

I just found out it didnt have a FQDN set, which has fixed IE taking ages to
browse.

Any other suggestions

Thanks a lot! Cheers for your help, really appreciate it :)
Andrew
 
Andrew,

Your server should do all the serving, that includes DHCP, DNS and if you
still have W9x, ME or NT4-clients WINS.
Your server should also have a static IP.

Marina
 
Hi,

Thanks for the info, but ive had it working before, without being a DHCP
server.

Could it be because i made it a DNS server before an AD controller? how to i
demote it from DNS, so i can re-promote it afterwards?

Thanks
Andrew
 
I meant stop it being a DNS server, then make it a DNS server again, to
refresh anything that wasnt set properly when i created the AD


Im now getting this when i log on:


Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11151
Date: 29/12/2003
Time: 14:55:58
User: N/A
Computer: ANDREW
Description:
The system failed to register network adapter with settings:

Adapter Name : {8E1E107A-CE72-46B1-98CB-D24C615CBBC4}
Host Name : andrew
Adapter-specific Domain Suffix : trull.no-ip.com
DNS server list :
192.168.0.5
Sent update to server : None
IP Address(es) :
192.168.0.4

The cause of this DNS registration failure was because of DNS server
failure. This may be due to a zone transfer that has locked the DNS server
for the applicable zone that your computer needs to register itself with.

(The applicable zone should typically correspond to the Adapter-specific
Domain Suffix that was indicated above.) You can manually retry registration
of the network adapter and its settings by typing "ipconfig /registerdns" at
the command prompt. If problems still persist, contact your network systems
administrator to verify network conditions.
Data:
0000: 2a 23 00 00 *#..


Cheers
Andrew
 
Andrew, do yourself a favor and put DNS-server and DHCP on your server.
Give your nic a static IP and set DNS to your server-IP, set an exclusion in
DHCP for example 192.168.0.1 - 192.168.0.10, add options 003, 006 and 015 in
Scope options.
Turn of the DHCP-server in your router. Start DHCP-server service on your
server.
Make sure DNS-server is only listening to the server-IP, enable Forwarders
and put the ISP-DNS-numbers in there, on tab General make sure that 'allow
dynamic updates' is enabled.
Check the Reverse and Forward Lookup Zones and make sure you have a
serverrecord in there.
Restart DNS-server.
 
Back
Top