Hello all:
I am setting up secure VNC access to three remote computers behind a firewall using SSH. For example the private IPs of the three machines are:
192.168.111.101
192.168.111.102
192.168.111.103
I have setup the following NAT through the firewall:
<PUBLIC-IP>:22:192.168.111.101
so essentially calls to the public IP on port 22 are forwarded to the first machine, which also has cygwin OpenSSH server listening. I then use an SSH client to connect to that machine, no problems and works as expected. I then setup the following SSH tunnels in the SSH client:
15901:192.168.111.101:5900
15902:192.168.111.102:5900
15903:192.168.111.103:5900
Connecting UltraVNC Viewer to localhost:15902 and localhost localhost:15903 work exactly as expected and I can access these two via the SSH tunnels. The problem however is attempting to connect to localhost:15901 which does not work at all. The first error was "Loopback connections are disabled", so I enabled loopback connections in the configuration. Now the error is "Connection Failed, Error reading Protocol Version". All three are setup exactly the same way and testing among the three on the local network works fine. I am guessing there is a problem with the loopback because this is the system with the SSH NAT forward. Interestingly if I setup the following tunnels for Microsoft Remote Desktop:
13901:192.168.111.101:3389
13902:192.168.111.102:3389
13903:192.168.111.103:3389
then all three remote desktop sessions work perfectly, but I really wish to use VNC. Am I missing something? NAT forward of port 5900 is not possible unfortunately.
This is being setup for our engineering staff so I am trying to keep things very simple, and I have done this many times for both windows and linux hosts using realvnc with no issues, but UltraVNC has the built in file transfer which I want the eng staff to use without having to launch a separate SCP client.
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Putty SSH Port Forwarding
Re: Putty SSH Port Forwarding
try usingclahti wrote:15901:192.168.111.101:5900
Code: Select all
15901:127.0.0.1:5900
let us know how you go ...
ask a silly question and remain a fool for 5 minutes...
don't ask, and remain a fool for life - JDaus 2003
without imperfections, neither you nor i would exist - Steven Hawkins
__
JD
SCPrompt - OpenSource Free Remote Screen\Desktop Sharing Solution
SecureTech.com.au
don't ask, and remain a fool for life - JDaus 2003
without imperfections, neither you nor i would exist - Steven Hawkins
__
JD
SCPrompt - OpenSource Free Remote Screen\Desktop Sharing Solution
SecureTech.com.au
Re: Putty SSH Port Forwarding
Thanks for the response, unfortunately I have the same problem. I recall that version 1.0.2 did not have this problem.JDaus wrote:try usingclahti wrote:15901:192.168.111.101:5900instead of the local IP ... as sometimes systems don't like using the real IP for loopback (have come accross this for several other systems ... never tried to setup UVNC to use anything other then loopback when doing a loopback ...Code: Select all
15901:127.0.0.1:5900
let us know how you go ...