"Personal thoughts, ramblings, and nonsense from Drew, himself."
This post was written on December 27, 2005 at, or around 1:16 pm by Drew. This post is composed of 980 words from the English language and currently has 8 comments to its name. Additionally, this article is tagged under Networking, VPC (MS Virtual PC), Windows and you can trackback to this article using this link. This post was last updated on Jul 16, 2009. Enough talk, carry on.
A VPN, or Virtual Private Network, allows users to create a private network between two or more computers on the internet (or through your own network without being on the same workgroup or domain). For this lab, I will show you how to set up a basic VPN using PPTP for file sharing (mapping in our case) using MS’ Virtual PC (“VPC”).
I assume that you have installed Windows 2000 Professional already and configured it the way I have in my other lab Configuring VPC. Great! Then let’s get started.
In Windows 2000 Pro, we will assign the workstation with a static IP address, and its corresponding subnet mask. We want to manually enter this using static addressing because we are not using DHCP for the VPN, if we do, we could run into a lot of connection errors and possibly have to reconfigure the workstation time and again (especially on a bigger network). To configure your Windows 2000 Pro host:
Right click My Network Places, and go down and left click Properties.
Next you will see a dialog box for the Network and Dial-up Connections. You need to right click the Local Area Connection, go down and click Properties.
Now we must edit your TCP/IP settings and configure them manually. So, select the Internet Protocol (TCP/IP) and click the Properties button.
When a dialog box opens, this is out Internet Protocol (TCP/IP) Properties. You will want to choose the Use the following IP address option and in IP address field, type: 192.168.54.2 and for your Subnet mask type: 255.255.255.0 (it might put the Subnet mask in automatically. Leave the rest of the settings at default, and no, you do not need to set anything for the Default gateway. Click OK when you are finished. Then click OK to save and exit the Local Area Connection Properies dialog.
For now, we are finished with the Windows 2000 workstation.
Setting up the servers’ TCP/IP settings are just like setting up the Workstations’ TCP/IP settings. Actually, EXACTLY alike. So instead of wasting time, configure your TCP/IP settings for the Server as you did for the Workstation. The only correction that needs to be made is the IP address for your Server machine. The IP address for the Server should be 192.168.54.1.
We need to configure the Routing and Remote Access so that we can connect the workstation to the server. So, on your Server, go to Programs – Administrative Tools – Routing and Remote Access.
Now you will see your computer name (local) with a server icon that has a red dot on it, letting you know that it is not running. Right click your computer name and click Configure and Enable Routing and Remote Access.
A dialog box with appear. This is the Routing and Remote Access Server Setup Wizard, what you will use to configure your VPN on the server. Click Next to continue.
Now we need to tell the computer what kind of configuration we want to give the connection. We want to set up a VPN, so we will choose Virtual private network (VPN) server. Click Next to continue.
The Server will let you know what protocols are required on the workstation. You should have TCP/IP configured on your workstation, since we have already manually configured it. So, select the option Yes, all of the available protocols are on this list, then click Next to continue.
The server will ask you for the internet connection, or the type of networking adapter that uses the internet. In this case, we are going to use our Local Area Connection, the one we configured using the IP address of 192.168.54.1. Select it from the list and click Next to continue.
In our simple case, we want to automatically assign IP addresses to the machine connecting to the server. So, we are going to click Automatically and click Next to continue.
Before going to the next section, an Alert message is displayed letting you know that your server is configured using a static IP address, and that you need to make sure that your static IP address is compatible with the DHCP address assigned when dialing in to the remote server. Just click OK and you will be directed to the next step.
RADIUS is the Remote Authentication Dial-In User Service that provides a central authentication when you have multiple remote servers. We only that one server and this section is an advanced topic, so we are going to select No, I don’t want to set up this server to use RADIUS now. Then click Next to continue.
We are now done setting up the Routing and Remote Access Server. You can click Finish and go grab a nice cold Coke. This concludes Part 1 of Configuring a VPN w/ PPTP using VPC.
UPDATE: There will not be a part two. I keep stating that I will, but it never happens. I don’t really dive into alot of Windows-related articles anymore. I’m a Unix administrator, so I’m not going to pretend that I know what I’m doing. At the time of writing this inital post, I knew what I was doing, as far as an update, you are better off searching Google, rather than me play around with Windows Server, just to figure this out and get it posted.
Haha, yea, I’d like some lasagne and a baked patato, please. What a place…
You know Microsoft Virtual PC is now free, and every version after is going to be also free? I have Microsoft Virtual PC 2004 installed and runs about 4 different VPC’s. ;-)
Yea, I know. It’s been free for quite awhile now. I was extremely happy about that. I will have to admit, though, that it wasn’t Microsoft’s initial idea.
With VMWare going free, they pretty much had to go along. I have found a few alternatives, such as Qemu and Virtual Box. Actually Qemu is only available on Linux I believe, but a port to Windows is available here. I actually prefer Qemu, as it is very powerful, and actually has USB support (which Microsoft hasn’t done yet – except for Mac systems).
Check it out, it’s good stuff.
Also – damn – I need to update this post. Well, not this one, but I do need to write part two, haha. I’ll get on that soon, I hope.
@Innuendo: I’m aware of this, as I did give a link and my regards to Joe stating that there was also a port available for Windows.
Yep… I guess I have swiss cheese memory… I couldn’t remember this. But yeah, I’m thinking about giving Virtual Box a try, but at the moment, I don’t think qemu lets you create the boxes, only view them. At least I can’t figure it out (on Windows) yet. But its a great portable player. VMware is good so far… But it just take up alot of space. Even though I’m using only 1 GB of space currently.
Note: If this is your first time commenting on my site, there will be a delay, as I have to approve your comment.
Ajax AOL/AIM Apache Applications Architecture Career Case Projects CentOS CSS Debian Design File Systems Google Hacks Hardware Humor JavaScript Life Management Movies Networking Open-Standards Personal PHP Programming Registry Samba Security Shell Scripting Software Sys Admin Tech The Notebook Tips UNIX/Linux Virtualization VMWare VPC (MS Virtual PC) Walkthrough Web Apps Windows Work Workaround XHTML XHTML 2.0