Once the connection is made, additional streams are opened and my guess is they were timing out (HTTPS proxy idle). During the time they were connected, there were no problems to report, other than the aforementioned issue. The session then freaks out and the user is disconnected. Only to be reconnect again and the timer reset. Without getting into the underbelly and details of the protocol itself, this The gateway (and RDP for that matter) doesn't use just 1 protocol stream in Server 2012 R2. It can use a few depending on the version of the client being used. this contact form
I figure, 30 some seconds for the firewall to signal the connection is idle, 10 minutes of idle time for disconnect, 30 some seconds for RDP to signal network connectivity lost, and that Event ID: 42, Source: WinMgmt also follows. x 2 EventID.Net This problem may occur after you install Microsoft Internet Security and Acceleration (ISA) Server 2004 Service Pack 2 (SP2). See ME917803 for details.
Event InformationAccording to Microsoft :CauseThis event is logged when the event logging service encountered an error when attempting to apply one or more policy settings.ResolutionGroup Policy settings need to be changedGroup We could see the event id signaling the disconnects, but just reason codes were given. (which we never found out what they mean). So, if the user was in an active RDP session, why would the firewall treat it as idle? Well my best guess is this. J james gonzales / December 2, 2015 / Remote Desktop Services Leave a Reply Cancel reply Your email address will not be published / Required fields are marked *Comment Author Email
Comments: Anonymous This problem can occur on a DC if you are using System Center Operation Manager and you forgot to install ADhelper (oomads.msi) on that DC. The session duration always ranged in 700-706 range, for every user. English: Request a translation of the event description in plain English. Remote Desktop Services Session Has Been Disconnected Event Id 24 See example of private comment Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...
Event ID: 40 Source: WinMgmt Source: WinMgmt Type: Error Description:WMI ADAP was unable to create the object
All users were using different flavors of Windows, 7, 8,8.1 at varying patch levels. The only unifying characteristic was their LAN. Event Id 103 The Disconnect Reason Is 0 TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from Windows servers and workstation via the Splunk Universal Forwarder. read more... The secondary ports that RDP uses is discussed here http://blogs.msdn.com/b/rds/archive/2013/03/14/what-s-new-in-windows-server-2012-remote-desktop-gateway.aspx I hope this post helps someone along the way, I found a whole bunch of posts out there regarding disconnections. But most
A little bit about the RDP environment in question: All Server 2012 R2, all licensed (windows and RDS CALs, all updated fully, etc) 1 RD Gateway (properly installed certificates) 1 RD Login here! Event Id 40 Terminalservices-localsessionmanager We eventually made our way to their firewall to look at their rules. They had a HTTPS proxy rule setup, but it wasn't really doing anything. The HTTPS web blocker feature Windows 10 Event Id 40 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?
This was the error on the Session host, TerminalServices-LocalSessionManager event id 40 We could also see the corresponding disconnect messages on the RD Gateway. weblink Event Id40SourceMicrosoft-Windows-EventlogDescriptionThe event logging service encountered an error when attempting to apply one or more policy settings. The connection protocol was UDP and sometimes HTTP. TerminalServices-Gateway event id 303. x 3 Private comment: Subscribers only. Event Id 40 Session Has Been Disconnected, Reason Code 0