ACN Lab Manual 2016-17 PDF

G.
S Mandal’s
Marathwada Institute of Technology, Aurangabad
Approved by All India Council for Technical Education
(AICTE), Delhi Affiliated to Dr. Babasaheb Ambedkar
Marathwada University, Aurangabad
Department of MCA
MCA23 –Adv. Computer Networks

Laboratory Manual
FOR III SEMESTER

SY-MCA
ACADEMIC YEAR: 2016 – 2017
This lab manual is specially designed for SYMCA Students for Private Circulations only
MIT/MCA/LM/CJ/2016-17/01
GENERAL INSTRUCTIONS FOR LABORATORY CLASSES
DO’S
1. Without Prior permission do not enter into the Laboratory.
2. While entering into the LAB students should wear their ID cards.
3. The Students should come with proper uniform.
4. Students should sign in the LOGIN REGISTER before entering into the laboratory.
5. Students should come with observation and record note book to the laboratory.
6. Students should maintain silence inside the laboratory.
7. After completing the laboratory exercise, make sure to shutdown the system
properly.
DONT’S
1. Students bringing the bags inside the laboratory.
2. Students wearing slippers/shoes insides the laboratory.
3. Students using the computers in an improper way.
4. Students scribbling on the desk and mishandling the chairs.
5. Students using mobile phones inside the laboratory.
6. Students making noise inside the laboratory.

HARDWARE REQUIREMENTS:
Pentium IV with 2 GB RAM,
160 GB HARD Disk, Monitor
1024 x 768 color 60Hz
SOFTWARE REQUIREMENTS:
Windows / Linux operating / Ubuntu Operating System
CISCO packet Tracer
UNIVERSITY PRACTICAL EXAMINATION
Allotment of marks
Internal assessment = 00 marks
Practical examination = 00 marks
---------------------
Total = 00 marks
---------------------
INTERNAL ASSESSMENT (00 marks)

Staff should maintain assessment pages of students and the HOD should monitor it
Split up of Internal Marks

Assessment = 00 marks
Record Note = 00 marks
Attendance = 00 marks
---------------------
Total = 00 marks
---------------------
UNIVERSITY EXAMINATION
The exam will be conducted for 00 marks.
Split up of Practical Examination Marks
Aim and Procedure = 10 marks
Execution = 10 marks
Record Book = 10 marks
Output & result = 10 marks
Viva voce = 10 marks
Total = 50 marks
3
LIST OF EXPERIMENTS
1. To Study basic communication commands like ping, hostname,

ipconfig, tracert & Netstat
2. To Study installation of Windows Server 2003 and Windows XP
Client
3. To Study installation of DHCP server
4. To Study installation of DNS server
5. To Study installation of FTP and Telnet server
6. To Study Static Routing configuration
7. To Study RIP Routing configuration
8. To Study OSPF Routing Configuration
9. To Study EIGRP Routing Configuration
10. To Study Access list configuration
MARATHWADA INSTITUTE OF LABORATORY
TECHNOLOGY, AURANGABAD MANUAL
PRACTICAL EXPERIMENT INSTRUCTION SHEET
EXPERIMENT TITLE: To Study installation of Windows
Server 2003 and Windows XP Client
DEPARTMENT: MASTER OF COMPUTER APPLICATION LABORATORY:
Experiment No - 02 YEAR: 2016-17
Class: SY MCA PART: I SUBJECT: Advance Computer Networks
Aim :- To Study installation of Windows Server 2003 and Windows XP Client

Steps to follow
Windows Server 2003

Windows Server 2003 is an operating system designed for users who want to create a network that
multiple computers can access. If you want to create a network, follow these instructions to install
Windows Server 2003 on the computer you've selected to be your server machine.
Steps
Put the Windows Server 2003 CD into the CD drive and turn your computer on. If you
can't open the CD drive while your computer is off, put the CD into the drive while the
computer is on, and then restart your computer. This is so the computer loads from the CD to
begin the installation process.
Wait as the Windows Setup screen loads. Hit the "Enter" button once the "Welcome to
Setup" message appears. Read the Windows Licensing Agreement and hit the "F8" button to
agree to the terms and continue to the next screen.
Create the partition on your hard drive where you will install Windows Server 2003.
Highlight "Unpartitioned space" and hit the "C" key. Type in the amount of the drive you
would like to partition. If you want to use the whole drive, type in the same number as shown
next to "The maximum size for the new partition." Hit the "Enter" key, and then hit "Enter"
again on the next screen to confirm your drive selection.
Use the arrow keys to highlight "Format the partition using the NTSF file system." Hit
the "Enter" key. Wait as the installer formats the drive. Then, wait as the installer copies the
Windows Server 2003 files to your hard drive. A yellow progress bar will show you the
progress of each of these processes.
Hit the "Enter" key to reboot your computer after the setup process completes. Wait as
the installer loads device drivers for your computer. Click "Next" on the screen titled
"Regional and Language Options."
Enter your name and organization on the next screen and click "Next." Then, enter the
product key that came with your CD and click "Next." Click the radio button next to "Per
server" and enter the number of connections to your server that you will need. Click "Next."
Think of an administrator password and enter it on the next screen. Change the computer
name if you don't like the default name and click "Next." Select your time zone and click
"Next."
Configure your network settings by clicking "Custom settings" on the screen titled
"Network Settings" and clicking "Next." Choose "Internet Protocol (TCP/IP)" and click
"Properties." Choose either "Obtain an IP address automatically" if you don't know your IP
address, or choose "Use the following IP address" and enter the IP address in the text box.
Click "OK" and then click "Next."
Leave the "No" option selected on the "Workgroup or Computer Domain" page and click
"Next." Wait as the installation process continues installing; a message to the left of the screen will
tell you how many minutes the remaining installation process will take. Your installation will be
complete once the installer reboots your computer.
Windows XP Client
Load the installer. Once your Boot Order is set, insert the Windows XP CD into your drive and Save
and Exit from the BIOS. Your computer will reboot and you will be presented with the message: Press
any key to boot from CD. Press any key on your keyboard to start the Setup program.
 Setup will load files necessary to begin the installation, which may take a few moments. Once
