Not doing double NAT. Public IP to my NAT router where the port forwards are.redge wrote:known issue - there not possible to double nat with javaviewer, unsupported for now. or bug ?
Router will not allow me to forward 2 incoming ports (12345 & 5800) to same internal port. My intention was to access home PC via http://dyndnsname.org:12345 instead of port 5800 for security reasons. Wrong of me?redge wrote:so you need to change to: incoming port 5800 = private, internal IP:5800 othewise fail.
I do not know what you mean by "using the standard VNC viewer from the remote machine." See below for what I know and what I am trying to do.B wrote:My guess is mudshark would have the SAME issue when using the standard VNC viewer from the remote machine. Could you confirm, mudshark?
I was under the impression that I NEEDED ports opened as such:B wrote:I think your "12345" port redirection should be fine, although there's no reason you couldn't simply tell your home PC to deliver the Javaviewer on 12345 instead of 5800; that way there would be no port redirection involved -- you'd go 12345>12345 at the router.
I do not understand.redge wrote:mudshark, wish version support java port forwarding success?
Here you show ports forwarding twice. Again, I do not understand. There are OUTSIDE (public, incoming) ports and private ports inside the LAN that go directly to a PC with a static IP address. That is a single forward only for each port that needs to be forwarded.redge wrote:incoming 12345 --> 5800 --> 5900
outgoing 5900 ---> 5800 --> 1245
I complete do not understand. It is here much more complex than it should be. Sorry to be so thick.redge wrote:i know only old version have the single port sharing override this limitation. so you only need to forward 1 port and not 2 ports.
anyway, there a rule of VNC port jump +10 or -10
5800 to 5899
5900 to 5999
forward 5840 external to 5800 internal
forward 5940 external to 5900 internal
So you are saying I can use the viewer app across the internet the same way as I would use a browser? Enter the URL:port and voilÃ ? I suppose then I can also use DSM encryption...B wrote:I was just saying you should test with UltraVNC Viewer (the program) instead of using the browser (Java) viewer.
I don't understand doing both.B wrote:You can do both, using the USB stick ordinarily but leaving the web version available on an obscure port with a good password.
Sheesh! I can worry about encryption once I get the viewer working unencrypted!!B wrote:b. You can always download a fresh copy of the standard VNC viewer, though it might be a little tricky if the encryption you've chosen is not public key. (Even then, you could leave yourself a key file downloadable from a password protected web or ftp site or e-mail account.) There are about a zillion other ways to slice it too (VPNs and other tunnels, proxies, repeaters, etc.)
I do not know what each port is for.B wrote:Re: "Problem #1", you don't need to keep using 5800 and 5900 on the WinVNC server itself -- just change the listening ports in the WinVNC server properties to match the ones you want your router to forward!
Correct (sorry, I mistyped). When trying to access the server with the viewer am entering NOT a 'real' URL, am entering myname.dyndns.org::12345 which never works. (From browsers add the http:// at the beginning and use only 1 : and it does work.)B wrote:Re: "Problem #2", are you really entering "http://" each time? Just enter the hostname::port.
Ah. No, I was using the same port in the viewer as I was in the web client. Excellent. Thank you! And thank others here also.B wrote:When you connect with the remote VNC viewer, you'd use myname.dyndns.org::15900 -- NOT the same port number you'd use for the web client! Again, the web client's port number is ONLY for delivering the Java applet.
Users browsing this forum: No registered users and 1 guest