emerym
asked on
Hardware upgraded Windows 2003 DC now client machines slow.
Replaced Win2003 DC (incl DNS) with another box for hardware reasons. On new box installed DHCP and DNS then ran Dcpromo. All worked fine so manually transferred FSMO roles and selected GC (removed GC from old server). Checked new DNS was primary and transferred DHCP from old server changing scope to reflect new DNS server. Left for 24hrs to replicate between old and new DC then took old server offline.
Run ipconfig/ release and renew on all clients to renew lease. Now all clients are working fine except 7 out of 80. These 7 are extremely slow to login and when browsing the network the machine locks up. These clients are pointing to the new DNS server but obviously still looking for the old first. This was proved by bringing the old DC server back online but disabling DHCP and Netlogon services. Have deleted DNS entries and run ipconfig/ flush and registerdns on these clients and both DNS zones are updated on new DNS server. I'm fairly certain it must be an DNS issue. Do not wish to demote old DC until everything hunky dory.
Run ipconfig/ release and renew on all clients to renew lease. Now all clients are working fine except 7 out of 80. These 7 are extremely slow to login and when browsing the network the machine locks up. These clients are pointing to the new DNS server but obviously still looking for the old first. This was proved by bringing the old DC server back online but disabling DHCP and Netlogon services. Have deleted DNS entries and run ipconfig/ flush and registerdns on these clients and both DNS zones are updated on new DNS server. I'm fairly certain it must be an DNS issue. Do not wish to demote old DC until everything hunky dory.
ASKER
Cheers Jay, but if DHCP settings had ref to old DC, problem would be for all clients. Also when using dcpromo in an established DNS integrated zone domain the zone settings are automatically copied to the new DNS server.
i agree with your DHCP comment to a point, often machines behave differently and they can be a prick to troubleshoot.....you didnt mention integrated zones so i thought i should check! :)
do your nslookups pass for the server from the client machines
do your nslookups pass for the server from the client machines
ASKER
yes they do and I can ping all servers by hostname
no old static wins entries lying around?
ASKER
Unfortunately not.
You might want check if they are using offline file caching, if so flush that as well.
ASKER
None of the clients in question have it enabled, good question though.
what do your event logs report?
ASKER
nothing out of the ordinary except application hung entries due to not locating their home drives.
ASKER
Think I have found the problem. Clients H:\ drive mapping points to new server and desktop 'My Documents' folder has UNC path to old server!!
ha! that could do it
well done
well done
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
check your DHCP settings, make sure they arent including a reference to your old DC for DNS, also make your DNS zones AD integrated