INDEX

S.NO EXPERIMENT NAME DATE T. SIGN

1. Management of the user and the domain

2. Configure DHCP

3. Setting up Local security policy

4. Use of Event viewer

5. Use of system monitor

6. Management of IIS and FTP server

7. Setting up of LAN

8. Setting up of router in windows server 2000

9. Use of utilities

10. Write a program to set up DNS server

11. Start and stop services from user windows

and command prompt
 EXPERIMENT NO -1

AIM: MANAGEMENT OF THE USERS & THE DOMAIN

Domain Name:

The term domain name has multiple meanings, all related to the:

 A name that is entered into a computer (e.g. as part of a Web site or other URL, or an e-mail
address) and then looked up in the global Domain Name System which informs the computer of
the IP address(es) with that name.
 The product that registrars provide to their customers.
 A name looked up in the DNS for other purposes.

They are sometimes colloquially (and incorrectly) referred to by marketers as "Web addresses".

 The authoritative definition is that given in the RFCs that define the DNS.

Domain names are hostnames that provide more easily memorable names to stand in for numeric
IP addresses. They allow for any service to move to a different location in the topology of the
Internet (or another internet), which would then have a different IP address.

Each string of letters, digits and hyphens between the dots is called a label in the parlance of the
domain name system (DNS). Valid labels are subject to certain rules, which have relaxed over
the course of time. Originally labels must start with a letter, and end with a letter or digit; any
intervening characters may be letters, digits, or hyphens. Labels must be between 1 and 63
characters long (inclusive). Letters are ASCII A–Z and a–z; domain names are compared case-
insensitively. Later it became permissible for labels to commence with a digit (but not for
domain names to be entirely numeric), and for labels to contain internal underscores, but support
for such domain names is uneven. These are the rules imposed by the way names are looked up
("resolved") by DNS. Some top level domains (see below) impose more rules, such as a longer
minimum length, on some labels. Fully qualified domain names (FQDNs) are sometimes written
with a final dot.

Translating numeric addresses to alphabetical ones, domain names allow Internet users to
localize and visit Web sites. Additionally since more than one IP address can be assigned to a
domain name, and more than one domain name assigned to an IP address, one server can have
multiple roles, and one role can be spread among multiple servers. One IP address can even be
assigned to several servers, such as with anycast and hijacked IP space.
Top-level domains

Every domain name ends in a top-level domain (TLD) name, which is always either one of a
small list of generic names (three or more characters), or a two characters territory code based on
ISO-3166 (there are few exceptions and new codes are integrated case by case). Top-level
domains are sometimes also called first-level domains.

The (gTLD) extensions are:

Generic top-level domains

Unsponsored .biz .com .edu .gov .info .mil .name .net .org

Sponsored .aero .cat .coop .int .jobs .museum .pro .travel

Infrastructure .arpa .root

Startup phase .mobi .post .tel

Proposed .asia .cym .geo .kid .kids .mail .sco .web .xxx

Deleted/retired .nato

Reserved .example .invalid .localhost .test

Pseudo-domains .bitnet .csnet .local .onion .uucp

Unofficial see Alternative DNS roots

See also: Country code top-level domains

 EXPERIMENT - 2

AIM: Windows XP to use DHCP

 Go to the Windows Control Panel (Start\Control Panel)

 Select "Network Connections"

 Right-click on the desired network adapter and select "Properties".

 Highlight Internet Protocol (TCP/IP) and select Properties

 Select or verify "Obtain an IP Address Automatically" is selected
 Note: If the radio button Obtain an IP address automatically is active, as in the image
above, your computer is configured to use DHCP.

 Click on the Advanced button

 Click on the DNS tab. Make certain the following DNS suffixes have been entered into the field
marked Append these DNS suffixes (in order)

 If these suffixes are not entered, click on the add button and add each of the following entries:
o alias.cs.cmu.edu
o cs.cmu.edu
o ri.cmu.edu
o edrc.cmu.edu
o cmu.edu
 Click on OK until the network dialogue boxes are closed
 Reboot your system
 EXPERIMENT NO-3

AIM: SETTING UP OF LOCAL SECURITY POLICIES

Windows XP Professional Edition allows full User Management and Security.

The permissions assigned to the Usergroups (assigned in User Management to users)
are defined in the Local Security Policies: select in the Control-panel :

"Administrative Tools" :

Select :

Local Security Policy

Select in the tree-view on the left : Security Settings / Local Policies / User Rights Assignment :
The "policies" are the permissions, which are/can be assigned to Usergroups
(and also to single usernames, although it is a kind of tradition to assign permissions to a
usergroup
and then make the user a member of the usergroup to get the permissions ).

Double click on a
policy/permission to
display
the list of usergroups,
which have already this
permission.

Note : all users created in

User Management
are automatically
member of the Usergroup
"Everyone"

To add a usergroup, use

the button
"Add User or Group..."
To get a lookup of the
usergroups and users,
select
"Advanced"

Use the button

"Find Now"
to display the
list of Users
and
UserGroups,
then
select to assign
the permission.
The Local Security Policies also define some rules for the use of passwords:

By default, users will be requested to change their passwords every 42 days

(unless you have declared a password to "never expire" in User management ).

Double-click the entries to change

the values.

You can change the password to

expire
already in less days or in more days
(max. 999).
 If you like to avoid password
changes,
change the value to 0.

The security policies also allow to define the behavior of the system, if somebody is entering
a bad/wrong password several times : it could be an intruder, making some guesses of passwords
and trying them:
 EXPERIMENT NO-4

AIM: USE OF EVENT VIEWER

Instructions :

 Go to Start, then to Control Panel, then to Administrative Tools, then to Event Viewer.
Alternately, got to Start, then to Run, and type in "eventvwr.msc" (without the quotes) and

press Enter. You'll see this:

 When the Event Viewer window opens, you'll see 2 panes (see picture above). The pane on the
left will contain the 3 categories of events (they are Application, Security, and System). The pane
on the right will reflect the messages for the category that is selected on the left. They will be
listed as Information, Warnings, or Errors. Errors are what will concern us here.

 Left click once on the Application category in the left hand pane - then check the right hand
pane for errors. Locate an error (example in the System description below) that occurred around
the time of the problem (there may or may not be one here depending on the type of error).
Then, right click on it and select "Properties". The information in the resulting window may be
able to be used by board members to help troubleshoot your problem. Here's an example of it:
 Next, we'll do the same thing for the Security category. You'll left click on the Security category
in the left hand pane, then will check for errors in the right hand pane. Locate an error (example
in the System description below) that occurred around the time of the problem (there may or
may not be one here depending on the type of error). Then, right click on it and select
"Properties". The information in the resulting window may be able to be used by board
members to help troubleshoot your problem. An example:

 Now, we'll do the same thing for the System category. You'll left click on the System category in
the left hand pane, then will check for errors in the right hand pane. An example:

Locate an error that occurred around the time of the problem (there may or may not be one
here depending on the type of error). Then, right click on it and select "Properties". The
 information in the window may be used by board members to help troubleshoot your problem.

