![]() There is no way (as far as we know) to connect to the console session and start your session where you left it ! When using xRDP software, it will always create a new session for the logged on user. It’s importan t to understand how xRDP works and how sessions are created with the software. We have quickly and simply demonstrated how to overcome this minor but annoying xRDP “issue”. We hope that this post will be useful to all these people that have encountered the xRDP black screen situation. However, there are other techniques (easier to implement that can be used) and we will share them with you soon…. In the next post, we will show you how to implement these techniques Final Notes This is basically the recommended approach to be used. So, you move to your Windows machine (or Linux machine), fire up your favorite remote desktop client and provide the ip address or the hostnameĪs mentioned in the title, this is the most command and most standard approach to fix this issue. Let’s also assume that you are still logged on into your Ubuntu machine system locally with your user account (which could be called User1). Let’s assume that you have performed a successful xRDP installation (manually or using our famous xrdp-installer-xx.sh script) and you are ready to test your rdp connection to your Ubuntu machine. Overview Reproducing the “Black Screen” Situation The “problem” is actually well known and there is really an simple and easy fix for that. This post will basically explain why this happens and how to reproduce the issue. When trying to connect via remote desktop protocol (rdp) to the Ubuntu machine, and after providing the credentials in the xRDP Login page, the user will only see a black screen displayed and the desktop interface is never loaded and displayed. Both devices are still up and running during the black screen as shown in the uptime.We have noticed that a lot of people hit the same issue over and over again. We rebooted the VPN and server regularly. ![]() We have ruled out resource issues due to the less than 50% utilization.Īnyone faced anything similar ? Any help would be appreciated.Įdit: Another thing to add, during non peak hours, there were no issues reported. The server in question is running Windows Server 2012 r2, with 150 license for RDP. I was still able to manually disconnect and reconnect to the VPN.Ĭheck the Firewall for alerts, but I couldn't find anything that can help me to identify the issue either. There were no alarms detected on the ISP end either. But bandwidth utilization is at less than 50% before it crashes to 0 during the black screen. We escalated the matter to ISP, thinking that its a network issue. Our VPN box which have almost 500 sessions, is also working at below 50% utilization for both memory and CPU. I've checked the memory / CPU utilization on the server, it is below 50% during peak. When the issue occurs, VPN remains connected. This persisted for 15-30 mins before users are able login back into their environment. If they attempt to reconnect, they will get a black screen. The server and VPN was upgraded in order to handle the increased load.ĭuring peak hours, all the users will get booted out of the server. So we are looking at alike 100-150 users connected via remote desktop to 1 physical server. But as time goes by, the number of people remoting in has increased significantly. This setup was working great in the initial years when there were only like 50 users. Recently, I've been encountering black screen issues when trying to remote to a server via vpn.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |