This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(48, 52%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJB%3C/text%3E%3C/svg%3E)
Hello,
Recently we're having an issue related to RDP/RDS, opening RDP connections take some time, and then display the following error your-remote-desktop-services-session-has-ended - 0x10b.
The reboot seems to fix the issue, but right after the reboot, the issue start to happen again.
-The issue happen on rdp connections (RDP connections + Opening Remote published applications on rds Farm)
-There is no persisting user sessions on the RDSH server when the issue is happening
-There is no Performance issue on the RDSH server
-Local Firewall is down
-I tried to disable the NLA connections but the issue is still persisting
-Restarting remote desktop service on the rdsh server when the issue is happening seems to be hung and cannot be restarted properly
-No interisting informations found on the logs
Anyone had a similar issue ? Any suggestions?
thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 31%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
Take a look in the Event Viewer, here:
Application and Services Logs -> Microsoft -> Windows -> Terminal Services-LocalSessionManager -> Operational
Also, take a look at all the other logs whose names start with "Terminal Services" and "Remote Desktop".
Report back here with the findings/event IDs/error codes...
Hello,
Thanks for the answer,
Nothing interesting on the localSessionManager (It gather only logs for the local sessions), and nothing interesting on the remoteSession logs either.
On the applicaiton logs, i can see multiple event id 4005 Winlogon failures (related to the rdp connections failures)
Another information, once i removed the RDSH server from the collection, RDP started working correctly again without rebooting the server
I added now a new server to the collection and see if the same behavior will be observerd
[...]once i removed the RDSH server from the collection, RDP started working correctly again[...]
That's interesting, because the difference here is that the Session Host has to contact the Session Broker to process a client connection when joined to a collection.
Check if there's a firewall between the Session Broker and the Session Host, and check the "Terminal Services*" and "Remote Desktop*" logs on the session broker too.
Hello Lucas,
I've Already checked the Firewall on both servers, they are disabled.
Indeed, it seems that for a reason, the broker cannot open RDS sessions on the RDSH server, weird thing is that it do it during the first session, but right after that it fails.
Another thing, i can see that there is no available license on my License server (all the user CALs are used), but the user that i'm testing with has already a license, so i don't think it is to related to a license issue.
I will check the logs on the broker and let you know
Rgds
Jihad
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello,
Try to connect directly to the session host when the issue occurs. If you encounter a winlogon error, it likely indicates that the problem is specific to that session host. Since restarting the winlogon service can cause a Blue Screen of Death (BSOD), I recommend updating the session host and monitoring it for any further issues.
If the Answer is helpful, please click "Accept Answer" and upvote it.
Hello Karlie,
Thanks for the feedback,
When the issue occurs, Direct RDP Access to the server is not working, it display the same error as RDS publications (0x10b error), and what do you mean by updating the session host? if you're talking about the Security patches, i installed this month cumulative update on the host and still have the issue.
Now i added a new session to the RDS farm and i'm monitoring the istuation, if you have any suggestions or helpful advices, i will take them
thanks
If you've recently installed a cumulative update and are facing issues with your Remote Desktop Services session, you might want to attempt a clean boot. This can help determine if any drivers or software are interfering with your ability to log in to the server.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 94%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBN%3C/text%3E%3C/svg%3E)
This discussion is beyond my ken, but I had the issue of disconnecting immediately after connecting on my home network. I found "Way 1. Disable WDDM graphics driver" at https://www.anyviewer.com/how-to/your-remote-desktop-services-session-has-ended-jkzbj.html solved my problem after hours of searching.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Hello Bob,
Thanks for the feedback,
For me, i ended up rebulding a new RDS server, the issue didn't reoccurs since then
