When using RDP to connect to my Azure Windows Server 2016 VM, I am able to connect and the blue loading screen appears briefly then turn black and the connection is broken. I have worked through all the troubleshoot suggestions of:
After each troubleshooting step, try reconnecting to the VM:
1) Reset Remote Desktop configuration.
2) Check Network Security Group rules / Cloud Services endpoints.
3) Review VM console logs.
4) Reset the NIC for the VM.
5) Check the VM Resource Health.
6) Reset your VM password.
7) Restart your VM.
8) Redeploy your VM.
But nothing has worked.
Any suggestions greatly appreciated.
According to your description. Many possible reasons may cause this black screen. Firstly You can try to upsize the VM via the Azure portal.
Also, I suggest checking the RDP client side.
Use control+alt+end, then sign out to close the RDP session and launch another one.
try to connect through Remote Desktop Manager which can resolve the same issue for someone.
Known issue: A black screen may appear while logon by using remote desktop
From Virtual Machine settings on the portal, find Diagnose and solve problems, follow the steps of SOLUTIONS TO COMMON PROBLEMS.
More references about Black Screen after RDP
Related
Trying to install a standard gateway on a Remote Desktop. The gateway works for about 24 hours and then fails. Once I login to the "On Premise Gateway" app, and restart the gateway it works again for another 24 hours.
The error message the incremental refresh shows is either "DM_GWPipeline_Gateway_SpooledOperationMissing" or "DM_GWPipeline_Gateway_TimeoutError"
Any help would be greatly appreciated!!
Thank you!
I have tried restarting the gateway and running the check network check to make sure reaching the ports is successful.
After a failure log onto the Remote Desktop machine and open Task Manager from the start menu. Go to the Performance tab and then the CPU tab. Note the Uptime metric. If that uptime is just a few minutes then this machine is not “always on”. This is typical for many virtual desktop machines which pause after a period of not being logged into.
As stated in the documentation:
Don't install a gateway on a computer, like a laptop, that might be turned off, asleep, or disconnected from the internet. The gateway can't run under any of those circumstances.
I am running a Windows Server VM on GCP.
When logging in via Remote Desktop, I am starting certain applications which should actively run for a couple of hours.
But when closing my Remote Desktop Connection, all applications stop working.
How can I prevent this from happening?
In order to keep the session ongoing, you'll have to configure the RD Session Host time limits.
Open the group policy editor with: Windows+R, then type gpedit.msc, confirm with Enter.
Then in the management console, navigate to:
Computer Configuration
Administrative Templates
Windows Components
Remote Desktop Services
Remote Desktop Session Host
Session Time Limits
There one can adjust the settings:
Set time limit for disconnected sessions
Terminate session when time limits are reached
Using vSphere Update Manager I've installed some updates and patches onto my host, however I have an issue with it picking up a datastore now so I want to roll back these changes to see if that fixes the issue.
From my research I understand that you can't uninstall these patches and you have to revert back to a previous ESXi version. I'm attempting to do this following the steps here: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1033604
However it does not give reference on how to access the Console for the Host. I can't find a way to access it in vSphere, but found a way by downloading putty and running the DCUI command.
The problem I have is that it says Reboot and then:
When the Hypervisor progress bar starts loading, press Shift+R.
However when I reboot putty loses connection to the host (presumably because it is rebooting) so I never get to see the boot up screen and Hypervisor progress bar to press Shift+R.
Am I missing something simple here? Server is Dell running ESXi 5.5. Thank you.
Dell ilo interface shall provide you the recover(Shift+R) while rebooting and hence rollback option.
The default credentials for dell ilo would be,
username : root
pwd : calvin
The steps to achieve this would be as follow,
Get ur ILO link, please see if below link is useful to you in this regard.
https://www.dell.com/community/Systems-Management/How-to-get-the-DRAC-IP-address-from-the-localhost/td-p/2374426
otherway would be ping your server FQDN and it would return the ILO IP.
Once you find ilo url or IP, login to it using above mentioned default login credentials(root/calvin).
Now, in ILO interface find the option to launch the console (server -> Virtual console preview -> Launch).
Save the JNLP file and run it.
Further, Press F12 for "Shout down /restart"
Here onward I believe you will get it.
Thanks,
Manjunath.
Before I'd traveled for 3 weeks, my connection to EC2 windows - ec2-54-186-219-106.us-west-2.compute.amazonaws.com - was perfect. In this period, I was away, on vacation, and didn't connect to it. Now, I try to connect via RDP from my MacBook and see the message:"Remote Desktop can't connect to the remote computer for one of these reasons: 1) Remote access to the server is not enabled 2) The remote computer is turned off 3) The remote computer is not available on the network". I've checked some forums and got some advice like: reboot my instance, change my security group, add port 80 to my security group, but nothing works. Any idea?
This is how I solve my problem: I've attached an IP to my instance, and it starts working again. I hope it helps someone who is facing a similar situation. That's all folks!
I've used the following guide in order to connect to a Debian 8 Server with GUI using a DigitalOcean server:
https://www.digitalocean.com/community/tutorials/how-to-set-up-vnc-server-on-debian-8
I know this works, however under Azure and now Google's Cloud Compute I am unable to connect. I think there should be some setting on Google's side that is blocking outside connections through VNC to the Debian 8 instance.
I only have the free support level, and I don't want to upgrade just to resolve this issue alone. Here is a screenshot from my console that perhaps has some relevant information:
Console Screenshot
I'd appreciate any input anybody could give me. I've tried trouble shooting this before under Azure, but after getting it to work on DigitalOcean, I know the problem isn't from my end.
The resolution was simple. I just had to allow the port tcp:5901 through Google's firewall in order to connect to my VNC server.