Hardware and Network Servicing

HARDWARE AND NETWORK SERVICING
Level III
LEARNING GUIDE # 1
Unit of Competence: Configure and
Administrate Server
Module Title: Configuring and

Administering
Server
Unit Code ICT HNS3 03 1110
Nominal Duration: 102 Hrs.
Unit of Competencies
 Confirm server specification
 Verify server compatibility and inter-operability
 Configure and test server
VerManual Level III

TTLM Development Configuring and Administering Server Page 1 of 58
General Objective
At the end of the module the learner will be able to:
 Administer, configure and test a server according to

business needs and technical requirements.
 Understand Single and multiple processors, memory,
Disk drives and internal/external storage devices.
 Determine Server applications (such as web
application, DNS, etc.)
 Server specification for different applications
 Determine server specifications
 Determine compatibility and operability
 Configure a server as required by technical requirements
VerManual Level III

LO1: Confirm Server Specification
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.
Confirm server design with client

 The first step in building and configuring a server is to confirm that the
information about the project is correct, current and that the client agrees with
documented specifications and design.
 You will need to reconfirm with the client
o The role of the server,
o How it will function with the remaining IT infrastructure, and the required
configuration.
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
VerManual Level III

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.
Functional requirements specification

The functional specification describes what the system will do, as opposed to how it will
be done. This distinction is important because
 The client may not be interested in the details of how a function is
implemented, and the technical details may simply cause confusion for the
client
 The implementation details may need to change during the design and
development of the project
 You don’t want to have to negotiate changes to the functional specification just
to change details of implementation
 The technical specification for large projects will be detailed in a separate
document, and you should not entangle one with the other.
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?
VerManual Level III

 Are their desktops all the same?
 What bandwidth restrictions occur presently?
 What security (login) will they need?
 What backup policies need to be in place?
 Who will have administration rights?
 What will the business do if the system fails at any stage?
 Who is the project sponsor?
 What does management expect the system will do and won’t do?
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?
VerManual Level III

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.
Identify vendor architecture

Each vendor in the marketplace supports specific platforms and server architecture.
VerManual Level III

When selecting equipment for the server, you will need to consider the hardware and
software platforms from each vendor.
Hardware platform refers to the hardware components that make up the computer
system.
software platform refers to the operating system or programming language
developed for the hardware. There are defined terms used in the IT industry to
describe the types of platforms, including
o Wintel
o Lintel
o Mac, Macintel
o Mainframe
o UNIX
o Alpha AXP
o Java
o .Net.
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
o network access
o Application services.
VerManual Level III

Hardware and software specifications
Detailed information about server hardware is available from the server documentation
and from the hardware manufacturer’s website.
At a minimum, the server vendor will have a component list detailing what hardware is in
the server.
Identify and evaluate resources

Identify server technologies
Information technology is constantly changing and improving at a high speed. Common
hardware technologies are
o Processors
o Random access memory
o Storage
o Optical drive.
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
o for hardware components you will need to ensure compatibility with the
existing system
o processor — ensure motherboard support for new CPU is available
o memory — ensure type and size is compatible with the motherboard
VerManual Level III

o Hard drives and optical drives — ensure that there is an available drive bay,
power cable and interface connection.
o Expansion cards — ensure that there is a suitable expansion slot for
installation of the expansion card.
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.
VerManual Level III

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?
VerManual Level III

LO2. Verify server compatibility and inter-operability
Ensuring Hardware Compatibility
 Networking is hardware-dependent, and not all hardware products are compatible.

 In order for two computers to communicate, they must use the same protocol.
 Computer hardware raises similar issues. In some instances, two pieces of
hardware simply can't communicate with each other. For example, consider an
analogy to automobile parts: two parts might look alike and be able to perform the
same function, but each is designed to work in a different car.
This lesson examines the issue of ensuring hardware compatibility and what you can do
to resolve incompatibilities.
After this lesson, you will be able to:
 Determine hardware compatibility issues.

 Take steps to avoid unnecessary hardware problems.
