ProcessGPOs: Processing failed with error 59

Hi.......

I have searched but can't find an answer to this problem........

Some of our users are getting an error message during logon to the effect that their profile cannot be downloded because of a network problem or permissions problem.

Our application logs show an event code 1504 and the error "Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted). Group Policy processing aborted."

I've swithced on the logging feature and can see errors  "ProcessGPOs: Processing failed with error 59" and "ImpersonateUser: Failed to impersonate user with 5".

When pinging clients from the server we get very erratic ping times.. sometimes sub 1ms sometimes a negative number.

Thing I've tried so far: reboot switches, check DNS is all OK, manually point clients to DC, install latest Gigabit Ethernet card driver.

Would be greatful for any help!

Cheers

Paul
Pdab1965Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TDKDCommented:
Check to see if there are any old false pointer records for the computers in question?? If so then delete them and try again....Also have you performed an nslookup on the clients in question, does the IP they actually have assigned to the computers host name match up?? This is also a good way to see if false pointer records exist for the clients in question...

Hope it helps :-)

Tony D.
0
Pdab1965Author Commented:
Thanks,

Sorry if I'm asking the obvious but how do you determine which are the false ones?

Also I've tried setting "group policy slow link detection" to zero in a policy object that applies to the client pcs but that has had no effect.

Thanks fo any further advice.

Cheers

Paul

0
Pdab1965Author Commented:
I think I've solved it myself.

It appears to be due to a problem with a clock drift on AMD dual core processors. See here.....

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01075682


0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.