When you made your IP change did you update your DNS records to show your reverse pointer for the new IP address ?
This error sounds like the workstations cannot find the GPO and so thats why this error gets thrown.
Main Topics
Browse All TopicsHi,
Ive just changed over the IPs on my DCs to a new subnet. Now my XP clients report eventID errors 40960 and 40961 when logging on. Basically they are aborting domain processing and logging on with cached credentials. They also take an age to log on. I can ping the DCs (with AD integrated DNS) from the clients but cant resolve hostnames. My member servers can resolve names and log on properly. So can one or two XP clients but the rest cant. Ive check the difference between the machines that cant and the machines that can are there dont seem to be any.
I reinstalled my DNS which didnt help. Ive removed machines from the domain and put them back in and no luck. I desperately need to sort this out for Monday&. Any ideas?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
The problem is definitely DNs related if you resolve all steps shown above do a dns flush run netdiag and b4 all else ensure the workstations are getting dns from a machine that can read the addresses of the servers you should have no isses are you getting IP's and DNS from a DHCP server if so are you having any probs with this server reading the doman controller.
From the machies that aren't happy i cant ping either my domain (xyz.co.uk) or a dc by name (server01.xyz.co.uk) With my dns i did amend the records for my dc and the pointers. All my clients have their DNS settings pointing to my DCs. I'm not using DHCP.
I've tried 25 clients so far and only two are working, even though they take an asge to load. Thanks for the replies.
I will point you to a resource that will help you to resolve this as the issues can be broad ranging from time sync to svc issues etc.
http://www.eventid.net/dis
give it a good read you should come out with a resolution.
This all has to do with changing the server maybe resetting the machine account or password might do the trick but do give it a read none the less it will leave you with more resources to handle future issues.
Thanks for the replies, I have thoroughly read the document that becraig pointed me to, and i have tried some proposed solutions non of which have really helped. Namely making sure there are no time sync issues and re-applying 2000 SP4 and demoting and promoting DCs.
I have now put one DC back on to its old IP/subnet and all clients are happily connecting, I've left the other in the new subnet and amending AD sites & services accordingly and both DCs are replicating. I did one last thing and tried to ping my domain name from my DCs. Both replies with the wrong IPs. My old network was class C and looked like this:
1st DC: 192.168.1.6
2nd DC: 192.168.1.5
I then moved them to 10.1.4.1 and 10.1.4.2 respectively. When they were in the new network and it tried to ping my domain name the results were thus: 10.1.4.1 resolved the domain to 192.168.1.6 and couldnt reach it and 10.1.4.2 resolved to 192.168.1.5 and also couldnt reach it. This must indicate DNS.
Strangely one of the XP clients that was working resolved the domain name to 10.1.4.1 correctly all other clients couldnt resolve the name at all.
I have already chnaged the IP address of both my DCs and amended the DNS records last saturday, even so my clients still resolve the domain name to the wrong IPs. I also flushed the dns from my clients. Where/is there is the DNS record for the domain name e.g. xyz.com, i can't see it in my DNS settings?
Okay, Ive fixed my own problem and thought Id post up the solution just in case others find themselves in a similar boat.
Problem:
When I moved my server over to their new IPs most of my XP boxes wouldnt log on, some would, most wouldnt. Using nslookup on my clients reported the old IPs of my DCs and no matter what settings I used/typed in on the client. Really frustrating
Solution:
When I moved my DCs I didnt properly investigate the current policies on my DCs.
My Workstations policy (affecting all my users) had the setting: Computer Configuration > Administrative Templates > Network > DNS Client > DNS Servers configured to the old IPs of my DCs. This setting automatically overrides the DNS settings in the properties of the network connection.
Since my clients couldnt log on to the domain they used the cached information theyd collected. I rectified this by amending the registry setting that the policy created to the new DC IPs and rebooted. My clients could then log on. However as soon as a policy refresh was applied the old settings, reflected in the registry, were back. This clearly indicated a policy problem, I scoured Group Policy, found the setting and promptly disabled it. I must have made this setting about two years ago and plain forgot. DOH!
Well, a lesson well learnt. Dont use policies for network connections unless you write down the fu**ing settings so as remember what youve done!!!!! Thanks for the responses. This question can now be closed.
Business Accounts
Answer for Membership
by: ashutosh_kumarPosted on 2007-09-23 at 05:59:14ID: 19944194
from the xp machine try to ping your domain name...suppose your domain is xyz.com and the dc's name is server01.xyz.com
then
ping xyz.com
it should show the IP of some DC
if this is fine, then there is problem at DC, try restarting the NetLogon Service, then run this command on the DC
netdiag /fix
this will fix DNS issues if any