up vote 2 down vote favorite
share [g+] share [fb]

I've got a new virtual Windows 2003 Server hosted. I would like to be able to connect to the server using a VPN connection so I don't need to open up ports for subversion, ftp and so on to the public.

My goal is to only have port 80/443 open and all the other services (source control, build server, ftp server) are only accessible via a VPN connection to the server.

Now, the tricky bit (I think) is that I only have one network card and one public IP address. Is it possible at all or do I need at least two IP addresses?

[UPDATE]

I also would like to use the build in VPN server, no 3rd party software.

link|improve this question
feedback

2 Answers

up vote 2 down vote accepted

You can do so with 1 NIC. You would set the VPN server to dish out local (Class C) IP addresses, which you can use as many as as you want. You would set the NIC on your server to have a local IP as well as the internet one. When you connect via VPN you should then be able to communicate over this IP range.

To do so with the built in VPN server (RRAS) you will need to select the 'custom' option during the wizard this will then let you setup a VPN that can be configured with all you need.

link|improve this answer
Sam, I've updated my question. I would like to do it using the build in VPN server. If I remember this correctly, the Windows 2003 VPN setup wizard asked me to have at least 2 network cards?! – Flo May 1 '09 at 11:07
It probably expected you to have two NICs on the assumption that the server would be routing VPN traffic for a private subnet behind the VPN, which isn't happening in this case. If the wizard won't handle the case you want, well, it's time to dig into the docs. Oh, and "local IP addresses" aren't "Class C"; don't use classful addressing, it's so 20th century. – womble May 1 '09 at 11:17
3  
You can setup a single NIC based VPN using RRAS, when you run the wizard you will need to use the 'custom' option, then you should have the options you need. – Sam♦ May 1 '09 at 12:45
feedback
up vote 0 down vote

I think what you want to do is setup a loopback adapter and give it a non-public IP range. The physical NIC would be your outside interface for the VPN and the loopback adapter would be the private NIC. You would then need the other services source control, build server, ftp server to be listening on the loopback NIC's IP range.

I've never done it before, but that would be my best guess.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.