When Hardware Is a Problem
Hardware incompatibilities are a fact of life.
In today's computer industry, hundreds of manufacturers develop hardware and

software.
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.
Evaluating and selecting hardware is a major part of planning for network

implementation.
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.
VerManual Level III

Reading the Documentation
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.
Search the manufacturer's Web site for additional information.
Detection during Installation
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.
Checking Minimum Requirements
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
Table 1 Minimum Hardware Requirements for server 2003
Requiremen Standard Enterprise Datacenter Web Edition

t Edition Edition Edition
Minimum CPU 133 MHz 133 MHz for 400 MHz for 133 MHz
Speed x86-based x86-based
computers733 computers733
MHz for MHz for
Itanium-based Itanium-based
computers* computers*
Recommended 550 MHz 733 MHz 733 MHz 550 MHz
CPU Speed
Minimum 128 MB 128 MB 512 MB 128 MB
RAM
VerManual Level III

Recommended 256 MB 256 MB 1 GB 256 MB
Minimum
RAM
Maximum 4 GB 32 GB for x86- 64 GB for x86- 2 GB
RAM based based
computers512 computers512
GB for Itanium- GB for
based Itanium-based
computers* computers*
Multiprocessor Up to 4 Up to 8 Minimum 8 Up to 2
Support ** required
Maximum 64
Network Hardware
Network hardware is not as susceptible as software to conflicts and compatibility

problems.
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.
VerManual Level III

LO3. Configure and test server
Objectives
 Describe characteristics common to all NOSs (network operating systems)

 Compare and evaluate NOSs to select the right one for your Network
 Installing Operating System
 Configuring Domain Controller
 Specifying Computer Role
 Configure Active Directory Directory Service
 Configuring DNS Servers
 Configuring DNS clients
 Testing DNS Configuration
 Troubleshooting DNS Configuration
 Configuring DHCP Servers
 Configuring DHCP clients
 Testing DHCP Configuration
 Troubleshooting DHCP Configuration
What is network operating system?

Network operating systems typically are used to run computers that act as servers. They
provide the capabilities required for network operation. Network operating systems are
also designed for client computers and provide functions so the distinction between
network operating systems and standalone operating systems is not always obvious.
Network operating systems provide the following functions:
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
VerManual Level III

 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, which include 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, which is 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.
VerManual Level III

 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
VerManual Level III

 Test environment: conditions under which the test is to be performed
 Roles and responsibilities
 Test script: steps to be performed during the test steps
 Results: procedures for processing and authorising results.
Determining defects
Determining critical defects

Critical defects are non-conformance of product to requirements, rendering the product
unusable. System tests usually encompass multiple software modules working together to
perform a user requirement. The ultimate critical defect is software causing the whole
system to crash. However, common critical defects involve the interoperability of
modules, the loss of data flow and poor performance.
Examples include
 data stored by one module in a system test cannot be accessed and processed by
another
 interface to a legacy system fails
 a process fails to initiate another in a defined sequence
 System crashes at less than maximum transaction levels.
Characteristics of Network Operating Systems

Based on client/server architecture
 NOS manages resource sharing
 NOS provides many other functions
o Some built in
o Some configured at installation
 Default, customizable settings
 NOS components vary by NOS version and type
Network Operating Systems and Servers
Networks use servers exceeding minimum hardware
Determining optimal server hardware
Questions
What kinds of applications will run on the server?
How many clients will connect to the server?
How much storage space will each user need?
How much downtime, if any, is acceptable?
What can the organization afford?
Determining optimal server hardware
VerManual Level III

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
VerManual Level III

 Is the most privileged user account
 Is an unlimited rights to server, domain resources, objects
 Created by default
 User names
NOS grants each network user access to files and other shared resources
 Groups
o Basis for resource and account management
o Assists in resource sharing and security control
The Windows Server 2003 Family
 Windows Server 2003 is, of course, more secure, more reliable, more available, and
