Configuring and Administering Server
Configuring and Administering Server
Configuring and Administering Server
sdafsdfds
INFONET COLLAGE
HARDWARE AND NETWORK SERVICING
Level III
LEARNING GUIDE # 1
Unit of Competence: Configure and
Administrate Server
TTLM Development Manual Level III Configuring and Administering Server Page 1 of 59
Ver
INFONET Collage
sdafsdfds
Unit of Competencies
Confirm server specification
TTLM Development Manual Level III Configuring and Administering Server Page 2 of 59
Ver
INFONET Collage
sdafsdfds
General Objective
At the end of the module the learner will be able to:
TTLM Development Manual Level III Configuring and Administering Server Page 3 of 59
Ver
INFONET Collage
sdafsdfds
Objective
This module will help you to confirm server specification within an information technology
environment and you will also learn about:
Confirming server design with client
Identifying server hardware and software specifications
Identifying and evaluate server resources
Compiling system requirements
Introduction
What is a server?
Definition: A network server is a computer designed to process requests and deliver data to
other (client) computers over a local network or the Internet.
This resource will help you to confirm server specification within an information
technology environment.
Functional requirements
Functional requirements capture the intended behaviour of the system. This behaviour
may be expressed as a service, task or function that the system is required to perform.
The functional requirements documents are the ‘blueprint’ for the project
implementation
TTLM Development Manual Level III Configuring and Administering Server Page 4 of 59
Ver
INFONET Collage
sdafsdfds
Requirements issues
One of the first and most important activities to get on on when confirming server
specifications is to confirm client needs and to ensure that they acknowledge that
requirements have been captured correctly and sign-off on the requirements
So one of the tasks in confirming client needs is to document the requirements.
This may include identifying or clarifying
The business case
What the client considers the project’s main objectives are, including the
services that are to be performed
What IT infrastructure is already in place
Basic specifications
Conflicting or overlapping requirements
Maintenance and backup requirements
Bandwidth issues that may affect the project
Role definition of parties involved
The nature of the data (eg text, multimedia)
Security needs (eg levels of user access and privileges)
Available support resources
Costing.
User requirements
How many users are expected to use the system?
How many people will be utilising the solution at one time?
Where the users will be located (eg overseas, interstate or at home?
Technical requirements
What types of computers/operating systems will the users operate?
TTLM Development Manual Level III Configuring and Administering Server Page 5 of 59
Ver
INFONET Collage
sdafsdfds
Hardware
Compatibility: will the solution work with existing systems?
Support for proprietary formats: will the existing systems and architecture
support all types of data?
Will the new system be supported by existing resources within the company?
What funding is available for new hardware?
What is the backup strategy? Has this been costed?
Does the system need to be redundant, load balanced or clustered?
Will there be time delays to purchase and install hardware?
Who will be building the server?
Are there other projects that you may be able to share hardware costs with?
Software
What is the true cost of the software?
Are there licensing issues? As the system is in development, should you pay for
all the licensing now or when the system is in live mode?
Can the software be licensed for use by multiple users who use it on different
machines? (Concurrent licensing)
How long has the software been on the market for?
What happens if the software company becomes insolvent? Who supports it?
Who owns the source code?
What happens if the source code is modified? Who supports the product then?
Does the solution work with all other company software systems?
If web-based, does the solution function on all common browsers?
If security is a concern, can the software be delivered in a ‘locked down’
format?
Does the software support all file formats?
Is the software easy to use, or are there major training issues/costs?
TTLM Development Manual Level III Configuring and Administering Server Page 6 of 59
Ver
INFONET Collage
sdafsdfds
Stage sign-off
A project is divided into many stages. Each stage will have entry and exit criteria
that must be met before the project can progress further.
At the planning stage, the owner of the system or project steering committee must
sign-off on stage exit criteria, which would include server design documentation.
This then would trigger the start of the next stage of the project the development
stage.
The exit criteria will normally state that the following items have been identified
and agreed to:
Server platforms
Operating systems
Applications
Hardware and software limitations
Client and developer responsibilities
Privacy issues
Initial timelines
Budget
State and federal regulations.
Identify specifications
Once requirements have been defined and client needs are clarified, it’s time to start
thinking about identifying products that fit the solution. In this case, we need to focus on
the possible server solutions. Remember: a server consists of
Hardware
Software
Network connections.
There are different types of server designs that need to be considered when identifying
equipment. There are multiple server architectures to choose from, including
Mainframe architecture
File sharing architecture
Client/server architecture
Web based architecture
Thin client architecture
Blade architecture.
TTLM Development Manual Level III Configuring and Administering Server Page 7 of 59
Ver
INFONET Collage
sdafsdfds
Platform selection
Platform choice is an important consideration very early on in a project. Most projects
cannot be changed midstream, as there are many different factors such as file
formats and protocols that are fixed requirements.
There are many different types of server platforms designed to perform many types of
functions. A server’s platform will mainly depend on the type of service provided.
Some of the functions provided by a server are
o mail services
o web services
o transactional processing services
o streaming media services
o remote access services
o file storage and retrieval services
TTLM Development Manual Level III Configuring and Administering Server Page 8 of 59
Ver
INFONET Collage
sdafsdfds
o network access
o Application services.
System requirements
For hardware and software components, you will need to ensure that any minimum
system requirements are met.
You will find this information at manufacturer’s websites as whitepaper, installation
documentation, and product overviews.
For software, you will need to ensure that your system meets minimum
requirements for
o the type and speed of the processor
o memory
o available disk space
o operating system
for hardware components you will need to ensure compatibility with the existing system
o processor — ensure motherboard support for new CPU is available
TTLM Development Manual Level III Configuring and Administering Server Page 9 of 59
Ver
INFONET Collage
sdafsdfds
Software
When evaluating software, the cost of the product will be determined by how many
licences are required.
A license is a legal agreement to use software, and the exact terms of the agreement vary.
An important part of managing software licences is to purchase the right types and mix of
licences. Software licenses are offered as follows:
A site licence for a number of computers at a particular office
A licence assigned to a specific computer
A licence assigned to one specific user.
TTLM Development Manual Level III Configuring and Administering Server Page 10 of 59
Ver
INFONET Collage
sdafsdfds
Self-Check
1. What is a server and what advantages do a server gives?
2. What is a system requirement?
3. List some of the hardware and software requirement consideration before installing server
operating system
4. Define hardware and software plat form
5. What are the common hardware server technologies on?
TTLM Development Manual Level III Configuring and Administering Server Page 11 of 59
Ver
INFONET Collage
sdafsdfds
This lesson examines the issue of ensuring hardware compatibility and what you can do
to resolve incompatibilities.
Each developer has a unique perspective on the best way to accomplish the same task,
and each will provide a unique solution. Copyright and patent issues further complicate
the matter.
It is likely that you will have to create a network out of an existing collection of hardware.
In such cases, the likelihood that problems stemming from incompatible hardware will
arise is very high. It is sometimes more cost-effective to discard the old hardware and
start over.
The most common incompatibilities occur between hardware and software. Changing or
upgrading a computer or network operating system can lead to major problems.
TTLM Development Manual Level III Configuring and Administering Server Page 12 of 59
Ver
INFONET Collage
sdafsdfds
Read all the documentation about the products involved. Your hardware or software
might have a recurring problem or might conflict with another product.
Frequently, the manufacturer will document these conflicts and provide a fix. If you do
not find the solution in the supplied documentation, you might contact the manufacturer
of the product and ask for undocumented conflicts.
When you install a new computer or network operating system, your computer will
usually attempt to detect the hardware in the system during the installation process and
load the appropriate drivers for it.
Check the list of detected hardware and ensure that it matches what is already in the
machine. If you are installing Novell's Intranet Ware, for example, the install utility will
automatically scan your computer for hardware such as hard disks, CD-ROM drives, and
NICs. If the devices are recognized, the appropriate drivers will then be loaded for the
recognized devices.
As a first step before you install, make sure that you exceed the minimum requirements
for the resources in the computer. These resources include processor speed, memory, and
disk space. Table lists some minimum hardware requirements for server 2003
TTLM Development Manual Level III Configuring and Administering Server Page 13 of 59
Ver
INFONET Collage
sdafsdfds
Network Hardware
Connectivity Devices, covers the basics of how these devices (repeaters, bridges, routers,
routers, and gateways) work.
Since these devices are common to many different types of networks and work mainly
with data packets, they are less likely to present conflicts. The manufacturers of these
products maintain strict adherence to the IEEE 802.x standards.
Therefore, any device that meets an IEEE standard can communicate with another device
that meets the same standard.
The only situation in which you can expect incompatibility issues to arise is when two
devices meet different standards.
TTLM Development Manual Level III Configuring and Administering Server Page 14 of 59
Ver
INFONET Collage
sdafsdfds
Configure server
Configuring server hardware and software means setting up the way the hardware and
software operates to suit the IT environment and organisational or user requirements.
Generally, server hardware is configured before the server operating system is installed or
afterwards, if hardware components in an operating server are being changed or added.
Software may be configured when installed, as part of the installation process, or
afterwards, if a default installation has been performed.
Some specific considerations for configuring server hardware and software configuration
follow.
Server hardware configuration
Server hardware configurations will depend on what components make up the server.
Configurations you may need to consider include those for
TTLM Development Manual Level III Configuring and Administering Server Page 15 of 59
Ver
INFONET Collage
sdafsdfds
storage
boot sequences
specific devices
Redundant components.
Server software configuration
Configurations for server software depend on the purpose or function of the server.
Generally, a server may be configured for one or more of the following roles:
An application server which runs specific software applications for end users,
such as a server that runs a central Oracle Database that is accessed by users across
an organisation.
A storage server which provides a central storage place for data that can be
accessed by computer users around a network.
A network services server which provides specific services such as print, user
authentication and authorisations, dynamic host configuration protocol (DHCP),
and domain name system (DNS) are some examples of the services that can be
provided.
Server items to be configured
Generally, the following items will need to be configured on a server:
Network setting, which includes network protocol to be used, network
addressing, server name and network adaptor settings.
Services, whichinclude enabling and configuring specific services to run on the
server, such as setting the server to run dynamic host configuration protocol
(DHCP) and domain name system (DNS) services for an organisation.
Authentication,which involves setting how users of the server will be identified.
This may involve setting up local user accounts with passwords on the server or
setting the server to authenticate users via some other mechanism.
Authorisation, whichis setting up which authenticated users are permitted to
access and use the server, such as allocating user permission to access data storage
or server applications or programs.
Environment setting and policies, which are settings for the server to operate as
required or settings dictated by organizational policy. Having data backup
schedules for the server is an example of environment setting.
Define the scope of testing
Integrated tests are performed during a server development project
A test is performed on the interoperability of each component.
TTLM Development Manual Level III Configuring and Administering Server Page 16 of 59
Ver
INFONET Collage
sdafsdfds
When complete, the testing process should verify that all the tests performed
support the acceptance by the user of the totally integrated product.
Tasks performed during stress and load testing of an integrated platform include
o Establishing testing acceptance criteria and procedures
o Performing test events
o Diagnosing test results
o Resolving software defects.
Test events are designed to establish operational levels at which the new server
starts to fail and to measure how it performs under overloaded conditions. The
failure and performance levels are compared with the acceptance criteria and are
either accepted or rejected.
Test events aim to reveal failures such as
o Total system crashes
o Bottlenecks in interfaces between components
o Data corruption
o process overloading
o Performance degradation below a usable level.
Planning tests
The purpose of planning the testing process is to identify, conduct and review test
events.
The planning process accesses user documentation and identifies the hardware
and software components of the product.
Documents used for planning include the
o project plan, which states the objectives of the product and the
operational environment
o Test plan, which details the scheduling and resources for all test events
o Functional specifications, which contain technical details of software
modules.
Test documentation
When objectives, scope and tests have been identified, they are used to prepare the
requirements documentation for each test.
Test requirements include
Test objectives: list what the test is supposed to test
Acceptance criteria: conditions for the test passing or failing
TTLM Development Manual Level III Configuring and Administering Server Page 17 of 59
Ver
INFONET Collage
sdafsdfds
TTLM Development Manual Level III Configuring and Administering Server Page 18 of 59
Ver
INFONET Collage
sdafsdfds
o Applications influence:
Type of application
Resources used
Processing burden
o Vendor reputation requirements
High quality, dependability, excellent technical support
Reliable server
o Spend as much as necessary
Component failure: widespread effects
Client Support
Important NOS function
Allows efficient communication, resource sharing
NOS client support tasks
Creating and managing client accounts
Enabling clients to connect to the network
Allowing clients to share resources
Managing clients’ access to shared resources
Facilitating communication between clients
Client/Server Communication
Logon process
Redirector
Intercepts requests, determines where to
handle
File access protocol
Windows XP client communication with Windows Server 2008
CIFS (Common Internet File System)
Older protocol SMB (Server Message Block)
Broad support allows every client type to authenticate, access resources
Middleware
Translates requests, responses between client, server
3-tier architecture
Client/server environment incorporating middleware
Users and Groups
After NOS client authentication,
Client gains access to NOS
services, resources
Administrator account
TTLM Development Manual Level III Configuring and Administering Server Page 19 of 59
Ver
INFONET Collage
sdafsdfds
Server components
Processing power, memory, and hard drive space
Windows Server Catalog
Windows Server 2008 compatible computer components
Available online
Consult it prior to hardware purchases
TTLM Development Manual Level III Configuring and Administering Server Page 20 of 59
Ver
INFONET Collage
sdafsdfds
Domains
A domain is just a group of servers and workstations that agree to centralize user
and machine accounts and passwords in a Shared database.
Domains do several things for us.
o Keep a central list of users and passwords.
o Provide a set of servers to act as “authentication servers” or “logon servers”
known as domain controllers
o Maintain a searchable index of the things in the domain, making it easier
for people to find resources
o Let you create users with different levels of powers
o
Allow you to subdivide your domains into subdomains calledorganization
units or OUs.
What is a Server
A server is a device with a particular set of programs or protocols that provide
various services, which other machines or clients request, to perform certain tasks.
Together, a server and its clients form a client/server network, which provides
routing systems and centralized access to information, resources, stored data, etc.
At the most ground level, one can consider it as a technology solution that serves
files, data, print, fax resources and multiple computers. The advanced server
versions, like Windows Small Business Server 2003 R2 enable the user to handle
TTLM Development Manual Level III Configuring and Administering Server Page 21 of 59
Ver
INFONET Collage
sdafsdfds
the accounts and passwords, allow or limit the access to shared resources,
automatically support the data and access the business information remotely
Types of Servers
TTLM Development Manual Level III Configuring and Administering Server Page 22 of 59
Ver
INFONET Collage
sdafsdfds
TTLM Development Manual Level III Configuring and Administering Server Page 23 of 59
Ver
INFONET Collage
sdafsdfds
TTLM Development Manual Level III Configuring and Administering Server Page 24 of 59
Ver
INFONET Collage
sdafsdfds
TTLM Development Manual Level III Configuring and Administering Server Page 25 of 59
Ver
INFONET Collage
sdafsdfds
Much like installing standalone operating system Few extra steps for
configuration of network and server services
Important to complete preparatory steps before installing NOS
Installation Preparation
Understand many aspects of network before installing NOS, including:
o Type of network (topology)
o Size of network
o Job requirements of server
o File system to be used
o Identification or naming convention
o Types of OSs on servers and clients
o Organization of storage devices
Job Requirements
Evaluate services that machine will do, including:
o DNS
o DHCP
o Web services
o Remote access
In Windows networking, server may be:
o Domain controller – maintains directory and security database
o Member server – hosts services and resources
TTLM Development Manual Level III Configuring and Administering Server Page 26 of 59
Ver
INFONET Collage
sdafsdfds
Office networks should use DHCP, in particular when workers make extensive
use of laptops which link directly to the network occasionally.
DHCP operations
DHCP operations fall into four basic phases.
These phases are
o IP lease request,
o IP lease offer,
o IP lease selection, and
o IP lease
o Acknowledgement.
TTLM Development Manual Level III Configuring and Administering Server Page 27 of 59
Ver
INFONET Collage
sdafsdfds
Self-Check
1. Which of the following versions of Windows Server 2003 require product activation?
(Select all that apply.)
a. Standard Edition, retail versionb. Enterprise Edition, evaluation version
c. Enterprise Edition, Open License versiond. Standard Edition, Volume License version
2. What is the primary distinction between an Active Directory tree and anActive
Directory forest?
3. Which of the following types of Active Directory objects are not containerobjects?
a. Userb. Groupc. Computerd. Organizational unit
4. Which of the following is true about setup in Windows Server 2003?(Select all that
apply.)
a. Setup can be launched by booting from the CD.
b. Setup can be launched by booting from setup floppy disks.
c. Setup requires an Administrator password that is not blank to meetcomplexity
requirements.
d. Setup requires you to activate the product license before it installsthe operating
system.
5. If the DHCP server is down of not set, can you still obtain an IP address? What is the
range of the IP addresses if there is any?
7. What happens if your computer and your neighboring students’ computer are both set
to a same static IP address? Is there any warning sign?
TTLM Development Manual Level III Configuring and Administering Server Page 28 of 59
Ver
INFONET Collage
sdafsdfds
Operation Sheet
Task 1
5. If you are installing an evaluation version of Windows Server 2003, the Setup
Notification screen appears, informing you of this. Read the Setup Notification message,
and then press ENTER to continue. The Welcome To Setup screen appears.
6. Read the Welcome To Setup message, and then press ENTER to continue.The License
Agreement screen appears.
TTLM Development Manual Level III Configuring and Administering Server Page 29 of 59
Ver
INFONET Collage
sdafsdfds
7. Read the license agreement and press F8 to accept it. A screen appears, containing a list
of the partitions on the computer’s available disk drives as well as any partitioned space.
8. Select an area of unpartitioned disk space at least 4 GB in size, and then press C and
specify 3072 as the size of the new partition. Then press ENTER.
9. A screen appears, prompting you to select the file system to use when formatting the
selected partition. Select the Format the Partition Using the NTFS File System option and
press ENTER to continue.
10. Setup initializes the Windows configuration and then displays a screen with a red
status bar that counts down for 15 seconds before the computer restarts and enters the
GUI mode phase of the installation process. Windows Setup launches and produces a
graphical user interface that tracks the progress of installation in the left pane.
TTLM Development Manual Level III Configuring and Administering Server Page 30 of 59
Ver
INFONET Collage
sdafsdfds
11. Modify the default regional and language option settings if necessary, by clicking the Customize
button or the Details button. Then click Next. The
Personalize Your Software page appears.
12. In the Name text box, type your name; in the Organization text box, type the name of an
organization, and then click Next. The Your Product Key
page appears.
13. Enter the product key included with your Windows Server 2003 installation CD in the Product Key
text boxes, and then click Next. The Licensing
Modes page appears.
14. Leave the default value of 5 in the Per Server Number Of Concurrent Connections option, and then
click Next. The Computer Name And Administrator
Password page appears.
TTLM Development Manual Level III Configuring and Administering Server Page 31 of 59
Ver
INFONET Collage
sdafsdfds
15. In the Computer Name text box, type Server.xx, where xx is a unique number assigned
to you by your instructor.
16. In the Administrator Password text box and the Confirm Password text box, type a
password for the Administrator account, and then click Next. The Date And Time
Settings page appears.
17. Specify the correct date and time, and select the correct time zone for your location. Then click
Next. After a brief delay, the Network Settings page appears.
18. Leave the default Typical Settings option selected, and then click Next. The
Workgroup Or Computer Domain page appears.
TTLM Development Manual Level III Configuring and Administering Server Page 32 of 59
Ver
INFONET Collage
sdafsdfds
19. Leave the default No option selected and the default workgroup name of
WORKGROUP in place, and then click Next. The setup program installs and configures
the remaining operating system components by copying files, installing Start menu items,
registering
components, saving settings, and removing temporary files.
TTLM Development Manual Level III Configuring and Administering Server Page 33 of 59
Ver
INFONET Collage
sdafsdfds
Task 2
NOTE: This lab must be done before continuing with the rest of the labs.
o Prerequisites
· Must be familiar with DNS concepts and operations
o Objectives
· Install DNS Server services
· Create Forward and Reverse Lookup Zones
· Create and configure Conditional Forwarding
· Test DNS by using nslookup command
Lab Setup
A computer running Windows Server 2003 Enterprise Server that is
configured as a standalone server.
Static IP Address and subnet mask.
DNS domain name. Refer to the table on page 5 for this information.
1. Start the Windows Components wizard and install the DNS subcomponent of
the Networking Services. Copy the required files from the Windows Server 2003
Advanced Server compact disc.
2. Create a Standard Primary Forward Lookup Zone for your domain.
Detailed steps
2. By default a screen called Manage Your Server will open. This screen allows you to add roles to
5. On the Server Role page, select DNS Server and click Next.
6. On the Summary of Selections page, review the summary and click Next. DNS will start to
TTLM Development Manual Level III Configuring and Administering Server Page 34 of 59
Ver
INFONET Collage
sdafsdfds
1. On the Welcome to the Configure a DNS Server Wizard page, click Next.
2. On the Select Configuration Action page, select Create forward and reverse lookup zones
3. On the Forward Lookup Zone page, select Yes, create a forward lookup zone now
5. On the Zone Name page, enter the zone name for example domainname.com and click Next.
7. On the Dynamic Update page, select Allow both non-secure and secure dynamic updates, click
Next.
To Add your partner’s computer and IP Address to the Name Servers
5. In the Server fully qualified Domain Name (FQDN), typeyour partner’s computer name. E.g.
server02.domaina.com
6. UnderIP Address, enter your partner’s IP Address, clickAdd, and then OK.
7. Click OKto close the Properties window. Close all other windows.
Objectives
After completing this lab, you will be able to install Active Directory by using the Manage Your
Server Wizard.
NOTE: The Manage Your Server is used to familiarize yourself with the new Wizards and tasks
that can be performed. However, you can still promote a server to become a domain controller
Prerequisites
TTLM Development Manual Level III Configuring and Administering Server Page 35 of 59
Ver
INFONET Collage
sdafsdfds
Lab Setup
o A computer running Windows Server 2003 Enterprise Server that is configured as a
standalone server.
o Drive C formatted with NTFS
o A domain name is required. Refer to the table on page 5 for this information.
Goal thisoperation, you will create a Windows 2003 domain by installing Active Directory. This
will only be done on one computer in each domain.
TTLM Development Manual Level III Configuring and Administering Server Page 36 of 59
Ver
INFONET Collage
sdafsdfds
TTLM Development Manual Level III Configuring and Administering Server Page 37 of 59
Ver
INFONET Collage
sdafsdfds
8. Next window select the default option of “Domain Controller for a new domain”
and click “Next”
TTLM Development Manual Level III Configuring and Administering Server Page 38 of 59
Ver
INFONET Collage
sdafsdfds
8. In this tutorial we will create a domain in a new forest, because it is the first DC, so
keep that option selected
Now we have to think of a name for our domain. If you have a domain like
windowsreference.com”, you can use it, but it isn’t suggested because computers inside of
your domain may not be able to reach the company website. Active directory domains
don’t need to be “real” domains like the one above – they can be anything you wish. So i
will create “windowsreference.int”.
9. Now in order to keep things simple, we will use “windowsreferenc”, which is the
default selection, as the NetBIOS name of the domain.
TTLM Development Manual Level III Configuring and Administering Server Page 39 of 59
Ver
INFONET Collage
sdafsdfds
10. The next dialog suggests storing the AD database and log on separate hard disks
and you can just leave the default settings.
The SYSVOL folder is a public share, where things like .MSI software packages can be
kept when you will distribute packages and you can just leave the default settings or you
can change the path.
Next Screen basically says that you will need a DNS server in order for everything to work
the way we want it (i.e., our “windowsreference.int” to be reachable).we will install the
DNS server on this machine or if you want you can installed else where select “Install and
Configure…” and click next.
TTLM Development Manual Level III Configuring and Administering Server Page 40 of 59
Ver
INFONET Collage
sdafsdfds
11. Here you need to select the permissions for win 2000 or win 2003 server if you
have any NT4 select first option otherwise select second option and click next
12. The restore mode password is the single password that all administrators hope to
never use, however they should also never forget it because this is the single
password that might save a failed server.click next
13. Now we will see a summary of what will happen click next
TTLM Development Manual Level III Configuring and Administering Server Page 41 of 59
Ver
INFONET Collage
sdafsdfds
14. Active directory installation process started this can take several minutes. It’s likely
that you will be prompted for your Windows Server 2003 CD (for DNS) so have it
handy.
16. Now you need to select “Restart Now” option to reboot your server.
TTLM Development Manual Level III Configuring and Administering Server Page 42 of 59
Ver
INFONET Collage
sdafsdfds
17. After rebooting you can see new option for logon
18. After logging in you can see similar to the following screen saying your server is
now domain controller.
That’s it now your server is configured as domain controller and DNS server.
Allow everyone the rights to logon locally onto the domain controllers and update the
policyThis only needs to be done from one Domain Controller.
Procedure
1. Log on as Administrator with a password of password.
2. On the Manage Your Server page, select Manage usersand computers in Active Directory.
TTLM Development Manual Level III Configuring and Administering Server Page 43 of 59
Ver
INFONET Collage
sdafsdfds
7. . Under the Allow log on locally window, click Add User orGroup and add the Everyone group.
8. Click OK and close the Group Policy Object Editor windowand the Domain Controller Properties
window.
10. From the run command type the following command: gpupdate
Task 4
In this Lab, you walk through the steps involved in installing DHCP server software on a
Windows Server 2003 system. You also configure and activate DHCP scopes.
1. Select Start, Control Panel, Add or Remove Programs. The Add or Remove Programs dialog
box appears.
2. In the left column of the dialog, click Add/Remove Windows Components. The Windows
Components Wizard dialog box, shown below
3. Scroll down in the Components area of the dialog until you reach the Networking Services
entry. Highlight the entry, and click the Details button. The Networking Services dialog,
shown below.
TTLM Development Manual Level III Configuring and Administering Server Page 44 of 59
Ver
INFONET Collage
sdafsdfds
4. From the Networking Services dialog box, Select the Dynamic Host Configuration Protocol
option and click OK. You are returned to the Windows Component Wizard dialog. Click Next,
and the DHCP server software is installed.
5. If your system is already configured to use DHCP for example, if you use a DHCP address from
your ISP you need to enter a static IP address. For this exercise, you can use one of the private
IP addresses discussed in this chapter. An example is 192.168.1.150.
6. After the DHCP server software is installed, the Completing the Windows Component Wizard
dialog appears. A shortcut for the DHCP Management Console, shown below, is added to the
Start, Administrative Tools menu.
7. To create a DHCP scope, first open the DHCP Management Console. Then, highlight the
server object in the left pane of the utility. Next, from the Action menu, click New Scope. The
New Scope Wizard is displayed.
8. From the front page of the New Scope Wizard, click Next. In the Scope Name screen, type a
name and description for this scope. In a real-world environment, you would typically choose
a meaningful name such as "Head Office" or "Sales." For the purposes of this exercise, use
Head Office and then add a description. Click Next when you are finished. The IP Address
Range page of the wizard is displayed.
TTLM Development Manual Level III Configuring and Administering Server Page 45 of 59
Ver
INFONET Collage
sdafsdfds
9. On the IP Address Range page, enter the starting and ending IP address of the range you want
to include in your DHCP scope. For the purposes of this exercise, use a Start IP Address of
192.168.1.50, and an End IP Address of 192.168.1.100. As you will see, the default subnet mask is
generated when the Start IP Address field is completed. This default subnet mask can be
altered as needed by using the Length field. The completed page should look like that shown
below.
The IP Address Range page of the New Scope Wizard with Start and End IP addresses
configured.
After you check your settings, click Next. The Add Exclusions page of the New Scope Wizard
is displayed.
10. The Add Exclusions page allows you to define one or more IP addresses in the defined scope
that will not be assigned to systems via DHCP. You can add a single address by entering the
same address in both the Start IP Address and End IP Address fields, or define a range of
addresses by using the first IP address of the range in the Start IP Address field, and the last IP
address of the range in the End IP Address field. For the purposes of this exercise, add a single
address exclusion of 192.168.1.63, and a range exclusion of 192.168.1.70 to 192.168.1.75. When
you finish, the Add Exclusions screen should look like the example provided below.
TTLM Development Manual Level III Configuring and Administering Server Page 46 of 59
Ver
INFONET Collage
sdafsdfds
When you finish your configurations, click Next. The Lease Duration screen of the New Scope
Wizard is displayed.
11. The Lease Duration screen of the New Scope Wizard allows you to define the maximum
amount of time an IP address can be kept by a client system before it must be renewed. Select
the desired duration, or leave at the default of 8 days, and click Next. The Configure DHCP
Options page is displayed.
12. In the Configure DHCP Options screen, select No, I Will Configure These Options Later, and
click Next. The final screen in the wizard indicates that you have successfully completed the
New Scope Wizard.
13. You are returned to the DHCP Configuration screen, where the newly created scope appears.
Notice in below that beside the scope is a red arrow that points down. This lets you know that
the scope is not yet active and cannot give IP addresses to clients. To activate the scope, right-
click on the new scope and select Activate from the menu that appears.
14. When the scope has been activated, the red "deactivated" arrow is removed. The figure below
TTLM Development Manual Level III Configuring and Administering Server Page 47 of 59
Ver
INFONET Collage
sdafsdfds
15 Once activated, let your partner’s PC get IP dynamically by running ipconfig commands.
ipconfig /release
ipconfig /renew
ipconfig /all
Check from which DHCP server the client has obtained its IP by typing the third ipconfig
command.
TTLM Development Manual Level III Configuring and Administering Server Page 48 of 59
Ver
INFONET Collage
sdafsdfds
Task 4
Objective: Troubleshooting DNS Configuration
DNS is one of the most essential services on any Windows network. Active Directory can’t
function without DNS, and it’s is also used by any number of other network functions. So
it’s critical to troubleshoot DNS problems as fast as possible. Thankfully, the process is
usually fairly easy. Here are10 favorite DNS troubleshooting techniques.
1. Check for network connectivity
2. Verify your DNS server IP addresses are correct and in order
3. Ping the IP address of the host you are trying to get to (if it is known)
4. Find out what DNS server is being used with nslookup
5. Check your DNS suffix
6. Make sure that your DNS settings are configured to pull the DNS IP from the
DHCP server
7. Release and renew your DHCP Server IP address (and DNS information)
8. Check the DNS Server and restart services or reboot if necessary
9. Reboot your small office / home DNS router
10. Contact your ISP
Troubleshooting DHCP configuration
Problem #1: No IP Address
The DHCP client does not have an IP address configured or indicates that its IP
address is 0.0.0.0.
Cause of Problem
The client was not able to contact a DHCP server and obtain an IP address lease,
either because of a network hardware failure or because the DHCP server is
unavailable.
Resolution of Problem
Verify that the client computer has a valid functioning network connection. First,
check that related client hardware (cables and network adapters) are working
properly at the client using basic network and hardware troubleshooting steps.
If the client hardware appears to be prepared and functioning properly, check that
the DHCP server is available on the network by pinging it from another computer
on the same network as the affected DHCP client.
TTLM Development Manual Level III Configuring and Administering Server Page 49 of 59
Ver
INFONET Collage
sdafsdfds
The DHCP client appears to have automatically assigned itself an IP address that is
incorrect for the current network.
Cause of Problem
Resolution of Problem
First, use the ping command to test connectivity from the client to the server.
Next, either verify or manually attempt to renew the client lease. Depending on
the network requirements, it might be necessary to disable IP auto configuration at the
client.
Problem #3: Missing Configuration Details
The DHCP client appears to be missing some network configuration details or is
unable to perform related tasks, such as resolving names.
Cause of Problem
The client might be missing DHCP options in its leased configuration, either
because the DHCP server is not configured to distribute them or because the
client does not support the options distributed by the server.
Resolution of Problem
For Microsoft DHCP clients, verify that the most commonly used and supported options
have been configured at the server, scope, client, or class level of options assignment.
Cause of Problem
The client has the full and correct set of DHCP options assigned, but its network
configuration does not appear to be working correctly.
Resolution of Problem
TTLM Development Manual Level III Configuring and Administering Server Page 50 of 59
Ver
INFONET Collage
sdafsdfds
Change the IP address list for the router (default gateway) option at the
applicable DHCP scope and server. In rare instances, configure the DHCP client
to use a specialized list of routers different from other scope clients. In such
cases, add a reservation and configure the router option list specifically for the
reserved client.
Many DHCP clients are unable to get IP addresses from the DHCP server.
The IP address of the DHCP server was changed, and now DHCP clients cannot
get IP addresses.
A DHCP server can only service requests for a scope that has a network ID that is
the same as the network ID of its IP address.
Ensure that the DHCP server’s IP address is configured correctly. Verify that all IP
helpers on routers and DHCP relay agents accurately refer to this IP address.
The DHCP clients are located across a router or switch from the subnet where the
DHCP server resides and are unable to receive an address from the server.
1. Configure a BOOTP Relay on the client subnet (that is, the same physical network
segment). Use the network vendor prescription for configuring the BOOTP Relay.
a. Configure a scope to match the network address on the other side of the router or
switch where the affected clients are located.
b. In the scope, make sure that the subnet mask is correct for the remote subnet.
TTLM Development Manual Level III Configuring and Administering Server Page 51 of 59
Ver
INFONET Collage
sdafsdfds
c. Use a default gateway on the network connection of the DHCP server in such a way
that it is not using the same IP address as the switch or router that supports the remote
subnet where the clients are located.
d. Do not include this scope (that is, the one for the remote subnet) in superscopes
configured for use on the same local subnet or segment where the DHCP server resides.
e. Make sure there is only one logical route between the DHCP server and the remote
subnet clients.
Make sure that multiple DHCP servers on the same LAN are not configured with
overlapping scopes.
The DHCP Relay Agent is not providing relay services for DHCP clients on a
network segment.
The interface on the server running routing and remote access that connects to
the network segment where the DHCP clients are located is not added to the
DHCP Relay Agent IP routing protocol.
Verify that the interface on the server running routing and remote access that
connects to the network segment where the DHCP clients are located is added to
the DHCP Relay Agent IP routing protocol to enable the DHCP Relay Agent on a
router interface.
The Relay DHCP packets check box is not selected for the DHCP Relay Agent
interface that is connected to the network segment where the DHCP clients are
located.
TTLM Development Manual Level III Configuring and Administering Server Page 52 of 59
Ver
INFONET Collage
sdafsdfds
Verify that the Relay DHCP packets check box is selected for the DHCP Relay
Agent interface that is connected to the network segment where the DHCP clients
are located.
Verify that the IP addresses of DHCP servers configured on the global properties
of the DHCP Relay Agent are the correct IP addresses for DHCP servers on your
internetwork.
From the router with the DHCP Relay Agent enabled, use the ping command to
ping each of the DHCP servers that are configured in the global DHCP Relay
Agent dialog box. If you cannot ping the DHCP servers from the DHCP Relay
Agent router, troubleshoot the lack of connectivity between the DHCP Relay
Agent router and the DHCP server or servers.
Verify that IP packet filtering on the router interfaces is not preventing the
receiving (through input filters) or sending (through output filters) of DHCP
traffic. DHCP traffic uses the User Datagram Protocol (UDP) ports of 67 and 68.
Manage packet filters
TTLM Development Manual Level III Configuring and Administering Server Page 53 of 59
Ver
INFONET Collage
sdafsdfds
Verify that TCP/IP filtering on the router interfaces is not preventing the receiving
of DHCP traffic. DHCP traffic uses the UDP ports of 67 and 68.
TTLM Development Manual Level III Configuring and Administering Server Page 54 of 59
Ver
INFONET Collage
sdafsdfds
Task 6
If your computer loses IP connectivity because it can’t look up a Web address, it may be
that the DNS server is down or perhaps there is DNS cache poisoning. DNS is a system
which looks up Internet addresses and directs computers to them by providing the
information they need to do this. This system may go awry, if, for one reason or another,
a part of the jigsaw puzzle is missing. Here is a guide for testing DNS using simple
commands.
Instructions
Things You’ll Need : Paper and pencil (to write down configuration details)
C:\>NSLOOKUP
Address: 208.67.222.222
On the other hand, you could get a message like this one:-
*** Can’t find server name for address 208.67.222.222: Timed out …
This indicates that in the time it normally takes to resolve any address, nothing has come
back from the server, so either there is something wrong at the server end or anywhere in
between.
TTLM Development Manual Level III Configuring and Administering Server Page 55 of 59
Ver
INFONET Collage
sdafsdfds
Type “Exit” to come out of the NSLOOKUP dialog. It will return you to a normal
command prompt.
Example:
>exit
C:\>
4. Type “ping –a” and the IP address from Step 3 to verify whether the DNS server is
actually up.
Example:
C:\>ping –a 208.67.222.222
5. Type another command to ensure that your computer’s store of IP addresses is not
causing a problem because it is so full that it has become scrambled:
C:\>ipconfig /flushdns
Windows IP Configuration
If there is no response, and the pings come back from the server, there could be another
issue affecting how the signal is getting there.
In the next step we’ll see how the signal gets to the DNS server.
6. Type the command:-tracert and add on the IP address from Step 3 above to verify
all of the intermediate hops between you and the DNS. If it cannot get to the
server it could be a router or switch somewhere in between is the source of the
problem:
Example:
C:\>tracert 208.67.222.222
If the signal cannot reach the DNS server, then it won’t translate the address, so it is the
same as if the DNS server were down.
TTLM Development Manual Level III Configuring and Administering Server Page 56 of 59
Ver
INFONET Collage
sdafsdfds
Remedy: Try another DNS server. You will need to add another DNS in the TCP/IP
configuration. (See illustration)
TTLM Development Manual Level III Configuring and Administering Server Page 57 of 59
Ver
INFONET Collage
sdafsdfds
Lap Test
Instruction
1. Check the statue of each device and fix if there is any problem.
TTLM Development Manual Level III Configuring and Administering Server Page 58 of 59
Ver
INFONET Collage
sdafsdfds
7. Verify connection.
Activities
TTLM Development Manual Level III Configuring and Administering Server Page 59 of 59
Ver