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.
Related
Noob here with AWS workspaces. Brand new AWS account, went through full tutorial to set up a Windows workspace as per this video (twice). Both times, I can sign in but trying to connect to the Workspace is unsuccessful via the AWS client or their web client. When trying to use their web client I get "Connecting..." for about 10 minutes, and then an error (see image below). Note that I can connect just fine using RDP to the Workspace windows desktop, using Remmina (I'm on ubuntu) so I know these hosts are spun up and working just fine. But the AWS clients aren't working. I've tried all troubleshooting steps provided by AWS including verifying that the right processes are running on the host with Powershell as Administrator.
Anybody else running into this? It seems pretty weak of Amazon to release this offering that doesn't work "out of the box" with pretty much default choices for everything including their own Windows image.
I'm trying to run my application on GCE VM. It uses nodeJs as frontend and a Java backend. I use this server to communicate with my local computer using MQTT. This is working but after some time (one hour and a half), the server seems to go to sleep (or the ports close ?).
Both MQTT and ssh terminal interface connections are lost.
When I connect back, the application is not running anymore, it seems like the VM restarted.
Do you have any idea on how to keep my server alive ? I can give further details.
Answering my own question as John Hanley explained the solution in comments:
"By what method are you running your frontend and backend code. VMs do not go to sleep. If you are starting your software via an SSH session, that will be an issue. Your code needs to run as a service. Edit your question with more details."
I was indeed running my application via the ssh terminal which caused the problem. The solution for me was to remotely access the VM via vncserver and to launch the application using the VM's terminal.
I have been trying to setup Docker in Windows Server 2016 in an AWS instance to run an IIS program.
From this question,
Cannot access an IIS container from browser - Docker, IIS has been setup inside a container and it is accessible from the host without port mapping.
However, if I want to allow other users from the Internet/Intranet to access the website, after Google-ing it, I guess we do need port mapping...
The error I have encountered in port mapping is given in the above question so... I guess using nat is not the correct option. Therefore, my team and I tried to create another network (custom/bridge) following instructions from
https://docs.docker.com/v17.09/engine/userguide/networking/#user-defined-networks
However, we cannot create a network as follows:
; Googled answer:
https://github.com/docker/for-win/issues/1960
My team guessed maybe its because AWS blocked that option, if anyone can confirm me, please do.
Another thing that I notice is: when we create an ECS instance in AWS,
So... only default = NAT network mode is accepted in Windows server?
Our objective: put the container hosted IIS application to Internet/Intranet in Windows Server 2016...
If anyone has any suggestion/advice, please tell me, many thanks.
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
I am newbie to VMware. When I am longing into the VCenter I am getting "Connection time out" in first 3 attempts, after 3 attempts I am able to Login to VCenter.
I did some troubleshoot and in vcenter changed the Client to server time extended to 300sec. But still I am facing same issue. Can anyone please help me how to resolve this issue.
Thanks in advance
Are you connecting by IP or hostname? Make sure DNS is OK. Are you using a standalone MSSQL server? Windows server built-in MSSQL? Is this VCSA (linux appliance)?
If Windows, did you reboot everything? Slowness within vCenter can indicate a sql issue of sorts. Check all applicable items for available resources, including disk space on all partitions.