easier to administer than any previous version of Windows. Let’s take a close look
at the platform and how it compares to Microsoft Windows 2000. This lesson
provides a brief overview of the Windows Server 2003 family, focusing on the
differences among the product editions: Web Edition, Standard Edition, Enterprise
Edition, and Datacenter Edition.
 Windows Server 2003 is available in 64-bit as well as 32-bit versions.
Windows Server 2008

Released on February 2008

Is an Enhancement of Windows Server 2003

GUI (graphical user interface)
o Pictorial representation of computer function
o NOS GIUs
 Enable administrator to manage files, users, groups, security, and
printers
 Enhanced security, reliability, remote client support, and performance
 Has New server management features
 Editions
o Standard Edition
o Web Edition
o Enterprise Edition
o Datacenter Edition
Hardware Requirements
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
VerManual Level III

UNIX and Linux
 Popular NOSs
o Provide resource sharing
o Older
 UNIX developed in 1969
 UNIX preceded, led to TCP/IP protocol suite development
o Most Internet servers run UNIX
 Efficient and flexible
 Some difficulty to master UNIX
 Not controlled, distributed by single manufacturer
 Some version nonproprietary and freely distributed
Network Computer Groups

Workgroups
 Used in Peer-to-peer network
 Decentralized management
o Each computer has own database, User accounts and security privileges
o Significantly more administration effort
 Practical for small networks
 Mostly used for few users
 Simple to design, implement
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 called organization
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
VerManual Level III

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
The multiple types of servers or types of network servers are as follows:

 File Server Provides convenient, centralized access to files and directories for
individual users, departments, and entire organizations. Choosing this option allows you
to manage user disk space by enabling and configuring disk quota management and to
provide improved file system.
 Print Server Provides centralized and managed access to printing devices
by serving shared printers and printer drivers to client computers..
 Application Server (IIS, ASP.NET) Provides infrastructure components
required to support the hosting of Web applications.
 Mail Server (POP3, SMTP) Installs POP3 and SMTP so that the server can act
as an e-mail server for POP3 clients.
 Terminal Server Provides applications and server resources, such as printers
and storage, to multiple users as if those applications and resources were installed
on their own computers.
 Remote Access/VPN Server Provides multiple-protocol routing and remote
access services for dial-in, local area networks (LANs) and wide area networks
(WANs).
 Domain Controller (Active Directory) Provides directory services to clients in
the network.
 DHCP Server Provides automatic IP addressing services to clients configured
to use dynamic IP addressing.
Directory Services
 Directory Services: allow users to look up things by name or by type of service or
resource (such as printers)
 The two complete directory services that use “tree and forest” metaphor to
organize directory content are:
o Active Directory, introduced with Windows 2000
o Novell Directory Services (NDS), introduced with Novell NetWare version 4
 Directory servers also store access control
 Connects all machines and peripherals; coordinates and controls functions of
machines and peripherals
 Supports security and privacy; controls access to resources on a user
authentication basis
 Advertises and manages resources from centralized directory; gives ability to share
resources such as printers
 Includes client and server network software
VerManual Level III

Installing Network Operating System
General NOS Components
 NOS includes many software components and services
o Naming Services
o Directory Services
o Client Network Software
o Server Network Software
Preplanning and Preparing a Server Installation
 Before you begin the actual installation of Windows Server 2003, you must make
several decisions.
 How well you plan these steps will determine how successful your installation is.
 Verifying Minimum Hardware Requirements: The first step of the installation

is verifying that your hardware meets the system requirements.
 Choosing a New Installation or an Upgrade: If you have an existing Windows
environment, you may need to perform a new installation or upgrade an
existing server.
 Determining the Type of Server to Install: You have the choice of making your
server a domain controller (DC), a member server, or a standalone server.
 Gathering the Information Necessary to Proceed: During the installation of
Windows Server 2003, you will have to tell the Setup Wizard how you want
your server configured.
o Select the Computer Name
o Name of the Workgroup or Domain
o Network Protocol and IP Address of the Server
 Backing Up Files: Whether you are performing a new installation on a
