coonasty
asked on
windows 7 client cannot join windows 2008 active directory domain
have a dell windows 7 64 bit all in one that has been rock solid for 6 months. couple days ago turned it on and could not access server programs/folders (hp proliant server)
server and client pc both have static ip, server ip is first on client dns setting.
nslookup shows server ip correctly
server does not show up in network list of computers, all others do.
left domain and tried to rejoin...getting error "network path not found"
tried connecting with both the internal nic and internal wireless, which both worked fine in past...neither work now
after trying to join domain and getting the error, i cant ping server. i have to do a net stop/start dnscache to ping server again
but i can ping it fine after. internet works fine. can see other computers fine on network
event viewer on client has event 5719 NETLOGON error
This computer was not able to set up a secure session with a domain controller in domain "---------" due to the following:
There are currently no logon servers available to service the logon request.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
also event 1058 GPO error due not connecting to DC
hoping someone has an idea of where to go b/c everything i have tried has failed. TIA
server and client pc both have static ip, server ip is first on client dns setting.
nslookup shows server ip correctly
server does not show up in network list of computers, all others do.
left domain and tried to rejoin...getting error "network path not found"
tried connecting with both the internal nic and internal wireless, which both worked fine in past...neither work now
after trying to join domain and getting the error, i cant ping server. i have to do a net stop/start dnscache to ping server again
but i can ping it fine after. internet works fine. can see other computers fine on network
event viewer on client has event 5719 NETLOGON error
This computer was not able to set up a secure session with a domain controller in domain "---------" due to the following:
There are currently no logon servers available to service the logon request.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
also event 1058 GPO error due not connecting to DC
hoping someone has an idea of where to go b/c everything i have tried has failed. TIA
ASKER
win 7 pro.
tried joining domain with multiple accounts as well as administrator. same error
tried joining domain with multiple accounts as well as administrator. same error
As the system wasn't running for half an year, first do a full windows update. After that try connecting to the domain again.
Secure channel broken. You need to reset secure channel. The computer which is not connected to the domain for more than 30 days will break the relationship with server which means that the secure channel password wouldn't work, you need to reset it but that's not straight forward.
You need to either use netdom or powershell. Use this link http://blogs.technet.com/b/heyscriptingguy/archive/2012/03/02/use-powershell-to-reset-the-secure-channel-on-a-desktop.aspx
You need to either use netdom or powershell. Use this link http://blogs.technet.com/b/heyscriptingguy/archive/2012/03/02/use-powershell-to-reset-the-secure-channel-on-a-desktop.aspx
ASKER
system has been "rock solid" as in has ran perfect since the day it went in 6 months ago.
updated already
updated already
Is there any other computer connected to your domain controller? also how the DNS is configured?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
good find, have a great day
ASKER
b/c the fix was not stated by someone else, i found it elsewhere on the internet
Could be a profile issue, can you try a different user to see if that works. This used to happen with XP once in a while, but have not heard of it happening in W7 yet.