Our supported method for delivering Windows 7 desktops using TurboVNC is to use VirtualBox or VMWare. You run the virtualization application in VirtualGL and run VirtualGL in TurboVNC. Voila-- remote Windows desktop with 3D acceleration. The VirtualGL User's Guide has more info.
"Listen mode" is a feature of the VNC viewer that lets you make a "reverse connection" from a VNC server session. Once the server session is running on a Un*x/Linux machine, then you run vncconnect on that machine, and it establishes an outbound connection from the server to the viewer (as opposed to the inbound connection from viewer to server that would normally occur.) We do not provide a Windows VNC server (WinVNC) solution. There used to be one (it was inherited from TightVNC 1.3.x), but it was incredibly buggy and stopped working once Vista was released. In order to get a WinVNC solution working again, I would have to take the current TightVNC 2.x code and spend a considerable amount of time (perhaps hundreds of hours) optimizing it like I did with Xvnc. I deal mainly in the remote 3D application space, and WinVNC is of little use in that market, because it's a single-user solution. WinVNC is a screen scraper, so only one user at a time can use it to access a remote machine. You could make WinVNC a multi-user solution through virtualization, but if you have multiple users, it's much more efficient to run the VM inside of TurboVNC instead of running TurboVNC inside of the VM. Besides, WinVNC solutions generally do not work well with hardware-accelerated 3D, which is another reason why we prefer to run the VM inside of VirtualGL. This makes the VM think that it is running locally on the server's hardware-accelerated display, so it eliminates any possibility of interference in the guest O/S. From the guest O/S's point of view, it does not notice any difference between remote and local, because all of that is being handled at the host level. Furthermore, it is much easier to administer, since the TurboVNC server is running on the host and not in the guest, and the sessions can therefore be scripted, launched by a web portal, etc. There are several corporate sites out there now who are using this solution actively to serve up Windows desktops to their users. If you absolutely need a WinVNC solution, then use UltraVNC on the server and TurboVNC as the viewer. On 9/29/14 2:06 AM, Григорий Пташко wrote: > Hello. > > I've got an issue with delivering Windows 7 desktop via turbovnc. I have > a server with Windows behind a firewall. I use OS X as a client. Here's > what did: > > 1 on Windows I run turbovnc in listener mode. > 2 I forward 5500 port via ssh via our router. > 3 I run turbovnc on the client (OS X) and connect to localhost:5500 > > Then this happens: > > 1 the client does not say any errors about a connection. I see the > window title Turbovnc viewer. But the remote desktop does not open. > 2 on the Windows box I see a little window that says Accepting reverse > connection... > > And that's all. So the questions are: > > 1 is it actually possible to run turbovnc inside a Windows box as a server? > 2 if yes then what am I doing wrong? ------------------------------------------------------------------------------ Slashdot TV. Videos for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk _______________________________________________ TurboVNC-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/turbovnc-users