Here's an example:

 Sometimes there will just be too many errors for you to pick just one out. In this case, generate
a report using the "Action" menu item. Select "Export list" from the dropdown menu, and save it
as a text file (that's the default). Then, open the text file by double clicking on it. Select the lines
around the time that the error occurred by highlighting it with your cursor. Then, right click on
the blue highlighting and select "Copy". Now, when you reply to your post, you can right click on
the post and select "Paste" to insert the lines into your post. With this information, someone
will be able to suggest which errors should be checked in detail.

 Lastly, a quick word about error messages. Often they will come in a format similar to this:
STOP: 0x0000007B (0xEB82784C, 0xC0000034, 0x00000000, 0x00000000)
These numbers are very important when diagnosing a problem with your system. They're
written in hexadecimal notation.
 EXPERIMENT-5

AIM: USE OF SYSTEM MONITOR.

The System Monitor tool included with Windows 2000, Windows XP and Windows Server 2003 is the
administrative tool that replaces the Performance Monitor tool included with Windows NT 4.0.

Here is a list of some improvements in the System Monitor tool:

 You can log specific counters and instances of an object, which helps you reduce the size of log
files.
 The Print Queue object is a new Performance object that allows you to monitor aspects of a
print queue.
 You can start the log on an event using Performance Logs and Alerts.
 Other Performance objects have also been added.
 A sample log file is included in Windows 2000.

To create a new log:

1. Right-click Counter Logs, click New Log Settings, type a name for the log, and then click OK.
2. On the General tab in Windows 2000,click Add to add the counters you want. On the General
tab in Windows XP or Windows Server 2003, click Add Counters.
3. On the Log Files tab, click the logging options you want.
4. On the Schedule tab, click the scheduling options you want.
 EXPERIMENT-6

AIM:How to setup and configure an FTP AND IIS server in window xp

The first thing you’ll need to setup your own FTP server in Windows is to make sure you have
Internet Information Services (IIS) installed. Remember, this only comes with Windows XP
Professional or Windows Vista Business or higher.

Click on Start, Control Panel and go to Add/Remove Programs. Then click on Add/Remove
Windows Components.

In the components wizard, scroll down until you see IIS in the list and check it off. Before you
click Next though, make sure you click on Details and then check off File Transfer Protocol
(FTP) Service.
Click OK and then click Next. Windows will go ahead and install the necessary IIS files along
with the FTP service. You may be asked to insert your Windows XP or Windows Vista disk at
this point.

Setup and configure IIS for FTP

Once IIS has been installed, you may have to restart your computer. Now we want to go ahead
and open the IIS configuration panel to setup our FTP server. So go to Start, then Control Panel
and click on Administrative Tools. You should now see an icon for Internet Information
Services.

When you open IIS for the first time, you’ll only see your computer name in the left hand menu.
Go ahead and click the + symbol next to the computer name and you’ll see a couple of options
like Web Sites, FTP Sites, etc. We’re interested in FTP Sites, so expand that out also. You
should see Default FTP Site, click on it.
You’ll notice after you click on the default FTP site that there are a couple of buttons at the top
that look like VCR buttons: Play, Stop, and Pause. If the Play button is greyed out, that means
the FTP server is active. Your FTP server is now up and running! You can actually connect to it
via your FTP client software. I use Smart FTP, but you can use whatever you like best.

Open your FTP client software and type in localhost as the host name and choose Anonymous
for the login. Connect and you should now see an empty folder.

Ok, so that’s step 1! Now where the heck is this folder that you are currently viewing? Well the
default FTP site is actually located in C:\Inetpub\ftproot. Open this directory and dump some
files into it.
Now refresh on your FTP client and you should now see your files listed!

So you now have an up and running FTP server on your local computer.

Installing IIS on Windows XP Pro

If you are running Windows XP Professional on your computer you can install Microsoft's web server,
Internet Information Server 5.1 (IIS) for free from the Windows XP Pro installation CD and configure it to
run on your system by following the instructions below: -

1. Place the Windows XP Professional CD-Rom into your CD-Rom Drive.

2. Open 'Add/Remove Windows Components' found in 'Add/Remove Programs' in the 'Control Panel'.

3. Place a tick in the check box for 'Internet Information Services (IIS)' leaving all the default installation
settings intact.

4. Once IIS is installed on your machine you can view your home page in a web browser by typing
'http://localhost' (you can substitute 'localhost' for the name of your computer) into the address bar of
your web browser. If you have not placed your website into the default directory you should now be
looking at the IIS documentation.

5. If you are not sure of the name of your computer right-click on the 'My Computer' icon on your
desktop, select 'Properties' from the shortcut menu, and click on the 'Computer Name' tab.

6. Your default web directory to place your website in is 'C:\Inetpub\wwwroot', but if you don't want to
over write the IIS documentation found in this directory you can set up your own virtual directory
through the 'Internet Information Services' console.
7. The 'Internet Information Services' console can be found in the 'Administration Tools' in the 'Control
Panel' under 'Performance and Maintenance', if you do not have the control panel in Classic View.

8. Double-click on the 'Internet Information Services' icon.

8. Once the 'Internet Information Services' console is open you will see any IIS web services you have
running on your machine including the SMTP server and FTP server, if you chose to install them with IIS.

9. To add a new virtual directory right click on 'Default Website' and select 'New', followed by 'Virtual
Directory', from the drop down list.
7. Next you will see the 'Virtual Directory Creation Wizard' from the first screen click the 'next' button.

9. You will then be asked to type in an 'Alias' by which you will access the virtual directory from your
web browser (this is the name you will type into your web browser after 'localhost' to view any web
pages you place in the directory).

10. Next you will see a 'Browse...' button, click on this to select the directory your website pages are in
on your computer, after which click on the 'next' button to continue.

11. On the final part of the wizard you will see a series of boxes, if you are not worried about security
then select them all, if you are and want to run ASP scripts then check the first two, followed by the
'next' button.

12. Once the virtual directory is created you can view the web pages in the folder by typing
'http://localhost/aliasName' (where 'aliasName' is, place the alias you called the virtual directory) into
the address bar of your web browser (you can substitute 'localhost' for the name of your computer if
you wish).
 EXPERIMENT NO-7

AIM: SETTING UP OF LOCAL AREA NETWORK (LAN).

One of the advanced troubleshooting methods used for Internet connection issues
is configuring the Local Area Network settings. For Windows XP computers, this is the Network and
Internet Connection properties. This T/S is only applicable to cable-internet connections, for either
wired or wireless network.

The LAN properties need to be configured or reconfigured correctly to avoid problems with your
Internet connection. Here’s how to configure LAN settings in Windows XP computers.

Step 1:
To get started, click on the start button or menu found on the taskbar of your computer.

Step 2:
From the list of sub-menu that appears, select and click on the Control Panel item.

Step 3:
Select either the Category View or Classic View to get in to the Network and Internet Connections
window.

Step 4:
Right click on the Local Area Connection item, for you to open the Network Connections window. Then
right click on the Network connection icon to check and configure the settings and protocols.

Step 5:
In the Local Area Connection properties, you can find the General, Authentication and Advanced Tabs.
You will use them to check the IP addresses.

Step 6:
Select on the Internet Protocol (TCP/IP) item under the General tab and click on the Properties button.
You will be prompted with the IP address of your computer. There are two types of IP address: static
and dynamic. Either IP types are used in LAN network settings. Moreover, they have to be valid to avoid
problems with the Internet connection.
Step 7:
You can change your IP address if it is static by performing the Release and Renew processes. You can
either do in the TCP/IP window; otherwise, use the command prompt to do so. Changing of IP address
will refresh the network connection between the computer and the networking device.

Step 8:
After reconfiguring the IP address, check if there are positive changes with the connection. If the IP
address is successfully changed and it is a valid IP, then there is no problem with the Network Adapters,
else, you need to refresh or reinstall the appropriate network adapter for your computer. The network
adapter communicates with the networking device, thus, taking a valid IP address assigned by the
network.
If the NIC is busted, then there will be a problem with the Internet connection.

If unfortunately, the connection issue is not resolved after the reconfiguration of the LAN settings,
contact the Original Equipment Manufacturer (OEM) for further assistance. You may also need to call
your Internet Service Provider to check if there are outages that may be the cause of the network
interruption.

Windows XP

How to set up a LAN in Windows XP

Once you've set up your hardware (i.e. slotted in the network card and connected all of the
computers - actually you don't have to connect to another computer at this stage, but you must
have installed the network card) boot up your computer (for instructions on installing your
network card, see the instructions that come with it).