previously used server or upgrading an existing server, you should perform a
complete backup of the data and operating system before you begin your new
installation.
Setting Up the Windows Server 2003 Operating System
o If you have installed Microsoft server operating systems before, you will be familiar
with the look and feel of the Windows server 2003 installation process.
o The familiar blue background with white text is still there for the first half of the
installation and, for the most part, the questions are the same.
o You still have to press F8 to accept the license agreement, but unlike with some older
versions, you aren’t required to page down to read the whole thing first anymore.
o The next step is to set up the hard drive and partitions you want to install to.
o Although the process is similar to previous versions, you have some new options to
choose from.
o Follow the instructions to prepare and select your desired partition for installation.
 Formatting the Partition
 Quick Formatting or Regular Formatting
o FAT or NTFS
VerManual Level III

 Customizing Regional and Language Options
 Personalizing the Software
 Inserting a Product Key
 Selecting Licensing Modes
 Setting Computer Name and Administrator Password
 Choosing Your Computer Name
 Selecting an Administrator Password
 Modifying Date and Time Settings
 Modifying Network Settings
 Typical Settings
 Custom Settings
 Joining a Workgroup or Computer Domain
 Completing the Installation
 Logging In
 Activating Windows Server 2003
Upgrading to Windows Server 2003

When upgrading to Windows Server 2003, all your configuration settings are retained
from the previous installation. However, you still should complete several very important
tasks before you perform the upgrade.
o Backing Up the Server
o Verifying System Compatibility
Domain Names and DNS

How the DNS works
 The domain name space consists of a tree of domain names. Each node or leaf in
the tree has one or more resource records, which hold information associated with
the domain name.
 The tree subdivides into zones. A zone consists of a collection of connected nodes
authoritatively served by an authoritative DNS name server.
 A resolver (DNS server) looks up the information associated with nodes. A resolver
knows how to communicate with name servers by sending DNS requests, and
heeding DNS responses
 A domain name usually consists of two or more parts (technically labels),
