How to configure UltraVNC for remote connection
freddyraf Posted messages 103 Status Member -
Hello everyone.
I just installed the latest version of UltraVnc on my office desktop and my laptop for connecting to my office from home.
I configured both computers through the "admin properties" menu.
However, when both machines are on the same office LAN, I can connect without any issues. But once I'm on a different network, I can no longer reach the office PC.
I need your assistance to resolve this problem, please.
Have a great day, everyone.
3 answers
-
Hello,
You need to clarify the network configuration between your home and your office.
Because the software, on the same network, does not encounter blocked ports and therefore works, it is the easiest environment.
To access your office network, configuration changes need to be made by the IT department. For example, on the internet connection modem/router, redirecting an incoming call to your PC. This is for small organizations. In a larger structure, the IT department will install VPN software on their network and remote users will have a VPN client software to join the corporate network, or a VNC connection may work, with the office PC and your personal PC being on the same network.
To avoid being dependent on this type of configuration, we also use software like Teamviewer where the connection method is different. The connection between the two PCs goes through Teamviewer's servers.
-
Hello,
Yes, otherwise we regularly get kicked off by TeamViewer, which always ends up claiming wrongly or rightly that our usage goes beyond the free context.
The truly free usage is fading away, try AnyDesk, AMMYY, NoMachine.
We also have to consider the firewall at home, but also the one at the office, which we might not have control over.
Besides the fact that VNC indeed goes from PC to PC and is therefore more difficult to implement, especially behind certain routers, it seems to me that no version of VNC is free anymore. -
-
-
Good evening Jee Pee.
It’s actually me who set up the core network of my network. It runs on a Mikrotik router that gets its internet via a fiber FTP converter.
Previously, I had installed realvnc which worked flawlessly, without any specific configuration on the network. Since they discontinued the family version allowing 5 connections, I had to switch to another solution, hence UltraVnc.
I would just like to know how to configure the application to connect with the hostname or DynDns, and for the rest to do on the router and firewall, I will know what to do.
Thank you in advance.
-
Hello,
I can't remember which port VNC and such use by default (5900), but it doesn't matter, it can be configured on the server for forwarding in IPv4. I'm not sure if the different versions are compatible with IPv6; for a long time, I've only been using nomachine, which works very well for me. By default, it operates on port 4000 (which is fortunately configurable) for the NX protocol, but it can also switch to SSH (I've never tried that or too quickly), and it works in IPv6, so no port forwarding is needed in any case.
PS, the server can be configured for access without authorization.
-
-
Hello,
You cannot connect to it from outside a local network using a 192 address, which by definition is not routable.
You have to do it by using the public IP if it's static (otherwise a redirector like DynDNS) or the hostname of the PC, with a NAT redirection to the local IP and the VNC port, in addition to passing through the firewall of the Box and/or the PC. -
Actually, I set up the core network of my network myself. It runs on a Mikrotik router that gets its internet through an FTP fiber converter.
Previously, I had installed RealVNC, which worked flawlessly, without any particular configuration on the network. Since they ended the family version allowing 5 connections, I was forced to switch to another solution, hence UltraVNC.
I just want to know how to configure the application to connect using the hostname or DynDNS, and for the rest to do on the router and firewall, I will know what to do.
Thank you in advance.
-
On the VNC side, you just need to connect to the public IP if it is static 123.123.123.123:5900 or MyHostName:5900, provided that the public IP is redirected by an appropriate dynamic DNS service (DynDNS, NoIP...) to the hostname you've chosen, for example tartempion.no-ip.org.
The appropriate NAT redirection rules in the local network for some of these services are pre-configured in certain routers; they are not always free (I used to use NoIp/NoIp DUC for free at one time).
In a local network where multiple machines would be accessible via VNC, you need to customize port 590n and create as many NAT rules as there are machines; it is often seen to customize the port of the remote control software for security reasons because default ports are known to malicious users and can be scanned. In the past, I did this not with TeamViewer but with Radmin, which is easier to configure (but paid), by replacing the default port (if I remember correctly 4899) with a high port of my choice after verifying that it was not assigned to an application. -
a fiber FTP converter, do you mean SFP or SFP+?
On your Mikrotik, you can configure a VPN server (preferably Wireguard unless you need to bypass a firewall, in which case it's better to use OpenVPN over TCP on port 443) with the client on the home PC.
However, via a VPN, you should not use the public address but the private address of the server PC on the LAN, with the Mikrotik router handling the routing between the private VPN address and that of its LAN.
-
