#246 COTVNC fails to connect to ElasticHosts

open
nobody
Networking (54)
5
2011-06-23
2011-06-23
Anonymous
No

elastichosts.com is a cloud services provider - we provide a VNC connection to our cloud servers. We recommend use of TightVNC or Vinagre, which just plain works on the windows and linux frionts, and yet we can't find any mac software that will connect to our VNC server, other than realVNC enterprise (which is pricey).

Is COTVNC non standard and only works for its own server? Is there some bug? We'd be happy to work with the COTVNC developers to try to work out why this is the case, so we'd have software for our mac users that we could recommend.

Discussion

  • dustinac

    dustinac - 2011-06-26

    Chicken of the VNC uses the standard VNC protocol and is supposed to work with any compliant VNC server. Indeed, it is only a client and has no preferred server. However, the development of CotVNC has been abandoned for many years with many bugs still outstanding.

    I recommend that you recommend that your clients use Chicken http://chicken.sourceforge.net which is a currently maintained fork of CotVNC. Chicken fixes many of the bugs in CotVNC and add some improvements as well. If you find any incompatibilities with Chicken, please open an item in the bug tracker and I'd be glad to try to fix them.

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2011-06-28

    Unfortunately, we keep getting reports that this doesn't work. Since our VNC connection is generated by the virtualization system (Qemu/Kvm) it should be fairly standard.

    We also have no macs, so can't actually test Chicken ourselves. It's easy to test for anyone that does - we offer free accounts.

    The CEO commented "Yes, there are problems with some VNC software - KVM uses a recent version of the protocol which isn't universally supported." If anyone out there in chicken land can tell us how to make Chicken connect correctly, we'd love to know.

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2011-06-28

    Oh, I misread the message... I'll look into the fork version. Thanks.

     
  • dustinac

    dustinac - 2011-06-28

    For the record, this morning I set up a trial account with a Debian 6.0.1 image. I was able to connect using both Chicken of the VNC 2.0b4 and Chicken 2.1.1 just by entering the IP address and the password. CotVNC was unbearably slow, but Chicken was very responsive (albeit on a small two-color screen). With Apple's Screen Sharing.app, I couldn't connect and only got an uninformative error message.

    As I said above, I think your users will be happy with Chicken. It is the only free, currently maintained VNC client on the Mac with good support for non-Apple servers. If your users find any incompatibilities with it, please file a bug report report:

    https://sourceforge.net/tracker/?group_id=364722&atid=1521165

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks