Archived from groups: microsoft.public.win2000.dns (More info?)
Background Info:
A couple of weeks ago, we introduced another w2k3 server into the domain.
Now the domain has only one w2k server left, which will soon be upgraded.
Anyway, the w2k server is a domain controller and has dns, dhcp, roles, and
so does the new w2k3 server, whick replaced a w2k server with the same roles.
Problem:
Clients that get there ip address from the w2k3 server, do not dynamically
update dns, but clients that get there ip addresses from the w2k server do,
as they always have in the past.
More Information:
I done quite a bit of research and have made sure that dhcp and dns are set
up exactly like the w2k server. The only thing I changed to try and get it to
work, was to change the dhcp - dns setting from dynamically update dns to
always update dns.
On my workstation and I suppose on the others, there is a NETLOGON error in
the event viewer\system folder which states:
Attempt to update DNS Host Name of the computer object in Active Directory
failed. The updated value was 'JON'. The following error occurred:
The parameter is incorrect.
I click on the link to trouble shoot, and I get this:
Explanation
Active Directory could not update the DNS Host Name of the computer object.
Possible causes include:
The computer is not configured to use the correct DNS servers.
The DNS servers do not support dynamic update.
The DNS zone is not configured to support secure dynamic updates.
User Action
To troubleshoot the problem, run the DCDiag.exe program. This program is
located on your Windows Server 2003 CD in the Support\Tools folder.
I ran dcdiag against the w2k and the w2k3 server to compare, and they both
pass all tests with the exception that the w2k3 server states this for the
first test:
Doing initial required tests
Testing server: North-Palm-Beach-FL\NPBEX01
Starting test: Connectivity
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly registered
with DNS
......................... NPBEX01 passed test Connectivity
Thanks for the help.
Background Info:
A couple of weeks ago, we introduced another w2k3 server into the domain.
Now the domain has only one w2k server left, which will soon be upgraded.
Anyway, the w2k server is a domain controller and has dns, dhcp, roles, and
so does the new w2k3 server, whick replaced a w2k server with the same roles.
Problem:
Clients that get there ip address from the w2k3 server, do not dynamically
update dns, but clients that get there ip addresses from the w2k server do,
as they always have in the past.
More Information:
I done quite a bit of research and have made sure that dhcp and dns are set
up exactly like the w2k server. The only thing I changed to try and get it to
work, was to change the dhcp - dns setting from dynamically update dns to
always update dns.
On my workstation and I suppose on the others, there is a NETLOGON error in
the event viewer\system folder which states:
Attempt to update DNS Host Name of the computer object in Active Directory
failed. The updated value was 'JON'. The following error occurred:
The parameter is incorrect.
I click on the link to trouble shoot, and I get this:
Explanation
Active Directory could not update the DNS Host Name of the computer object.
Possible causes include:
The computer is not configured to use the correct DNS servers.
The DNS servers do not support dynamic update.
The DNS zone is not configured to support secure dynamic updates.
User Action
To troubleshoot the problem, run the DCDiag.exe program. This program is
located on your Windows Server 2003 CD in the Support\Tools folder.
I ran dcdiag against the w2k and the w2k3 server to compare, and they both
pass all tests with the exception that the w2k3 server states this for the
first test:
Doing initial required tests
Testing server: North-Palm-Beach-FL\NPBEX01
Starting test: Connectivity
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly registered
with DNS
......................... NPBEX01 passed test Connectivity
Thanks for the help.
Facebook
Twitter
Instagram