NAT listening UVNC-SC on port 3389 + other NAT PC viewer

Laszlo · Post by **Laszlo** » 2005-10-21 12:54

Hi guys,
please help me I am already going crazy with this...
I have searched all the topics but have not find any solution...

There are to LANs and I need to provide help from a compuer on LAN1 to a computer on LAN2.
I am the admin of the server of LAN#1 (W2K ISA) but have no influence on LAN#2.
LAN#1 server has internet access and can run repeater.

LAN2 is pretty well defended, almost all in- and out-ports are closed but 3389 out
is open (for MS Remote Desktop I think). Practically no incoming connections allowed.

UVNC-SC connection "connect OUR_FIRM:3389 -noregistry" on LAN#2 +
"vncviewer.exe -listen 3389" on LAN#1 works great.

OUR_FIRM is a DDNS of the server on LAN#1 .

But this way I need to run the viewer on the server of LAN#1 but I want to use another
comp on LAN#1 for this purpose.

How should I set up the repeater on the server LAN#1 to pass the connection?
I tried 3389/5900/0 but this does not work. I think I shouls use the ID thing but
I have not found out how.

please, please

Laszlo from Hungary

bevtech · Post by **bevtech** » 2005-10-23 18:50

SCIII is in beta still

From Rudi:

loopback ports used
server
59000
99911
viewer
59001
99912

outgoing
443 or http proxy (8080)

repeater
loopback ports
5901 5500 (settings)
listen
443

The repeater need to have 443 direct connected to the internel (or Nat forwarded)
Server and viewer use 443 or proxy port (outgoing)

No checking for open ports --> terminate application
NO pem key repeater --> terminate repeater

-id XXXX -sslproxy -connect repeater_ip:443 -noregistry
ONLY THIS SYNTAX works

NO pem KEY (repeater) OR PORTS IN USE --> CRASH

will only work on port 443 and there is no changing that at the present time. You are probably running IIS on the Server which uses port 433

so you may want to look at SC or SCII

Look on the FAQ and look at SC

Hope this helps,

Post by **Rudi De Vos** » 2005-10-23 19:15

You could try some exprimental version
winvnc+rdp.zip
from
http://sc.uvnc.com/V2

It use the MS RDP viewer to access VNC, so it also use the RDP port.

http://www.microsoft.com/windowsxp/down ... entdl.mspx
RDP viewer <--(RDP protocol)--->winvnc

Status is alpha and just released as experiment

Laszlo · Post by **Laszlo** » 2005-10-26 14:47

Bevtech, Rudi, thanks for your quick reply,
actually, what I really want to do is to forward the reverse connection from a computer (HELP_ME)
on LAN#2 with UVNC-SC using port 3389 to my computer ("I_HELP_YOU" 192.168.0.19) on another LAN (LAN#1).
The connection between HELP_ME and the server (W2K SBS) works great this way:
I start a VNCViewer on the server on LAN#1 a "vncviewer.exe -listen 3389" and the user on
HELP_ME starts UVNC-SC ("connect OUR_FIRM:3389 -noregistry").
The server has an Internet connection (DDNS: OUR_FIRM) and it is a router for all the other PCs on that lan. Remote Desktop is not installed on the server so 3389 is free to use.

This works great. But I'd like to work on my PC on LAN#1.
How can I do this reverse connection thing access my PC ?!?

1. HELP_ME has to initiate the connection on port 3389 (until I find another open port...). Incoming ports a closed (at least I know of) and only a few outgoing ports are allowed (like 3389).
The most I can expect from the elder lady at that computer is starting an EXE file...
2. I can set up a repeater on the server of LAN#1 or do whatever I want to.
3. I'd like to use VNC viewer (listening mode or not) on my PC (192.168.0.19) on LAN#1 to see the desktop of HELP_ME.

I think using "ID" should help me achieving this but I have not figured out the settings...
I swear I have tried all possible settings (but the correct one it seems).

Rudi, I think what you suggest is good for reverse connection?
Bevtech, thank you for all the ports you listed but I can use only 3389 and it must initiate from a PC LAN#2...

thanks guys
Laszlo

bevtech · Post by **bevtech** » 2005-10-26 16:25

Do you have remote connection turn off on the pcs? and disabled in the windows registry??? You may be running into a port in use issue.

I would use SC I or II with a repeater in mode II

You have access to the to setup a repeater then you can use ID's. Do you have access to your Router off of the W2k SBS server or is it doing all of the routing for you?

If you can control port forwarding you can try this ( not sure if it will work)

You can have the SC goto port 3389 and at the router forward it to a different port like 5500..

Then the port 5500( router) can be forward to a repeater(LAN)

The Poblem my be that port 3389 may be used if you do any remote work to the server..