A

PROJECT REPORT
ON

“Virtual Private Network”

Submitted in partial fulfillment of the requirements for the
Award of the degree of

Bachelor of Technology
(Computer Science & Engineering)
Submitted To: Submitted By:
AMIT KUMAR
15ERECS200

RAJASTHSAN INSTITUTE OF ENGINEERING &

TECHNOLOGY
(Affiliated to RTU University) KOTA
CERTIFICATE OF THE INSTITUTION

This is certified that AMIT KUMAR of Computer

Science & Engineering, 4th year has successfully
completed the industrial training for partial fulfillment of
the requirement for the award of B.Tech Degree by the
University.
This report is the record of authentic work carried out by
the student during the academic year 2015-2016.
 ACKNOWLEDGEMENT
Firstly I wish my best gratitude towards Computer Science department
which gave me this opportunity to present this project.
I take this opportunity to thank all those who helped me in completing
the project successfully.
I am highly obliged to Mr. Sushil Sharma and at KVCH for
providing me continuous and invaluable guidance throughout the
project. Their kind and elderly advice always inspired us in putting our
best efforts to develop an efficient project.

AMIT KUMAR
B.Tech. 4th year
(Computer science & Engineering)
 INTRODUCTION
This project report pertains to Two months industrial training that I had
underwent at KVCH Preet Vihar as part of curriculum of degree in
Bachelor of technology in Computer Science And engineering as
required by Rajasthan Institute of Engineering & Technology
(affiliated to RTU, KOTA) .
I learnt a lot from professional managers and
skilled engineers. I had a great learning experience as trainee in this
firm. I learnt a lot about how different networks are controlled in the
industry or any department with the help of networking processes, under
MCSA.

Justification cannot be done to whatever I have learnt in these Two

months within a Few pages but I have still tried my best to cover as
much as possible in this report. In this report I have tried to sum up the
technical knowledge I have gained in my Two months of training.
 Introduction to Windows Server 2012
Windows Server 2012 is an operating system built by Microsoft and is
the successor of Windows Server 2008 R2. Windows Server 2012 is the
server-edition of Windows 8 and is available since September 2012. Its
minor update (Windows Server 2012 R2) is available since October
2013.

This article shows the differences between the individual Windows

Server 2012 editions.

Editions
Windows Server 2012 is available in 4 editions:

 Foundation
 Essentials
 Standard
 Datacenter
 The editions are suitable for the following application area

High level
Licensing Memory
Edition Ideal for... feature-
model limits
comparison

Essential
server
Cost-efficient all- functionality Server (Limited 32 GB
Foundation
round server without to 15 users) RAM
virtualization
rights

Essential
server
Environments in functionality Server (Limited 64 GB
Essentials
small companies without to 25 users) RAM
virtualization
rights

All features,
Non-virtualized or
with two Processor + 4 TB
Standard lightly virtualized
virtual CAL* RAM
environments
instances

Highly-virtualized All features,

Datacenter private cloud with unlimited Processor + CAL* 4 TB RAM
environments virtual instances
 (*) CALs are required for each user or device, which directly or
indirectly accesses a server.

Minimal System Requirements for Windows Server 2012

The following are the minimal system requirements for Windows Server
2012 R2

Description Requirements

CPU architecture x64

CPU clock rate 1,4 GHz

RAM 512 MB

Disc capacity 32 GB *

Key points for Server 2012

– Greater Hyper-V Virtualization mechanisms

– Less complex networking facility
– Streamlined security and identity management
– Storage and overhead management improvements
– Shift to cloud emphasis and connectivity in underlying functionality
 INTRODUCTION TO MICROSOFT
Microsoft Corporation is an American multinational company
headquartered in Redmond, Washington. It develops, manufactures,
licenses, supports and sells computer software, consumer electronics,
personal computers, and services. Its best known software products are
the Microsoft Windows line of operating systems, the Office suite, and
the Internet Explorer and Edge web browsers.

INTRODUCTION TO VPN

A virtual private network (VPN) extends a private network across a

public network, and enables users to send and receive data across shared
or public networks as if their computing devices were directly connected
to the private network.
It creates a secure, encrypted connection, which can be thought of as a
tunnel, between your computer and a server operated by the VPN
service. Applications running across the VPN may therefore benefit
from the functionality, security, and management of the private network.
VPNs may allow employees to securely access a
corporate intranet while located outside the office.
They are used to securely connect geographically separated offices of an
organization, creating one cohesive network. Individual Internet users
may secure their wireless transactions with a VPN, to circumvent geo-
restrictions and censorship, or to connect to proxy servers for the
purpose of protecting personal identity and location.
However, some Internet sites block access to known VPN technology to
prevent the circumvention of their geo-restrictions.

A VPN is created by establishing a virtual point-to-point connection

through the use of dedicated connections, virtual tunneling protocols, or
traffic encryption.
 A VPN available from the public Internet can provide some of the
