Q3-CSS11 - Las 3
Q3-CSS11 - Las 3
COMPUTER SYSTEMS
SERVICING
LEARNING ACTIVITY SHEET 3
3rd Quarter
Maintaining and Repairing Computer Systems and Networks (MRCN)
Welcome to the Computer System Servicing Grade 11 on Prepare maintenance and/ or diagnosis of faults in
line with job requirements !
Hence, the hand in this learning resource signifies that you as a learner is capable and empowered to
successfully achieve the relevant competencies and skills at your own pace and time. Your academic success
lies in your own hands!
This Learning Activity Sheet was designed to provide you with fun and meaningful opportunities for
guided and independent learning at your own pace and time. You will be enabled to process the contents of the
learning material while being an active learner.
Learning Competency:
LO 1. Plan and prepare for maintenance and repair. (TLE_IACSS9-12MRCN-IIa-e-40)
1.2 Prepare maintenance and/ or diagnosis of faults in line with job requirements
Objective/s:
a) Know the guidelines for testing computer
b) Implement these guidelines to test computer successful and safe to use.
c) Manage the set standards or planned guidelines in order to achieved a productive
workplace.
PRE–TEST
Before you proceed in this module it is important to know that the network you designed
should be properly working and managing a computer network takes a lot of uneasy
circumstances. There are two procedures that you may frequently doing in maintaining
your network or system unit.
1. Troubleshooting. a process of trial and error, in some cases, you may need
to use several different approaches before you can find a solution; other problems
may be easy to fix. This may takes a lot of steps or a single step to fix the problem.
2. Diagnosing. computer problems can be hardware of software-related.
Through a well-executed diagnostic procedure, you will be able to pinpoint the
exact problem that is impairing your computer’s functionality. After you’ve plainly
defined the problem, you can them work your way to finding the perfect remedy.
This will ensure the proper and direct action to resolve the problem.
Directions: Encircle the letter of the correct answer by identifying the statement as
diagnosing process or troubleshooting procedure.
1. Make sure the computer is rebooted at least A. Diagnosing
once after the program is installed. Some
programs require the computer to be restarted B. Troubleshooting
after installation to work properly.
2. ipconfig- This command can be utilised to A. Diagnosing
verify a network connection as well as to verify
your network settings. B. Troubleshooting
3. Make sure all other programs are closed A. Diagnosing
when you run the program or utility. If the
program successfully runs after closing all B. Troubleshooting
other programs, the program may have
conflicts with other programs
4. To ensure Windows is getting addresses A. Diagnosing
from the new DNS servers instead of using
old, cached entries, run the ipconfig /flushdns B. Troubleshooting
command after changing your DNS server.
5. Update the application. To do this, click the A. Diagnosing
Help menu and look for an option to check for
Updates. If you don't find this option, another B. Troubleshooting
idea is to run an online search for application
updates.
6. Windows includes a system file checker tool A. Diagnosing
that scans all the Windows system files and
looks for problems. If system files are missing B. Troubleshooting
or corrupted, the system file checker will
repair them.
7. Check the cables. Make sure external A. Diagnosing
2
speakers are plugged in, turned on, and
connected to the correct audio port or a USB B. Troubleshooting
port. If your computer has color-coded ports,
the audio output port will usually be green.
8. One of the most interesting variants of A. Diagnosing
netstat is netstat -an , which will display a list
of all open network connections on their B. Troubleshooting
computer, along with the port they’re using
and the foreign IP address they’re connected
to.
9. Test ping to the computer. Packet dropping A. Diagnosing
and high network latency may be observed.
B. Troubleshooting
10. type nslookup howtogeek.com at the A. Diagnosing
Command Prompt to quickly find out our
server’s assigned IP address. B. Troubleshooting
RECAP
System maintenance is an umbrella term that encompasses various forms of
computer maintenance needed to keep a system running. The two main
components of system maintenance are preventive and corrective maintenance.
Preventive maintenance involves taking measures to help keep the system
functioning, whereas corrective maintenance involves the replacement or repair of
a system or its components after they have already failed.
Always remember it is better to have prevention than to repair and replace part or
revised configuration. There are five things to remember in planning a monitoring
guide for your network. These are early detection of issues, prevention against
viruses and malware, speed up your computer, maximize your Software efficiency,
and prevent data loss.
3
4
LESSON
5
Identify and diagnose computer network faults
In this first step you define and determine the nature of the problem. Is it the user
or computer that is problematic? Are all websites unreachable, or just one or a few?
Is the computer consistently online or is the connection flapping? Are websites
reachable by IP address but not by name? Are there any error messages indicating
what type of error was encountered? Based on your answers to these questions you
can begin to make educated guesses as to the cause. Gather detailed information.
This step is similar to the first step, but here you determine the extent of the
problem. Is it affecting one computer or user, or multiple computers or users? Are
all computers in the subnet (or all users in the domain) affected? Is the whole
network down? If you are providing support to another user, can you reproduce the
error yourself? Gather detailed information.
This is where you try to put the connectivity problem in some kind of time frame.
Find out if the user was ever able to successfully do what he now cannot do. When
did the error first appear? Before the appearance of the error were there any
programs or operating system updates installed? How about new drivers or browser
plugins? Were any new nodes (clients, servers, networking devices, printers, etc)
added to the network? Any new users, user groups, or Active Directory objects such
as domains, OUs, or sites?
Use your technical expertise to isolate and explain the cause of the problem. Some
indepth investigation and diagnostic tools will probably be required. This step is
described in more detail below.
If you believe that the connectivity error is outside your scope of administration,
you will need to transfer responsibility for its resolution to another entity. For
example, if you cannot connect to the Internet and you strongly believe that the
problem is not your computer, router, or other equipment, you will need to contact
your Internet service provider (ISP) and ask them to investigate...perhaps one of
their lines or routers is down. Another scenario might involve a piece of equipment
on your network that is contractually administered by a third party.
Whether the responsibility to fix the error falls on you or if you need to transfer it to
another party, you must devise a resolution and start checking off action items.
Once a solution has been found, ensure that normal network operation has been
restored and that no new problems have been introduced.
Describe the error conditions and the steps taken for a solution. This will aid you in
troubleshooting the same or similar problems in the future. Make sure you include
a sufficient amount of detail, including operating system versions, application
versions, driver versions, software vendor update numbers, etc.
Whether you are fixing a UTP cable, an IPV4 configuration or folder sharing in a
network always follow the nine-basic process in diagnosing fault in your network.
An example below will be useful for your next exercise.
Despite boasting fast connection speeds, both wireless and wired connections can
still get bogged down for a few reasons:
2. No connection at all.
3. Service fluctuations.
Internet service providers (ISPs) also experience problems on their end, often
resulting in users not getting their contracted internet speed 24/7.
4. Equipment failure.
Your modem or router can be damaged, possibly as a result of power outages frying
the wires. You may also have outdated equipment in your hands that needs
upgrading.
5. Operator error.
7
The most common operator errors that cause faulty internet includes wires plugged
into the wrong jack, bad firewall rules set up, and duplicating IP addresses.
WRAP–UP
The combination of computer and network technology has changed people's life and
learning mode. As the computer network technology is developing rapidly and network
fault is very complex, all kinds of network fault emerge in endlessly. Computer network has
very high speed, low production cost, so it is quickly accepted by people, and become one
of the important ways that people process daily office data. The resulting network faults are
becoming more and more common and have various types, and we must have a
professional knowledge of network theory foundation and practical skills of network
maintenance that to deal with network failure problems timely and make network
maintenance quick and effective so that the network can restore normal with the fastest
speed.
For specific diagnostic techniques, on the network fault diagnosis, the general principle for
dealing with the network fault is “software first, hardware second”, but in practice, it will
depend on specific analysis, to find out the corresponding solution.
VALUING
Base on the steps in Diagnosing Faults in Network, what are the benefits a persevering
person can achieved even there are steps to accomplished to meet the goal.
1.
8
2.
POST TEST
Direction: Given the problem on internet connection failure, try to match column A to B
for the steps in resolving the connection failure.
9
H. 8 Identify the results and
Check the computer for effects of the solution.
malware and remove any found.
On Windows computers try
resetting the network connection.
10