Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: 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://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

A few questions

Post Reply
legion1202
Posts: 2
Joined: 2014-01-13 20:39

A few questions

Post by legion1202 »

First of all I wanted to say hello first time poster here....

I have a small home health company that do support for and I am very interested in UVNC. I`ve tried it on a few computers in my house and it works perfect. I am now trying to put it to use for my company to support 3 of are offices.

We have 3 office that are lined via vpn tunnels. (A)192.168.52.1, (B)192.168.53.1 and (C)192.168.54.1

I`m kinda confused on how I should roll UVNC out..

So far I installed UNVC server on are file server in office A 192.168.52.183 and I opened up port 5900 on the sonic wall. I try to install the service on the machine but I Get this message could not connect to 127.0.0.1 and when I try to connect to the machine from home it does not work. So I know I have a problem some where but it might be my deployment.

I see other programs for UVNC such as the repeater and the PChelpt and I think I will be using all three. My goal is to get all the pcs on all three networks to be able to remote right into to troubleshoot. We also have a few people who work from home the I might need to help with too but I think that would just be opening ports on there firewall or is there a easier way?

Thanks for the help

Greg
Bonji
100
100
Posts: 339
Joined: 2008-05-13 14:54

Re: A few questions

Post by Bonji »

If your offices are all connected via a VPN, you should only need the base uVNC components.

You should just be able to connect to any other computer via the viewer by using that computer's IP address. Of course, there are a lot of assumptions I have to make concerning your VPN network, but if you can ping the remote computers you should be able to connect to them via uVNC.
-Ben
Bonji
100
100
Posts: 339
Joined: 2008-05-13 14:54

Re: A few questions

Post by Bonji »

Here's the information from your other post:
I have been playing around with UVNC and I have it working on my person lan just fine. My goal is to use it at work to provide quick and easy support for my users. I have 3 offices and some users who work from home. Each office has its own sonic wall and has 3-4 pcs per office. My question is this.

For each office do I need to open up ports for every computer I want into the server on? Or can I just open up 1 port and be able to click what machine I want to t connect too.. I`ve read info about the repeater but not sure on how it really works.. My guess would be to open a port (5900) install the server on the 4 machines and a reapers on one of the machines for each office..

Each office vpns to are main office with hold 2 of are servers via VPN tunnel.. Could that help or mess with my setup?
Should I set the repeater up on my DNS server ? (running server 2003)
If the SonicWall is restricting the VPN tunnel traffic, then you will need to make sure it is allowing TCP port 5900 through the tunnel. The computer running the uVNC server will also have to allow TCP port 5900 through its own firewall. I'm guessing the VPN is routing traffic and not NAT'ing it as those two cases require different setups to allow a remote connection. A routed connection is simpler as you can use the IP address of the remote computer directly. If it's NAT'd, then you have to map ports on the SonicWall to private internal IP addresses so traffic on the outside can make it to devices on the inside.

I've made several posts lately about dealing with the networking side of uVNC (more general network information than VNC information), so that may or may not be helpful. Basically, implementing a complicated network setup without understanding how that network functions makes troubleshooting very tough.
-Ben
Post Reply