benefits of a wide area network (WAN). From a user perspective, the
resources available within the private network can be accessed remotely.
REQUIREMENT DURING CONFIGURING VPN SERVER
1. Windows server 2012 (DC)
2. Windows server 2012(Member server)
3. Windows 7 ultimate(Client user)

STEPS ON WINDOWS SERVER 2012-DC

After installing windows server 2012 in system we must follow some guideline

1. Adjust date and time properly

2. Turn off the firewall
3. Change computer name
4. Configure static ip
IP address-10.0.0.2
Dns-10.0.0.2
DG-10.0.0.8
5. Now there are following steps how to install DC in windows server 2012

DC or also known as domain controller is a Windows Server 2012

that has Active Directory Domain Services role installed. When
installing Windows Server on a computer, you can elect to configure
a specific server role for that system. When you create a new forest, a
new domain, or add a DC in an existing domain, you are installing
Active Directory Domain Services role on Windows Server 2012. For
me, since this is the first server in the domain
From Server Manager, select “add roles”

2. Select a server from a server pool and select a local server

3. Select “Active Directory Domain Services” role.

6. 4. Once installation complete, you are not done. You need to click on “Promote this server to a
domain controller” to complete the process.

7. Since, I am adding a brand new domain, I will select Windows 2008 R2 so it’s backward
compatible.
8.
Once the Installation completes, you will find all related administrative tools under the start
menu. Active Directory Domain Controller role installs below tools:
9. Active Directory Aministrative Center
Active Directory Module for powershell
ADSI Edit
Active Directory Domains and Trusts
Active Directory Users and Computers
Group Policy Management
 Now our DC is complete
STEPS ON 2ND WINDOWS SERVER 2012(as member server)
After installing 2nd windows server 2012 in system follow the guidelines that we have done for
the 1st windows server (DC)

1. Adjust the date and time properly

2. Turn off the firewall
3. Change computer name
4. Configure Static ip(1st ADAPTER)
Ip address-10.0.0.8
DNS-10.0.0.2
(2nd ADAPTER)
Ip address-11.0.0.1
DNS-10.0.0.2

Now join this server To DC and Make It Member server

NOW STEPS FOR INSTALLING VPN WITH DHCP ROLE

STEPS:
– Start the Server Manager

– Click Add Roles and Features from the Manage Menu

– On Add Roles and Features wizard begins and click Next

– Select the Role-based or feature-based installation option and

click Next
– If you have more than one server managed via the server
manager console, then select the desired server you’d like to
install Routing and Remote Access on
– From the Roles lists select Remote Access, click Add
Features on the popup window
– Click Next
– No additional features required at this point, click Next
– Have a quick read on what DirectAccess & RRAS VPN is,
then click Next
– Select DirectAccess and VPN (RAS), click Next
– Click Next after reading this if you care
– Accept default selections and click Next
– Review the confirmation page and click install to begin
– When installation is completed, click Close
– From the Server Manager screen, click on the warning
sign and click ‘Open the Getting Started Wizard’
On Configure Remote Access, click Deploy VPN Only.
– From the Routing and Remote Access mmc, right-click on
the server and click ‘Configure and Enable Routing and
Remote Access’
– Click Next on the wizard
– Select Custom Configuration
– Select VPN access
– On completion, click Finish
– Click Start service to start the RRAS service

– Wait for the service to startup

– After the service had started, you should have your Routing
and Remote Access service configured

NEXT STEPS: We need to configure the following additional

tasks
1. Add IPv4 IP address range that would be assigned to each
client machines as they connect to the VPN
– From the Routing and Remote Access mmc, right-click on
the server and click ‘Properties’

– Under properties screen click IPv4 tab, select Static address

pool, click Add and enter the desired IP address range on
the windows popup
– Click OK to close
2. Enable Remote Access for users
– On a domain based network, open the properties of a
domain user account via Active Directory Users and Computer
mmc. Click on Dail-in, under Network Access Permission
click Allow access
STEPS ON WINDOWS 7 ULTIMATE (CLIENT USER)

No need to join client machine to domain

STEPS:
– On your Windows 7 , go to Control Panel, select Network and
Sharing Center

– Click Setup a new connection or network

– Click Connect to a workplace
– Click Use my internet connection (VPN)
– Click I’ll setup an Internet connection later
Enter ip address of public interface of VPN Server.
Then check Allow other people to use this connection if you
wish
– Enter client user name, password. Note this user account must
have been granted Dial-in permission via user AD properties.
Click Create(Optional)
– Click Close on completion
– From the desktop, click on the network icon, right-click on
newly created VPN icon and click Properties
– Click on Security tab, select Optional encryption under Data
encryption. Select Allow these protocol and check MS-CHAP
v2. Click OK to accept changes
– Click back on the network icon, right-click on VPN
Connection and click Connect
– On the popup dialog box, enter the username, password and
ensure the specified domain is correct. Click Connect
– Wait for the connection to establish

– When connection is established, the connection screen would

