Virtual Private Networks - Coursework Example

Virtual Private Networks (VPN) Affiliation Virtual Private Networks happens to be a secure private tunnel of communicationbetween more than a single device (remote users), through a public network, for instance the internet. Such devise could be VPN enabled routers or computers that run some kind of VPN software. This paper is about setting up a Virtual Private Network test network infrastructure. The network is meant to connect together remote users by ensuring security such that any individual who intercepts the encrypted data is unable to read it. It applies to; Windows server 2003, Windows server 2003 with SP1, Windows server 2003 with SP2, Windows server 2003 R2 (Microsoft, 2005) Infrastructure Set up Infrastructure for the virtual private Network consists of five computers that perform these services; A computer that runs windows 2003 (standard edition) given the name DC1 which acts as the Domain Name system or DNS, Domain controller as well as a certification authority. A computer that runs windows server 2003 (standard edition), given the nameIAS1 RADIUS (Remote Authentication Dial in User Service) server. A computer that runs windows server 2003 (standard edition) given the name IIS1, which acts as a file sharing server as well as a web server. A computer running windows server 2003 (standard edition), given the name VPN1, which acts as VPN server. The VPN1 is installed with two network adapters. A computer that runs windows XP professional that is given the name CLIENT 1 and act as a VPN client (Microsoft, 2005). Arrangement for the Virtual Private Network test lab is shown by the following illustration: FIG- Arrangement for the Virtual Private Network test lab (Microsoft, 2005) There is a segment of the network that represents a corporate intranet as well as another segment of the network that represents the internet. Every computer on the corporate intranet has been connected to some common hub or the layer 2 switch. Those on the internet have been connected to some separate common hub or the layer 2 switch. There is use of private addresses throughout the configuration of the test lab. For the intranet, private intranet that has been made use of is of 172.16.0.0/24. For the internet, used is the private network of 10.0.0.0/24. Every computer is configured manually with the appropriate subnet, IP Address as well as DNS server IP address. There are no WINS (Windows internet name service servers) or Dynamic host configuration protocol (DHCP) present (Jeff & Stephanie, 2014). The instructions below are used to configure the test lab making use of a limited number of computers. To show desired functionality as well as to separate services that are provided on this network, individual computers are required. The configuration is not designed to reflect the best practices or recommended or desired arrangement for some production network. It has been designed, including the IP addresses as well as all other configuration parameters, to work only on a separate test-lab network. DC1 This is a computer that runs a windows server 2003 (standard edition), which does provide the services below: The Domain controller test lab. microsoft.com domain The DNS server testlab.Microsoft.com DNS domain The enterprise root certification (CA) testlab.microsoft.com domain The following steps are performed to configure DC1 for the services: 1. Install a windows server 2003 (standard edition) as a separate server 2. Configure the IP/TCP protocol with the 172.16.0.1 IP address as well as the 255.255.255.0 subnet mask. 3. Run an active wizard for directory installation for the new domain known as testlab.microsoft.com within a new forest. When prompted, install the DNS service. 4. Carry out the installation of certificate services component as the enterprise root CA. 5. Carry out configuration of testlab.microsoft.com domain for computer certificates automatic enrolment (Microsoft, 2005). IAS1 This is a computer that runs windows server 2003, standard edition, which provides RADIUS authorization, authentication as well as accounting for the VPN server computer. For configuration of the ASI1 as the RADIUS server, 1. On DC1 add an account for the IAS1 compute 2. Run installation of windows server 2003 (standard edition) as a separate server 3. Configure the IP/TCP protocol with the 172.16.0.2 IP address, the DNS server IP address of 172.16.0.1 as well as the 255.255.255.0 subnet mask. 4. To the testlab.microsoft.com domain, join IAS1. 5. Run installation of internet authentication service, as well as registering it within the testlab.microsoft.com domain IIS1 This is the computer that runs windows server 2003 (standard edition) as well as internet info services (IIS). It is performing services of the web server the clients of the intranet. The following steps will help configure IIS1 as the web server: 1. Add a computer account for IIS1 on DC1 2. Run installation of the windows server 2003, standard edition as some separate server after which IIS1 can is installed 3. Configure the IP/TCP protocol using IP address of 172.16.0.3, DNS server IP address 172.16.0.1 as well as 255.255.255.0 subnet mask 4. Join the IIS1 to the testlab.microsoft.com domain 5. Install the IIS1 6. For determination as to whether the web server is correctly working, run the web browser on IIS1. Configure the LAN connection wizard when internet connection wizard prompts for it. If http://IIS1.testlab.microsoft.com/wnetStndS_v_s_rgb.gif is typed in the in address of the web browser, one should be able to view the graphic of windows server 2003, standard edition. 7. On theIIS1 on Windows Explorer, share the local disk © root directory by use of a share name ROOT to the group ALL with full access (Microsoft, 2005). VPN1 This is a computer that runs Windows server 2003, standard edition, which provides internet based VPN clients with VPN server services. The following steps must be performed for configuration of VPN1 as the VPN server: 1. Add a VPN1 computer account on DC1 2. As a separate or stand-alone server, install the windows server 2003, Standard Edition 3. For the connection of the intranet LAN, configure the IP/TCP protocol with the 255.255.255.0 subnet mask, the 172.16.0.1DNS server IP address 4. For the local area connection of the internet, configure the IP/TCP protocol with the 10.0.0.2 IP address and the 255.255.255.0 subnet mask 5. To testlab.microsoft.com domain, join the VPN1 6. Configure as well as enable routing and the remote access service. In the set up wizard for routing and the remote access services, make a selection of virtual private network server from the common configurations list. When IP address assignment prompts, select from the specified addresses range and then configure range 172.16.0.248 to 172.16.0.255. Avoid configuring RADIUS authentication (Microsoft, 2005). CLIENT 1 CLIENT 1 is the computer that runs windows XP professional, which acts as the VPN client as well as attaining remote access to the intranet resources through the simulate internet (DISCO, 2008). For client 1 to be configured as a VPN client, the steps below have to be performed: 1. Add client computer account on DC1 2. To the intranet segment of the network, connect CLIENT 1 3. Windows XP professional be installed as a workgroup computer on CLIENT 1 4. Configure the IP/TCP protocol with the 172.16.0.5 IP address, the 255.255.255.0 subnet mask and the 172.16.0.1 DNS server IP address. 5. To testlab.micrososft.com domain, join CLIENT 1 6. Configure IP/TCP protocol with 10.0.0.1 IP address, the 255.255.255.0 subnet mask and no IP address for DNS server 7. Shut down the CLIENT 1 computer 8. Disconnect CLIENT computer from the intranet segment of the network and then connect it to the network segment of the simulated internet ` 9. `Restart client computer then log on by use of cached credentials of the administrator account of the testlab.microsoft.com (Microsoft, 2005) The Virtual Private Network is based on user ID as well as password for authentication, authorizations purposes. It can support 120 VPN connections simultaneously. User speed ranges between 3-30 megabits. References DISCO. (2008). How Virtual Private Networks Work. Retrieved 10 5, 2014, from http://www.cisco.com/c/en/us/support/docs/security-vpn/ipsec-negotiation-ike-protocols/14106-how-vpn-works.html Jeff, T., & Stephanie, C. (2014). How VPNS work. Retrieved 10 5, 2014, from http://computer.howstuffworks.com/vpn1.htm Microsoft. (2005). Setting up the VPN test network infrastructure. Retrieved 10 5, 2014, from http://technet.microsoft.com/en-us/library/cc727930%28v=ws.10%29.aspx Read More