the loading is complete, you will be taken to the Welcome screen.
Press ENTER to begin installation. Once the loading is complete, you will be taken to the Welcome
screen. You are given several options, but if you are installing or reinstalling Windows XP, you’ll
want to press ENTER to start the installation configuration.
Read the License Agreement. This document tells you what you can and can’t do with Windows,
and your rights as the consumer. After reading, press F8 indicating you agree to the terms.
Select the partition you want to install on. You will see a list of available partitions on your
installed hard drives. If you are installing Windows XP on a new hard drive, you should see only one
entry labeled "Unpartitioned space." If you have a previous version of Windows or Linux installed on
your computer, you will potentially have multiple partitions.
 Installing Windows XP will erase all of the data on the partition that you choose. Select a
partition that is empty or that contains data that you do not care to lose.
 You can delete your partitions with the “D” key. This will return them to “Unpartitioned
space”. Any data on the partition will be lost when it is deleted.
Create a new partition. Select the Unpartitioned space and press “C”. This will open a new screen
where you can set the partition’s size from the available space. Enter the size in megabytes (MB) for
the new partition and then press ENTER.
 By default, the partition will be set to the maximum amount of available space. Unless you
plan on creating multiple partitions, you can usually leave this at its default.
 Windows XP requires at least 1.5 gigabytes (1536 MB) for its installation files, but you will
want more than this for programs, documents, downloads, and other files. 5 gigabytes (5120
MB) is a good baseline amount for Windows XP, with more if you plan on installing a lot of
programs.
 You can create multiple partitions on a single drive. This can allow you to separate your
programs from your movies and music, or to install another operating system. Windows XP
can only be installed on one discrete partition.
Select your new partition. Once you’ve created your installation partition, you will be returned to the
partition selection screen. Select your new partition, usually labeled "C: Partition 1 [Raw]" and press
ENTER.
Select "Format the Partition using the NTFS File System" and press ENTER. NTFS is the
preferred method, supporting a larger amount of disk space per partition than FAT, and including
security features at the file system level. NTFS also includes system level compression. There are
almost no situations anymore where choosing FAT would be preferable.
 If your partition size is larger than 32 GB, you will not be given the option to choose FAT.
 It is highly recommended to avoid Quick Format, as this skips an important process that
checks the hard drive for errors or bad sectors. This scan is what consumes the majority of the
time taken when performing a full format. If there are errors on a disk at the physical level, it's
best to catch them now rather than later.
Wait for the format to complete. The system will now format the partition. The length of time this
process requires depends on the speed and size of the drive. In general, the larger the partition, the
longer the process will take.
Wait for the Setup files to copy. Windows will now start copying files from the installation disc and
prompt you to reboot the computer when the process is completed. Press ENTER when prompted to
reboot, otherwise it will do so automatically after 15 seconds
Allow the computer to boot normally. You will see the message asking you to press a key to boot
from CD. Ignore it and allow the computer to continue booting from the hard drive. You will see the
Windows logo as the Setup program loads.
Wait for the installation to proceed. After the Windows logo goes away, you will see a list of steps
remaining on the left side of the screen, and tips for using windows on the right. The time remaining
for the installation will be displayed below the list of steps remaining.
 It is normal for the screen to flicker, turn on and off, or resize during this process.
Choose your language and region settings. During the installation process a dialog window will
appear, asking you to choose your Regional settings. Select appropriate settings native to your area.
Click the Next button when that is completed.
 Enter your full name if you want. This will be set as the “owner” of Windows, and will be
attached to certain things, such as Document creation.
Enter your Product Key. You will not be able to complete the installation process without a valid
Product Key. Click "Next" to continue.
 Some versions of Windows will not ask for the Product Key until installation is complete.
Set your computer’s name. This will be the name that represents the computer on a network.
Windows sets a default name, but you can change it if you would like. You can also set a password for
the Administrator account. This is optional, but recommended for public computers.
Select your time zone. Ensure that the date/time are correct. Click "Next" to continue.
Choose your network settings. Almost all users installing Windows XP on a home or personal
computer can leave "Typical Settings" selected for Network Setup. If you are installing Windows XP
in a corporate or academic environment, check with the system administrator, though Typical Settings
will most likely work.
1) In the next window, nearly all users can select “No, this computer is not on a network, or is on
a network without a domain.” If you are in a corporate setting, ask your system administrator
which you should choose.
2) You can typically leave the workgroup name set to default.
Wait for the installation to finalize. This will only take a few minutes, and the computer will reboot
when it is finished installing. Once the computer reboots, you will be taken to the Windows XP
desktop. At this point, installation is complete, though there are a few things left to do before
Windows is completely usable..
Set your display preferences. Once Windows loads, you will be told that Windows will
automatically configure your display. Click OK to start the configuration. Your screen will flash a
couple times, and then you will be asked if you can read the box that appears.
Set your connection preferences. If your computer is connected to the internet, select your
connection type. Press Next to continue.
Activate your copy of Windows. If connected to the Internet, Select "Activate Now." Windows will
connect to the activation server and automatically authenticate your copy of Windows. If you haven’t
entered your Product Key yet, you will need to enter it now
Create Users. After the Activation Process, a window will appear allowing you to select the users for
the computer. Enter your name, and the names of others who will be using the machine. Press Next to
continue.
PREPARED BY : Shaikh Parvez VERIFIED BY : Dr. Madhuri Joshi APPROVED BY : Dr. M.H Kondekar
(Subject Teacher) (Module Coordinator) (HMCAD)
EXPERIMENT TITLE: TO STUDY INSTALLATION OF DHCP SERVER

Aim :- To Study installation of DHCP server

Steps to follow
Installation of DHCP server on Windows 2003 Server
This step-by-step article describes how to configure a new Windows Server 2003-based Dynamic
Host Configuration Protocol (DHCP) server on a stand-alone server to provide centralized
management of IP addresses and other TCP/IP configuration settings for the client computers on a
network.
How to Install the DHCP Service

