Windows – rdesktop for windows

With the settings in the question is right without problem.

The Solution to Xming for Windows in the case is like this:

The running order of Xming and Putty

After installation of Xming for Windows, just run Xlaunch to config and then run xming. Config option: for

• multi windows
• start no client
• and then next and complete

Once it(Xming) is opened, It will stay in Windows taskbar. Then run Putty for the SSH account well configured for X11 Forward, this time, when xclock is run in the command, it will then forward to XWindows and open in your Windows desktop.

** the current Login identity for current session is also important **

If using SSH to connect Azure, the default user is not root. To elevate the privilege, using command sudo su is necessary. If running Xming with Putty and X11 Forwarding turned on. The forwarding is working for the first login. If issued the sudo su command. The link will be broken and GTK application such as xclock is no more working for the elevated account.

So make sure this is the first login user and to test the desktop installation, run xclock in the command line, if in Putty, error message will be displayed for it cannot be opened.

For CentOS 6.5, tigervnc-server is needed

However, when the VNC is connected, it is blank with nothing. Because the Vino Server is VNC server for Gnome. To properly install VNC server, tigervnc-server is necessary. For details please refer to CentOS HowTos -> VNC-Server

Tips:

The previous failure is mainly due to using Xlaunch to create a config to run for Putty which is a tutorial found in the web which is not working. The above running order make it working in my own case. I cannot say the not working method is wrong, maybe it is for other purpose that I didn't know yet.

After that, because Xming is working for xclock, so it is also working for vino-preference now. The VNC is then immediately working to connect the remote Linux on azure after check the Allow other users to view your desktop option and uncheck You must confirm each access.... But because in non-root-elevated, vino-preference is not being saved, it is not a proper way to setup the VNC, please refer to above link for details.

Have never tried this but you may be able to keep the RDP session in active state if you connect to it from the console session on the same server. You can also try to use one of the standard monitor drivers with fixed resolution for the console session if you don't have a physical monitor attached.