Professional Documents
Culture Documents
Uc 3 Setup Computer Server Final
Uc 3 Setup Computer Server Final
Module Title:
SETTING -UP COMPUTER SERVERS
You must pass the Institutional Competency Evaluation for this competency before
moving to another competency. A Certificate of Achievement will be awarded to you
after passing the evaluation.
LIST OF COMPETENCIES
MODULE CONTENT
MODULE DESCRIPTOR:
This module covers the knowledge, skills and attitudes needed to set-up
computer servers for LANs and SOHO systems. It consists of competencies to set-up
user access and configures network services as well as to perform testing,
documentation and pre-deployment procedures.
COMPETENCY SUMMARY
This unit covers the knowledge, skills and attitudes needed to set-up computer
servers for LANs and SOHO systems. It consists of competencies to set-up user access
and configures network services as well as to perform testing, documentation and pre-
deployment procedures.
Learning Outcomes:
ASSESSMENT CRITERIA
CONTENTS:
Introduction to Network Operating System
Introduction to Client/Server Configuration
ASSESSMENT CRITERIA:
ASSESSMENT METHODS:
Practical Demonstration w/ oral questioning
Interview
Portfolio
Learning Experiences
Learning Outcome 1
Read Information Sheet 3.1-1: This Learning Outcome deals with the
“Introduction to Network Operating development of the Institutional Competency
System” Evaluation Tool which trainers use in
evaluating their trainees after finishing a
Answer Self-check 3.1-1
competency of the qualification.
Read Information Sheet 3.1-2:
Go through the learning activities outlined for
“Introduction to Client / Server
you on the left column to gain the necessary
Configuration”
information or knowledge before doing the
Perform Task Sheet 3.1-2 on “How tasks to practice on performing the
to Setup a server” requirements of the evaluation tool.
Perform Task Sheet 3.1-2 on “How The output of this LO is a complete Institutional
to Join a domain” Competency Evaluation Package for one
Competency of Computer Systems
Servicing NC II. Your output shall serve as
one of your portfolio for your Institutional
Competency Evaluation for Setting up User
Access.
After doing all the activities for this LO, you are
ready to proceed to the next LO: Configuring
Network Services
Learning Objectives:
After reading this information sheet, you must be able to:
1. Identify Initial NOS Components.
2. Define pre-emptive and non pre-emptive multitasking
3. Describe the elements of clients software
4. Describe the elements of server software
5. Define network services
Overview
Depending on a network operating system's manufacturer, a desktop computer's
networking software can be either added to the computer's own operating system or
integrated with it.
Novell's NetWare is the most familiar and popular example of an NOS in which the
client computer's networking software is added on to its existing computer operating
system. The desktop computer needs both operating systems in order to handle stand-
alone and networking functions together.
Memory.
CPU time.
Disk space.
Peripheral devices.
Multitasking
A multitasking operating system, as the name suggests, provides the means for a
computer to process more than one task at a time. A true multitasking operating system
can run as many tasks as there are processors. If there are more tasks than
processors, the computer must arrange for the available processors to devote a certain
amount of time to each task, alternating between tasks until all are completed. With this
system, the computer appears to be working on several tasks at once.
Because the interaction between the stand-alone operating system and the NOS is
ongoing, a preemptive multitasking system offers certain advantages. For example,
when the situation requires it, the preemptive system can shift CPU activity from a local
task to a network task.
Software Components
For computer operating systems that do not include networking functions, network client
software must be installed on top of the existing operating system. Other operating
systems, such as Windows NT, integrate the network and the computer operating
systems. While these integrated systems have some advantages, they do not preclude
using other NOSs. When setting up multivendor network environments, it is important to
consider the issue of interoperability. (Elements or components of computer operating
systems are said to "interoperate" when they can function in different computer
environments.) A NetWare server, for instance, can interoperate with other servers such
as Windows NT, and users of Apple computers can interoperate with (that is, access
resources on) both NetWare and Windows NT servers.
Client Software
In a stand-alone system, when the user types a command that requests the computer to
perform a task, the request goes over the computer's local bus to the computer's CPU
(see Figure 4.2). For example, if you want to see a directory listing on one of the local
hard disks, the CPU interprets and executes the request and then displays the results in
a directory listing in the window.
The Redirector
Redirector activity originates in a client computer when the user issues a request for a
network resource or service. Figure 4.3 shows how a redirector forwards requests to the
network. The user's computer is referred to as a client because it is making a request of
a server. The request is intercepted by the redirector and forwarded out onto the
network.
The server processes the connection requested by client redirectors and gives them
access to the resources they request. In other words, the server services—or fulfills—
the request made by the client.
Figure 4.3 The redirector forwards requests for remote resources onto the network
Designators
If you need to access a shared directory, and you have permission to access it, your
operating system will usually provide several choices for how to access the directory.
For example, with Windows NT you could use Windows Explorer to connect to the
network drive using the Network Neighborhood icon. You can also map to the drive.
(Drive mapping is the assignment of a letter or name to a disk drive so that the
operating system or network server can identify and locate it.) To map to the drive, right-
click the directory icon from the Network Neighborhood; a dialog box will prompt you to
assign an available letter of the alphabet as a drive designator, such as G:. Thereafter,
you can refer to the shared directory on the remote computer as G:, and the redirector
will locate it. The redirector also keeps track of which drive designators are associated
with which network resources.
Peripherals
Redirectors can send requests to peripherals as well as to shared directories. Figure 4.4
depicts the redirector on a local computer sending a request to a print server. The
request is redirected away from the originating computer and sent over the network to
the target. In this case, the target is the print server for the requested printer.
With the redirector, LPT1 or COM1 can refer to network printers instead of local printers.
The redirector will intercept any print job going to LPT1 and forward it out of the local
machine to the specified network printer.
Figure 4.4 Request to print redirected out LPT1 to a printer on the network
Using the redirector, users don't need to be concerned with the actual location of data or
peripherals, or with the complexities of making a connection. To access data on a
network computer, for example, a user need only type the drive designator assigned to
the location of the resource, and the redirector determines the actual routing.
Server Software
With server software, users at other machines, the client computers, can share the
server's data and peripherals including printers, plotters, and directories.
In Figure 4.5, a user is requesting a directory listing on a shared remote hard disk. The
request is forwarded by the redirector on to the network, where it is passed to the file
and print server containing the shared directory. The request is granted, and the
directory listing is provided.
Resource Sharing
Sharing is the term used to describe resources made publicly available for access by
anyone on the network. Most NOSs not only allow sharing, but also determine the
degree of sharing. Options for sharing include:
For example, an office manager wants everyone on the network to be familiar with a
certain document (file), so she shares the document. However, she controls access to
the document by sharing it in such a way that:
Managing Users
Create user privileges, tracked by the network operating system, that indicate
who gets to use the network.
Grant or deny user privileges on the network.
Remove users from the list of users that the network operating system tracks.
To simplify the task of managing users in a large network, NOSs allow for the creation of
user groups. By classifying individuals into groups, the administrator can assign
privileges to the group. All group members have the same privileges, which have been
assigned to the group as a whole. When a new user joins the network, the administrator
can assign the new user to the appropriate group, with its accompanying rights and
privileges.
Some advanced NOSs include management tools to help administrators keep track of
network behavior. If a problem develops on the network, management tools can detect
signs of trouble and present these in a chart, or other, format. With these tools, the
network manager can take corrective action before the problem halts the network.
In planning a network, the choice among network operating systems can be narrowed
significantly if you first determine which network architecture—client/server or peer-to-
peer—best meets your needs. This choice can often be made by deciding which kinds
of security are called for. Server-based networking allows you to include security
capabilities well beyond those available to a peer-to-peer network. If security is not an
issue, a peer-to-peer networking environment might be appropriate.
After your network security needs have been identified, your next step is to determine
the kinds of interoperability necessary for the network as a whole. Each NOS addresses
interoperability in different ways, so you should keep your own interoperability needs in
mind when evaluating each NOS. If your network choice is peer-to-peer, your options
for security and interoperability will be diminished because of the limitations inherent in
that architecture. If your network choice is server-based, further assessment is needed
to determine whether interoperability will be dealt with as a service on the network
server or as a client application on each networked computer. Server-based
interoperability is easier to manage because, like other services, it is centrally located;
client-based interoperability requires installation and configuration at each computer,
making interoperability much more difficult to manage.
It is not uncommon to find both methods—a network service on the server and network
client applications at each computer—in a single network. For example, a NetWare
server is often implemented with a service for Apple computers, whereas Microsoft
Windows network interoperability is achieved with a network client application at each
personal computer.
When choosing a network operating system, first determine the networking services that
will be required. Standard services include security, file sharing, printing and messaging;
additional services include interoperability support for connections to other operating
systems. For any given NOS, determine which interoperability services or networking
clients are best implemented to suit your needs.
The major server-based network operating systems are Microsoft Windows NT 4 and
Windows 2008 Server, and Novell NetWare 3.x, 4.x and 5.x. The principal peer-to-peer
network operating systems are AppleTalk, Windows 95 and 98, and UNIX (including
Linux and Solaris). The lessons that follow examine the major network operating
systems to learn how each of them defines the networking environment.
In this module we will be using Windows 2008 Server as our Network Operating
System.
3. A request to use a remote resource is forwarded out onto the network by the
_________________.
5. All group members have the same ________________ as have been assigned
to the group as a whole.
1.) servers
2.) preemptive, nonpreemptive
3.) redirector
4.) network resources
5.) privileges
6.) service, client
Learning Objectives:
After reading this information sheet, you must be able to:
1. Assign IP address to a Server
2. Create a Domain Controller
3. Assign IP address to a Client
4. Create a User Account
5. Prepare a workstation and joining domain
When you have finished installing Microsoft Windows Server 2008 R2, a window titled
Initial Configuration Tasks may come up:
The Initial Configuration Tasks window is used to perform the most fundamental or
routine operations of Microsoft Windows Server 2008 R2. This window displays when
the computer starts. If you don't want to come up like that, click the bottom check box.
If it doesn't come up when the computer starts, to restore this window, click Start ->
Run, typeoobe and press Enter.
After installing the operating system, there are a few things you should (must) do
before continuing:
You must make sure the computer is connected to the Internet
If this is the first computer, you must make it a domain controller (this is not a
requirement if the computer will not be a domain controller; if you don't (yet) know
what a domain controller is, don't worry about that now)
Click OK
A dialog box will ask you to restart your computer. Click OK
Click Close
Click Restart Now
Network Discovery
Network discovery makes it possible for a computer to allow other computers to "see" it
on the network. To take care of it on the server, start Windows Explorer and click
Network (you can click the Start button and click the Network option). A message should
appear under the toolbar stating "Network discovery is turned off...":
Click that message and click "Turn on network discovery and file sharing":
Click "Yes, turn on network discovery...". If some computers are already installed
and connected to the same router, their names may appear in the Network node
in Windows Explorer.
Windows Update
You should make sure your installation of the operating system can regularly get its
updates from Microsoft. To take care of this:
Every computer on the network needs an IP address so that other computers of the
network can locate it (just like every house needs a physical address so that the post
office and other people can find it).
A computer has two main ways of getting an IP address:
A server, called a DHCP server (the word "server" here represents an application;
it doesn't have to be a different server than the one you installed), can
automatically assign (provide) an IP address to each computer
You can manually assign an IP address to each computer. Of course, you need
to know a little bit about something named TCP/IP, which means you would need
to know how to create and assign IP addresses
To assign an IP address to a server (that runs Microsoft Windows Server 2008 R2):
In the Initial Configuration Tasks, click Configure Networking
On the Taskbar, click Start and click Network. In the left frame, right-click Network
and click Properties. Click Local Area Connection. In the Local Area Connection
Status dialog box, click Properties
To assign an IP address to the server:
a. Click Start
b. Right-click Network and click Properties
(For our example, we are building a small network and we will just use a small
range of IP addresses. In the real world or for a large network, you would need to
actually know TCP/IP, design a range of IP addresses you plan to use, then
assign those IP addresses, or design a way to assign the IP addresses to the
computers)
e. Click Close
f. In the Local Area Connection Status dialog box, click Properties
g. In the checked list box, click Internet Protocol Version 4 (TCP/IPv4)
h. Click Properties
i. Click Use the Following IP Address
j. Type the IP address you want the server to use. For our example, and based on
the above dialog box, we type 192.168.001.001
k. Press Tab
l. Type the subnet mask (normally, it should be added automatically when you
press Tab from the previous IP address text box) and press Tab
m. Type the default gateway address (use the first and the second octets of the IP
address you had provided (such as 192.168) and use 001.001 for the other two
bytes)
n. Provide the Preferred DNS server address (we use 127.0.0.1 for our example)
and the Alternate DNS Server address (we leave ours empty)
o. Click Advanced to check the values that were put in the IP Settings and DNS
property pages
p. Click OK
q. Click OK
r. Click Close
s. Click Close
server, so that, if you provide the name of the computer, the server can "translate" the
name into the corresponding computer that use the actual IP address of the computer.
The Domain Name System, named DNS, is a language (again, named a protocol) that
allows the server that receives (or is provided) the name of a computer. Then the
server checks a list (called a table) that has the names of computers and their
corresponding IP addresses. That way, the server can locate, through the IP address,
the intended computer.
To make this description possible in your network, you can install an application
named DNS server. To do this:
a. From the Initial Configuration Tasks, click Add Roles
(an alternative is to click Start -> Server Manager, then in the left frame, right-
click Roles and click Add Roles)
b. In the first page of the wizard, titled Before You Begin, read the text and click
Next
c. In the second page of the wizard, click the check box of DNS Server
d. Click Next
e. In the third page of the wizard, titled DNS Server, read the text and click Next
f. Click Install
i. Type CD\ and press Enter to return to the root of the disc
ii. Type dcpromo (which stands for Promote This Computer to a Domain
Controller) and press Enter
iii. A small window will come up:
b. In the second page of the wizard, read the text and click Next
c. In the third page of the wizard, click Create a New Domain In a New
Forest
d. Click Next
e. The next page asks you to create a fully-qualified domain name (FQDN).
Enter a name made of two or three parts. Examples
are example.local or learning.example.com. Remember that the
computer already has a name and every computer on the network has or
will have a name. So this is what will happen with the name you give:
If you give a name in two parts such
as example.local or example.com, the network name to use from
a browser to access this computer will
be ThisComputerName.example.local orThisComputerName.ex
ample.com.
This means that this is the name the other computers will use to
"intranetly" or "webly" access its resources. This means that, later
on, you can create a web site stored in a computer (in a server or a
workstation), share resources of that computer, and make those
resources available so that other computers can access those
resources from a browser
If you give a name in three (or more) parts such
as support.example.local or intranet.example.local orWhatSUp.
example.local or support.example.com or intranet.example.co
m orWhatSUp.example.com or anything like those, the network
name of this computer will
beThisComputerName.support.example.local or ThisComputer
Name.intranet.example.local orThisComputerName.WhatSUp.e
xample.local or ThisComputerName.support.example.com orT
hisComputerName.intranet.example.com or ThisComputerNam
e.WhatSUp.example.com. That's the name the other computers
will use to access this computer from a browser
There is no rule as to whether the name you use (in two parts or more parts) is
bad. You just have to decide and keep the scheme in mind.
For our example, we are using functionx.local
f. After specifying the FQDN, click Next. A window will start some
operations:
g. When a dialog box comes up, read its text and click Next
h. On the next page, read the text and click Next. A window will come and
start performing some operations:
i. Click Next
j. Click Next. If you didn't create (assign) an IP address on (to) the server, a
dialog box will come up, about IP address assignment:
In you didn't assign an IP address to the server, it means you plan to use a DHCP
server that will automatically assign IP addresses to the computers of the network. In
this case, click Yes, ...
n. The next page asks you to specify the administrator's password. Click the
Password text box and type the password
o. Click the Confirm Password text box and type the same password
q. Click Next. A new dialog box will start performing an operation: This may
take a while …
r. Click Finish
s. A new dialog box will ask you to reboot:
t. When the computer comes up, press CTRL + ALT + DELETE and log in
Configuration Tools
When you have finished installing Microsoft Windows Server 2008 R2, a window titled
Initial Configuration Tasks may come up:
The Initial Configuration Tasks window is used to perform the most fundamental or
routine operations of Microsoft Windows Server 2008 R2. This window displays when
the computer starts. If you don't want to come up like that, click the bottom check box.
If it doesn't come up when the computer starts, to restore this window, click Start ->
Run, typeoobe and press Enter.
After installing the operating system, there are a few things you should (must) do
before continuing:
You must make sure the computer is connected to the Internet
If this is the first computer, you must make it a domain controller (this is not a
requirement if the computer will not be a domain controller; if you don't (yet) know
what a domain controller is, don't worry about that now)
(For our example, we are building a small network and we will just use a small
range of IP addresses. In the real world or for a large network, you would need to
actually know TCP/IP, design a range of IP addresses you plan to use, then
assign those IP addresses, or design a way to assign the IP addresses to the
computers)
e. Click Close
f. In the Local Area Connection Status dialog box, click Properties
g. In the checked list box, click Internet Protocol Version 4 (TCP/IPv4)
h. Click Properties
i. Click Use the Following IP Address
j. Type the IP address you want the server to use (for our example, and based on
the above dialog box, we type 192.168.001.102) and press Tab
k. Type the subnet mask (normally, it should be added automatically when you
press Tab from the previous IP address text box)
l. Type the default gateway address (use the first and the second octets of the IP
address you had provided (such as 192.168) and use 001.001 for the other two
bytes)
m. Provide the Preferred DNS server address (we use 127.0.0.1 for our example)
and the Alternate DNS Server address (we leave ours empty)
n. Click OK
o. Click Close
p. Click Close
A computer network has to be managed. Some aspects can be done manually and
some others electronically. In order to do anythinig, you must have a user account that
can perform the necessary tasks. Such an account must have appropriate rights on
the network.
To create the primary account to manage the network, on the server:
a. Click Start -> Administrative Tools -> Active Directory Users and Computers (if a
message box comes up, click Continue)
b. If necessary, in the left frame, expand the name of the domain.
Click Users
c. In the left frame, right-click Users -> New -> User
d. Type the first name of the user and press Tab. If you have a middle initial, type it
and press Tab
e. Type the last name
f. Click the User Logon Name text box and type a user name. Here is an example:
g. Click Next
j. Click Next
k. Click Finish
Making a User Account an Administrator
Some of the operations you will perform on the network require that the account have
the appropriate rights (also called permissions). An administrator's account is one that
can do anything on the network, such as creating users accounts or adding computers
to the network.
To make a user account become an administrator, on the server:
a. Click Start -> Administrative Tools -> Active Directory Users and Computers
b. In the left frame, expand the domain's node
c. Click Users
d. Double-click the user name whose rights you want to manage (or right-click that
user name and click Properties)
e. Click Member Of
f. Click Add...
g. In the bottom text box (where the caret is blinking), type admin.
j. Click Ok
To use the network, a user must log in. This is done by providing a user name and a
password. If this is the first time you are logging in, you may be asked to change your
password.
If you are logged but you want to use another account, you can switch to another
account. To do this:
a. Click Start -> Switch User
b. Press CTRL + ALT + DELETE
c. Click Other User
d. Type the user name (such as the one you created earlier) and press Tab
e. Type the password (such as Password1 if you are continuing from the account
created earlier) and press Enter
i. If this is the first time you are logging in, a message will tell you that you
must change the password. Click OK
ii. Type a good password for the account and press Tab
iii. Type the password again and press Enter.
A message will inform you that your password has been changed
iv. Click OK
Then click OK. After creating an account for a computer, you can add it to the domain.
Actually, primarily creating an account for a computer is not required.
Preparing a Workstation
There are two primary ways you prepare a computer to join the domain:
Do Nothing: In this case, you would let the various wizards take care of
everything. You would simply follow the instructions on the screen, click Next,
OK, Finish when prompted to do so
Take care of things as much as possible: the disadvantage of this technique is
that you should know what you are doing. The advantage is that you would know
as much as possible, what you did where.
If you use the second option, you would for example assign an IP address to the
server instead of the letting the DHCP server take care of that (Do Nothing option). In
this case also, you must prepare the workstations to join the network. For example,
you must assign an IP address to it. If you are working on a small network, TCP/IP is
not the most difficult thing you will deal with (in fact you don't need to know that much
about TCP/IP; you can follow other people's instructions and you will be fine).
To prepare a workstation to join the domain, on the workstation:
a. Click Start -> Control Panel
b. Click View Network Status and Tasks (or click Network and Internet, then
Network and Sharing Center)
c. Click Local Area Connection
d. Click Properties
e. In the Networking tab of the Local Area Connection Properties, in the checked list
box, click Internet Protocol Version 4 (TCP/IPv4)
f. Click Properties
l. Click OK
m. Click Close
n. Click Close
d. In the Computer Name text box, enter the desired name of the computer. If you
had already created an account in the domain for this computer, type that name
e. In the Member Of section, click the Domain radio button
f. Click the Domain text box and enter the name of the domain
g. After specifying the name of the computer and the domain to join, click OK
h. You would then be asked to provide a user name and a password for a user who
has the permissions to let a computer join a domain.
Type the name of the domain, followed by \ and followed by the user name of an
account that can allow a computer to join a domain and press Tab
i. Type the account's password
j. After entering a user and a password, click OK. If you have the right to add
computers to the domain, you would receive a Welcome message:
Click OK
k. You will be ask to restart the computer
Click OK
Post Installation
After letting a workstation join a domain, there are a few things you should take care of,
such as Network Discovery. This time, you may be asked to provide a user name and
password.
Performance Objective:
Given all the necessary tools and equipment needed, you must be able to setup a domain
controller for the server computer
Supplies: Availability board, pen, paper, related information sheet, Windows 2008
Installer , windows 7 Installer
Equipment:
2 PC, Router, Cables, Switch
Steps/Procedure:
1. Set up a domain controller
2. Provide the following information to your server
3. IP Address : 192.168.0.100
4. Computer Name: Server
5. Customize the server by adding a role
6. Enable Remote Desktop
7. Setup a Domain Name by using TESDA.com as a Domain name
8. Set an Administrator Password: use your own password
9. Login to your Domain
10. Create a two user account one is an Administrator account and the other is an
ordinary user
Assessment Method:
Criteria YES NO
1. Setup a computer name.
2. Setup an IP Address
3. Add an active directory domain service
4. Setup a Domain name
5. Add a User account
Performance Objective:
Given all the necessary tools and equipment needed, you must be able to join to a domain server
computer.
Supplies: Availability board, pen, paper, related information sheet, Windows 2008 Installer ,
windows 7 Installer
Equipment:
2 PC, Router, Cables, Switch
Steps/Procedure:
1. Setup a Client Computer
2. Provide the following information: Computer name: Client
3. Provide an IP Address
4. Provide a Preferred DNS and Gateway
5. Setup a Domain name
6. Restart and Connect to server by using the created User account
Assessment Method:
Criteria YES NO
1. Setup a computer name
2. Provide IP Address
3. Provide DNS
4. Setting up a domain name
5. Connect to server using ordinary user
6. Connect to server using administrator account
CONTENTS:
Network Services
Setting up a windows server 2008 Print Server
ASSESSMENT CRITERIA:
ASSESSMENT METHODS:
Practical Demonstration w/ oral questioning
Interview
Portfolio
Learning Experiences
Learning Outcome 2
Read Information Sheet 3.2-1: This Learning Outcome deals with the
“Network Services” development of the Institutional Competency
Evaluation Tool which trainers use in
Answer Self-check 3.2-1
evaluating their trainees after finishing a
Read Information Sheet 3.2-2: competency of the qualification.
“Setting up a windows server 2008
Go through the learning activities outlined for
Print Server”
you on the left column to gain the necessary
Perform Task Sheet 3.2-2 on “How information or knowledge before doing the
to Configure a network printer” tasks to practice on performing the
requirements of the evaluation tool.
After doing all the activities for this LO, you are
ready to proceed to the next LO: Perform
testing, documentation and pre-
deployment procedures
Learning Objectives:
The term network services are used to describe a wide range of software and
connectivity tools that are managed by a central group and distributed to the networked
computers. A networked computer environment occurs when multiple computers are
connected to each other or a central server. The computers are able to access shared
files and utilities from a central location. There are several advantages to this type of
environment, ranging from increased quality control to performance and issue
management.
There are four types of network services: user management, email, printing, and system
administration. In a networked environment, the desktops are known as client
computers or workstations. The servers are typically stored in a special temperature-
controlled room that is often physically located in a different building or space than the
workstation users. Access is provided through network cables that are used to transmit
data packages within the network. These cables also provide access to the Internet,
typically after being routed through a central server or network switch.
Clients and servers will often have a user interface, and sometimes other hardware
associated with them.
Learning Objectives:
Windows Server 2008 Print Services allow printers to be shared over a network and
provide a centralized printer management infrastructure allowing multiple print servers
and printers to be managed from within the Print Management tool.
The first step is to insure that the Print Services role is installed, which enables a
number of required administrative steps. This is not the same as the Printers applet in
the Control Panel: the latter doesn't run in an administrative context, and will not allow
many of the required operations to installation and management of printers.
1. Launch the Server Manager, and approve the User Account Control prompt when
offered. We are strongsupporters of UAC and never disabled it.
2. If a "Before You Begin" box is displayed, read and click through it.
Likewise, review the Introduction to Print Services page and click Next to get started.
3. Launch Server Manager< from the Start Menu, expand the local server's name,
and then expand the Roles item. If Print Services are already found, then stop.
Otherwise right-click on Roles and select Add Roles from the context menu.
5. Most users require only Print Server — this provides normal ordinary Windows
printing support.
6. This final dialog confirms what's about to be performed, and though it warns that a
system reboot may be necessary. It didn't require one when we added print services
to our server.
But removing the Print Services role did require a restart before any additional role-
related changes could be made.
Obviously, a print server without any printers isn't going to be of much use. Not
surprisingly, therefore, the next step after installing Print Services is to add printers.
Printers may either be network based, or locally connected to the server. In the case of
network printers, these may be added either manually or using auto-detection. Under
auto-detection, Print Management scans the subnet on which the server resides and
searches for any devices it can identify as being printers. As printers are detected on
the network they are displayed in a list where they may be selected and added to the
print server.
To add network printers using auto-detection, open the Print Management tool via Start
-> All Programs -> Administrative Tools -> Print Management, unfold the Print
Servers from the list in the left pane, right click the local or remote print server to which
the new printer is to be added and select Add Printer.... This will display the Network
Printer Installation Wizard as illustrated below:
In order to have the wizard search for printers on the network, ensure that the Search
for network printers is selected and click on Next. At this point the wizard will begin the
process of scanning the network for printers. As each printer is detected it will be listed.
In the following example, the wizard has detected an HP Deskjet 5800 printer on the
network with an IP address of 192.168.2.10:
If no printers are detected, ensure that the printers are connected to the network and
powered on and are on the same subnet as the print server. Once the scan is complete,
select the required printer from the list and click Next to proceed to the Printer
Driver screen. If a driver for the printer is already installed, select it from the drop down
list. Alternatively select the Install a new driver option and click Next to proceed to
the Printer Installation screen where a list of printer manufacturers and models is
presented. Select the make and model of the printer from the list:
If the make and model of printer are not listed, check to see if the printer was supplied
with a driver disk, or whether a driver can be obtained from the manufacturer's web site.
Assuming this to be the case, use the Have Disk button to browse for and select the
appropriate manufacturer driver. With either a printer selected from the list, or a suitable
driver specified, click on Next to configure the Printer Name and Share Settings. On this
screen, enter the name by which the new printer will be shared to clients over the
network. If the printer is not to be shared, ensure that the Share this printer is not
selected. Also, enter a location description (for example, "Printer in Accounts") and
comment if desired. Click Next to display the printer summary screen as illustrated
below where the selected settings are presented for review:
Assuming the configuration summary is correct, click Next to install the new printer. At
this point the wizard will report that the driver has been successfully installed and that a
test page is ready to be printed. If another printer is to be added to the print server,
select the Add Another Printer option to instruct the wizard to loop back to the start of
the installation process.
The option is also provided to have the wizard attempt to identify the appropriate driver
for the new printer. The following figure illustrates the screen as described:
Click Next to install a printer driver. If a driver for the printer is already installed on the
print server, select it from the drop down list. Alternatively select the Install a new
driver option and click Next to proceed to the Printer Installation screen where a list of
printer manufacturers and models is presented. Select the make and model of the
printer from the list, or use the Have Disk to install the manufacturer supplied driver.
With either a printer selected, click on Next to configure the Printer Name and Share
Settings. On this screen, enter the name by which the new printer will be shared to
clients over the network. If the printer is not to be shared, ensure that the Share this
printer is not selected. Also, enter a location description (for example, "Color Printer in
Sales") and comment if desired. Click Next to perform the installation and print an
optional test page.
Since servers are generally sequestered in climate controlled server room and printers
are located in proximity to the users it always seems a little odd to talk about installing
printers with are locally connected to servers. That said, it is a topic which needs to
covered, and cover it we will.
Local printers will be connected to the server using a serial (COM) port, a parallel (LPT)
port or a Universal Serial Bus (USB) port. Often, Windows will automatically detect a
new printer as soon as it is connected and powered up. In this situation an icon will
appear in the task bar indicating that the new device has been detected. Clicking on this
icon presents the option to view details about the installation process, resulting in the
appearance of a dialog similar to the one illustrated below, where a Brother MFC-
420CN printer has been detected and is being installed:
Once the printer has been installed, it will likely need to be configured for network
sharing. To achieve this, launch the Print Management tool, select the print server to
which the printer is physically connected and click on Printers. The center pane of the
tool will display a list of printers installed on the current print server. Identify the required
printer in the list, double click on it to display the properties dialog and select
the Sharing tab:
If the printer is to be shared with network client, set the Share this printer check box and
enter a suitable share name for the printer. This page also allows Client-side Rendering
(CSR) to be configured. When selected, all rendering of print jobs is performed on the
client and just the RAW print data sent to the server for printing. This offloads the
rendering overhead to the client computers, thereby reducing the load, and increasing
the scalability of the print server.
If Windows fails to auto-detect the printer it may be added manually from Print
Management by right clicking on the print server to which the device is attached and
selecting Add Printer.... On the initial screen select the Add new printer using an
existing port and choose the port to which the printer is connected from the drop down
list. Once selected, click Next to install a printer driver. If one is already installed, select
it from the drop down next to the use an existing printer driver on the computer.
Alternatively, select install a new printer driver and either select the printer make and
model from the list, or use the Have Disk to install the manufacturer supplied driver.
Click Next to proceed to the Printer Name and Sharing screen. Choose whether the
printer is to be shared and, if so, by what name. Proceed to the summary screen, review
the information and complete the installation.
1. Click on the Start button, and then click on Devices and Printers.
2. In the Devices and Printers window, click on the Add a printer button.
3. In the Add Printer wizard, click on the option Add a network, wireless, or
Bluetooth printer.
Select the option Add a printer using a TCP/IP address or hostname, and
then click on the Next button. (Note: Consult the printer list to find your printer's
IP address.)
Enter the IP address in the Hostname or IP address text area. (As you type the
address, Windows also adds the address automatically to the Port name text
area, as shown in the example below.)
Install the driver for your printer by selecting the printer's manufacturer from the
Manufacturer and then the model number. (If the model number of your printer
isn't listed, click on the Windows Update button to list additional printer models.)
6. Enter a descriptive name for your printer in the Printer name text area or leave
the name that is already filled in, then click on the Next button. (In the example
below, "Xerox WorkCentre 7345 PCL6" has been entered for the printer name.)
You should see the following window showing that Windows 7 has started the process
of installing the printer:
7. In the next window, make sure the option Do not share this printer is selected,
and then click on the Next button.
If the printer was added successfully, you should see the following
window:
8. In the message window shown in step 7, click on the Print a test page button if
you want to print a test page to verify you can print with the printer, and
then click on the Finish button.
9. You can view the new printer listing by clicking again on the Start button, and
then clicking again on Devices and Printers. You should see the entry for your
printer. (In the example below, "Xerox WorkCentre 7345 PCL6" has been added.)
Performance Objective:
Given all the necessary tools and equipment needed, you must be able setup network printer.
Supplies: Availability board, pen, paper, related information sheet, Windows 2008 Installer ,
windows 7 Installer
Equipment:
2 PC, Router, Cables, Switch, Printer
Steps/Procedure:
1. Add Printer Services into the server
2. Connect the printer to the server
3. Install Printer Driver
4. Share the Printer
5. Install Network Printer to the Client PC
6. Print Test
Assessment Method:
Criteria YES NO
1. Add Printer Service
2. Install the printer
3. Share the printer
4. Connect the client PC to the Server Printer
5. Print a “Print Test ” page
CONTENTS:
ASSESSMENT CRITERIA:
ASSESSMENT METHODS:
Practical Demonstration w/ oral questioning
Interview
Portfolio
Learning Experiences
Learning Outcome 3
Read Information Sheet 3.3-1: This Learning Outcome deals with the
“Network Connectivity Testing development of the Institutional Competency
Procedure” Evaluation Tool which trainers use in
evaluating their trainees after finishing a
Perform Task Sheet 3.3-1 on “How
competency of the qualification.
to test the network connectivity”
Go through the learning activities outlined for
you on the left column to gain the necessary
information or knowledge before doing the
tasks to practice on performing the
requirements of the evaluation tool.
Learning Objectives:
1.) Examine a machine’s IP address configuration for possible clues to the cause of the
problem.
2.) Know some steps for testing basic connectivity between two machines
When one host has trouble communicating with another, the first thing that you must do
is to gather some information about the problem. More specifically, you need to
document the host’s configuration, find out if the host is having trouble communicating
with any other machines on the network, and find out if the problem effects any other
hosts.
For example, suppose that a workstation is having trouble communicating with a
particular server. That in itself doesn’t really give you a lot to go on. However, if you
were to dig a little bit deeper into the problem and found out that the workstation
couldn’t communicate with any of the network servers, then you would know to check
for a disconnected network cable, a bad switch port, or maybe a network configuration
problem.
Likewise, if the workstation were able to communicate with some of the network
servers, but not all of them, that too would give you a hint as to where to look for the
problem. In that type of situation, you would probably want to check to see what the
servers that could not be contacted had in common. Are they all on a common subnet?
If so, then a routing problem is probably to blame.
If multiple workstations are having trouble communicating with a specific server, then
the problem probably isn’t related to the workstations unless those workstations were
recently reconfigured. More than likely, it is the server itself that is malfunctioning.
The point is that by starting out with a few basic tests, you can gain a lot of insight into
the problem at hand. The tests that I am about to show you will rarely show you the
cause of the problem, but they will help to narrow things down so that you will know
where to begin the troubleshooting process.
PING
PING is probably the simplest TCP/IP diagnostic utility ever created, but the information
that it can provide you with is invaluable. Simply put, PING tells you whether or not your
workstation can communicate with another machine.
The first thing that I recommend doing is opening a Command Prompt window, and then
entering the PING command, followed by the IP address of the machine that you are
having trouble communicating with. When you do, the machine that you have specified
should produce four replies, as shown in Figure A.
The responses essentially tell you how long it took the specified machine to respond
with thirty two bytes of data. For example, in Figure A, each of the four responses were
received in less than four milliseconds.
Typically, when you issue the PING command, one of four things will happen, each of
which has its own meaning.
The first thing that can happen is that the specified machine will produce four replies.
This indicates that the workstation is able to communicate with the specified host at the
TCP/IP level.
The second thing that can happen is that all four requests time out, as shown in Figure
B. If you look at Figure A, you will notice that each response ends in TTL=128. TTL
stands for Time To Live. What this means is that each of the four queries and responses
must be completed within 128 milliseconds. The TTL is also decremented once for each
hop on the way back. A hop occurs when a packet moves from one network to another. I
will be talking a lot more about hops later on in this series.
Figure B: If all four requests time out, it could indicate a communications failure
At any rate, if all four requests have timed out, it means that the TTL expired before the
reply was received. This can mean one of three things:
Communications problems are preventing packets from flowing between the two
machines. This could be caused by a disconnected cable, a bad routing table, or a
number of other issues.
Communications are occurring, but are too slow for PING to acknowledge. This
can be caused by extreme network congestion, or by faulty network hardware or wiring.
Communications are functional, but a firewall is blocking ICMP traffic. PING will
not work unless the destination machine’s firewall (and any firewalls between the two
machines) allow ICMP echos.
A third thing that can happen when you enter the PING command is that some replies
are received, while others time out. This can point to bad network cabling, faulty
hardware, or extreme network congestion.
The fourth thing that can occur when pinging a host is that you receive an error similar
to the one that is shown in Figure C.
Figure C: This type of error indicates that TCP/IP is not configured correctly
The PING: Transmit Failed error indicates that TCP/IP is not configured correctly on the
machine on which you are trying to enter the PING command. This particular error is
specific to Vista though. Older versions of Windows produce an error when TCP/IP is
configured incorrectly, but the error message is “Destination Host Unreachable”
Believe it or not, it is not uncommon for a ping to succeed, even though two machines
are having trouble communicating with each other. If this happens, it means that the
underlying network infrastructure is good, and that the machines are able to
communicate at the TCP/IP level. Typically, this is good news, because it means that
the problem that is occurring is not very serious.
If normal communications between two machines are failing, but the two machines can
PING each other successfully (be sure to run the PING command from both machines),
then there is something else that you can try. Rather than pinging the network host by IP
address, try replacing the IP address with the host’s fully qualified domain name, as
shown in Figure D.
Figure D: Try pinging the network host by its fully qualified domain name
If you are able to ping the machine by its IP address, but not by its fully qualified domain
name, then you most likely have a DNS issue. The workstation may be configured to
use the wrong DNS server, or the DNS server may not contain a host record for the
machine that you are trying to ping.
If you look at Figure D, you can see that the machine’s IP address is listed just to the
right of its fully qualified domain name. This proves that the machine was able to resolve
the fully qualified domain name. Make sure that the IP address that the name was
resolved to is correct. If you see a different IP address than the one that you expected,
then you may have an incorrect DNS host record.
Confirming Connectivity
In the previous article, I showed you the basics of using the PING command to test
network connectivity. However, if you are having trouble communicating with other hosts
on the network, or hosts on remote networks, then there are a few more PING tests that
you can perform in order to get a better idea of what’s going on.
Before I show you those techniques though, it is important to understand how the host
that is having communications problems is configured. The procedure for doing so
varies from one version of Windows to the next, so I will show you how to check the
network configuration on a machine that’s running Windows Server 2003
The first thing that you must do is to determine whether the machine in question is
running a static or a dynamic IP address configuration. To do so, open the Control
Panel, and choose the Network Connections option. Now, right click on the connection
that you are trying to diagnose, and choose the Properties command from the resulting
shortcut menu. Upon doing so, you will see the connection’s properties sheet, as shown
in Figure A.
Now, scroll through the list of items that the connection uses until you locate the TCP/IP
protocol (selected in Figure A). Select this protocol, and click the Properties button to
reveal the Internet Protocol (TCP/IP) Properties sheet, shown in Figure B.
Figure B: The Internet Protocol (TCP/IP) Properties sheet is used to configure the
TCP{/IP protocol
Once you arrive at this screen, it is important to make note of the machine’s IP
configuration. Specifically, you will want to make note of the following items:
Before I move on, I also want to mention that if a computer has multiple network
adapters installed, then there will be multiple connections that are listed in the Control
Panel. It is very important that you know which connection corresponds to which
network adapter, or else the techniques that I am about to show you will not work.
If you have any doubt as to which connection corresponds to which network adapter,
then check the adapter type. If you look at Figure A, you will notice that the adapter type
is listed at the top of the screen. If need be, you can open the case to see which
network adapter the network cable is connected to, so that you can be absolutely sure
that you are looking at the correct network connection.
Now that you know how TCP/IP is configured for the network adapter in question, we
must determine whether or not Windows acknowledges the configuration. To do so,
open a Command Prompt window, and enter the following command:
IPCONFIG /ALL
It might seem strange to have to make sure that Windows acknowledges your
configuration, but IPCONFIG can really tell you a lot about what’s going on. For
example, take a look at the screen that’s shown in Figure C. When you enter the
IPCONFIG /ALL command, the first thing that you must do is to locate the correct
network adapter. In this case, locating the correct adapter is easy, because only one
adapter is listed. Notice though that IPCONFIG provides you with the connection
number (in this case it’s Ethernet adapter Local Area Connection 2). If you look back at
Figure A, you will notice that the title of the properties sheet shown in the figure bears
the same name. That along with the description of the physical network adapter tells
you exactly which network connection you are looking at.
Figure C: The IPCONFIG /ALL command shows you the machine’s IP configuration as
Windows sees it
Of course the first thing that you will probably notice about Figure C is that it lists many
different IP addresses for the connection. The reason for this is that I created the
screenshot on a Web server. The Web server hosts multiple Web sites, each with its
own IP address. I wanted to use this server to illustrate the point that the IP address
configuration that you see when you glance at the TCP/IP properties sheet isn’t always
what Windows is using. In this case, the IP configuration information shown in Figure B
is still valid. It serves as the machine’s primary IP address. However, there are many
other IP addresses that are also in use.
The next step in the troubleshooting process varies depending on whether the machine
is using a static or a dynamic IP address configuration. If the machine is using a static
configuration, then for right now, just check to make sure that the IP address, subnet
mask, default gateway, and DNS server address that is listed matches those entered on
the TCP/IP properties sheet.
If the machine is using a dynamic IP address, then you will want to look at the address
and see if it falls within the expected address range. If you are troubleshooting a
problem on an unfamiliar network, then you may not know what the address range
should be. If that’s the case, there are a few values that you can look for that have
special meanings.
The most obvious clue that something has gone wrong is an IP address of 0.0.0.0. This
presence of this address usually indicates one of three things:
The network adapter is not connected to the network (possibly because of a cable
problem or a bad switch port)
If you receive this address, then try entering the following three commands:
IPCONFIG /RELEASE
IPCONFIG /RENEW
IPCONFIG /ALL
These commands will essentially tell the computer to give up its current address, try to
obtain a new address, and then show you the new configuration information.
Sometimes this process will fix the problem, and sometimes it won’t. Often though, it will
yield clues as to the cause of the problem.
Another tell tale clue that something has gone wrong is that the IP address falls into the
169.254.x.x range with a subnet mask of 255.255.0.0. Some versions of Windows will
automatically use this address if an IP address cannot be acquired from a DHCP server.
Performance Objective:
Given all the necessary tools and equipment needed, you must be able to test the basic
connectivity of two computers
Supplies: Availability board, pen, paper, related information sheet, Windows 2008 Installer ,
windows 7 Installer
Equipment:
2 PC, Router, Cables, Switch, Printer
Steps/Procedure:
1.Open the Server PC and run the command prompt
2.Using Ping command list down all the network configuration information
3.Record all the information on a piece of paper
4.Open the Client PC and run the command prompt
5.Using Ping command list down all the network configuration information
6.Record all the information on a piece of paper
7. Use the Ping Command to communicate with the server
8. If no reply troubleshoot the problem
Assessment Method:
Criteria YES NO
1. Use the Ping command to list down all the network configuration
2. Use the Ping command to communicate the two machines
RESOURCES:
http://pluto.ksi.edu/
http://www.functionx.com/networking/
http://www.unixwiz.net/
http://www.windowsnetworking.com/
INSTITUTIONAL ASSESSMENT
EVIDENCE PLAN
n Demonstrati
Written Test
Interview
Ways in which evidence will be collected:
[tick the column]
Table of Specifications
Objectives/
# of items /
Content Knowledge Comprehension Application
% of test
Area/Topics
5% 5% 10% 20%
1 1 2 4 20%
2 6 8 40%
2 2 4 8 40%
TOTAL 3 5 12 20 100%
Written Test
Multiple Choice
Please select the best answer that corresponds to each given item by encircling the
letter of your choice.
3. Is a TCP/IP diagnostic utility that can tell you wether or not your workstation can
communicate with another machine.
a. trace
b. cmd
c. tracert
d. Ping
4. Is the term used to describe resources made publicly available for access by anyone
on the network.
a. networking
b. sharing
c. pairing
d. all of the above
5. Is a term used to describe a wide range of software and connectivity tools that are
managed by a central group and distributed to the networked computers.
a. network services
b. connectivity devices
c. utility software
d. networking
6. Is a new tool available with Windows Server® 2008 that guides information
technology administrators through the process of installing, configuring, and
managing server roles and features that are part of Windows Server 2008.
a. server role
b. DHCP
c. server manager
d. control panel
7. Enables you to share printers on a network, as well as to centralize print server and
network printer management tasks.
a. Print Services
b. Internet Printing
c. LDP Service
d. Web services
9. Connection is a technology that allows you to sit at a computer (sometimes called the
client computer) and connect to a remote computer (sometimes called the host
computer) in a different location.
a. remote desktop
b. server role
c. remote admin
d. all of the above
1. C
2. A
3. D
4. B
5. A
6. C
7. A
8. C
9. A
10. D
INSTITUTIONAL ASSESSMENT
Trainee name:
Trainer name: REY G. SOMBRERO
Qualification: CSS NC - II
Unit of competency: Setup Computer Server
Date of assessment:
Time of assessment:
Instructions for demonstration
Given the necessary tools, the candidate will be able to demonstrate, Setting up user access,
Configuring Network Services, Perform testing, documentation and pre-deployment
procedures, following standard procedures within 1.5hrs.
to show if evidence is
DEMONSTRATION demonstrated
Yes No N/A
During the demonstration of skills, did the candidate:
Setup a domain controller
Customize the server
Setting up a domain
Creating an Active Directory
Create a User Account
Adding computer to the Domain
Setup Print Services
Test the connection
To allow printers to be shared over a network and provide a centralized printer management
infrastructure allowing multiple print servers and printers to be managed from within the Print
Management tool.
Answer:
So that other computers of the network can locate it
5. State some causes by some communication problems that can prevent packets from flowing
between two computers?
Answer:
This could be caused by a disconnected cable, a bad routing table, or a number of other issues.
Trainee name:
Trainer name: REY G. SOMBRERO
Qualification: CSSS – NC II
Unit of competency: Setup Computer Servers
Date of assessment:
Time of assessment:
Instructions for Oral Questioning
The candidate will be assessed based on his/her answers to the given questions. The assessor
should not deviate from the standard questions provided herein.
Oral Questions Satisfactory response
2. If you are logged but you want to use another account. What key
combination you will press to switch to another account?
3. What are the two primary ways you prepare a computer to join the
domain.
4. TTL stands for Time to Live. What does it mean if one of the
response of the Ping is TTL=128?
5. Advantage of Printer sharing?
2. If you are logged but you want to use another account. What key combination you will press to
switch to another account ?
3. What are the two primary ways you prepare a computer to join the domain?
Answer: Do Nothing
Take care of things as much as possible
4. TTL stands for Time to Live. What does it mean if one of the response of the Ping is TTL=128?
Answer: It means that a queries and responses must be completed within 128
milliseconds.