James Weatherall asked "Why do people want to move the VNC port under 100"
Because many of us behind corporate firewall's and Proxy's are only allowed
to talk to the outside world on port 80.
Incidentally, I tried setting the VNC port to 80 (decimal - in the
registry) on a PC that was not behind the firewall, and was able to connect
with the VNC client from another PC (not behind the firewall) using the port
65616 (based on the formula from the following vnc posting:
http://www.uk.research.att.com/vnc/archives/2001-04/0194.html ). When I try
it with a browser from the same PC that worked with the VNC client, setting
the port to "http://ip_address_of_server:4294961476"; or
"http://ip_address_of_server:65616";, I get the "page can not be displayed"
message from Internet Explorer. If I specify port
"http://ip_address_of_server:80";, I get the following message on the browser
window:
RFB 003.003
Any ideas what is still wrong?
Regards,
Steve
_________________________________
Steve Gordon
Motorola - Engineering Computing
Global Telecom Solutions Sector
(817) 245-6811
[EMAIL PROTECTED]
-----Original Message-----
From: James ''Wez'' Weatherall [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 30, 2001 8:19 AM
To: [EMAIL PROTECTED]
Subject: Re: Changing port number on VNC Server for NT
> >I want to use a low number like 50 or something (I just pulled that out
of
> >the air without consulting my "standard port numbers" list). Since
that's
> >less than 5999, can I just use "50" as the registry value or should I use
> >(2^32)-5850 = 4,294,961,446?
>
> For everything under 100, you have to use the formula (otherwise it gets
> interpreted as a display number and VNC adds 5900 to it). For ports >=
100
> yoou should just be able to use the raw port number.
This is completely wrong. The PortNumber registry setting does exactly as
described - it sets the port on which the VNC protocol will be served by the
server. The viewer has problems with ports below 100 for the reasons you
describe, though, so you need to use the "formula" there.
Out of interest, why do people want to move the VNC port to something below
100?
> well. If I was *at all* interested in Win32 programming, I'd whip up a
> separate GUI which could set up the Registry entries and could control the
> WinVNC application and/or service. Maybe someone else would like to do
> that - I think VB should be "powerful" enough to handle this simple task.
It'd be easier to do this in something sensible, like Python. VB is
horrendously overblown for simple registry editting.
Cheers,
James "Wez" Weatherall
--
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
