Case Project 13-1

Case Project 13-1

1. A. The first thing to do is identify the problem and the symptoms – It’s only after this that you can begin to find the cause of the issue.

B. Determining the Problem’s Scope – Does the problem affect one user or multiple users. Once you figure that out, then you can figure out when it began, how often it happens, and if it happens at certain times of the day, week, month, or year.

C. Question Users – As a human being, it’s natural to make mistakes. They could’ve had CAPS lock on by mistake for example. Ask them to perform their network tasks to watch them by using a remote desktop program.

D. Determine If Anything Has Changed – Such as Operating Systems or the configurations on a server, workstation, or connectivity device change. Were new users added, anything moved to a new location, etc.

E. Re-create the Symptoms – You do this to see the problem or error for yourself. If you aren’t able to reproduce the symptom or symptoms, you might suspect that the problem was a one-time occurrence or that a user performed an operation incorrectly.

F. Verify Physical Layer Connectivity – Here is where you check any connections of cabling and network adapters. Also check the signaling of both wired and wireless. These are quite common and are often easily fixed, so you should be thoroughly familiar with the symptoms of such problems.

G. Verify Logical Connectivity – This is where you examine the firmware and software configurations, settings, installations, protocols, routes, and privileges. Depending on the type of symptoms, you might need to investigate networked applications, the network operating system, or hardware configurations. you are a network support technician for farm kettle foods, a specialty food supplier with five locations across the state.

H. Test Physical Layer Theories and Logical Connectivity Theories – Here is where you can assess the component individually to determine if it is the source of the problem. You can test...