Chances are the network card you have is PnP (Plug and Play) compatible. If so Windows should
detect the network card and (provided you follow the on screen instructions correctly) complete
the installation process (it probably gave your network card the Realtek drivers). Your computer
may rebooted automatically to complete the installation process.

Once installed you can either follow the Windows XP networking wizard or set it up manually.
The easiest option is to use the wizard - then you can manually tweak it later if you want to.

To start the New Connection wizard either:

 Boot up your PC after installing your new network card - it should then appear
 Insert your Windows XP CD and choose the New network Connection Wizard option
 Start | Control Panel | Network Connections | Create a new connection

This will bring up the network connection wizard screen:

Select Next
Select the 'Set up a home or small office network' option and then press Next

Select Finish to close this Wizard and then open the Network Setup wizard

Select Next
Select Next

Select the required connection method (view the examples if you are unsure).
If you want your computer to connect directly to the Internet, you mucst already have this set up
(e.g. a modem, ISDN, ADSL or Cable connection). If not you will asked to set up the connection
first before being allowed to continue with this wizard.

If you choose to connect to the Internet via another computer or a gateway, the wizard will
search for it later.

Select other if you do not have an available Internet connection or if your PC connects to a hub
which in turn connects to an Internet gateway or modem

Then select Next

Enter a Computer name and description (optional). Then select Next

Enter a name for the Workgroup, or accept the default name of 'MSHOME'. Then select Next

Select Next and Windows will wizz off and set everything up for you!

Once completed, run the wizard on any remaining Windows XP based PCs on the network. With
any luck you will have a LAN up and running within 5 - 10 minutes and all of your PCs will be
able to connect to the internet!

Now just follow the next few pages of this site to configure your LAN so that you can share files,
printers.

Special note if some of the PCs on your LAN are running operating systems other than
Windows 2000, NT4 and XP.

In order for people on the other operating systems to view files on your computer you will need
to enable the 'guest' account on your computer. This is disabled by default for security reasons.
To enable it go to:
Start | Settings | Control Panel | Administrative Tools | Computer Management | Local
Users and Groups | Users

Double click on Guest and then un-tick the 'Account is Disabled' checkbox.

All computers on your LAN should now be able to see the files on the PC that you have set up
sharing on.

Once everyone has restarted their computers, double click on the Network icon on your desktop
(also in Explorer). You should now see the names of all of the computers connected to the
network. If not, try pressing the F5 key to refresh your display (although this should be done
automatically). If you still can't see everyone, ask EVERYONE to reboot their computer - this is
sometimes necessary. if you still can't see everyone's computer, check your settings; you
probably overlooked something.
 EXPERIMENT NO-8

AIM: SETTING UP ROUTER IN WINDOW 2000 SERVER.

In previous discussions about Windows 2000 RRAS, I’ve explained how to deploy a Windows 2000
remote access server, including how to configure the server to support VPN connections using PPTP
and/or L2TP. In this Daily Drill Down, I’ll take a look at a topic you might already have used without
realizing it: using a Windows 2000 RRAS server as a network router. I’ll touch on dynamic routing
through RIP and OSPF, but I’ll focus first on static routing. In an upcoming Daily Drill Down, I’ll cover RIP
and OSPF in detail.
As a refresher, Windows 2000’s RRAS service supports several different capabilities, one of which is
supporting dial-up clients through POTS, ISDN, and other connectivity options. You can use integrated
Windows authentication or rely on a RADIUS server (which could be the RRAS server) to authenticate
clients. PPTP and L2TP support enable the RRAS server to function as a VPN server, giving remote clients
a means of establishing a secure, private network connection to the LAN through a public network such
as the Internet. Typically, the VPN connections come in through a dedicated, 24/7 Internet connection.
Why would I want to use Windows 2000 for routing?
Because you can? Okay, that’s not really a good answer. But you’ve probably wondered why you would
use a Windows 2000 server as a router, rather than using a dedicated router from Cisco, Bay Networks,
or another manufacturer. In a lot of situations, a dedicated router makes more sense and is generally
less expensive. There are situations, however, where it makes sense to use Windows 2000 for routing.

For example, assume you have three network segments, which currently are not interconnected, and
you are setting up a remote access server on one of those segments. At the same time, you want to
provide dial-up capability to each segment by remote clients. In this situation, it makes sense to install a
single RAS server and let it provide routing services to all segments. Windows 2000 can fulfill both roles
with no problem. So, using Windows 2000 as a router makes sense when you’re providing services to
your LAN that require routing and no other routers are currently online to handle the traffic, or you
don’t want the additional expense and management of a dedicated router in addition to your server.

Another reason to use Windows 2000 for routing is to provide DHCP Relay services for DHCP clients that
reside on network segments where there is no DHCP server. Windows 2000 includes a DHCP Relay agent
that provides this functionality in conjunction with RRAS.

A third reason to use Windows 2000 RRAS for routing is ease of use. Although router manufacturers
have come a long way toward improving the configuration and management interfaces for their routers,
the GUI management tools in Windows 2000 make it very easy to configure and manage Windows 2000
routers.

A Windows 2000 RRAS server can function as a dedicated router, connecting other routers continuously,
or it can function as a demand-dial router. In this latter scenario, the router dials and connects to a
remote router only when traffic that requires routing to the remote network comes to the router.
Demand-dial routing is often used to reduce connectivity costs. If you only send traffic over a metered
connection once or twice a day, for example, why pay for a full-time connection? With demand-dial
routing, the router dials the remote network when traffic needs to be routed, then disconnects
automatically after a defined period of inactivity. This helps keep costs down by keeping the connection
live only when needed.

Understanding IP routing
Without IP routing, the Internet and many private networks would stop functioning instantly. Routing is
a crucial aspect of IP networking. Understanding how routing works is the place to start when you’re
thinking about setting up a Windows 2000 RRAS server to function as a router.

The primary function of a router, whether a dedicated box or a Windows 2000 router, is to route
network packets between different network segments. When you open a browser to connect to a Web
site, for example, your computer looks up the IP address of the remote site through DNS and then sends
network packets to the remote site’s IP address to request the site’s content.

Your network router, identified by your workstation at its default gateway, receives the traffic, analyzes
the destination IP address for the packets, and determines that the packets are destined for a network
segment beyond your own. Based on its routing tables, the router sends the packet out on the
appropriate interface to another router. The traffic gets routed through potentially several routers and
eventually reaches the server where the site is hosted. Then, the process happens again in reverse for
the traffic coming from the server to your computer.

Routers generally are connected to at least two subnets and, in effect, the router resides as a node in
each of the subnets to which it is connected. This gives the router local connectivity to each of the
subnets on which it resides and is the mechanism by which routing is possible. Figure A illustrates a
router connected to three different subnets, which in turn are connected to other subnets and
eventually the Internet. Each router is sometimes referred to as a “hop,” and a packet’s hop count is
increased by one each time it passes through another router (more about this later).
As the figure illustrates, router A connects subnet 1 to subnets 2 and 3, which are in turn connected to
the Internet by other routers, B and C. Router A therefore is assigned three IP addresses, one in each
subnet, making it a member of each subnet and directly accessible to the nodes in each connected
subnet. When a client in subnet 1 sends traffic destined for subnet 3, the traffic is directed to the client’s
default gateway, which in this case is the IP address of the router at A1. The default gateway is defined
in the client computer’s TCP/IP properties.

The router analyzes the packets when they come in to determine the destination address. Discovering
that the traffic is destined for subnet 3, the router directs the traffic out the interface A3, based on its
internal knowledge that the destination node must reside on subnet 3.

But what happens when the traffic is destined for a subnet that resides beyond the router’s locally
connected segments, such as a remote Internet server? The router uses its routing table to determine
which interface to use to route the traffic. The router’s default route, which you configure, is the route
used when traffic is destined for an address that resides beyond the router’s local interfaces. The default
route specifies the IP address of the router to which all traffic that isn’t destined for a known interface
(also determined by the routing table) should be routed. So, the router analyzes the packet, recognizes
that the destination IP address doesn’t match the subnets of defined routes in the routing table, and
directs the packet to the default route. The router specified by the default route analyzes the packet and
routes it based on its routing table.

Each route in a routing table falls into one of three categories:

 Network route: Provides a route to a specific network ID and all addresses within that network.
 Host route: Provides a route to a specific host. A host route entry defines the host IP address as
well as the network address.
  Default route: Used to route traffic for which there is no corresponding network route or host
route.

The routing table contains routing entries against which the router checks the destination address of all
packets to determine how to route each packet. Each entry in the routing table has specific general
properties:

 Network ID, host address, subnet mask: These properties serve to identify the destination
network ID or host address and the destination’s subnet. If the router determines that the
destination address stored in the packet’s header matches these properties in a routing table
entry, it forwards the packet to the forwarding address associated with the route (see next).
 Forwarding address: This is the address of the remote router to which the router forwards
packets that match the network ID, host address, or subnet defined by the entry.
 Interface: This property specifies the local router port through which the traffic should be
routed for packets that satisfy the criteria of the routing table entry.
 Metric: This value identifies the relative cost of the route, which is based on actual connection
cost, available bandwidth, and other factors that you determine when you create a route. If
more than one route exists for the same destination, the router uses the one with the lowest
metric, if available.

Here’s a summary of the whole process: A packet comes into the router. The router analyzes the
destination address in the packet’s header. The router then examines its routing table, attempting to
match the packet’s destination address against the network ID, host address, or subnet properties of
each routing table entry. If a match is found, the router directs the packet to the forwarding address
defined by the matching routing table entry, using the interface and metric to decide how to physically
route the packet out of the router. If the packet’s destination address doesn’t match any of the routing
table entries, the router sends the packet to the forwarding address defined by the router’s default
route. If no default route is defined, the packet is rejected and routing fails. The routing table is
therefore the blueprint by which the router accomplishes its job.

How are routing entries added to the routing table? A router can learn its routes dynamically from other
routers or it can use statically defined routes, or static routes. With dynamic routes, routers
communicate with one another to share learned routes, which enables routes to propagate to adjacent
routers. Routing protocols are used to enable the routers to share this routing information. The two
most common routing protocols are Routing Information Protocol (RIP) and Open Shortest Path First
(OSPF), both of which are supported by Windows 2000.

The administrator who configures the router creates static routes manually. In a small network with few
subnets, static routes are an effective means of routing all traffic. As the number of routers grows,
however, dynamic routing becomes more desirable because of the reduced management overhead. You
don’t have to manage existing routes or create new ones when another segment is added to the
network. Instead, the router learns its routing table from adjacent routers automatically when the
router comes online.

Overview of RIP
Of the two routing protocols included with Windows 2000, RIP is easier to configure. RIP is limited to a
maximum hop count of 15, making RIP useful for small to medium-sized installations. Any address more
than 15 hops away is deemed unreachable by the router.

Each time a router boots, it recreates its routing table. The routing table initially only contains the
routing table entries for physically connected networks. A router using RIP periodically broadcasts
announcements regarding routes, which enables adjacent routers to modify their routing tables. So,
after a router comes online, it begins using RIP announcements to build its routing table. Also, RIP
provides for triggered updates in addition to broadcast updates. These triggered updates occur when a
router detects a network change, such as an interface going down. The router then broadcasts the
change to adjacent routers, which modify their routing tables accordingly. When the interface comes
back up, the router that recognizes the change broadcasts a triggered update to adjacent routers, which
again modify their routing tables to accommodate the change.

Windows 2000 supports RIP version 1 and version 2. RIP v2 provides additional features over RIP v1,
such as authentication for security and route filtering. RIP v2 also supports multicast broadcast of RIP
announcements and several other features. RIP v1 routers are forward compatible with RIP v2 routers,
enabling them to coexist.

Overview of OSPF
OSPF was developed to address the needs of large networks, such as the Internet. Each OSPF router
maintains a link-state database (LDB) that contains link-state advertisements (LSAs) from adjacent
routers. The LSA contains information about a router, its connected networks, and configured costs. The
cost is similar to a route metric discussed earlier, in that it defines the relative cost of using the route.
OSPF uses an algorithm to calculate the shortest path for routing based on the information contained in
its LDB, making it a very efficient means of routing. Adjacent routers recalculate and synchronize their
LDBs as network changes occur, such as network interfaces going down or coming online.

