#241 high port ranges not handled

v2.0
open
nobody
Networking (54)
2
2010-01-05
2010-01-05
No

In version 2.0b4, when a high port number is specified (such as foo.com::10203), cotvnc returns an error saying 'could not connect to display 0'. It seems that there is a port number range check somewhere that rejects valid, though unusual, port numbers.
Hacking the connection by specifying 'port_num - 5900' for the display (in my example, 4303) makes a valid connection.

Discussion

  • Paul Navratil

    Paul Navratil - 2010-01-05

    just discovered that a single colon works, so the issue is my use of the double colon. Other vncs support/require double-colon syntax for direct port calls, so I'll leave it to the community whether to support this.

     
  • Paul Navratil

    Paul Navratil - 2010-01-05
    • priority: 5 --> 2
     

Log in to post a comment.