Before you can configure the DHCP service, you must install it on the server. DHCP is not installed
by default during a typical installation of Windows Standard Server 2003 or Windows Enterprise
Server 2003. You can install DHCP either during the initial installation of Windows Server 2003 or
after the initial installation is completed.
How to Install the DHCP Service on an Existing Server

1. Click Start, point to Control Panel, and then click Add or Remove Programs.
2. In the Add or Remove Programs dialog box, click Add/Remove Windows Components.
3. In the Windows Components Wizard, click Networking Services in the Components list, and
then click Details.
4. In the Networking Services dialog box, click to select the Dynamic Host Configuration
Protocol (DHCP) check box, and then click OK.
5. In the Windows Components Wizard, click Next to start Setup. Insert the Windows Server
2003 CD-ROM into the computer's CD-ROM or DVD-ROM drive if you are prompted to do
so. Setup copies the DHCP server and tool files to your computer.
6. When Setup is completed, click Finish.
How to Configure the DHCP Service
After you have installed the DHCP service and started it, you must create a scope, which is a range
of valid IP addresses that are available for lease to the DHCP client computers on the network.
Microsoft recommends that each DHCP server in your environment have at least one scope that does
not overlap with any other DHCP server scope in your environment. In Windows Server 2003,
DHCP servers in an Active Directory-based domain must be authorized to prevent rogue DHCP
servers from coming online. Any Windows Server 2003 DHCP Server that determines itself to be
unauthorized will not manage clients.
How to Create a New Scope

1. Click Start, point to Programs, point to Administrative Tools, and then click DHCP.
2. In the console tree, right-click the DHCP server on which you want to create the new DHCP
scope, and then click New Scope.
3. In the New Scope Wizard, click Next, and then type a name and description for the scope.
This can be any name that you want, but it should be descriptive enough so that you can
identify the purpose of the scope on your network (for example, you can use a name such as
"Administration Building Client Addresses"). Click Next.
4. Type the range of addresses that can be leased as part of this scope (for example, use a range
of IP addresses from a starting IP address of 192.168.100.1 to an ending address of
192.168.100.100). Because these addresses are given to clients, they must all be valid
addresses for your network and not currently in use. If you want to use a different subnet
mask, type the new subnet mask. Click Next.
5. Type any IP addresses that you want to exclude from the range that you entered. This
includes any addresses in the range described in step 4 that may have already been statically
assigned to various computers in your organization. Typically, domain controllers, Web
servers, DHCP servers, Domain Name System (DNS) servers, and other servers, have
statically assigned IP addresses. Click Next.
6. Type the number of days, hours, and minutes before an IP address lease from this scope
expires. This determines how long a client can hold a leased address without renewing it.
Click Next, and then click Yes, I want to configure these options now to extend the wizard
to include settings for the most common DHCP options. Click Next.
7. Type the IP address for the default gateway that should be used by clients that obtain an IP
address from this scope. Click Add to add the default gateway address in the list, and then
click Next.
8. If you are using DNS servers on your network, type your organization's domain name in the
Parent domain box. Type the name of your DNS server, and then click Resolve to make
sure that your DHCP server can contact the DNS server and determine its address. Click Add
to include that server in the list of DNS servers that are assigned to the DHCP clients. Click
Next, and then follow the same steps if you are using a Windows Internet Naming Service
(WINS) server, by adding its name and IP address. Click Next.
9. Click Yes, I want to activate this scope now to activate the scope and allow clients to
obtain leases from it, and then click Next.
10. Click Finish.
11. In the console tree, click the server name, and then click Authorize on the Action menu.
Troubleshooting
The following sections explain how to troubleshoot some of the issues that you may experience
when you try to install and configure a Windows Server 2003-based DHCP server in a workgroup.
Clients Cannot Obtain an IP Address

If a DHCP client does not have a configured IP address, this typically indicates that the client was
not able to contact a DHCP server. This can be caused by a network problem, or because the DHCP
server is unavailable. If the DHCP server started and other clients can obtain valid addresses, verify
that the client has a valid network connection and that all the related client hardware devices
(including cables and network adapters) are working properly.
The DHCP Server Is Unavailable

If a DHCP server does not provide leased addresses to clients, it is frequently because the DHCP
service did not start. If this is the case, the server may not be authorized to operate on the network. If
you were previously able to start the DHCP service, but it has since stopped, use Event Viewer to
check the System log for any entries that may explain why you cannot start the DHCP service.
To restart the DHCP service:

1. Click Start, and then click Run.
2. Type cmd, and then press ENTER.
3. Type net start dhcpserver, and then press ENTER.
-or-
1. Click Start, point to Control Panel, point to Administrative Tools, and then click Computer
Management.
2. Expand Services and Applications, and then click Services.
3. Locate and then double-click DHCP Server.
4. Verify that Startup is set to Automatic and that Service Status is set to Started. If not, click
Start.
5. Click OK, and then close the Computer Management window.
EXPERIMENT TITLE: TO STUDY INSTALLATION OF DNS SERVER

Aim :- To Study installation of DNS server

Steps to follow
Installing a DNS Server

What is a DNS Server?
A DNS server is a server that translates alphanumeric names such as www.google.com into a
numerical value you will know as an IP addess, in the form 123.123.123.123. There are two types of
DNS server. One that simply translates domains into their IP address and others that host the
records, known as name servers. However the general term for both of these is a DNS server, and
that is why it is often confused.
This tutorial will help you install a DNS server so you can run your own domain from your server,
rather than using your registrars name servers. It is very complicated and this tutorial must be
followed with due care and attention to make sure it goes smoothly. You MUST have furfilled ALL
of the requirements before continuing this tutorial. If you get this wrong your domain could go
totally offline, leaving your website offline and e-mail inaccessible. If you have a spare domain
you don't use it might be worth testing it out on that first instead of your main production domain.
Now the tutorial may look long, but its really not! Its because of the amount of images I have
provided to help you understand how the DNS system works. It shouldn't take you more than 15-20
minutes to carry out this tutorial. The longest part is the propagation wait for your domain which is
out of your hands.
Step 1: Requirements
In order to run your own DNS server, you must furfil the following requirements, or it simply won't
work.
You must have:

- Windows Server (any edition)
- 2 STATIC INTERNET IP addresses routed to the same server (1 will work, but is not
recommended, and it MUST be STATIC)*
- A domain that allows its DNS servers to be changed
- Knowledge of how DNS records function
- Port 53 unblocked on your firewall, both TCP and UDP (DNS service)
- Very reliable connection and server (your connection or server goes down, so does your domain!)
- Patience, and lots of it
* If you only have 1 IP then miss out all steps that include "ns2.yourdomain.com" since you will
only have one. This single IP MUST be STATIC or the DNS system won't work. It should be noted
that not all registrars allow a single name server to be used, but must use two or more. Check this
before proceeding if in doubt.
Step 2: Installing the server

You can install the DNS server by going to Control Panel > Administrative Tools > Manage your
Server and Add new role, and selecting DNS. It is straight forward and has step by step
instructions. You may need your Windows Server disk to install certain system files for this step.
When you get the Configure a DNS Server Wizard, click Cancel.
Step 3: Adding your first domain
Open up the DNS configuration window located at Control Panel > Administrative Tools > DNS.
Begin by right clicking Forward Lookup Zone and selecting New Zone.
You will be presented with the following window.
Click next and you will get another window. Select Primary Zone (default).
Click next and you will get a window asking you to enter your domain name. Enter it without the
www. part in front of the name. Then click next.
On this screen, simply click next.

Again on this screen, simply click next.
The new domain setup wizard is now finished, so select finish.

Now you will be presented with the following screen with your new domain entered.
Now double click on the top most entry labelled "Name Server (NS)". A box will appear. Delete the
entry as shown in the image below.
Now click Add and enter ns1.yourdomain.com and its IP address. Click OK, then click Add again
and enter ns2.yourdomain.com and its IP address, making two separate entries.
You should now have both entries as shown below. If you do click Apply, then OK, and proceed to
the next step.
For this step, follow the instructions in the image below. There is a small glitch which requires you
to do this to be able to see the entries that were automatically added.
Now double click on the "Start of Authority (SOA)" record and a box will appear. You need to fill
in the boxes precisely or the DNS system will not work.
Serial number: This must conform to the following series of numbers

> YYYYMMDDnn
YYYY = Date, e.g. 2008

MM = Month, e.g. 08 (for August)
DD = Day, e.g. 12 (for the 12th)
nn = Incrememnt number. Set this to 01 to begin with. It will auto
increment as you update records.
In the example I have used "2008081201" which is 12th August
2008, increment 01.
Primary Server: "ns1.yourdomain.com"

Responsible Person: "hostmaster.yourdomain.com"
Because of some registrars having such bad servers, and in an aid to reduce their load, you must set
the update and refresh intervals etc differently from their defaults. Now while this won't affect you it
will affect the checking test later in this tutorial, so in order to pass it you must set them to the
correct values.
Refresh interval: 3 hours

Retry interval: 30 minutes
Expires after: 7 days
Minimum (default) TTL: 3 days
TTL for this record: 0:0:10:0 (10 minutes)
When you have done this you can click Apply then OK. The main window will update to reflect the
changes.
Next we can finally get round to telling the server where to direct when someone connects to your
domain, using the A records you should already know about. This is very simple to do.
First, right click in an open space on the window, and select New Host (A). A box will appear.
Here, enter what you see in the boxes below, of course substituting your main IP for the one used in
the box. You need at least these two entries for a fully working website.
Now you have entered these two records, you can click Cancel to stop adding more. The window
will have updated to reflect your changes with these two new records.
Now, you will most likely be running a mail server, so we need to add some records for that to work
correctly. If you're not running a mail server you can skip this step.
We can begin with two more A records, so as before, right click and select New Host (A). Add, as
above, two new records but this time use smtp and pop like we did with www.
When you're finished, click Done. Now we need to add the MX record, which tells each mail server
that sends you mail which IP to send it to. Right click and select "New Mail Exchanger (MX)" and
a box will appear.
It is slightly different than before but works the same way.
Leave the first box blank but enter your full domain name into the second box. Leave the mail server
priority on 10, and click OK.
The window will have updated to reflect your changes.
The DNS server is now configured, however, your domain has not yet been told to use it yet! The
next few steps will instruct you on how to do this. It varies on a per registrar basis but the general
concept is the same.
EXPERIMENT TITLE: TO STUDY INSTALLATION OF FTP AND TELNET
SERVER

Aim :- To Study installation of FTP and Telnet server