disappear. Click back on the network icon and your VPN
Connection should now show Connected
NOW OUR VPN SERVER IS READY
Install and Configure WDS in Windows
Server 2012(DC)
WDS Prerequisites

The Windows Deployment Services server must be a member of an Active Directory

Domain Services (AD DS) domain or a domain controller. You may need to ‘Install Active
Directory in Windows Server 2012 R2‘.

The Domain Name System (DNS) server on the network before you can run Windows
Deployment Services.

For deploying IP address you must have a Dynamic Host Configuration Protocol (DHCP) server
with an active scope on the network because Windows Deployment Services uses PXE, which
relies on DHCP for IP addressing the clients that want to install OS remotely. Read the topic
‘Install and Configure DHCP Server on Windows Server 2012 R2‘ for DHCP Server.

You must have the appropriate credential to install role. It means you must be the member of
local admin or domain admin. The hard disk volume must be NTFS.

How to Install and Configure WDS?

In Windows Server, sign in to the server as a domain admin and open the Server Manager if it’s
not will start automatically.
Windows Server Manager

On the Server Manager click Manage and then click Add roles and features. On the Before you
begin page click Next.
Role-based or Feature-based installation page

On the Select installation type page, click Role-based or feature-based installation, and then
click Next.
Destination Server for Windows Deployment Services

On the Select destination server page, select the appropriate server, and then click Next. By
default the MS2.technig.local server has selected.
Windows Deployment Services Role

On the Select server roles page, scroll down and then select Windows Deployment Services
check box. In the Add feature that are required for Windows Deployment Services? Click
Add Features and click next. This task will install the Windows Deployment Services Tools
which included in Windows Remote server administration tools.
Install Windows Deployment Services Role

On the Select features page, click next.

Windows Deployment Services Features

On the WDS page once read the information and click Next.
Deployment Server and Transport Server

On the Select role services page, select the role services to install for Windows Deployment
Services. Leave these role services selected by default if you want to install both the Deployment
Server and Transport Server. Click Next.
Confirm Installation of Windows Deployment Services

Finally on the Confirm installation selections page, click Install.

How to Install and Configure WDS In Windows Server 2012 R2

When the installation process complete successfully, click Close and go to Server Manager
dashboard. Now we have the WDS role and lets try to configure it.

How to Configure Windows Deployment Services?

While you are log in as domain admin account or local administrators members, go to Server
Manager and click Tools then click Windows Deployment Services in order to open it.
Windows Server Manager Dashboard

On the Windows Deployment Services console page expand the Servers and right click the
MS2.technig.local then click Configure Server.
Windows Deployment Services Console – Install and Configure WDS

On the Windows Deployment Services Configuration Wizard page, read it once and click
Next.
Windows Deployment Services Configuration Wizard

On the Install Options page select integrated with Active Directory and then click Next.
WDS Install Options

On the Remote Installation Folder Location, select the location where you want to keep all
Windows Images and configuration files and then click next.
Remote Installation Folder Location – Install and Configure WDS

On the PXE Server Initial Settings page select Respond to all client computers (Know and
unknown) and click Next. Remember, we are in the test area so in the real network environment
select whatever you want.
WDS PXE Server Initial Settings

The sever will start and complete the configuration. On the Operation Complete page
unchecked the Add image to server now and then click Finish
Insert Server 2012 DVD and

Select Checkbox of add images to server now

WDS – Operation Complete – Install and Configure WDS

Here is the Windows Deployment Services in Windows Server 2012 R2.

Windows Deployment Services in Windows Server 2012

OK, that’s all Install and Configure WDS.

IN THIS STEP WE WILL ADD BOOT IMAGE AND INSTALL IMAGE. BOOT IMAGES ARE IMAGES
THAT YOU BOOT A CLIENT COMPUTER INTO TO PERFORM AN OPERATING SYSTEM
INSTALLATION. TO ADD THE BOOT IMAGE, RIGHT CLICK BOOT IMAGES AND CLICK ON ADD
BOOT IMAGE.
To add the Install image, right click Install Image, click on Add Install Image, provide a
name and create a new Image Group. Click on Next.

Now we have to select and add the Install image. Install images are the operating system
images that you deploy to the client computer. Click on Browse and the select Install.wim.
Click on Open.
In the below screenshot we will select all the editions of windows 7 that are listed. click on
Next.
Click on Finish to close the Add Image Wizard.
To add the boot image, right click Boot Images and click on Add Boot Image.

Browse to the location where the operating system installation files are stored. The boot.wim
file can be found under folder named Sources. Select boot.wim and click on Open
Enter the name for the boot image. Click on Next.

We have imported or added a boot image to our WDS server. Click on Finish.
Testing the Configuration

We need only single client machine that supports network-based installation of operating system
to test this whole configuration.

When you boot the machine and it gets an IP lease and WDS information, you can assume your
DHCP is working

Press F12. Follow the wizard and start the operating system installation