Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Netlogon Event ID 5789

376 views
Skip to first unread message

Karl

unread,
Oct 1, 2006, 3:05:01 PM10/1/06
to
I recently had to reinstall SBS 2003 because of a hardware failure and
repeatedly get the following error in the event viewer on one of my WinXP Pro
workstations:
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5789
Date: 10/1/2006
Time: 1:33:53 PM
User: N/A
Computer: KARL
Description:
Attempt to update DNS Host Name of the computer object in Active Directory
failed. The updated value was 'KARL'. The following error occurred:
The parameter is incorrect.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 57 00 00 00 W...

I have tried the various fixes suggested my Microsoft to no avail.

Any ideas?

--
Thank you, Karl

Robert L [MVP - Networking]

unread,
Oct 1, 2006, 4:09:41 PM10/1/06
to
Did you change the domain name after re-installed it? This search result may help,
 
Troubleshooting DNS
DNS registration errors 5788 and 5789 when DNS domain and Active Directory domain ... in the application event log for DNS Server: Event ID: 407 Source: DNS ...
www.howtonetworking.com/domain/dns6.htm

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com

Karl

unread,
Oct 2, 2006, 10:02:02 AM10/2/06
to
Thanks, but these seem to reference things I have already tried ... All the
DNS and AD tools seem to indicate all is ok ... any other thoughts?
--
Thank you, Karl

Ed Walters [MSFT]

unread,
Oct 2, 2006, 11:16:41 AM10/2/06
to
What happens when you remove the client from the domain. Reboot then add
it back to the domain?
What device is the client pointing to for DNS?

Ed Walters [MSFT]

Karl

unread,
Oct 2, 2006, 11:24:02 AM10/2/06
to
Thanks to Robert and Ed for your responses ... I eliminated this problem by
changing the name of the client and adding it to the network.
--
Thank you, Karl
0 new messages