separated by dots. For example wikipedia.org.
 The rightmost label conveys the top level domain (for example, the address
en.wikipedia.org has the top level (domain org).
 Each domain or subdomain has one or more authoritative DNS servers that
publish information about that domain and the name servers of any domains
"beneath" it.
VerManual Level III

Client Network Software
 Installed on user’s computer; requests resources from server
 Redirector is most important software component
 Operates on both client and server at Presentation level
 Intercepts user’s request, examines it, and determines if request can be filled by
local CPU
 If not, redirector routes requests over network to server or host of resource
 Designator is another NOS software component
o Aids in interaction with network resource
o Keeps track of drive letters assigned locally to remote or shared drives
o Substitutes real network address for mapped drive letter
 Both redirector and designator are important for file and print sharing
Server Network Software
 Hands out resources and services to
clients
 Server components are more complex than
client components
 Allows sharing of resources, as seen in
Figure
 Restricts access to resources Called access
controls
 Provide data privacy and protection
Other responsibilities of server NOS include:

 Management of users and groups
 Resource advertisement, name services, and directory services
 Logon authentication of users
 Management, control, and auditing tools to administer network
 Fault-tolerance protect integrity of network and its data
Installing a Network Operating System
VerManual Level III

 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
Configuring Dynamic Host Configuration Protocol (DHCP)

• The Dynamic Host Configuration Protocol (DHCP) is a set of rules used by a
communications device such as a computer, router or network adapter to allow the
device to request and obtain an IP address from a server which has a list of addresses
available for assignment.
• IP addresses and other parameters such as the default gateway, subnet mask, and IP
addresses of DNS servers can be assigned by the DHCP server.
• The DHCP server ensures that all IP addresses are unique.
• DHCP functionally became a successor to the older BOOTP (Bootstrap protocol), whose
leases were given
for infinite time and does not support options (DNS, Router, addresses).
DHCP Process
 IP address assignment occurs when the DHCP client boots up or regains
connectivity to the network.
 The DHCP client sends out a query requesting a response from a DHCP server.
 The DHCP server then replies to the client with its assigned IP address, subnet
mask, DNS server and default gateway information.
 The assigned IP address generally expires after a predetermined period of time,
at which point the DHCP client and server renegotiate a new IP address from the
server’s predefined pool of addresses.
VerManual Level III

 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.
VerManual Level III

Self-Check
1. Which of the following versions of Windows Server 2003 require product activation?
(Select all that apply.)
a. Standard Edition, retail version b. Enterprise Edition, evaluation version
c. Enterprise Edition, Open License version d. Standard Edition, Volume License version
2. What is the primary distinction between an Active Directory tree and an Active
Directory forest?
3. Which of the following types of Active Directory objects are not container objects?
a. User b. Group c. Computer d. 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 meet complexity
requirements.
d. Setup requires you to activate the product license before it installs the 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?
6. What are the purposes of a DNS and a WINS?
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?
VerManual Level III

Operation Sheet
Task 1
Objective: Installation and Configuration of Windows Server 2003

Installation Procedure
This operation contains a detailed account of the Windows Server 2003 installation
process.
To install Windows Server 2003, use the following procedure:
1. Insert the Windows Server 2003 installation CD into the CD-ROM drive and restart the
computer. If you are prompted to do so, press a key to boot from the CD.
2. After the computer starts, a brief message appears, stating that Setup is inspecting your
computer’s hardware configuration. The Windows Setup screen appears.
3. If your computer requires special mass storage drivers that are not part of the Windows
Server 2003 driver set, press F6 when prompted and provide the appropriate drivers.
4. The system prompts you to press F2 if you want to perform an Automated

System Recovery (ASR). Do not press F2 at this time. The setup
continues.
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.
VerManual Level III

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 un partitioned 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.
VerManual Level III

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.
VerManual Level III

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.
VerManual Level III

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.
VerManual Level III

Task 2
Objective: Configuring and Troubleshooting DNS and DHCP Server
Install & Configuring DNS Server
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
1. Log on as Administrator with a password of password.
2. By default a screen called Manage Your Server will open. This screen allows you to add roles to
your server and to manage your server roles.
3. Under Adding Roles to Your Server, click Add or remove a Role.
4. On the Preliminary Steps page, click Next.
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
VerManual Level III

install. (Insert Windows Server 2003 CD when required)
To Create a Standard Primary Forward Lookup Zone for your domain.
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
(recommended for large networks) and click Next.
3. On the Forward Lookup Zone page, select Yes, create a forward lookup zone now
(recommended), click Next.
4. On the Zone Type page, select Primary Zone, click Next.
NOTE: Select Only Primary Zone on the first server in each domain.
5. On the Zone Name page, enter the zone name for example domainname.com and click Next.
6. Leave defaults on Zone File page, 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
1. Open the DNS console
2. Expand your server and then expand forward lookup zone
3. Right-click your Domain name -----Properties ---Name Servers
4. Under Name Servers, click Add
5. In the Server fully qualified Domain Name (FQDN), type your partner’s computer name. E.g.
server02.domaina.com
6. Under IP Address, enter your partner’s IP Address, click Add, and then OK.
7. Click OK to close the Properties window. Close all other windows.
Lab 02 Installing Active Directory

NOTE: This lab is depended on lab 01.
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
using the DCPROMO command.
Prerequisites
VerManual Level III

o Understand the logical components of Active Directory
o Understand the purpose and function of Domain Controllers
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 Static IP Address and subnet mask.
o A domain name is required. Refer to the table on page 5 for this information.
o A forward lookup zone is required that matches your domain name.

Task 3
Objective: Installing Active Directory
Goal this operation, you will create a Windows 2003 domain by installing Active Directory. This
will only be done on one computer in each domain.
Start the Active Directory Installation Wizard to create:
 A new domain controller for a new domain.
 A new domain tree.
 A new forest of domain trees
Now start DC and DNS Setup process
1. First you need to go to Start–>All Programs–>Administrative Tools–>Manage Your

Server
VerManual Level III

2. Here you need to select Add or remove a role
3. Verify the following steps click on Next
4. Select Server Role as Domain Controller option click on Next
5. Summary of Your Selections click on Next
VerManual Level III

6. Active Directory Installation Wizard click on Next
7. Click “Next” on the compatibility window
8. Next window select the default option of “Domain Controller for a new domain”
and click “Next”
VerManual Level III

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.
VerManual Level III

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.
VerManual Level III

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
VerManual Level III

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.
15. Active directory Installation finish screen click Finish.
16. Now you need to select “Restart Now” option to reboot your server.
VerManual Level III

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
policy This 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 users and computers in Active Directory.
3. In the left pane, right click Domain Controllers and select Properties.
4. Select Group Policy under Domain Controller Properties.
5. Select the Default Domain Controller Policy and Click Edit.
6. Under the Group Policy Object Editor page navigate to

Computer Configuration ---Windows Settings----Security Settings---Local Policies---
User Rights Assignment.
Double click Allow log on locally.
VerManual Level III

7. . Under the Allow log on locally window, click Add User or Group and add the Everyone group.
8. Click OK and close the Group Policy Object Editor window and the Domain Controller Properties
window.
9. Close Mange Users and Computers in Active Directory.
10. From the run command type the following command: gpupdate
Task 4
Objective: Installing the DHCP Server Service and Configuring a DHCP Scope
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
The Windows Components Wizard dialog box.
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.
The Networking Services dialog box.
VerManual Level III

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.
The DHCP management console.
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.
VerManual Level III

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.
A single address exclusion and a range exclusion.
VerManual Level III

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.
A deactivated DHCP scope.
14. When the scope has been activated, the red "deactivated" arrow is removed. The figure below
VerManual Level III

shows an activated DHCP scope.
An activated DHCP scope.
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.
VerManual Level III

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.
Problem #2: Incorrect IP Address
VerManual Level III

 The DHCP client appears to have automatically assigned itself an IP address that is
incorrect for the current network.
Cause of Problem
 The Windows XP, Windows Millennium Edition (ME), or Windows 98 DHCP

client could not find a DHCP server and has used IP auto configuration to
configure its IP address.
 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.
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.
Problem #4: Incorrect or Incomplete Options
 The DHCP client appears to have incorrect or incomplete options, such as an

incorrect or missing router (default gateway) configured for the subnet on which
it is located.
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.
VerManual Level III

 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.
Problem #5: Unable to Obtain IP Addresses
 Many DHCP clients are unable to get IP addresses from the DHCP server.
Possible Cause of Problem (1)
 The IP address of the DHCP server was changed, and now DHCP clients cannot
get IP addresses.
Resolution of Problem (1)
 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.
 A DHCP server can provide IP addresses to client computers on remote multiple

subnets only if the router or switch that separates them can act as a BOOTP Relay.
Completing the following steps might correct this problem:
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.
2. At the DHCP server, do the following:
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.
VerManual Level III

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.

 Multiple DHCP servers exist on the same LAN.
 Make sure that multiple DHCP servers on the same LAN are not configured with
overlapping scopes.
Problem #6: No Relay Services
 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.
VerManual Level III

 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.
 The IP addresses of DHCP servers configured on the global properties of the

DHCP Relay Agent are incorrect.
 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.
 The correctly configured DHCP servers are not reachable.
 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.
 IP packet filtering is preventing the receiving (through input filters) or sending

(through output filters) of DHCP traffic.
 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
 TCP/IP filtering is preventing the receiving of DHCP traffic.
VerManual Level III

 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.
VerManual Level III

Task 6
Objective: How to Test DNS
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)
1. Open a browser like Mozilla Firefox or Internet Explorer. Type www.google.com

