![]() Let me know what your experiences are, and if you have any different ideas.VNC® Viewer from RealVNC® gives you instant remote access to your Mac, Windows and Linux computers from anywhere in the world. They are very subjective, because bandwidth and CPU are always affecting the performance. Most of these observations are from running different clients side-by-side. However, I think with the latest VNC protocols, which already do compression, this doens’t make much of a difference. I’ve read that running VNC over a compressed SSH tunnel will help performance. Windows Remote Desktop/rdesktop (logs off server GUI, so unusable for remote pairing).It’s a great option if you are connecting to Linux) NoMachine NX (server only runs on Linux.Timbuktu Pro (no faster than VNC, and had refresh issues).Apple Remote Desktop (which is really just VNC too, and just as slow and unconfigurable).The built in VNC server in OSX (slow and unconfigurable).Your mileage may vary.Īlternatives I’ve tried and found to be inferior: They seem to be slow and crash a lot (both RealVNC and TightVNC). I’ve not been too impressed with the VNC linux servers or clients. There are several other mac clients such as VNCThing and VNCDimension, but they don’t work on my mac for some reason, and don’t seem to have any more features than Chicken of the VNC or RealVNC. ![]() Free RealVNC is OK, but it doesn’t do scaling.Chicken of the VNC is OK, but it doesn’t do scaling, and doesn’t allow you to specify ports via the double-colon syntax (only displays, which means you have to do math if you are ssh tunneling).RealVNC does not have this problem, so it’s probably a better client in this situation, even though it doesn’t allow configuration of all the above options like UltraVNC does (at least not from the GUI). UltraVNC client has a bug where it scales, but will still not show any more width than one of the client’s monitors, even though you make the window bigger. Windows Client for a server with a dual monitor and a client with a dual monitor: Zip/Tight Compression enabled, set to 9.256 colors (less colors don’t seem to help that much).If you are not using the UltraVNC video hook on your server, then UltraVNC is still a good client, with these settings: If you are using the UltraVNC windows server with the video driver hook, then you should use the UltraVNC client, with the “Ultra” encoding and 256 colors, with CopyRect and Cache encoding enabled. Windows Client for server with a single monitor: The “WinVNC Current User Properties” I use for the UltraVNC server are: ![]() If this happens, you can fall back to the Tight protocol on the client. This seems to be due to network or CPU issues, because it works great most of the time on most machines. However, sometimes you get screen redraw issues with the video driver hook. UltraVNC with the Video Driver Hook seems to work best it’s almost as fast as Windows Remote Desktop, but it requires that you use the UltraVNC client, which is only available for Windows. Turn on shared VNC connections if you want. OSXVNC (Vine Server) with default settings. I’m using the term “server” to mean the machine running the VNC server, and “client” to mean the machine running the VNC client. CPU also makes a big difference – performance on an iMac is a lot better than on a Mac mini, especially the 1.6Mhz mini. Remote pairing is pretty usable unless bandwidth is causing problems. If you are on a LAN, other options will be better (and you should just get on the same machine as your pair anyway!). This is specifically for working over a WAN. ![]() Here’s a quick writeup on what I’ve found to work best. I am a remote employee at Pivotal, so I do a lot of remote pairing, and I’m always trying new options. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |