![]() ![]() The running desktop on PCLOS is retained.Īll of this can be tunneled through ssh for security, if accessed from the internet. When finished, simply use the putty connection to stop the x11vnc service, or, simply close the vnc window on windows. No need to mess with any other RDP or X for windows software. Then tightvnc client can be used to connect to it from a windows machine. The x11vnc can be running all the time on the PCLOS machine or it can be started manually with a ssh connection (putty) from windows. I recently started using it and it enables one to connect to the PCLOS machine running the x11vnc server with a vnc client such as tightvnc. The description in the repos mentions that it is sort of a bridge between the x11 of linux to the RDP in windows. I am thinking that X11vnc would help here. Normally, vncserver such as tightvnc-server would start a new xsession, hence the need to start the xsession at time of ssh connection. ![]() It seems to me that you would like to use vnc on the windows machine to access the PCLOS host with the vncserver running. I too am trying to wrap my head around this so I started at the top and started reading over. I am trying to use SSH from a win7 laptop using putty and I get the following message when I use "startx" after connecting Quote -need some help to get my head around this Interesting Xforwarding does not work until I enter "export $(dbus-launch)" (no quotes) into a terminal, dont understand why (yet) The actual VM is reasonably fast (after memory adjustment)įorwarding X using the VM is painful thats why I gave win7 another crack using Xmin and Putty its still slow but not quite as bad Is it slow on the VM window directly, or only when you forward X over the network? ![]()
0 Comments
Leave a Reply. |