connecting via gateway

Guest · Post by **Guest** » 2005-02-12 14:06

Hi,

i am running Ultr@vnc on a dynamic IP (dyn dns) Server direct connected to Internet at port 443.
If the Client PC is also direct connected everything is fine.
Well done.

But i hope you can give me a hint for this problem:

my server is connected to internet as above, but the viewer ist behind a router, on which i don't have access.
Let's say router (192.168.0.1::3128, open ports are 80, 443, 21, etc.)
So in my opinion it should be possible to connect via router option and server port 443 !
But viewer won't connect. allways aboarting after "connecting..."

How to access my server from befind the router?

thanks for any suggestions

redge · Post by **redge** » 2005-02-12 14:11

try NAT2NAT feature (don't support firewall !)
http://www.uvnc.net/index.php?section=21

don't forget to active allow loopback on winvnc server admin properties
don't forget to connect on localhost on vncviewer

ipsec · Post by **ipsec** » 2005-02-13 06:58

How have you verified that your port is open on your router going to your server under port 443? Unless you specify this it will not work.

If you have specified this please use a port scan website to ensure that it says FAILED.. which means the port responds..

https://grc.com/x/ne.dll?bh0bkyd2

if you go there, specify user port use 443. Since this is the one you say is being used.

If this does not fail then your router is not forwarding the requests properly and no matter what you do on any viewer machine outside of that network you can not connect.

Nat2Nat is pretty cool too.. but.. havent gotten this to work with a friend... Technically you dont have a NAT on the other end so not sure if you need this to work.

Try ensuring the port is open on your router and if it isnt, log in and make certain it is.

Guest · Post by **Guest** » 2005-02-14 10:57

Thanks for answering,

i will try that out.
@Ipsec why does the viewer need an incoming open port?
i don't think so, because the viewer establishes the conntection through an open outgoing port. Im my mind there is no open incoming port necessary. For example if you browse a website with you normaly only need an open Port 80, no incoming port 80...
Why does the viewer needs an incoming open port?

Another thing i thought about is the java applett version.
But i can't find the right apllet to download. can you tell me where to download the best version for RC18?

best regards

ipsec · Post by **ipsec** » 2005-02-14 16:35

Anonymous wrote:@Ipsec why does the viewer need an incoming open port?

Another thing i thought about is the java applett version.
But i can't find the right apllet to download. can you tell me where to download the best version for RC18?

Where did i say that the VIEWER needs to have the port forwarding??

My first statement

I wrote: How have you verified that your port is open on your router going to your server under port 443? Unless you specify this it will not work.

is asking if you have verified the port being open on the "Server" not viewer and how you may have accomplished this confirmation..

Maybe this was the statement that confused you -

I wrote: If this does not fail then your router is not forwarding the requests properly and no matter what you do on any viewer machine outside of that network you can not connect.

What that means is... you cant do anything from any viewer to connect if the port isnt properly forwarded??

And BTW the java viewer should be either the Microsoft Virtual Machine or the Sun Java Viewer google it? (Of which I think works much better

)

Guest · Post by **Guest** » 2005-02-15 14:52

@IPSEC

Yes it confused me, because have a look at my posted picture.
My Server is doing fine and port 443 is open (1. by portscan, 2. because UltraVNC works over internet direct to direct.

The thing i want to know is, that only the viewer is behind a proxy... and there is, as you said no incoming open port.

But outgoning 443 is available because otherwise the https wouldn't do its work.

So if i use the viewer and writing in my server and proxy adress, it might do, but why doesn't it?

like: mydyndns.org::443
proxy: 192.168.0.1::3128

best regards

ipsec · Post by **ipsec** » 2005-02-15 19:10

I dont use, nor have I used the proxy repeater option.

Therefore the syntax for the port your proxy uses I am not sure if it is the same... but would make sense if it was the same. I am also wondering if your proxy requires authentication in order to go out to the internet? This may prove to be hard to get past if there isnt any prompt for credentials on the proxy.

But what your saying should work if you properly initiate an outgoing connection through your proxy.

If your computer on the net has 443 open and ready to accept clients then as long as you initiate a successfull outgoing connection from your computer behind the proxy through that proxy you would work.

But if the proxy is blocking the requests due to an authorization problem that will not allow you to connect at all..