Home > Event Id > The Security System Could Not Establish A Secure Connection With The Server Ldap 40961

The Security System Could Not Establish A Secure Connection With The Server Ldap 40961

Contents

If the 40960/40961 events happen at a regular interval (i.e., hourly), try to determine what service may be need to authenticate at that interval. Proposed as answer by iamrafic Monday, August 22, 2011 1:58 AM Friday, August 19, 2011 5:39 AM Reply | Quote 0 Sign in to vote It appears that Kerberos authentication attempts In my place our security team ran a scan and found that this same Event Log is reported in several workstations as well. I believe this hotfix is in SP3, btw. have a peek at this web-site

JoinAFCOMfor the best data centerinsights. Microsoft Customer Support Microsoft Community Forums Windows Server TechCenter   Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 I disabled DNS registration on the WAN NIC and the error went away. Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended

The Security System Could Not Establish A Secure Connection With The Server Ldap 40961

When that was deleted from User accounts Password Management, the errors disappeared and Folder Redirection finally happened for this user. Microsoft article ME259922 describes a situation in which this event occurs. However, system event logs are still being polluted with this error. Connect with top rated Experts 12 Experts available now in Live!

Advertisement Related ArticlesJSI Tip 5612. Resolving Event ID 40961 LSASRV http://blogs.technet.com/b/jhoward/archive/2005/04/20/403946.aspx Resolution 2: Re-entering credentials for DNS dynamic updates registration in the DHCP snap-in may resolve this issue. Proposed as answer by MumthazMuhsin1 Tuesday, December 20, 2011 1:58 PM Friday, August 19, 2011 2:38 AM Reply | Quote Moderator 1 Sign in to vote My suggestion would be disabling Event Id 40961 Windows 2012 The reason we had to chase this down was because we had apps that were configured to use AD for kerberos authentitcation and those SSO would fail when a users has

I could try this, but what i dont like, is if it works I wont know what the the actual problem was -aW IMPORTANT: This email remains the property of the No Authentication Protocol Was Available Custom search for *****: Google - Bing - Microsoft - Yahoo Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? PST on Dec. 30th with the primary email address on your Experts Exchange account and tell us about yourself and your experience. x 77 EventID.Net See ME885887 for a hotfix applicable to Microsoft Windows XP Professional Service Pack 2.

When the Windows XP Firewall was disabled and the computer was removed and re-joined to the domain this event stopped. Event Id 40961 Vss Thanks! Apparently the workstation could no longer locate SVR records for the kerberos authentication server. This posting is provided "AS IS" with no warranties and confers no rights!

No Authentication Protocol Was Available

I don't remember the outcome of that - either an AV patch or re-install of the AV software. http://kb.eventtracker.com/evtpass/evtpages/EventId_40961_LSASRV_45904.asp What is the sulution for this error? 0 Comment Question by:andrewijnholds Facebook Twitter LinkedIn https://www.experts-exchange.com/questions/22850927/EventID-40961-LSASRV-No-authentication-protocol-was-available.htmlcopy LVL 26 Active 1 day ago Best Solution bysouseran With that additional information, I'd recommend the The Security System Could Not Establish A Secure Connection With The Server Ldap 40961 Looking back in my own knowledge base of stuff we've run across, we've seen this error a couple of times (on XP machines). Lsasrv 40961 Ldap JSI Tip 7089.

I did not find specific information concerning what gets screwed up in the profile or why it causes GPO failures. Check This Out Resolution 1: Nslookup works just fine. restart. This was consistent with what I was seeing. Lsasrv 40961 No Authentication Protocol Was Available

However, client PCs with Win XP (SP2 installed) show an LSASRV Event ID 40961 warning every hour, on the hour when the PCs are logged into the network. Verify the necessary SPNs are registered, based on the information in the event description. 12. This would probably also apply to any network card connected to the internet through any modem or router. Source Verify the DHCP client service is started on all machines.

The default settings were to "Register this connection's address in DNS". What Is Lsasrv No authentication protocol was available. Privacy Policy | Cookies | Ad Choice | Terms of Use | Mobile User Agreement A ZDNet site | Visit other CBS Interactive sites: Select SiteCBS CaresCBS FilmsCBS RadioCBS.comCBS InteractiveCBSNews.comCBSSports.comChowhoundClickerCNETCollege NetworkGameSpotLast.fmMaxPrepsMetacritic.comMoneywatchmySimonRadio.comSearch.comShopper.comShowtimeTech

meantime can anyone please guide/advice me to get rid of this warning message...??

Note: Card A IP: 10.10.10.0 series Card B IP: 192.168.10.0 series Regards, 0 Message Expert Comment by:DAQuintyne ID: 349451122011-02-21 would the simple removal from the domain Increasing the kerberos ticket size, as suggested by MS, didn't do the trick. Reset the secure channel. 10. Lsasrv 40960 Unchecking "Register this connection's address" solved the problem.

The customers internal address space turned out to be192.168.x.x. I was not using roaming profiles, so User As profile on PC01 was (potentially) different than it is on PC02. Rebooted the workstation and he was able to log in to the domain and access domain resources once again. http://homecomputermarket.com/event-id/active-directory-domain-services-was-unable-to-establish-a-connection-with-the-global-catalog-1126.html I noticed that the problem was occurring right after EventID 35 from source W32time.

No    >    authentication protocol was available."    >    >Interesting i can still log on using AD credentials. Towards the bottom of the dialogue box, you will see a button labeled "Credentials". End User was able to logon to the domain but the domain account would then get locked out right away. x 6 Peter Kaufman This error may result from securing Client-to-Domain Controller and Domain Controller-to-Domain Controller traffic with IPSec.

This resolved the issue for me. We use a Win 2000 Server in the office, with both Win > 2000 and Win XP clients. Take Survey Question has a verified solution. If you don't find any events related to LsaSrv then you can confirm that your issue is solved.

Danger Mouse Ars Legatus Legionis et Subscriptor Tribus: Los Angeles, CA Registered: Nov 14, 2000Posts: 33262 Posted: Mon Aug 30, 2010 2:40 am Bastard wrote:Have you set the "Wait for the Click once on the Advanced tab. 4. However, client PCs with > Win XP (SP2 installed) show an LSASRV Event ID 40961 warning every hour, > on the hour when the PCs are logged into the network. The information is intended to be for the use of the individual(s) or entity named above.

Concepts to understand: What is the LSA? x 7 Micheal What I discovered, for our situation, is that the credentials for DNS dynamic updates were invalid.