Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: viewtopic.php?t=37885 Important: Please update to latest version before to create a reply, a topic or an issue: viewtopic.php?t=37864
I'm trying to get up and running with the linux repeater. I've tried running the repeater on a local (LAN) server box and a remote one and I get the same result. Whe I telnet to the repeater on ports 5900 and 500 I get this:
[root@bacon Linux]# ./ultravnc_repeater.pl
Fri Feb 17 16:39:35 2012: ultravnc_repeater: starting up. pid: 19006
Fri Feb 17 16:39:35 2012: watching for IPv4 connections on 5900/client.
Fri Feb 17 16:39:35 2012: watching for IPv4 connections on 5500/server.
Fri Feb 17 16:40:20 2012: new vnc client connecting.
Fri Feb 17 16:40:20 2012: ultravnc_repeater: read error: Connection reset by peer
Fri Feb 17 16:40:31 2012: new vnc client connecting.
Fri Feb 17 16:40:31 2012: storing new vnc client with ID:691244.
I'm trying to connect using an XP machine and an XP virtual machine. This works OK when I run the repeater and viewer on my XP machine viewng the server on the virtual machine.
Both Linux boxes have https enabled on port 443
I get the vnc viewer popup but I'm not prompted for a password.
Please tell us which Linux repeater you have installed. I've had good success with http://koti.mbnet.fi/jtko/uvncrepeater/
There are alternatives that (I understand) also work well but I haven't switched since it works for me.
Port 443 is the default for InstantSupport (VNC server) to connect to the repeater.
Port 5901 will have to be open as well if ChunkViewer (VNC viewer) needs to connect from an outside network.
It looks like you are using the Perl repeater without sending it the proper command line to use ChunkVNC's default ports.
ultravnc_repeater.pl:
perl script implementing the ultravnc repeater
proxy protocol.
protocol: Listen on one port for vnc clients (default 5900.)
Listen on one port for vnc servers (default 5500.)
Read 250 bytes from connecting vnc client or server.
Accept ID:<string> from clients and servers, connect them
together once both are present.
The string "RFB 000.000\n" is sent to the client (the client
must understand this means send ID:... or host:port.)
Also accept <host>:<port> from clients and make the
connection to the vnc server immediately.
Note there is no authentication or security WRT ID names or
identities; it is up to the client and server to completely
manage that aspect and whether to encrypt the subsequent VNC
session, etc.