OSPF is more complicated to configure than RIP. Its performance advantages are geared primarily
toward very large networks, so if you’re setting up a router for a small or medium-sized network, RIP is
generally the better option. Where network size is a factor, however, OSPF is the better choice.

Unicast routing vs. multicast routing

Another important aspect to understand about routing is the difference between unicast routing and
multicast routing. In unicast routing, a packet is sent from one node to only one other node, as
illustrated in Figure B. This is the most common type of routing and the one you use every time you
open a Web browser and browse an Internet site, retrieve your e-mail, move a file with ftp, and perform
most other common IP-based network tasks.
In multicast routing, however, traffic is broadcast from one node to many nodes, as illustrated in Figure
C. Multicasting is most commonly used for audio and video conferencing, enabling packets to be
efficiently transmitted to multiple clients from a single host. Without multicasting, the packets would
have to be transmitted multiple times to each client, generating a considerably larger amount of
network traffic and imposing more overhead on the server. Plus, as you can imagine, conferencing
would be difficult to set up without multicasting, as the conferencing server would need to be
preconfigured with the list of all participants. With multicasting, the participants simply listen on a
designated multicasting address, which can be allocated by a DHCP server to automate configuration.
 Examples of conferencing with and without multicasting

Configuring a unicast router

As with other RRAS configurations, you can use the RRAS wizard to configure a Windows 2000 server as
a router. Setup installs RRAS by default, so you only need to enable and configure the server according
to your routing needs. To start the RRAS wizard, open the RRAS console from the Administrative Tools
folder. Right-click the server and choose Configure And Enable Routing And Remote Access. In the
wizard, select the option to configure a network router. The wizard prompts you for the following
information:

 Protocols: Select the protocols to be supported for routing, such as TCP/IP and/or IPX. If the
protocols are not installed, the wizard gives you the option of adding them. By default, all
installed protocols are enabled for routing but you can choose to disable some if you don’t want
the protocol to be routed.
 Use demand-dial connections: You can choose to enable demand-dial routing at this point or
accomplish the task later.
In addition to configuring the router through the wizard, you also can enable routing manually. You need
to choose this latter option if the server is already configured and enabled for RRAS (such as a VPN
server) and you want to add routing to the server’s list of roles.

To enable routing for a server that already has RRAS enabled, open the RRAS console from the
Administrative Tools folder. Right-click the server and choose Properties. Select the Router check box
and then select the type of routing you want to support, either LAN or LAN and demand-dial. Then click
OK.

Next, configure the IP address for which RRAS performs routing on that interface. By default, Windows
2000 uses the first interface to process routing tasks on that interface, and on interfaces with only one
address no configuration is needed. If the interface has multiple addresses, however, you’ll need to
reconfigure RRAS if the default address is not the one you want to use. To configure the address, open
the RRAS console, expand the server, and expand the IP Routing branch. Click General and, in the right
pane, right-click the interface you want to modify and choose Properties. Use the Configuration page to
set the IP address, subnet mask, and default gateway (if needed) for the interface. To set the metric for
the interface, click Advanced.

Configuring a router with static routes

At this point I assume you have the server enabled for routing and have configured the desired address
on each interface. Now it’s time to think about how you’ll implement routing. As mentioned earlier, you
can use static routes, RIP, or OSPF (if the router only routes traffic between two subnets, you don’t need
to worry about creating routes or using RIP or OSPF). Let’s take a look at static routes, which are a good
option if you’re setting up your Windows 2000 RRAS router in a small network.

For this example we’ll use privately addressed network segments. Figure D shows our sample network
structure. We’ll work on configuring router B, which we’ll assume has two network interfaces. As Figure
D illustrates, router B resides on subnets 192.168.0.n and 192.168.1.n. The IP addresses of the router’s
interfaces are 192.168.0.20 (LAN 0) and 192.168.1.1 (LAN 1). In these examples I’ve renamed the
network interfaces from their default names of Local Area Connection and Local Area Connection 2 to
LAN 0 and LAN 1, respectively. It’s a good idea on multihomed systems to rename the interfaces to help
you keep track of what’s what. To rename the interfaces, open the Network And Dial-Up Connections
folder, right-click an interface, and choose Rename.
Let’s add a static route at router B to route traffic to the 192.168.2.0 subnet (subnet 2) through interface
LAN 1. To add a static route, first open the RRAS console. Expand the IP Routing branch and click Static
Routes. Either right-click in the right pane or right-click Static Routes and choose New Static Route. RRAS
displays the Static Route dialog box in which you provide the following data:

 Interface: Choose the network interface that RRAS should use to route traffic that meets the
static route criteria. In this example, we want to configure a static route for traffic destined for
192.168.2.0 to be routed through LAN 1, so select the LAN 1 interface.
 Destination: Rather than create a host route, we’ll create a network route. Enter the network ID
of the destination network, which in this example is 192.168.2.0. Remember that the router
compares the destination IP address of incoming packets against this network address to
determine if the route entry matches and the route is appropriate for routing the packets. You
can specify a network address, host address, or use 0.0.0.0 for this value (this latter option
creating a default route). Use the low network address to specify a network address, as we did
in this example, or specify the actual IP address of the host if creating a host route.
 Network mask: Specify the subnet mask of the destination network or host. In this example,
enter 255.255.255.0, the subnet mask for our Class C private network.
 Gateway: Specify the IP address to which packets matching the route criteria are routed. In this
example, you need to specify the IP address of router C on the 192.168.1.0 subnet. As you can
see from Figure D, the address to enter is 192.168.1.2.
 Metric: Enter the relative cost for the route by specifying a metric. If more than one route exists,
the one with the lowest metric is used to route the traffic if that route is available.
  Use this route to initiate demand-dial connections: If you have configured at least one demand-
dial interface for the router, this option is available. Select this option if you want the router to
initiate a demand-dial connection when it receives traffic that matches the selected route.

Next, you create a static route to accommodate the 192.168.3.0 subnet. The data for this static route is
the same as the one you just created, except the destination network address is 192.168.3.0. The
Gateway is the same as in the previous route. The static routes you set up on Router C handle the traffic
from that point, routing it to Router D.

Finally, we should create a default route on Router B that directs all other traffic not destined for
subnets 1, 2, or 3 to Router A, with the assumption that the traffic is destined for a public address on the
Internet. So, create another static route on Router B using the following values:

 Interface: LAN 0
 Destination: 0.0.0.0
 Network mask: 0.0.0.0
 Gateway: 192.168.0.1
 Metric: As desired
 Use this route to initiate demand-dial connections: As needed

Conclusion
You can see that setting up static routes takes a little work but can be an effective means of configuring
routing for small networks. As the number of routers you manage grows, you’ll likely turn to RIP and/or
OSPF to provide dynamic routing. While RIP and OSPF are a little more complicated to set up, they are
much easier to manage. In an upcoming Daily Drill Down, we’ll take a detailed look at both protocols, as
well as demand-dial routing and multicast routing.
The authors and editors have taken care in preparation of the content contained herein but make no
expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No
liability is assumed for any damages. Always have a verified backup before making any changes.
 EXPERIMENT NO-9

