pcchiu
asked on
No Logon Servers?
On Some workstation there's a event error:
No Domain Controller is available for domain XXXX due to the following:
There are currently no logon servers available to service the logon request.
Domain is windows 2003 while workstation is Windows XP Pro with SP2
However the workstation don't have any issue on any drive mapping and all 4 domain controller is up and reachable... Is there any testing I can run on the workstation since it's annoying.
Thanks.
No Domain Controller is available for domain XXXX due to the following:
There are currently no logon servers available to service the logon request.
Domain is windows 2003 while workstation is Windows XP Pro with SP2
However the workstation don't have any issue on any drive mapping and all 4 domain controller is up and reachable... Is there any testing I can run on the workstation since it's annoying.
Thanks.
Carol Chisholm
Does it have a fixed IP address ? Is the default gateway correct?
ASKER
Yes workstation got fixed ip address, got correct gateway.
Are the settings of the dns servers OK?
Can you ping the hostname of the domain controller?
You can try to flush the dns, run - cmd - ipconfig /flushdns and maybe also to register dns, ipconfig /registerdns
Can you ping the hostname of the domain controller?
You can try to flush the dns, run - cmd - ipconfig /flushdns and maybe also to register dns, ipconfig /registerdns
Hi:
Does the failing workstation show same hour than the workstations that are ok? If the difference is more than 5 minuts, you won´t be able to log on.
Does the failing workstation show same hour than the workstations that are ok? If the difference is more than 5 minuts, you won´t be able to log on.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
1. I can ping the hostname for all domain controller.
2. Run the ipconfig /flushdns couple time
3. The error only occurs every couple hours and beside that there's no other error, the workstation is running totally fine.
2. Run the ipconfig /flushdns couple time
3. The error only occurs every couple hours and beside that there's no other error, the workstation is running totally fine.
take out of domain and put back in
Ipconfig /registerdns
Today I had the same problem.
Tried solution from chaseturbo:
remove the workstations from the domain, they re-add them to the domain. Creates new cid on active directory
Problem solved !!!!!!!
THX TO CHASETURBO
Tried solution from chaseturbo:
remove the workstations from the domain, they re-add them to the domain. Creates new cid on active directory
Problem solved !!!!!!!
THX TO CHASETURBO
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.