DNS Error

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi all,

I keep getting this event error on one of my client machines.....even though it shows up everywhere on the server and client as a FQDN.

"Attempt to update DNS Host Name of the computer object in Active Directory failed. The updated value was 'DAM2'. The following error occurred:
The parameter is incorrect."


The name shows up on the client as dam2.damexpress.local. The name shows up the same way in properties in ADUC. The only place it show up as DAM2 only is in WSUS

I have tried to disjoin the domain and rejoin using "http://servername/connectcomputer but it did not fix the way it shows up in WSUS.

Any suggestions?


Randy

.

Relevant Pages

  • Add user wont set up mailbox
    ... I have the following event error: ... >to install the service pack to resolve the problem ... >>using the server management screen in SBS 2003. ... >>through the wizard and setup the user and their client ...
    (microsoft.public.windows.server.sbs)
  • Event ID 5719 at boot only
    ... All seems fine except the xp client shows event error '1054', ... I also get event error '5719', source 'NetLogon' in the system log. ... available to service the logon request. ... At first I thought this could be a DNS issue, ...
    (microsoft.public.windows.server.general)
  • Event ID 5719 at boot only
    ... All seems fine except the xp client shows event error '1054', ... I also get event error '5719', source 'NetLogon' in the system log. ... available to service the logon request. ... At first I thought this could be a DNS issue, ...
    (microsoft.public.windows.server.dns)
  • Event ID 5719 at boot only
    ... All seems fine except the xp client shows event error '1054', ... I also get event error '5719', source 'NetLogon' in the system log. ... available to service the logon request. ... At first I thought this could be a DNS issue, ...
    (microsoft.public.windows.server.general)
  • Re: WSUS Client not yet reported
    ... I understand that a client workstation is always in "not ... The root cause can be at either the server side or the client side. ... please check if it works with WSUS. ...
    (microsoft.public.windows.server.sbs)