Question Locked

DNS Address Wrong In DHCP Scope

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a Windows 2003 server running DHCP to several clients runing mostly XP Pro. Many of the clients intermittently pull a DNS address of 192.168.1.1 in their scope when the address they should receive is 10.0.0.1. When the faulty address is pulled applications such as exchange e-mail and many things runing from the server at 10.0.0.1 hang and won't launch.

IPCONFIG/RENEW from the DOS prompt renews the lease coeerctly every time. Does anyone have an idea as to the source and cause of the faulty DNS address within the scope?

5 replies

by cg it

might check the options in DHCP see if the DNS address listed there is correct.

by lowlands

Or is the IP address the client gets wrong as well?

by dhouchin

1) Check the ROUTER entry in both the Server Options and the Scope Options on your DHCP Server.

2) Check the TCP/IP properties on any VPN or additional network connections to see if they are using statically defined DNS.

3) Make sure you don't have another network device (like a Linksys router) operating as a DHCP Server. Normally, this would shut down the MS DHCP server, so this is unlikely, but possible depending on your environment.

by huoml

You could check if the clients have preferred/Alternate DNS entries in TCP/IP settings, or choose 'obtain DNS server address automatically' option for DNS entries.

-H

This discussion is closed to new replies.