cotvnc on intel mac; no window after connect

  • Filip Defoort

    Filip Defoort - 2006-05-31


    I'm running cotvnc 2.0b4 and also compiled and tried on the CVS version; 2.0b2 on my PPC mac was able to connect without problems to a host; 2.0b4 on my Intel PowerbookPro seems to connect fine, except that the window never shows up at all. The application "seems" fine, but no window.

    When running under debug mode, the stdout gives the following clue:

    [Session started at 2006-05-30 18:09:30 -0700.]
    2006-05-30 18:09:40.573 Chicken of the VNC[29306] Server reports Version RFB 003.130

    Anybody any idea what could be going on ?

    Thanks in advance,

    - Filip

    • Nathan

      Nathan - 2006-06-02

      I also have the same problem. So I opened up tcpdump on the receiving side (server) and captured these packets.

      17:01:14.773750 IP > S 3325899346:3325899346(0) win 65535 <mss 1460,nop,wscale 0,nop,nop,timestamp 1073758221 0>
      17:01:14.773797 IP > R 0:0(0) ack 3325899347 win 0
      17:01:15.866177 IP > S 119504268:119504268(0) win 65535 <mss 1460,nop,wscale 0,nop,nop,timestamp 1073758223 0>
      17:01:15.866228 IP > R 0:0(0) ack 119504269 win 0

      local (client) is, remote (server) is

      Apparently there are packets being sent, but nothing happens. Also, I am able to telnet into the server with the following information.

      telnet 5801
      Connected to
      Escape character is '^]'.
      HTTP/1.1 400 Bad Request
      Server: RealVNC/4.0
      Connection: close
      Content-Type: text/html

      <TITLE>400 Bad Request</TITLE>
      Bad Request
      Connection closed by foreign host.

      Thanks in Advance for any help.

    • Nathan

      Nathan - 2006-06-02

      Heh, I didn't state it but from the looks of it, the port dosen't seem to have effect when I type out, "" it appears to try and connect to 5901. Although, I could be wrong about this.


Log in to post a comment.

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

Sign up for the SourceForge newsletter:

No, thanks