Re: NT to W2K Upgrade-DDNS issue
From: Patricia (keithala2000_at_yahoo.com)
Date: 12 Mar 2004 06:19:04 -0800
Thank you for your response, I apologize for the lateness of this reply.
To answer your questions:
1. Neither of the networks we upgraded were running DHCP, all machines were
assigned static ip addresses.
2. We were not previously running DNS on our pre-migration NT Domains.
3. Unfortunately, the most recent NT/2000 migration was performed on a
closed, secure network - so it's not permitted for me to export event viewer
I checked most of the event viewer records on the client machines, and saw
no DNS errors logged. Also no DNS errors were logged our DNS server.
During the migration, we attempted several times to get the workstations to
self register using the ipconfig/registerdns command. But they never
registered, and logged no event viewer errors. (This was while using the
"Only Secure Updates" DNS setting.)
What I did notice looking through the event viewer logs, were a number of
w32time errors, both on the servers and workstations. At the time of the
migration, we had not yet configured w32time to perform the time synchs.
I'm wondering if that had anything to do with the inability of the
workstations register themselves using ONLY SECURE Updates? (I thought I
read somewhere that Kerberos needs w32time operational to correctly work.)
Our fix for this was to change the DNS server to accept "All" updates, then
later change the setting back to "Only Secure". The machines seem to be
registering themselves correctly now. (Of course, by the time we'd changed
the setting back to "Secure Updates Only" we'd also corrected the w32time
I realize I'm not giving you enough information to diagnose the problem.
Both of our migrated W2K networks are now functioning fine, so I guess this
is really a moot point.
It's mainly an intellectual curiosity on my part as to what we may be doing
wrong in our migration procedure. I appreciate any thoughts you might have
firstname.lastname@example.org ("Eric Shen [MSFT]") wrote in message news:<3llDb36$DHA.email@example.com>...
> Hi Pat,
> In order to identify why this issue occurs, could you please provide some
> information to me for further investigation?
> 1. Are you using DHCP to assign IP addresses to these clients? If so, we
> can try to configure DHCP to register the IP address for the clients and
> then check if this issue persists. To do this, try:
> a. Open DHCP console.
> b. Right-click on the server. Select "Properties".
> c. Click "DNS" tab, check "Enable DNS dynamic updates according to the
> settings below" and then "Always dynamically update DNS A and PTR records".
> Then check if this issue persists.
> 2. Are your DNS server upgraded from an NT 4 DNS server or it is new
> installed? Have you changed any security settings on this DNS server?
> 3. I would recommend you send the client event log which contains the DDNS
> failure to me and the server DNS event log. I will check the logs and then
> check if there is any possible cause related to this issue. You can save
> the log as .evt files and then send to me at firstname.lastname@example.org
> Please feel free to let me know if you have any other information or
> further questions. I look forward to hearing from you.
> Eric Shen
> Product Support Services
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Get Secure! - www.microsoft.com/security