Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1113
  • Last Modified:

5723 NETLOGON: Session could not be created

We are using SBS 2008 (primary DC) and Server 2008 (backup DC) with about 20 XP and W7 clients. Yesterday morning all clients encountered login problems (5805 NETLOGON: The session setup from the computer [DOMAINCOMPUTER] failed to authenticate. The following error occurred: Access denied).

We reintegrated all clients into the domain (put into workgroup, reboot, put into domain, reboot). Login with severals accounts o all clients was successful, but after about 30 minutes the problem reappeared for new logins with:
1.  5723 NETLOGON: Session could not be created ...             followed by
2.  5805 NETLOGON: The session setup ... (see above).

What can cause these problems? All clients are listed in the AD.

Many thanks
sg08234


0
sg08234
Asked:
sg08234
  • 3
  • 2
3 Solutions
 
Glen KnightCommented:
Access denied normally indicates a time issue.

Is the time different on the SBS server to what it is on the client machines?

It could also be a DNS issue.  Can you post IPCONFIG /ALL from the SBS server and one of the clients please?
0
 
sg08234Author Commented:
Thanks so far --> I'll check on monday. SBS time is correct. I assume client times to be correct too.

What ist the idea behing asking for IP-settings (those have not been changed and worked fine for 3 months)?

sg08234
0
 
Glen KnightCommented:
I just want to check it's setup properly.  Just because it's worked for 3 months doesn't mean they are correct.  I've seen sites that gave been working for years with the wrong IP configuration but then something happens and all of a sudden it stops working.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
K_WilkeCommented:
I wonder if the computer names in AD are all invalid for some bizarre reason.
I would try on one PC to remove from domain, go into AD sites and computers and delete the computer, then rejoin the domain and see what happens.
Also are these happening to all computers or just the XP ones?
I know that you will get this if XP has it's firewall on if you are trying to do this.
Thanks,
Kelly W.
0
 
sg08234Author Commented:
Would renaming of the clients (in addition to rejoining the domain) help (--> New entries in the AD)?

What if DC replication of "sites and computers" does not work properly? There are some Google hints that this also may cause the problems. How can I check correct replication (our domain admin is not available today)?

Thanks - sg08234
0
 
sg08234Author Commented:
Sorry for late feedback: After the weekend the problem did come up again. So I assume that DC replication of "sites and computers" did not work properly before and succeeded over weekend.

Many thanks for you assistance. I only spend 100 points as none of your answers really hit the point.

sg08234
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now