AIM:USE OF UTILITIES

a) PING

A utility to determine whether a specific IP address is accessible. It works by sending a packet to the
specified address and waiting for a reply. PING is used primarily to troubleshoot Internet connections.
There are many freeware and shareware Ping utilities available for personal computers.

ping is a computer network tool used to test whether a particular host is reachable across an IP
network. Ping works by sending ICMP “echo request” packets to the target host and listening for
ICMP “echo response” replies. Using interval timing and response rate, ping estimates the
round-trip time and packet loss rate between hosts.

Sample pinging

The following is a sample output of pinging www.google.com under Linux with the iputils
version of ping:

$ ping www.google.com
PING www.l.google.com (64.233.183.103) 56(84) bytes of data.
64 bytes from 64.233.183.103: icmp_seq=1 ttl=246 time=22.2 ms
64 bytes from 64.233.183.103: icmp_seq=2 ttl=245 time=25.3 ms
64 bytes from 64.233.183.103: icmp_seq=3 ttl=245 time=22.7 ms
64 bytes from 64.233.183.103: icmp_seq=4 ttl=246 time=25.6 ms
64 bytes from 64.233.183.103: icmp_seq=5 ttl=246 time=25.3 ms
64 bytes from 64.233.183.103: icmp_seq=6 ttl=245 time=25.4 ms
64 bytes from 64.233.183.103: icmp_seq=7 ttl=245 time=25.4 ms
64 bytes from 64.233.183.103: icmp_seq=8 ttl=245 time=21.8 ms
64 bytes from 64.233.183.103: icmp_seq=9 ttl=245 time=25.7 ms
64 bytes from 64.233.183.103: icmp_seq=10 ttl=246 time=21.9 ms

--- www.l.google.com ping statistics ---

10 packets transmitted, 10 received, 0% packet loss, time 9008ms
rtt min/avg/max/mdev = 21.896/24.187/25.718/1.619 ms
This output shows that www.google.com is a DNS CNAME record for www.l.google.com
which then resolves to 64.233.183.103. The output then shows the results of making 10 pings
to 64.233.183.103 with the results summarized at the end.

 smallest ping time was 21.896 milliseconds

 average ping time was 24.187 milliseconds
 maximum ping time was 25.718 milliseconds
 mean deviation time was 1.619 milliseconds

b) TRACEROUTE

A utility that traces a packet from your computer to an Internet host, showing how many hops the
packet requires to reach the host and how long each hop takes. If you're visiting a Web site and pages
are appearing slowly, you can use traceroute to figure out where the longest delays are occurring.

The original traceroute is a UNIX utility, but nearly all platforms have something similar.
Windows includes a traceroute utility called tracert. In Windows, you can run tracert by
selecting Start->Run…, and then entering tracert followed by the domain name of the host. For
example:

tracert www.pcwebopedia.com

Traceroute utilities work by sending packets with low time-to-live (TTL) fields. The TTL value
specifies how many hops the packet is allowed before it is returned. When a packet can't reach its
destination because the TTL value is too low, the last host returns the packet and identifies itself.
By sending a series of packets and incrementing the TTL value with each successive packet,
traceroute finds out who all the intermediary hosts are.

Traceroute (tracepath on modern Linux systems, tracert on Windows operating system) is a

computer network tool used to determine the route taken by packets across an IP network.

Implementation

traceroute works by increasing the "time-to-live" value of each successive batch of packets sent.
The first three packets have a time-to-live (TTL) value of one (implying that they make a single
hop). The next three packets have a TTL value of 2, and so on. When a packet passes through a
host, normally the host decrements the TTL value by one, and forwards the packet to the next
host. When a packet with a TTL of one reaches a host, the host discards the packet and sends an
ICMP time exceeded (type 11) packet to the sender. The traceroute utility uses these returning
packets to produce a list of hosts that the packets have traversed en route to the destination.
traceroute may not list the real hosts, it indicates that the first host is at one hop, the second host
at two hops. IP does not guarantee that all the packets take the same route.
On modern Unix and Linux-based operating systems, the traceroute utility by default uses UDP
datagrams with a destination port number starting at 33434. The traceroute utility usually has an
option to specify use of ICMP echo request (type 8) instead, as used by the Windows tracert
utility. There are also traceroute implementations that use TCP packets, such as tcptraceroute or
Layer Four Trace. A new utility, pathping, was introduced with Windows NT, combining ping
and traceroute functionality. Matt's Trace Route (MTR) is an enhanced version of icmp
traceroute available for Unix and Windows systems under a GNU GPL license. All
implementations of traceroute rely on ICMP (type 11) packets being sent to the originator.

c) IPCONFIG

Ipconfig (sometimes written as IPCONFIG) is a command line tool used to control the network
connections on Windows NT/2000/XP machines. There are three main commands: "all",
"release", and "renew". Ipconfig displays all current TCP/IP network configuration values and
refreshes Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS)
settings. Used without parameters, ipconfig displays the IP address, subnet mask, and default
gateway for all adapters.

ipconfig is a command line tool used to control the network connections on Windows
NT/2000/XP/Vista machines. There are three main commands: /all, /release and /renew. (For a
full list of commands, use "ipconfig /?".) A GUI tool named wntipcfg with similar functionality
exists as well. On Windows 9x machines, only the GUI tool winipcfg is available. The Unix
equivalent of 'ipconfig' is ifconfig.

The following instructions tell you how to find your IP address under Windows 2000 and
Windows XP. These instructions will also help you find your MAC (hardware) address, DHCP
server, DNS server and other useful information. They might help you troubleshoot a bad ResNet
connection too. If you have Windows 95, 98 or Me, check out the instructions for using winipcfg
instead.

Go to the start menu and select Run.... Then type cmd in the box and click OK.
 At the C:\> prompt type ipconfig . Then press Enter. Your IP address, subnet mask and
default gateway will be returned to you. If your IP address is 192.168.x.x, 10.x.x.x, or
172.16.x.x, then you are receiving an internal IP address from a router or other device. The IP
address that the world sees is that of the router. If you are receiving a 169.254.x.x address, this is
a Windows address that generally means your network connection is not working properly. On
ResNet, the only valid IP addresses will begin with 152.7.

If you want more detailed information about your network connection, type ipconfig /all at
the prompt. Here you can get the same information as ipconfig with the addition of your MAC
(hardware) address, DNS and DHCP server addresses, IP lease information, etc. If your IP
address is 192.168.x.x, 10.x.x.x, or 172.16.x.x, then you are receiving an internal IP address from
a router or other device. The IP address that the world sees is that of the router. If you are
receiving a 169.254.x.x address, this is a Windows address that generally means your network
connection is not working properly.

If you are having trouble with your ResNet connection, it may be fixed by releasing and
renewing your IP address. Type ipconfig /release at the prompt and press enter. Then type
ipconfig /renew and press enter again. If your connection is okay, a valid IP address, subnet
mask and default gateway will be returned to you after a few seconds.
d) IFCONFIG
There are a lot more parameters to ifconfig than we have described above. Its normal invocation is this:

