Windows server 2008 r2, network issues after update
We have a Windows Server 2008 r2, yestreday it updated and re-started. Now network users cannot re-connect to network drives until they are re-entered their username and password. This they have to do this each time they log back in. Why?
ASKER
The AD does not see the Domain. This server is the only one in use so it cannot see iteself. Is it OK to do the NETDO VERIFY and rejoin?
ASKER
It seems that AD has failed, "there are no logon servers available", any idea why this has happened after the updates and how can we fix it?
this typically means that the DNS for teh server is misconfigured, and cant locate a domain controller
make sure the DNS configuration of teh server is still correct ( should be pointing to the Active directory DNS zone)
so the machine itself the windows2008 machine is the domain controller?? on which file shares are there as well or where is the domain controller.
make sure the DNS configuration of teh server is still correct ( should be pointing to the Active directory DNS zone)
so the machine itself the windows2008 machine is the domain controller?? on which file shares are there as well or where is the domain controller.
ASKER
This is the PDC, all file shares are on the main Drive. Nothing unuslaul expect this all occured after updates.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
All checks run indicated a problem with netlogon
As suggested I re-started this and that seem to have fixed it. Thanks
As suggested I re-started this and that seem to have fixed it. Thanks
ASKER
All seems to work now, exchange and AD.
ASKER
Netlogon re-start but with no answer as to why it was stopped despite several re-starts.
I would verify the domain membership of the computer account, and potentailly unjoin and rejoin it to the domain. (use tools like NETDO VERIFY)