into the address bar. If it doesn’t appear, a message will appear saying that it
cannot find the site.
2. Next, open a command prompt: Go to “Start or “Run and type CMD into the box.
Press the “Enter” key. (Press the “Shift key plus “Enter” for Windows Vista.)
3. Type NSLOOKUP in the black box which pops up. Then press [ENTER]
The following message should appear:-
C:\>NSLOOKUP
Default Server: resolver1.opendns.com
Address: 208.67.222.222
This tells you that the DNS is working.
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.
VerManual Level III

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
Successfully flushed the DNS Resolver Cache
Return to Step 3 to see if this has cleared the issue.
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.
VerManual Level III

Remedy: Try another DNS server. You will need to add another DNS in the TCP/IP
configuration. (See illustration)
7. Adding Another DNS Address
VerManual Level III

Lab Test
Job title: Building a server based local area network (LAN)

Objective
You are required to build and configure desktop computer and server with Active
directory, DNS and DHCP on a server and client computer In order to build this, follow
the instruction below:
Tools and equipment
No. Items Qty Unit Specification

1 one In number With minimum of 512 MB RAM
,Pentium IV,80 GB hard disk and
Desktop Computer network interface card.
2 one In number Pentium IV with 80GB hard disk
Server computer whose RAM (512MB).
3 Switch One In number 8 port switch
4 The set contains all necessary tools

