Hi all The point is that at one time ntlm_auth stop to work on the primary server. When I test it from the command line it says "No logon server" I noticed in the logs that there were 10 attempts per minute with wrong password from one of our routers. When I applied ACL on the router to block this attempts, ntlm_auth started to work During this time standby radius was able to communicate with AD So the question is if there are some restrictions in freeradius when it will stop to communicate with AD in some special cases ? It happened few times with the same scenario Thanks pet
So the question is if there are some restrictions in freeradius when it will stop to communicate with AD in some special cases ?
No. This is not a FreeRADIUS issue, this is a Samba issue. NTLM Auth is not part of FreeRADIUS, FreeRADIUS merely calls the ntlm_auth executable to proxy MSCHAPv2 data to an Active Directory server. Or to perform simple authentication with a username and plaintext password. Get ntlm_auth working reliably, then try and use it with FreeRADIUS. -Arran Arran Cudbard-Bell a.cudbardb@freeradius.org RADIUS - Half the complexity of Diameter
participants (2)
-
Arran Cudbard-Bell -
Jevos, Peter