ifconfig interface [[-net|-host] address [parameters]]

interface is the interface name, and address is the IP-address to be assigned to the interface. This may
either be an IP-address in dotted quad notation, or a name ifconfig will look up in /etc/hosts and
/etc/networks. The -net and -host options force ifconfig to treat the address as network number or host
address, respectively.

If ifconfig is invoked with only the interface name, it displays that interface's configuration.
When invoked without any parameters, it displays all interfaces you configured so far; an option
of -a forces it to show the inactive ones as well. A sample invocation for the Ethernet interface
eth0 may look like this:

# ifconfig eth0
eth0 Link encap 10Mbps Ethernet HWaddr 00:00:C0:90:B3:42
inet addr 191.72.1.2 Bcast 191.72.1.255 Mask 255.255.255.0
UP BROADCAST RUNNING MTU 1500 Metric 0
RX packets 3136 errors 217 dropped 7 overrun 26
TX packets 1752 errors 25 dropped 0 overrun 0
The MTU and Metric fields show the current MTU and metric value for that interface. The metric value is
traditionally used by some operating systems to compute the cost of a route. doesn't use this value yet,
but defines it for compatibility nevertheless.

The RX and TX lines show how many packets have been received or transmitted error free, how
many errors occurred, how many packets were dropped, probably because of low memory, and
how many were lost because of an overrun. Receiver overruns usually happen when packets
come in faster than the kernel can service the last interrupt. The flag values printed by ifconfig
correspond more or less to the names of its command line options; they will be explained below.

The following is a list of parameters recognized by ifconfig with the corresponding flag names
are given in brackets. Options that simply turn on a feature also allow it to be turned off again by
preceding the option name by a dash (-).

up

This marks an interface ``up'', i.e. accessible to the IP layer. This option is implied when an
address is given on the command line. It may also be used to re-enable an interface that has
been taken down temporarily using the down option. (This option corresponds to the flags UP
RUNNING.)

down

This marks an interface ``down'', i.e. inaccessible to the IP layer. This effectively disables any IP
traffic through the interface. Note that this does not delete all routing entries that use this
interface automatically. If you take the inter- face down permanently, you should to delete
these routing entries and supply alternative routes if possible.

netmask mask

This assigns a subnet mask to be used by the interface. It may be given as either a 32-bit
hexadecimal number preceded by 0x, or as a dotted quad of decimal numbers. that involve only
two hosts. This option is needed to config- ure, for example, SLIP or PLIP interfaces.

pointopoint

address This option is used for point-to-point IP links that involve only two hosts. This option is
needed to config- ure, for example, SLIP or PLIP interfaces. (If a point-to-point address has been
set, ifconfig displays the POINTO- POINT flag.)

broadcast address

The broadcast address is usually made up from the network number by setting all bits of the
host part. Some IP implementations use a different scheme; this option is there to adapt to
these strange environments. (If a broadcast address has been set, ifconfig displays the
BROADCAST flag.)

metric number

This option may be used to assign a metric value to the routing table entry created for the
interface. This metric is used by the Routing Information Protocol (RIP) to build rout- ing tables
for the network.(8) The default metric used by ifconfig is a value of zero. If you don't run a RIP
 daemon, you don't need this option at all; if you do, you will rarely need to change the metric
value.

mtu bytes

This sets the Maximum Transmission Unit, which is the maximum number of octets the interface
is able to handle in one trans- action. For Ethernets, the MTU defaults to 1500; for SLIP
interfaces, this is 296.

arp

This is an option specific to broadcast networks such as Eth- ernets or packet radio. It enables
the use of ARP, the Address Resolution Protocol, to detect the physical addresses of hosts
attached to the network. For broadcast networks, is on by default.

-arp

Disables the use of ARP on this interface.

promisc

Puts the interface in promiscuous mode. On a broadcast net- work, this makes the interface
receive all packets, regardless of whether they were destined for another host or not. This
allows an analysis of network traffic using packet filters and such, also called Ethernet snooping.
Usually, this is a good technique of hunting down network problems that are otherwise hard to
come by. On the other hand, this allows attackers to skim the traffic of your network for
passwords and do other nasty things. One protection against this type of attack is not to let
anyone just plug in their computers in your Ethernet. Another option is to use secure
authentication protocols, such as Kerberos, or the SRA login suite.(9) (This option corresponds
to the flag PROMISC.)

-promisc

Turns off promiscuous mode.

allmulti

Multicast addresses are some sort of broadcast to a group of hosts who don't necessarily have
to be on the same subnet. Multicast addresses are not yet supported by the kernel. (This option
corresponds to the flag ALLMULTI.)

-allmulti

Turns off multicast addresses.

e) NETSTAT

Netstat is a command-line tool that displays a list of the active network connections the
computer currently has, both incoming and outgoing. It is available on Unix, Unix-like, and
Windows NT-based operating systems.

On the Windows platform, netstat information can be retrieved by calling the GetTcpTable and
GetUdpTable functions in the IP Helper API, or IPHLPAPI.DLL. Information returned includes
local and remote IP addresses, local and remote ports, and (for GetTcpTable) TCP status codes.
In addition to the command-line netstat.exe tool that ships with Windows, there are GUI-based
netstat programs available.

Syntax

netstat [-a] [-e] [-n] [-o] [-p Protocol] [-r] [-s] [Interval]

Note that options and capabilities vary on different operating systems. On unix or linux based
systems, including Mac OS X, use man netstat to see the man page for netstat. Other ways to
get a brief list of valid options are:

Linux/Unix: netstat --help

Windows: netstat /?

Parameters

-a : Displays all active TCP connections and the TCP and UDP ports on which the computer is
listening.

-b : Displays the binary (executable) program's name involved in creating each connection or
listening port.

-e : Displays extended statistics, such as the number of bytes and packets sent and received. This
parameter can be combined with -s.

-n : Displays active TCP connections, however, addresses and port numbers are expressed
numerically and no attempt is made to determine names.

-o : Displays active TCP connections and includes the process ID (PID) for each connection.
You can find the application based on the PID on the Processes tab in Windows Task Manager.
This parameter can be combined with -a, -n, and -p.
-p Protocol : Shows connections for the protocol specified by Protocol. In this case, the Protocol
can be tcp, udp, tcpv6, or udpv6. If this parameter is used with -s to display statistics by
protocol, Protocol can be tcp, udp, icmp, ip, tcpv6, udpv6, icmpv6, or ipv6.

-r : Displays the contents of the [[IP routing table]]. This is equivalent to the route print
command.

-s : Displays statistics by protocol. By default, statistics are shown for the TCP, UDP, ICMP, and
IP protocols. If the IPv6 protocol for Windows XP is installed, statistics are shown for the TCP
over IPv6, UDP over IPv6, ICMPv6, and IPv6 protocols. The -p parameter can be used to
specify a set of protocols.

