Mark Minasi's Tech Forum
Register Calendar Latest Topics Chat
 
 
 


Reply
  Author   Comment  
nikolas.e

Senior Member
Registered:
Posts: 131
Reply with quote  #1 

Lately i am getting this error : EVENT ID 5719 on one Member Server only in our network

This computer was not able to set up a secure session with a domain controller in domain DOMAIN due to the following:
There are currently no logon servers available to service the logon request.


i can verify i can access our domain controller in our network using start, run \\dc
i I have restarted the member server already and authenticated with out issue (though i still get this error) twice per day at least
i run nltest /sc_verify[biggrin]omain and results are successful
i run the ping command also nslookup for the dc and the domain and results also successful.

i googled the internet and some people are mentioning about  either switch issue or nic issue also. Wondering if anyone had similar issue and how did you fix it. 


Thanks





 


__________________
Just call me the 1000Questionsguy
0
donoli

Senior Member
Registered:
Posts: 505
Reply with quote  #2 
http://www.eventid.net/display-eventid-5719-source-NETLOGON-eventno-104-phase-1.htm

There is a list of comments ^^
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 152
Reply with quote  #3 
Before you do this : be sure to have a local admin account+PW
  1. Unjoin domain ('join' workgroup)
  2. Reboot
  3. logon with local admin account
  4. Join domain again
I have no idea why nltest /sc_verify is successful





__________________
Pieter Demeulemeester
0
nikolas.e

Senior Member
Registered:
Posts: 131
Reply with quote  #4 
Quote:
Originally Posted by Pieter
Before you do this : be sure to have a local admin account+PW
  1. Unjoin domain ('join' workgroup)
  2. Reboot
  3. logon with local admin account
  4. Join domain again
I have no idea why nltest /sc_verify is successful


Removing and Joining again the Member Server on the domain will not affect the shared folders currently this member server is holding? 





__________________
Just call me the 1000Questionsguy
0
wkasdo

Avatar / Picture

Administrator
Registered:
Posts: 188
Reply with quote  #5 
Try this. Log on to the member server using a domain account, then browse to SYSVOL. If this works without authentication prompts, the computer account is OK and you are looking at networking problems of some kind.
__________________
[MSFT]; Blog: https://blogs.technet.microsoft.com/389thoughts/
0
nikolas.e

Senior Member
Registered:
Posts: 131
Reply with quote  #6 
Thank you for your replies. Willem  I can verify that i can access sysvol folder for both domain controllers with a domain administrator account with out issue (Tested it again today). Pieter i have a Local Administrator account setup already in case i will have to rejoin the member server to the domain.




__________________
Just call me the 1000Questionsguy
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 152
Reply with quote  #7 
Given the fact that you can access the sysvol (see Willems suggestion), there is no need to unjoin en rejoin.

BTW: no need to do Willems test with a domain admin. Any 'normal' account must have acces to the SYSVOL share. Otherwise they can't run there logonscripts.

__________________
Pieter Demeulemeester
0
nikolas.e

Senior Member
Registered:
Posts: 131
Reply with quote  #8 
Today i run some more tests. From the member server i have the issue to the domain controller currently the server is logged on. Note: I was able to see which dc by running command : echo %LOGONSERVER%

i was using the ping command to ping the dc using the hostname only and i was getting reply successful (Ping servername). But when i was pinging the dc using the fqdn (Ping servername.domain.local) the msg i was getting was "Could not find host". I can verify that server is pointing to the correct dns servers in our enviroment.

Note: After a while member server was able to get reply from the dc using fqdn so my guess is something in between is causing this. If i am allowed next weekend switching ports on switch and changing cables.


Thank you all for your replies. I will let you know if anything new.

__________________
Just call me the 1000Questionsguy
0
nikolas.e

Senior Member
Registered:
Posts: 131
Reply with quote  #9 
Okay i did something simple. Rebooted the backup domain controller after some lot of days [smile] and event id is not showing up anymore on our nas server(Note:I checked all other servers also just to make sure). It has been 3-4 days hopefully it will stay like that.

I believe that one of the 2 nics that backup domain controller has with static ip was causing the issue. Sometimes when i was pinging both of them one would not reply back but later on it will. Drivers Issue? Bug Issue? cant really tell i will be monitoring and see.

Thanks all


__________________
Just call me the 1000Questionsguy
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.