Bug in 1.3.9?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug in 1.3.9?

Rohit Patil
When I specify a server:port it does not seem to be able to reach the
server. I also see the addition of a ':' in the server:port
specification when it tries to connect to the server. Is this a bug or
am I doing something wrong?

Thank you,
-Rohit.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

Re: Bug in 1.3.9?

Rohit Patil
Sorry, I forgot to mention that the same server:port spec. works in v1.2.9.

-Rohit.

On 10/4/07, Rohit Patil <[hidden email]> wrote:
> When I specify a server:port it does not seem to be able to reach the
> server. I also see the addition of a ':' in the server:port
> specification when it tries to connect to the server. Is this a bug or
> am I doing something wrong?
>
> Thank you,
> -Rohit.
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

Re: Bug in 1.3.9?

Constantin Kaplinsky
In reply to this post by Rohit Patil
Hello Rohit,

>>>>> Rohit Patil wrote:

> When I specify a server:port it does not seem to be able to reach the
> server. I also see the addition of a ':' in the server:port
> specification when it tries to connect to the server. Is this a bug
> or am I doing something wrong?

TightVNC 1.3.9 interprets display and port numbers exactly like VNC4.
The rules are the following:

  1. If the number after a colon is in the range 0..99, then it's
     interpreted as a "display number" -- an offset from the port 5900.

  2. If the number after a colon is not in that range, then it's
     assumed to be a port number.

  3. If there is a second colon, then the number is always treated as a
     port number.

  Examples:

     host:80      -> port is 5980
     host:443     -> port is 443
     host::80     -> port is 80

TightVNC 1.2.9 interpreted the syntax differently (more straightforward
-- one colon always meant display). Considering the example above, the
interpretation would look like this:

     host:80      -> port is 5980
     host:443     -> port is 6343
     host::80     -> port is 80

--
With Best Wishes,
Constantin

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list