Hello, I have recently upgraded an old NT4.0 domain to Windows Server 2003 with Active Directory. The upgrade itself went fine, with the NT4 machine being upgraded to 2003, the new server being brought online to run parallel with it, and the domain, account and file information transfering between the servers without a hitch. The old NT4 server was then demoted via DCPROMO so it was no longer was part of the active directory. After the old server was demoted and no longer on the network, I configured the new server to act as DHCP, DNS and WINS server. The clients all find the DHCP server fine (10.170.65.2) and all the network settings are properly populated with the exception of the "Primary DNS". Instead of the DNS server specified in the DHCP configuration, it points to 10.10.1.1 which is a setting that has never been configured on this network. If I go to the client machine, click on the network connection, click on "repair" then the correct DNS server is found without fail. As a result of this DNS server being incorrectly specified from DHCP the client machines are taking a considerable time to log on. I know that I could provide a static IP address on every client machine and solve the problem, but that isnt so much a fix, as more of a hack in my eyes. It is just infuriating that this 10.10.1.1 is appearing from nowhere for no good reason. I have stripped down and rebuilt the DHCP portion of the server 3+ times now, and I have also triple checked the DNS server settings and everything is correct in regards to forwarding. I have also checked the internet router and DHCP has been disabled on it. Any help or recommendations would be fantastic. Cheers, Simon

if you ping that ip what comes back? Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.

is that box an authorized one on your network, is it a rogue DNS server?

I have tried pinging the box and it does not exist on the network. In case 'it' was blocking pings I have also tried to access it via various remote access software but to no avail. As far as I can tell 10.10.1.1 does nt exist on the entwork, neither has it ever existed on the network in the past. Cheers, Simon

So that narrows it down to just the server and in particular DNS and DHCP Start checking the server's nic dns entries dns forward and reverse lookup zones dhcp server options [where you set the dns server] Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.

Wanderer, I have checked the DNS forward and reverse lookup zones, along with the DHCP server options, and they are all fine. There is not a single reference to 10.10.1.1. Although I must admit that I havent checked the servers NIC DNS entry. I shall check it when I am next on site. Cheers, Simon

Ten bucks that 10.10.1.1 is configured on the servers NIC as the DNS. Holy Wow.