PC not communication to DC

Getting these errors
 This computer was not able to set up a secure session with a domain controller in domain TAP 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, no gpupdate.

The PC is Windows 7 PRO connecting to domain server using Windows 2003 server.
No other issues with domain or other PC's. No other problems with PC connecting to other resources on and outside of domain.

I see no errors on the DC itself regarding this issue.

What would you do about this? Rejoin computer to the domain?
Who is Participating?
Mohammed KhawajaConnect With a Mentor Manager - Infrastructure:  Information TechnologyCommented:
Removing from domain and joining again will fix.  The issue is most likely the computer account is messed up.
Schnell SolutionsConnect With a Mentor Systems Infrastructure EngineerCommented:

Lets start with these basic TroubleShooting about connectivity

can you confirm that this client is configured with the correct primary DNS (The one used in your domain).

Second try in a command prompt to type "nslookup" and press enter. When it appears the nslookup connection, confirm that this is your internal DNS name and type your domain name and press enter. You are suppose to resolve the IP Address of one of your DCs

Third, if the previous steps work, try making ping to your DC

Given there are no other apparent issues, I would rejoin the domain and see how it goes. There may be some issue with this computer.

Do you have a duplicate mac address? I've see this once in over 20 years, was a horrible thing to trace. You rejoin this computer to the domain and that one computer stops functioning on the domain. Then you rejoin that one and this one stops working. After a few days and a few trips back and forth I finally saw the pattern and found the issue.

Let me know how it goes.

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

cebu1014Author Commented:
Yes the nslookup finds the right DNS server which is same as DC

The domain.local entry produces IP addresses of servers plus some beginning with 169 which are unknown...

However, it didnt if just simply typed domain without the .local

The PC name is listed under Computers in AD.

All other tests you mentioned work.
pgm554Connect With a Mentor Commented:
169 is an auto configure failsafe when a DHCP server can't be found.

I would unjoin to a workgroup,reboot and then rejoin domain.
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
Removing from domain and joining again will fix.  The issue is most likely the computer account is messed up.
cebu1014Author Commented:
I will give it a try. It has worked in past before me but wanted to get more info from experts before doing so.  Thanks
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.