-v : When used in conjunction with -b it will display the sequence of components involved in
creating the connection or listening port for all executables.

Interval : Redisplays the selected information every Interval seconds. Press CTRL+C to stop the
redisplay. If this parameter is omitted, netstat prints the selected information only once.

/? : Displays help at the command prompt.

f) Pathping

Pathping is a network utility supplied in Windows NT, Windows 2000 and Windows XP. It
combines the functionality of Ping with that of Traceroute (in Windows: tracert), by providing
details of the path between two hosts and Ping-like statistics for each node in the path based on
samples taken over a time period, depending on how many nodes are between the start and end
host. The advantages of pathping over ping and traceroute are that each node is pinged as the
result of a single command, and that the behaviour of nodes is studied over an extended time
period, rather than the Ping's default sample of four messages or Traceroute's default single route
trace. The disadvantage is that it often takes more than five minutes to produce a result.

PATHPING (Windows 2000)

Trace route and provide network latency and packet loss for each router and link in the path.

Syntax

PATHPING [-n] [-h max_hops] [-g host_list] [-p period]

[-q num_queries] [-w timeout] [-t] [-R] [-r] target_name

Key
 -n Don't resolve addresses to hostnames

-h max_hops Max number of hops to search, default=30

-g host_list Loose source route along host-list

up to 9 hosts in dotted decimal notation, separated by spaces.

-p period Wait between pings, default=250 (milliseconds)

-q num_queries Number of queries per hop, default=100

-w timeout Wait timeout for each reply, default is 3000 (milliseconds)

-T Test each hop with Layer-2 priority tags (QoS connectivity)

-R Test if each hop is Resource Reservation Protocol (RSVP) aware

All parameters are Case-Sensitive

Pathping is invaluable for determining which routers or subnets may be having network problems - it
displays the degree of packet loss at any given router or link.

Pathping sends multiple Echo Request messages to each router between a source and destination over a
period of time and computes aggregate results based on the packets returned from each router.

Pathping performs the equivalent of the tracert command by identifying which routers are on the path.
 EXPERIMENT NO-10

AIM: WRITE A PROGRAM FOR SETTING UP OF DNS SERVER

To start the DNS server:

Step 1 Start the SCM.

Step 2 Choose Domain Name from the Available Services box.

Step 3 Click on Start.

To stop the DNS server:

Step 1 Start the SCM.

Step 2 Choose Domain Name from the Available Services box.

Step 3 Click on Stop.

Configuring Basic Name Service

Although the majority of DNS server management involves changing information about the
zones for which the server is authoritative, you must also configure the DNS server to handle
queries for data in other zones. You must:

Specify the root name servers to which the DNS server should direct queries for data that is
neither in its cache nor within its authority. For details, see the next section, "Specifying the Root Name
Server File".

Specify name servers the DNS server should consult before directing resolvers to root name servers.
For details, see "Specifying Forwarders" on page 4-5.

Specifying the Root Name Server File

All name servers require access to root name servers to help resolve names that are not within
their authority. The CDDM provides a file, bind.ca in the CDDM servers directory, that contains
a list of root name servers on the Internet. This root name server file is known as a cache file.
Your DNS server can query these root name servers if a DNS resolver asks the server for DNS
information that is neither within its authority nor cached in memory.

To specify a cache file in place of the default cache file:

Step 1 Start the SCM.

 Step 2 Choose Domain Name from the Available Services list.

Step 3 Click on the Config tab.

Step 4 Enter the pathname of the desired cache file in the Cache group's File field.

Unless you plan to obtain or create your own cache file, enter the standard CDDM cache file:

 On UNIX, enter installation_dir/servers/bind.ca.

 On Windows NT, enter installation_dir\servers\bind.ca.

You must specify an absolute pathname.

Step 5 To save the configuration, choose Save Configuration from the File menu.

Your changes take effect the next time you start the DNS service.

Changing Default DNS Server Parameters

When you install the CDDM or the Cisco Server Suite 1000, the DNS server is configured with
default parameters appropriate for most DNS environments. Table 4-1 shows the defaults.

Table 4-1: Default DNS Server Parameters

Parameter Description Default Value

Bootfile Name of the file in which the SCM stores DNS server config/bind.conf in the
configuration data. directory in which you
installed the software

Cachefile File in which the names of root name servers are stored. servers/bind.ca in the
directory in which you
installed the software

Debugfile File in which the DNS server stores debugging messages. disabled

Log-lame- When enabled, the DNS server logs failed attempts to direct disabled
delegation queries to advertised name servers that do not provide
authoritative answers.
Port Port on which the DNS server listens for name service 53
queries. The port on which the DNS server requests and
receives zone transfers is specified individually for each zone
(see "Specifying Zone Data Sources for Each Zone" on page 4-
9).

To change these defaults:

Step 1 Start the SCM.

Step 2 Choose DomainName from the Available Services list.

Step 3 Click on the StartUp tab.

Step 4 Click on the Parameters tab.

Step 5 Change the defaults as needed.

Step 6 Choose Save Configuration in the File menu.

Your changes take effect the next time you start NetControl.
 EXPERIMENT NO-11
AIM: START AND STOP SERVICES FROM USER WINDOW AND COMMAND PROMPT.

To start, stop, pause, resume, or restart a service

 Using Services

 Using the command line

Using Services

1. Open Services.

2. In the details panel, do one of the following:

 Click the service, and then, on the Action menu, click Start, Stop, Pause, Resume, or Restart.

 Right-click the service, and then click Start, Stop, Pause, Resume, or Restart.

Notes
 To open Services, click Start, click Control Panel, double-click Administrative Tools, and then
double-click Services.

 To start a service with startup parameters, right-click the service, click Properties, type the
parameters in Start parameters, and then click Start. These settings are not persistent; they are
used only once, and then the default settings are restored. (A backslash (\) is treated as an
escape character; type two backslashes for each backslash in a parameter.)

Using the command line

1. Open Command Prompt.

2. Type one of the following:

 To start a service, type:

net startservice
  To stop a service, type:

net stopservice

 To pause a service, type:

net pauseservice

 To resume a service, type:

net continueservice

Value Description

net start Starts a service.

net stop Stops a service.

net pause Pauses a service.

net continue Continues a service that has been paused.

service Specifies the name of service.

Notes
 To open a command prompt, click Start, point to All programs, point to Accessories, and then
click Command Prompt.

 To view the complete syntax for these commands, at the command prompt, type:

net helpcommand

 For more information about these commands, see Related Topics.

Caution
 If you stop, start, or restart a service, any dependent services are also affected. Starting a service
does not automatically restart its dependent services. For more information, see View service
dependencies.
 Changing the default service settings may prevent key services from running correctly. It is
especially important to use caution when changing the Startup type and Log on as settings of
services that are configured to start automatically.

 In most cases, it is recommended that you not change the Allow service to interact with
desktop setting. If you allow the service to interact with the desktop, any information that the
service displays on the desktop will also be displayed on an interactive user's desktop. A
malicious user could then take control of the service or attack it from the interactive desktop.