Question Locked

No local server DNS resolution for W2K workstations after AD migration

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

Just migrated 2 W2k Pro workstations to the new domain. All other machines are XPPro.

After the migration, the W2k machines do not resolve servernames from the old domain. (We haven't migrated the servers yet). All XP machines do not have a problem.

The W2k machiens can resolve server1.domain.com but do not resolve server1

Migrating from domain.com (w2k3)to domain.local (w2k8)

The workstaions machines have been migrated to domain.local and users are authenticating to the new domain. THis happens with both regular users and Domain Admin accounts logging on to the workstation.

Anyone have any idea what is different for w2k in this situation?

5 replies

by wizard-09

So what your saying is that it can resolve the FQDN but not the dns name have you did a ipconfig /flushdns on the effected machines, try adding the server name to a host file in the system32 folder with the information server1 192.164.12.18 or what ever the IP may be as you said its a dns problem have you got dns forwards in place?

by 1bn0

Yes we released and renewed the IP. ipconfig /flushdns, ipconfig /registerdns and rebooted the workstation. WE have checked the IP configuration to make sure there is nno leftover dns information.

DHCP is providing the new DNS server information.

This is only happening on the W2k machines NOT the XP machines.

We don't want to use a LMHOSTS files.

by churdoo

I suppose I would compare the DNS suffix search list from an IPCONFIG /ALL of a typical XP workstation versus a typical W2K workstation.

You may have to force the DNS Suffix Search List in your DHCP options to include both domain.com and domain.local. I can't explain why this would be different for XP versus W2K but it's my first thought (maybe XP automatically uses all trusted domains in its DNS search list, I don't know).

Another thought -- are all of your machines on a single local network? Seems to me, the W2K workstations failing a DNS lookup for a given name, should then make a NETBIOS broadcast looking for same, which if on the same local network, would be answered ... unless NETBIOS is disabled or if it's crossing networks which would not pass the broadcast.

by 1bn0

added domain.com and everything works fine.

No dns on default domain (domain.local)add domain.com to servername and try again.

Thanks for the response.

This discussion is closed to new replies.