Network tool kit 1set In set including cable tester
5.
Cable Tester 1 In number Standard
Instruction
1. Check the statue of each device and fix if there is any problem.
2. Determine the compatibility and operability of the system (Hardware and

software)
VerManual Level III

2. Crimp cables and test it by using network cable tester.
3. Install server operating system and drivers on a server computer
4. Connect the cable the server and desktop to switch.
5. Configure the server to be a DNS, DHCP server.
7. Verify connection.
8. Make the client commuters to have IP address automatically
9. Check the entire configuration you have done
Activities
VerManual Level III


Hardware and Network Servicing

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Hardware and Network Servicing

Încărcat de

Drepturi de autor:

Formate disponibile

HARDWARE AND NETWORK SERVICING

Module Title: Configuring and

 Verify server compatibility and inter-operability

 Configure and test server

VerManual Level III

 Administer, configure and test a server according to

VerManual Level III

Confirm server design with client

VerManual Level III

Functional requirements specification

VerManual Level III

VerManual Level III

Identify vendor architecture

VerManual Level III

VerManual Level III

Identify and evaluate resources

VerManual Level III

VerManual Level III

VerManual Level III

Ensuring Hardware Compatibility

 Networking is hardware-dependent, and not all hardware products are compatible.

After this lesson, you will be able to:

 Determine hardware compatibility issues.

When Hardware Is a Problem

Hardware incompatibilities are a fact of life.

In today's computer industry, hundreds of manufacturers develop hardware and

Evaluating and selecting hardware is a major part of planning for network

VerManual Level III

Search the manufacturer's Web site for additional information.

Detection during Installation

Checking Minimum Requirements

Table 1 Minimum Hardware Requirements for server 2003

Requiremen Standard Enterprise Datacenter Web Edition

VerManual Level III

Network hardware is not as susceptible as software to conflicts and compatibility

VerManual Level III

 Describe characteristics common to all NOSs (network operating systems)

What is network operating system?

VerManual Level III

VerManual Level III

VerManual Level III

Determining critical defects

Characteristics of Network Operating Systems

VerManual Level III

VerManual Level III

VerManual Level III

Network Computer Groups

VerManual Level III

The multiple types of servers or types of network servers are as follows:

VerManual Level III

 Verifying Minimum Hardware Requirements: The first step of the installation

VerManual Level III

Upgrading to Windows Server 2003

Domain Names and DNS

VerManual Level III

Other responsibilities of server NOS include:

VerManual Level III

Configuring Dynamic Host Configuration Protocol (DHCP)

VerManual Level III

VerManual Level III

6. What are the purposes of a DNS and a WINS?

VerManual Level III

Objective: Installation and Configuration of Windows Server 2003