PORT 80 Issue
Fri Oct 11 20:30:01 2002
First of all the viewer is perfectly capable of accepting ports. I do it
all the time, especially when ssh tunneling.
<server ip or address>:80 will connect on port 80.
I am a bit curious how how you managed to come up with 2 different numbers
for the ports though.
I have a webserver running on my test machine, but I set the display to
65617 (port 81) and then in my viewer I did "server:81" and it connected
From: Jae P. Lupo [mailto:email@example.com]
Sent: Friday, October 11, 2002 01:44 PM
Subject: PORT 80 Issue
I know this issue has been brought up many times in the past but, I am still
having problems with VNC working through Port 80. I don't understand why it
is not easer to set the port number in VNC. Why don't you guys just program
VNC to ask for a port number instead of a display number system that is
currently being used? I have to add numbers and subtract numbers. You have
a different number on the viewer then on the server. Someone should make
this easer! OK enough complaining! I am using the latest version of eSVNC.
I have the Display number on the server set to 59716 which translates to 80.
And on the Viewer 65616 which translates to 80 as well. I still can't
connect through my two firewalls. Can someone tell me if I am doing this
right! I feel it is VNC and not my firewalls. I have static numbers on
both sides and no NAT or proxy. I have used Remotely Anywhere with no
problems using port 80. I just can't get any form of VNC to work through
80. Thanks for the help.
Ansett Aircraft Spares & Services
12675 Encinitas Avenue
Sylmar, CA 91342
[demime 0.99d.1 removed an attachment of type application/ms-tnef which had
a name of winmail.dat]
VNC-List mailing list