using vpn to connect with remote desktop?

Joined
Feb 22, 2009
Messages
928
Hi Guys
I just wanted to know if there is anyway that I could use vpn connection to connect to remote desktop? because I only want couple people access my server by remote desktop.

the reason why I am asking this because I work for a local ISP as a tech support and they have a vpn connection that I connect to so I can use there network. after I am connected I can do remote desktop to a other server and I want to know how I can something up like that.

pretty much what I am looking to do is have people use vpn connection so they connect to my network so they can use remote desktop to access my server.
 
I have this setup for a client of mine. Its faster for the client for his database work to VPN in, then connect to a workstation there via remote desktop. You would need to setup a vpn through hardware or software.
 
well I am using windows server 2003 R2 SP2. so I want the my buddys do this:

from there computer w/vpn--------------to my network--------then remote desktop into my server 2003 server.

can that work?
 
well I am using windows server 2003 R2 SP2. so I want the my buddys do this:

from there computer w/vpn--------------to my network--------then remote desktop into my server 2003 server.

can that work?

Yes, we only allow remote desktop over my organization's VPN. This neatly avoids issues with remote file access. We allow remote desktop to desktops or servers, based on your access level. Most people just hit their desktops only. Of course this requires leaving the PC's on all the time.

The OP needs to put your VPN clients on a subnet that is routable to the network that the server is on. You can restrict it via ACLs if desired to certain destination hosts.

For example in our case:

desktops are on 10.1.56.0/22
servers are on 10.1.52.0/22
VPN clients are issued IP's on 10.1.2.0/24
all subnets are also each on a unique VLAN.
(not the actual IP's we use, but you get the idea)

The VPN device is plugged directly into the core switch (which does routing internally) on the VLAN corresponding to the VPN client subnet, with a default route pointing to the IP address set on the switch to that VLAN, example 10.1.2.248. The switch then handles routing to other destination subnets such as the server and desktop subnets.

Hope this helps.
 
I am using smoothwall.

If you want VPN...you can set it up with Smoothwall as your VPN host.

Or just open/forward port 3389 to your server..they can authenticate directly to the server. Setup a rule so the host cancels out for a period of time after X number of failed login attempts..that keeps it quite secure. This way you don't have to bother with VPN.

Another security option to make you feel warm 'n fuzzy..setup an ACL on the smoothwall so that it only accepts incoming 3389 traffic from the IPs that you designate (your remote users).
 
Back
Top