Steps to follow
FTP SERVER
Preliminary Steps
As mentioned in the previous article, IIS is not installed by default during a standard installation of
Windows Server 2003, and if you installed IIS using Manage Your Server as described in the
previous article this installs the WWW service but not the FTP service. So before we can create FTP
sites we first have to install the FTP service on our IIS machine. To do this, we need to add an
additional component to the Application Server role we assigned our machine when we used
Manage Your Server to install IIS.
Begin by opening Add or Remove Programs in Control Panel and selecting Add/Remove Windows
Components. Then select the checkbox for Application Server:
Click Details and select the checkbox for Internet Information Services (IIS):
Click Details and select the checkbox for File Transfer Protocol (FTP) Services.
Click OK twice and then Next to install the FTP service. During installation you''ll need to insert
your Windows Server 2003 product CD or browse to a network distribution point where the
Windows Server 2003 setup files are located. Click Finish when the wizard is done.
Creating an FTP Site
As with web sites, the simplest approach to identifying each FTP site on your machine is to assign
each of them a separate IP address, so let''s say that our server has three IP addresses (172.16.11.210,
172.16.11.211 and 172.16.11.212) assigned to it. Our first task will be to create a new FTP site for
the Human Resources department, but before we do that let''s first examine the Default FTP Site that
was created when we installed the FTP service on our machine. Open IIS Manager in Administrative
Tools, select FTP Sites in the console tree, and right-click on Default FTP Site and select Properties:
Just like the Default Web Site, the IP address for the Default FTP Site is set to All Unassigned. This
means any IP address not specifically assigned to another FTP site on the machine opens the Default
FTP Site instead, so right now opening either ftp://172.16.11.210, ftp://172.16.11.211 or
ftp://172.16.11.212 in Internet Explorer will display the contents of the Default FTP Site.
Let''s assign the IP address 172.16.11.210 for the Human Resources FTP site and make D:\HR the
folder where its content is located. To create the new FTP site, right-click on the FTP Sites node and
select New --> FTP Site. This starts the FTP Site Creation Wizard. Click Next and type a description
for the site:
Click Next and specify 172.16.11.210 as the IP address for the new site:
Click Next and select Do not isolate users, since this will be a site that anyone (including guest
users) will be free to access:
Click Next and specify C:\HR as the location of the root directory for the site:
Click Next and leave the access permissions set at Read only as this site will only be used for
downloading forms for present and prospective employees:
Click Next and then Finish to complete the wizard. The new Human Resources FTP site can now be
seen in IIS Manager under the FTP Sites node:
To view the contents of this site, go to a Windows XP desktop on the same network and open the
URL ftp://172.16.11.210 using Internet Explorer:
Note in the status bar at the bottom of the IE window that you are connected as an anonymous user.
To view all users currently connected to the Human Resources FTP site, right-click on the site in
Internet Service Manager and select Properties, then on the FTP Site tab click the Current Sessions
button to open the FTP User Sessions dialog:
Note that anonymous users using IE are displayed as IEUser@ under Connected Users.
Now let''s create another FTP site using a script instead of the GUI. We''ll create a site called Help
and Support with root directory C:\Support and IP address 172.16.11.211:
Here's the result of running the script:
The script we used here is Iisftp.vbs, which like Iisweb.vbs and Iisvdir.vbs which we discussed in
the previous article is one of several IIS administration scripts available when you install IIS on
Windows Server 2003. A full syntax for this script can be found here. Once you create a new FTP
site using this script you can further configure the site using IIS Manager in the usual way.
Note: At this point you could add structure to your FTP site by creating virtual directories, and this
is done in the same way as was described in the previous article for working with web sites.
Controlling Access to an FTP Site
Just like for web sites, there are four ways you can control access to FTP sites on IIS: NTFS
Permissions, IIS permissions, IP address restrictions, and authentication method. NTFS permissions
are always your first line of defense but we can't cover them in detail here. IIS permissions are
specified on the Home Directory tab of your FTP site's properties sheet:
Note that access permissions for FTP sites are much simpler (Read and Write only) than they are for
web sites, and by default only Read permission is enabled, which allows users to download files
from your FTP site. If you allow Write access, users will be able to upload files to the site as well.
And of course access permissions and NTFS permissions combine the same way they do for web
sites.
Like web sites, IP address restrictions can be used to allow or deny access to your site by clients that
have a specific IP address, an IP address in a range of addresses, or a specific DNS name. These
restrictions are configured on the Directory Security tab just as they are for web sites, and this was
covered in the previous article so we won't discuss them further here.
FTP sites also have fewer authentication options than web sites, as can be seen by selecting the
Security Accounts tab:
By default Allow anonymous connections is selected, and this is fine for public FTP sites on the
Internet but for private FTP sites on a corporate intranet you may want to clear this checkbox to
prevent anonymous access to your site. Clearing this box has the result that your FTP site uses Basic
Authentication instead, and users who try to access the site are presented with an authentication
dialog box:
Note that Basic Authentication passes user credentials over the network in clear text so this means
FTP sites are inherently insecure (they don't support Windows integrated authentication). So if
you're going to deploy a private FTP site on your internal network make sure you close ports 20 and
21 on your firewall to block incoming FTP traffic from external users on the Internet.
Configuring FTP Site Logging
As with web sites, the default logging format for FTP sites is the W3C Extended Log File Format,
and FTP site logs are stored in folders named
%SystemRoot%\system32\LogFiles\MSFTPSVCnnnnnnnnnn
where nnnnnnnnnn is the ID number of the FTP site. And just as with web sites, you can use the
Microsoft Log Parser, part of the IIS 6.0 Resource Kit Tools, to analyze these FTP site logs.
Stopping and Starting FTP Sites
If an FTP site becomes unavailable you may need to restart it to get it working again, which you can
do using IIS Manager by right-clicking on the FTP site and selecting Stop and then Start. From the
command-line you can type net stop msftpsvc followed by net start msftpsvc or use iisreset to
restart all IIS services. Remember that restarting an FTP site is a last resort as any users currently
connected to the site will be disconnected.
Implementing FTP User Isolation
Finally, let's conclude by looking at how to implement the new FTP User Isolation feature of IIS in
Windows Server 2003. When an FTP site uses this feature, each user accessing the site has an FTP
home directory that is a subdirectory under the root directory for the FTP site, and from the
perspective of the user their FTP home directory appears to be the top-level folder of the site. This
means users are prevented from viewing the files in other users' FTP home directories, which has the
advantage of providing security for each user's files.
Let's create a new FTP site called Staff that makes use of this new feature, using C:\Staff Folders as
the root directory for the site and 172.16.11.212 for the site's IP address. Start the FTP Site Creation
Wizard as we did previously and step through it until you reach the FTP User Isolation page and
select the Isolate users option on this page:
Continue with the wizard and be sure to give users both Read and Write permission so they can
upload and download files.
Now let's say you have two users, Bob Smith (bsmith) and Mary Jones (mjones) who have accounts
in a domain whose pre-Windows 2000 name is TESTTWO. To give these users FTP home
directories on your server, first create a subfolder named \TESTTWO beneath \Staff Folders (your
FTP root directory). Then create subfolders \bsmith and \mjones beneath the \Accounts folder. Your
folder structure should now look like this:
C:\Staff Folders
\TESTTWO
\bsmith
\mjones
To test FTP User Isolation let's put a file name Bob's Document.doc in the \bsmith subfolder and
Mary's Document.doc in the \mjones subfolder. Now go to a Windows XP desktop and open Internet
Explorer and try to open ftp://172.16.11.212, which is the URL for the Staff FTP site we just
created. When you do this an authentication dialog box appears, and if you're Bob then you can enter
your username (using the DOMAIN\username form) and password like this:
When Bob clicks the Log On button the contents of his FTP home directory are displayed:
Note that when you create a new FTP site using FTP User Isolation, you can't convert it to an
ordinary FTP site (one that doesn't have FTP User Isolation enabled). Similarly, an ordinary FTP site
can't be converted to one using FTP User Isolation.
We still need to explore one more option and that's the third option on the FTP User Isolation page
of the FTP Site Creation Wizard, namely Isolate users using Active Directory. Since we've run out
of IP addresses let's first delete the Help and Support FTP site to free up 172.16.11.211. One way we
can do this is by opening a command prompt and typing iisftp /delete "Help and Support" using
the iisftp.vbs command script. Then start the FTP Site Creation Wizard again and select the third
option mentioned above (we'll name this new site Management):
Click Next and enter an administrator account in the domain, the password for this account, and the
full name of the domain:
Click Next and confirm the password and complete the wizard in the usual way. You'll notice that
you weren't prompted to specify a root directory for the new FTP site. This is because when you use
this approach each user's FTP home directory is defined by two environment variables: %ftproot%
which defines the root directory and can be anywhere including a UNC path to a network share on
another machine such as \\test220\docs, and %ftpdir% which can be set to %username% so that for
example Bob Smith's FTP home directory would be \\test220\docs\bsmith and this folder would
have to be created beforehand for him. You could set these environment variables using a logon
script and assign the script using Group Policy, but that's beyond the scope of this present article.
EXPERIMENT TITLE: TO STUDY STATIC ROUTING
CONFIGURATION

Aim :- To Study Static Routing configuration

Steps to follow
Configure Static Routing in Packet Tracer- CCNA

Configure Static Routing is the routing that network administrator configure the network routers
manually, instead of using routing protocols, RIP or OSPF which used in the dynamic routing. The
benefits of static routing is minimum bandwidth usage, no overhead on router CPU and many more
and perfect for small network with a few routers. But it is not without cons. Difficult to configure all
routers manually in the large network and troubleshooting is always harder than configuration.
As network administrator or student of CCNA you must know the configuration of static routing. It
help you to understand the process and functions of routing in the network clearly.
Configure Static Routing Using Cisco Packet Tracer

To perform this task you must create your lab and configure the basic IP addressing for all PCs and
Routers or download CCNA Lab – Static Route with Cisco packet tracer. CCNA Lab – Static Route
– no Configure
CCNA Lab- Configure Static Routing

I have configured the Static Route the same as screenshot and it is not yet configured routing. You
must configure it with below step by step static Routing guide.
Static Routing command syntax: Ip route [destination network address] [mask] [next hop
address or interface name]
In the R1 type the following commands to introduce two LANs 192.168.10.0/24 and
192.168.30.0/24 for Router 1.
R1(config)#ip route 192.168.30.0 255.255.255.0 10.10.20.2 150
R1(config)#ip route 192.168.10.0 255.255.255.0 10.10.10.2 150
Router2: Add three networks for router 2 and be sure that do not configure it with wrong IP
address.
R2(config)#ip route 192.168.10.0 255.255.255.0 10.10.10.1 150
R2(config)#ip route 10.10.10.0 255.255.255.0 10.10.20.1 150
R2(config)#ip route 192.168.20.0 255.255.255.0 10.10.20.1 150
Router3: Do the same as router 2 but with different destination and exit interface address.
R3(config)#ip route 192.168.30.0 255.255.255.0 10.10.20.1 150
R3(config)#ip route 10.10.20.0 255.255.255.0 10.10.10.1 150
R3(config)#ip route 192.168.20.0 255.255.255.0 10.10.10.1 150
So it’s easy and not too much hard. If you want to accomplish this task, firstly you must try to
understand the concept of routing and then try to configure it.
EXPERIMENT TITLE: TO STUDY RIP ROUTING CONFIGURATION

Aim :- To Study RIP Routing configuration

Steps to follow
Today I’m going to show you, how to configure Routing Information Protocol (RIP) on the Cisco
Routers. The RIP is one of the oldest distance-vector routing protocols and work perfectly with
IPv4. The next generation of routing information protocol for IPv6 is know as RIPng (RIP next
generation). So in this article we are going to test the RIP with IPv4.
It would be good if you have a physical Cisco lab for testing RIP, otherwise you can use GNS3
, Cisco Packet Tracer or equivalent network simulator software. Here I’m using packet tracer and
the Cisco RIP routing lab I have created is downloadable from the below link. Just download and
configure the basic routing with the IP addresses which assigned for each router interfaces. It help
your to practice some basic router commands also. I’m sure you can do it, but in case of
requiring some help, read the basic router commands from this post.
Downlaod the non configured Routing RIP Prococol lab that need basic configuration and this
oneRouting RIP Prococol – CCNA Lab -Ready for RIP Lab for CCNA is configured with basic and
essential configuration.
Configure Routing Information Protocol
Configure Routing Information Protocol (RIP)
So let’s start configure routing information protocol in this lab. Go to your lab and open the router 1
(R1) which is the main router connected to ISP router. Do the following command for RIP Routing.
1 R1>enable
2 R1#configure terminal
3 Enter configuration commands, one per line. End with CNTL/Z.
4 R1(config)#router rip
5 R1(config-router)#version 2
6 R1(config-router)#network 200.100.10.0
9 R1(config-router)#
After enabling router with enable command then go to privileged mode with configure terminal
command. Now with router rip command, enable routing for all routers. The version 2 command,
configure routing information protocol with version two. And next set all network id like the above
network command. I have set all three network which connect directly to R1.
RIP configuration
Now go to router R2 and configure routing protocol the same as router R1. On router 2 you must
assign the network ids of all connected network the R2.
R2>enable
R2#configure terminal
Enter configuration commands,
R2(config)#router rip
1 R2>enable
2 R2#configure terminal
3 Enter configuration commands, one per line. End with CNTL/Z.
4 R2(config)#router rip
5 R2(config-router)#version 2
9 R2(config-router)#
EXPERIMENT TITLE: TO STUDY OSPF ROUTING
CONFIGURATION

Experiment No – 08 YEAR: 2016-17
Aim :- To Study OSPF Routing Configuration

Steps to follow
The Open Shortest Path First (OSPF) is a routing protocol for wide area networks and enterprise
network. OSPF is perhaps the most widely used interior gateway protocol (IGP) in large enterprise
networks. The IS-IS, is another link-state dynamic routing protocol, which is more common in large
service provider networks. The most widely used exterior gateway protocol is the Border Gateway
Protocol (BGP), the principal routing protocol between autonomous systems on the Internet.
Basic Router Commands
Router 1: Do the basic configuration of your routers, switches and computers. Set the IP address for
each interfaces the same as screenshot. The diagram is classless IP addresses and sub-netted to
many networks. So it means you must familiar with IP sub-netting and VLSM.
Basic Router Commands

R1>enable
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#interface serial 1/3
R1(config-if)#ip address 20.10.10.1 255.255.255.252
R1(config-if)#no shutdown
R1(config-if)#exit
R1(config)#
R1(config-if)#clock rate 64000
R1(config-if)#exit
R1(config)#
R1(config-if)#clock rate 64000
Router 2: Do the following configuration for Router 2.
Configure OSPF Routing

R2(config-if)#exit
R2(config)#interface fastEthernet 0/0
Router 3: Now try to set IP address for Router 3 interfaces also.
Router Commands
Router#enable
Router#configure terminal
Router(config)#hostname R3
R3(config-if)#exit
Good, the basic configuration has competed and now start configure OSPF routing protocol on this
network.
EXPERIMENT TITLE: TO STUDY EIGRP ROUTING
CONFIGURATION

Aim :- To Study EIGRP Routing Configuration

Steps to follow
EIGRP
Before you can configure EIGRP (Enhanced Interior Gateway Routing Protocol), you should know
the basics of EIGRP routing protocol. EIGRP is an enhanced version of IGRP. The core features
of the EIGRP routing protocol remain same as provided by the IGRP protocol. However, it provides
better performance and scalability than IGRP. EIGRP is one of the most preferred, best, and loved
routing protocol. Unfortunately, it is a vendor-specific “Cisco-proprietary” protocol and can only
be used on Cisco routers. In this post, we will discuss the basic features of EIGRP protocol, EIGRP
tables, and the EIGRP configuration commands with examples.
Features of EIGRP Protocol
Some of the major characteristics and features provided by the EIGRP routing protocol are:
 It is an Interior Gateway Routing (IGP) protocol, means it can only be used to perform
routing within the same autonomous system.
 It supports up to 255 hops count.
 It is used for a mid-sized network.
 It uses composite metric (bandwidth, load, reliability, delay, and MTU) to calculate the best
path.
 It uses Diffusing Update Algorithm (DUAL).
 Since it has the characteristics of both, the distance vector and link-state protocols, hence,
sometimes is referred as a hybrid protocol. However, I have seen many times that Cisco
called it as an advanced distance-vector routing protocol.
 It supports multiple routed protocols, such as IP, Apple Talk, and IPX.
 The Administrative Distance value of the EIGRP protocol is 90.
 Unlike IGRP, it is a classless routing protocol, hence, it supports CIDR and VLSM.
 It also supports route summarization and discontinuous network.
 It supports up to six equal or unequal paths to provide load balancing for a single destination.
 The route update time of EIGRP protocol is 90 seconds.
 It supports trigger update which helps to reduce the size routing table.
 It uses 224.0.0.10 multicast address to exchange routing information between (neighbors)
routers.
EIGRP Tables
Since the EIGRP protocol has the characteristics of link-state routing protocol, it uses three different
types of tables for fast convergence.
 Neighbor table: Used to store information about the directly connected routers (called
neighbors).
 Topology table: Used to store information about all the possible routes from a source to
destination. In addition, it also stores the entire logical network structure.
 Routing table: Used to store routing information. The best path for a destination called
successor is stored in the routing table and all other alternative paths, called feasible
successors, for the same destination are stored in the topology table.
Step by Step EIGRP Configuration
Now, you have learned the basics of the EIGRP routing protocol, let us have a look EIGRP
configuration. To configure EIGRP, we will use the following topology.
Configure the IP addresses, as mentioned in the preceding topology on each device. Once you have
configured the appropriate IP addresses, you can start to configure EIGRP routing. Before doing so,
first, look at the EIGRP configuration command’s syntax.
Router(config)#router eigrp <autonomous number>
Router(config)#network <destination network>
To configure EIGRP routing, you need to perform the following steps:
 On Router1, execute the following commands.
Router1(config)#router eigrp 500
Router1(config-router)#network 10.0.0.0
Router1(config-router)#exit
EIGRP Commands
You can use various EIGRP commands to test, verify, and troubleshoot the EIGRP configuration.
The following are some of the commonly used EIGRP commands.
 To view the routing table, execute the following command.
Router# show ip route
 To view the neighbor table, execute the following command.
Router# show ip eigrp neighbors
The following figure displays the EIGRP routing and neighbors tables.
As you can see in the preceding figure, the 20.0.0.0/8 ad 150.150.0.0/16 networks are added through
the EIGRP routing protocol.
 To view information about the EIGRP routing protocol operations, execute the following
command.
Router# show ip protocols
 To view the EIGRP metric information for an interface, execute the following command.
Router# show interface <interface name/number>
The following figure displays the EIGRP metrics for the FastEthernet 0/0 interface.
Once you have configured the EIGRP configuration, test your configuration by checking the
connectivity between PC0 and Router3. To do so, open the Command Prompt window on PC0,
and execute the following command.
PC0>ping 150.150.150.2
You should be able to ping successfully as shown in the following figure.
EXPERIMENT TITLE: TO STUDY ACCESS LIST CONFIGURATION

Aim :- To Study Access list configuration

Steps to follow
The Standard Access List (ACL) on Cisco router works to permit or deny the entire network
protocols of a host from being distinguishing. These decisions are all based on source IP address
which filter network traffic by examining the source IP address in a packet. We can create the
standard IP access list by using the access-list command with numbers 1 to 99 or in the
expanded range of 1300 to 1999.
I’m using Cisco Packet Tracer to do this task. You can create your own network topology within
Cisco packet tracer or using the best network simulator GNS3. If you are new in GNS3, I
recommended to read the topics of GNS3 installation “Install GNS3 Network Simulator Step by
Step in Windows” and the configuration article “Essential GNS3 Configuration for Cisco Lab“,
these will help you to find your way in using GNS3.
Here I share my own created topology for standard IP access list with packet tracer. Download and
test it. Download CCNA Lab: Configure Standard Access List.
CCNA Lab – Standard Access List
Try to configure it with any routing protocol you want. Static route, RIP, or OSPF. This article
“Configure Static Routing in Packet Tracer” can help you to configure static routing for CCNA.
Configure Standard Access List on Cisco Router

Let’s test the standard access list on our network with preventing access from subnet 192.168.10.0 to
network 192.168.0.0 which connected directory to router R1 and just allow PC2 can get access to
the network 192.168.0.0/24.
Standard Access List – Technig
In the router R1, create an access list “access-list 10 permit 192.168.10.3 0.0.0.0” and then set it on
the fastEthernet 0/0 which is the gateway of network.
R1>enable
R1(config)#access-list 10 permit 192.168.10.3 0.0.0.0
R1(config-if)#ip access-group 10 out
R1(config-if)#exit
The command ” access-list 10 permit 192.168.10.3 0.0.0.0” deny all host on the network
192.168.10.0 but permit only PC3. We use the wildcard 0.0.0.0 for PC3. It’s only allowed the exact
host with 192.168.10.3 IP address.
The command “ip access-group 10 out” just apply this outbound traffic to this network.
Remember, we set the access list command on the global configuration and set the ip access-gorup
to interface configuration.
Now test the with ping from PC3 to any host on the network 192.168.0.0/24. It must ping
successfully but not allowed for other PCs of the network 192.168.10.0/24.
You can configure it with the following configuration also.
R1>enable
R1(config)#access-list 10 deny 192.168.10.3 0.0.0.0
R1(config)#access-list 10 permit any
R1(config-if)#ip access-group 10 out
Working with Standard access list on Cisco router is easy and simple. Just try to do some more
practice to get expert. If you want to know and test more access list commands, simply type question
mark (?) in front of your command.
R2(config)#access-list ?
<1-99> IP standard access list
<100-199> IP extended access list
R2(config)#access-list 10 ?
deny Specify packets to reject
permit Specify packets to forward
remark Access list entry comment
R2(config)#access-list 10 permit ?
A.B.C.D Address to match
any Any source host
host A single host address
R2(config)#access-list 10 permit any ?
<cr>
Hope it would be helping you to understand the Standard IP access list on Cisco routers.

ACN Lab Manual 2016-17 PDF

Uploaded by

Copyright:

Available Formats

You might also like

ACN Lab Manual 2016-17 PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ACN Lab Manual 2016-17 PDF

Uploaded by

Copyright:

Available Formats

G.

MCA23 –Adv. Computer Networks

FOR III SEMESTER

GENERAL INSTRUCTIONS FOR LABORATORY CLASSES

1. Without Prior permission do not enter into the Laboratory.

3. The Students should come with proper uniform.

6. Students should maintain silence inside the laboratory.

1. Students bringing the bags inside the laboratory.

2. Students wearing slippers/shoes insides the laboratory.

3. Students using the computers in an improper way.

4. Students scribbling on the desk and mishandling the chairs.

5. Students using mobile phones inside the laboratory.

6. Students making noise inside the laboratory.

UNIVERSITY PRACTICAL EXAMINATION

INTERNAL ASSESSMENT (00 marks)

Split up of Internal Marks

1. To Study basic communication commands like ping, hostname,

Aim :- To Study installation of Windows Server 2003 and Windows XP Client

Windows Server 2003

DEPARTMENT: MASTER OF COMPUTER APPLICATION LABORATORY:

Aim :- To Study installation of DHCP server

Installation of DHCP server on Windows 2003 Server

How to Install the DHCP Service

How to Install the DHCP Service on an Existing Server

How to Create a New Scope

Clients Cannot Obtain an IP Address

The DHCP Server Is Unavailable

To restart the DHCP service:

DEPARTMENT: MASTER OF COMPUTER APPLICATION LABORATORY:

Aim :- To Study installation of DNS server

Installing a DNS Server

You must have:

Step 2: Installing the server

Step 3: Adding your first domain

On this screen, simply click next.

The new domain setup wizard is now finished, so select finish.

Serial number: This must conform to the following series of numbers

YYYY = Date, e.g. 2008

Primary Server: "ns1.yourdomain.com"

Refresh interval: 3 hours

TTL for this record: 0:0:10:0 (10 minutes)

It is slightly different than before but works the same way.

DEPARTMENT: MASTER OF COMPUTER APPLICATION LABORATORY:

Aim :- To Study installation of FTP and Telnet server

DEPARTMENT: MASTER OF COMPUTER APPLICATION LABORATORY:

Aim :- To Study Static Routing configuration

Configure Static Routing in Packet Tracer- CCNA

Configure Static Routing Using Cisco Packet Tracer

CCNA Lab- Configure Static Routing

DEPARTMENT: MASTER OF COMPUTER APPLICATION LABORATORY:

Aim :- To Study RIP Routing configuration

DEPARTMENT: MASTER OF COMPUTER APPLICATION LABORATORY:

Aim :- To Study OSPF Routing Configuration

Basic Router Commands

Configure OSPF Routing

DEPARTMENT: MASTER OF COMPUTER APPLICATION LABORATORY:

Aim :- To Study EIGRP Routing Configuration