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

Firewall Help, can not connect with 5900

Post Reply
Guest

Firewall Help, can not connect with 5900

Post by Guest »

Hi,

UltraVNC is an excellent application and just what we need here, but I am having some issues when trying to connect externally to our server.

I have tried the FAQ and done a pretty extensive search on previous topics...

I can connect internally on both web and client using the servers name only ie "enterprise".

From externally, I can connect using my Browser (Mozilla) using IP address:5800.

My problem is that I can not connect using the client app and get the error: "Failed to connect to server!"

I am entering: xxx.xxx.xxx.xxx::5900

The Ultra servers Incoming connections are set to:

Display Number of Ports to use: AUTO, (although I have tried selecting the Ports option)

I have set up port forwarding on both 5800 & 5900 on our Fortigate 60 firewall, using the same settings for both (apart from the port numbers)

Where am I going wrong?

thank you,


regards,


Heds
madcowz
Posts: 3
Joined: 2005-05-24 11:17

Post by madcowz »

Forgot to say,

Both ports show as open when scanned.

Windows XP Firewall is off (client machine)

Also, I had no problems using RealVNC before switching to UltraVNC.

Still confused.

thanks,


/Heds
Last edited by madcowz on 2005-05-24 12:13, edited 1 time in total.
madcowz
Posts: 3
Joined: 2005-05-24 11:17

RESOLVED

Post by madcowz »

Er,

I have fixed it...

er um, er I was <shuffle> using the wrong IP, <hoping ground will open up>.

It works fine.

I will get my coat and never come back.

Fool.


/Heds
Cobra
20
20
Posts: 36
Joined: 2005-05-19 18:44

Post by Cobra »

Hi madcowz,

LOL, I'm glad that such things not just happen to me. :-D You're installing and setting up everything correct and then do a newbie error - I guess this happens to every network administrator once in his lifetime. :D
madcowz wrote:Both ports show as open when scanned.


Ever thought about using a VPN tunnel to connect to your computers from the outside? Then your ports 5800 & 5900 wouldn't show up a open/closed. Just an idea... :wink:

Best regards,

Cobra
PEN

Post by PEN »

can you please explain for point to what this tunnel thing means?

thanks

PEN
Cobra
20
20
Posts: 36
Joined: 2005-05-19 18:44

Post by Cobra »

Hi PEN,
PEN wrote:can you please explain for point to what this tunnel thing means?

thanks

PEN
This might help you for starting:

http://en.wikipedia.org/wiki/VPN

It has some nice external links on that page, which will explain you the basics. :wink:

Best regards,

Cobra
Guest

Post by Guest »

Great thanks for that - I'm currently trying to set up a server and VPN so that a couple of people can stay at home and access information at the office..... I'm sure iot's just me but it seems to be such hard work!!

Cheers

PEN
sbest

Post by sbest »

PEN:

Heya. There's an easy way to setup a "poor man's" VPN for VNC-based remote access. The idea is to run an echoServer on a publically-available IP, then use EchoVNC to connect to it from both the VNC Viewer and VNC Server sides. You can then initiate UltraVNC connections via the EchoVNC GUI, without any further adjustment to your firewalls or routers. And if OpenSSL is installed on both sides, the whole VNC connection is secured with 128-bit AES.

Hope that helps!

-Scott
ipsec
Former moderator
Former moderator
Posts: 565
Joined: 2004-09-20 18:56
Contact:

Post by ipsec »

sbest wrote:PEN:

Heya. There's an easy way to setup a "poor man's" VPN for VNC-based remote access. The idea is to run an echoServer on a publically-available IP, then use EchoVNC to connect to it from both the VNC Viewer and VNC Server sides. You can then initiate UltraVNC connections via the EchoVNC GUI, without any further adjustment to your firewalls or routers. And if OpenSSL is installed on both sides, the whole VNC connection is secured with 128-bit AES.

Hope that helps!

-Scott
Make sure when you compare EchoVNC to a VPN they understand they can use 128Bit encryption but must manually configure it to do so.

VPN by nature is secured / at least using 128 bit encryption.
madcowz
Posts: 3
Joined: 2005-05-24 11:17

Post by madcowz »

Cobra wrote:
madcowz wrote:Both ports show as open when scanned.


Ever thought about using a VPN tunnel to connect to your computers from the outside? Then your ports 5800 & 5900 wouldn't show up a open/closed. Just an idea... :wink:
Yes,

We were originally using VPN and SSH Sentinel, but it is such a pain in the $"4"$^&^!&.

Everything would be running fine for a couple of weeks, then all of a sudden, the clients would receive an error, which would vary from the certs not being correct to IPSEC layer 2 failing, and I would then have to do a reinstall and re configure. Sometimes having to do this several times before it worked.

I was using a settings file so it should have been a simple matter of dragging this onto the app and restarting but oh no, not with Sentinel. I also couldn't blame the users as it happened to me several times :-), and one of the users is a developer who has been using VPN for years. So in a fit of rage, it was removed and VNC installed instead. Which, apart from that silly mistake above <cough> has worked like a charm.
Post Reply