Windows 2003 DHCP lease options reverting to old settings

Hi,

We recently moved our dc services to another server while we upgraded our
last Windows 2000 dc to Windows 2003. Our users have constantly complained
about slow logins, sharepoint access denials, printer problems, etc. It
appears that the Windows clients keep reverting back to the old scope options
for DNS servers so they are not able to access AD for authentication. I have
reviewed some technet articles that stated that DNS server settings changes
should take effect with a renewal routine, domain settings require a release
and renew, and wins settings require a reboot. Does anyone have any
information as to why the clients keep reverting back to the old settings?

I have walked a few people through the release and renew commands and so far
after a shutdown and power up, they appear to retain the new settings at the
moment.

Thanks,
Mike

A release and renew is not fixing the problem either. There are no other dhcp
servers on the local area network and the client shows the correct dhcp
server ip in an ipconfig /all so I know they are getting their options from
the new dhcp server. This server is a Windows 2003 R2 release with SP2.

"Mike" wrote:

> Hi,
>
> We recently moved our dc services to another server while we upgraded our
> last Windows 2000 dc to Windows 2003. Our users have constantly complained
> about slow logins, sharepoint access denials, printer problems, etc. It
> appears that the Windows clients keep reverting back to the old scope options
> for DNS servers so they are not able to access AD for authentication. I have
> reviewed some technet articles that stated that DNS server settings changes
> should take effect with a renewal routine, domain settings require a release
> and renew, and wins settings require a reboot. Does anyone have any
> information as to why the clients keep reverting back to the old settings?
>
> I have walked a few people through the release and renew commands and so far
> after a shutdown and power up, they appear to retain the new settings at the
> moment.
>
> Thanks,
> Mike

After some further troubleshooting, I did note that we still had the old
server's dhcp service still running but the scope had been deactivated. I
found some information that eluded to this being the possible cause but the
information was not official Microsoft documentation. I would like to
substantiate this with an official word from Microsoft if this is true. ONLY
DNS Servers reverted to the configuration on the old server, WINS never did
change. This is certainly odd behavior.

I have disabled the service on the old server to see if it clears up the
problem.

Thanks,
Mike

"Mike" wrote:

> Hi,
>
> We recently moved our dc services to another server while we upgraded our
> last Windows 2000 dc to Windows 2003. Our users have constantly complained
> about slow logins, sharepoint access denials, printer problems, etc. It
> appears that the Windows clients keep reverting back to the old scope options
> for DNS servers so they are not able to access AD for authentication. I have
> reviewed some technet articles that stated that DNS server settings changes
> should take effect with a renewal routine, domain settings require a release
> and renew, and wins settings require a reboot. Does anyone have any
> information as to why the clients keep reverting back to the old settings?
>
> I have walked a few people through the release and renew commands and so far
> after a shutdown and power up, they appear to retain the new settings at the
> moment.
>
> Thanks,
> Mike