[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 814
  • Last Modified:

VNC over VPN (3 computers)

Hi,

I'm trying to set up VNC through a VPN connection.

I have three computers.
Computer A, Computer B, and Computer C.

Computer A will connect to Computer B through a VPN and through the VPN connection will VNC with Computer C.

Computer A is not on the same network.
Computer B shares a connection with Computer C. (will act itself as the tunnel from A->C)
Computer C will be remotely controlled by Computer A.

Currently, I'm using UltraVNC server on Computer C and can access it using Computer B.
I'm using Hamachi as the VPN connection from Computer A to Computer B, but I don't know how to connect to the VNC of Computer C through the connection from Computer A.

Any recommendations on software and set up? If I need to clarify anything, I'll be happy to try and rephrase it.

Thank you.
0
nu_gen68
Asked:
nu_gen68
  • 3
  • 3
  • 2
  • +2
1 Solution
 
digitapCommented:
what kind of computer is computer is computer B? if windows, simply RDP to computer B from Computer A and get a vnc to computer C within the RDP session on computer B.

why don't you just get a vpn from computer A to computer C?
0
 
shadowmantxCommented:
You can setup VNC with different ports for example:

Computer A - 192.168.1.100:5900
Computer B - 192.168.2.100:5901
Computer C - 192.168.3.100:5902
0
 
nu_gen68Author Commented:
For RDP part, didn't want to access RDP to another RDP, or VNC to another VNC.
Also, wouldn't that cause some lag by running 2 RDP sessions versus 1 RDP over a VPN?

Computer C's only access will come from Computer B, trying to limit outside access to Computer C.
Computer B in this scenario is just the tunnel for Computer A to access Computer C in a secure manner.

Computer A runs Windows 7.
Computer B and Computer C both run Windows XP Pro.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
kevdinesCommented:
Hi nu_gen68,

If I understand this right, you want to VPN to CompB, then VNC from CompA directly to CompC via this VPN connection (rather than having an intermediary VNC/RDP connection to CompB)? If so, then the principle sounds fine to me - it just sounds like a routing issue. CompB is going to have to be able to act as a router for CompA, and as I'm unfamilar with Hamachi I can't guarantee that this will work (but I'd be surprised if software that allowed incoming VPN connections couldn't also act as a router). If CompB is a Windows server, then you would just need to install the RRAS component and enable LAN routing.

Assuming that the network address ranges of the local network (CompA) and the remote network/s (CompB & CompC) don't overlap:

If CompB and CompC are on the same subnet on the remote network, then this should be pretty straight-forward. Once the VPN is up, confirm that you can ping CompB, then you should be able to ping other network resources, including CompC, on the remote network. If you can ping CompB, but not other resources, post back the output of pathping CompC.

If CompB and CompC are on different subnets, then you have two options. The easiest is just to make sure that your VPN connection to CompB has the 'Use default gateway on remote network' option ticked. I'm not familiar with Hamachi, so I can't direct you to the setting, but it shouldn't be hard to find. Provided that CompB is capable of routing, you should then be able to ping/VNC to CompC.

Alternatively, you can manually add a static route to CompA and CompC, i.e.:

CompA - 192.168.0.100 / 24
CompB - 192.168.10.150 / 24
CompC - 192.168.50.200 / 24

Provided that you can ping CompC from CompB already, you would need to type the following command on CompA:

route add 192.168.50.0 mask 255.255.255.0 192.168.10.150

This will direct all traffic for the network address range that CompC is on over your VPN connection to CompB (you could alternatively use: route add 192.168.1.50.200 mask 255.255.255.255 192.168.10.150 to only route traffic for CompC over the VPN). It doesn't matter whether you do this before or after you connect the VPN. You may also need to add a static route to CompC (as it will have no idea where to route traffic to the 192.168.0.x subnet in the example above). In this case, the command would be:

route add 192.168.0.0 mask 255.255.255.0 192.168.10.150

I think I'm making it all sound more complicated than it really is, but give it a try and let us know how you get on. If you're still having problems, post back the local IP addresses and subnets for CompA, CompB and CompC, and the ping results (once the VPN is connected) for:

CompA -> CompB
CompB -> CompC
CompA -> CompC
CompC -> CompA

HTH,

Kev
0
 
kevdinesCommented:
Boiling that, frankly massive, blurb down a bit:

CompB is going to have to be able to act as a router. XP can't do this natively, so hopefully the Hamachi VPN software will have the functionality for this. If not, digitap's advice is spot on - you'll just have to use two RDP/VNC connections. In my experience, nesting RDP sessions results in less lag than nesting VNC sessions.

Cheers,

Kev
0
 
nu_gen68Author Commented:
I've actually found another way. It's a program that forwards the connnection from Computer A to Computer C, while using Computer B as the tunnel.

Thank you for your replies and help.
0
 
digitapCommented:
what's the program?
0
 
nu_gen68Author Commented:
http://www.quantumg.net/portforward.php

That's the program that I ended up using.
0
 
digitapCommented:
cool...thx!
0
 
QlemoDeveloperCommented:
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

  • 3
  • 3
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now