Create a trouble shooting report so i have answered some questions , if you can answer remaining
Question:
- Create a trouble shooting report so i have answered some questions , if you can answer remaining question that would be great please and problem is that they mixed up default fateway ip addresses
- Describe the Problem Domain
On 5 November 2020 at 9:30, Mr Bunyuck who is an Accounts Technician in the Accounting Department reported that communication between PCs in different networks is not working. Recently a network engineer completed upgrades to the network.
It's a small company with two admins pcs and two accounting pcs.
Mr Brunyuck reported that accounting pcs are not able to communicate with admin pcs who are on different network.
TICKET INFORMATION
User name: | Arthur Bunyuck | User ID: | abunyuck |
Job title: | Accounts Technician | ||
Manager: | Ernest Young | Department: | Accounting |
Ticket category: | Urgent | ||
Date and time: | 05 November 2020 ? 9:30 am | Technician: | Haider Ali |
Network physical topology
- Describe your framework for solving the Problem (A+ Certification).
Having A+ certification helps me learn how to troubleshoot a variety of gadgets, from cell phones to laptops. To solve any issue, we follow six steps.
1. Determine the issue.
2. Develop a likely cause theory. (Ask the obvious question)
3. To determine the cause, test the theory.
4. Create a plan of action to solve the issue and put the solution into practise.
5. Check the complete system functions and, if necessary, take preventative action.
6. Keep track of your results, decisions, and actions.
- Troubleshooting Strategy for Solution (e.g. Half Split, bottom up, top bottom or other)
The troubleshooting strategy we will be using is top bottom where we will check every application and devices before the potential root of the issue is identified.
Every conclusion and situation will be recorded. We will have to decide what device we should examine first.
This approach is for minor problems or when you think there may be a software-related issue, which is what we now consider to be the issue.
- Identify the area affected
Admin and accounts pc are most affected is they are not able to communicate with each other. They are also having trouble communicating with the router, which prevents them from connecting to other networks or users outside the structure.
- What are the Symptoms of the problem and what is affected?
There may be a variety of problems causing these users to communicate with one another outside of their network.
- Physical connectivity issue meaning these devices are not connected to each other with right cable or cable could be broken. If the cable is damage it can reduce amount of data that can travel through it without losing any packet. Connecting these devices with wrong cable will result in no communication.
- When a network administrator manually assigns IPs to hosts or devices, this is known as static IP allocation. It is one of the main reasons why two devices may have the same IP address established by the network administrator, which might result in a Windows IP address conflict. This issue might result from the use of poor IP address management solutions, like spreadsheets.
- If the incorrect default gateway IP address is put on these devices, it may also prevent communication with users outside of your network because the default gateway is a mechanism for connecting your host to remote network segments or users outside of your network.
- Most Likely Source of the Problem
Most likely source of the problem could be not entering the default gateway IP addresses properly because these users were able to communicate inside their network which indicates there's no physical connectivity issues and there's no issue with IP addresses either. The only issue they were facing was communicating with users outside which could be because of not communicating with routers.
2. Establish a Theory of Probable Causes
2.1. Hierarchy of Probable Causes
There are several potential reasons that might cause the issue you described. These include:
- Hardware failure: It is possible that a hardware component is not functioning properly, which could be causing the issue.
- Software bug: There may be a bug in the software that is causing the issue.
- User error: It is possible that the issue is being caused by a mistake made by the user.
- Network issue: The issue could be related to a problem with the network or internet connection.
- Environmental factors: External factors such as temperature or humidity could be affecting the functioning of the system.
2.2. Using your knowledge, prioritize the list.
When trying to determine the cause of an issue, it is typically most likely that the problem is due to user error. Software bugs and hardware failures are also common causes. These types of issues can often be resolved quickly and inexpensively. Network and environmental issues are less common and may be more challenging and expensive to fix.
2.3. Escalate to a higher level if a probable cause cannot be determined.
If a problem cannot be solved through testing and troubleshooting, it may be necessary to ask for help from someone with more expertise. Before doing this, gather as much information as possible about the problem
3. Test the Theory to Determine Cause
3.1. Apply a series of tests to ensure the solution is valid/
4. Establish a Plan of Action to Resolve the Problem and Implement the Solution
4.1. Complete a set of steps to demonstrate the solution
Comment: Suggest a short set of key steps (less than 8 steps) that could be followed easily by a junior technical support employee to implement the solution.
Comment: List any limitations to your system - or any other points you want to explain
- Verify Full System Functionality and Implement Preventative Measures
5.1. Testing Unit or Complete set of testing logs for the system
Comment: Output for the complete Testing Log placed here
Tester:
Date:
Location:
5.2. Preventative Measures
Comment: suggest two (2) measures to ensure somehow this problem could be prevented or minimised in future>
6. Document Findings, Actions, and Outcomes
6.1. Reviewing and evaluate the problem solving process you used to solve the problem.
Comment: Was the methods, strategies and processes effective in arriving at a solution?
|
6.2. List a set of conclusions regarding the effectiveness of the problem solving process
Comment: (provide 3 conclusions - in bullet point format)
|
6.3. Recommendations (improvements on the system)
Comment: (provide 3 recommendations for the future - in bullet point format) - here some discussion that includes ways that the network might be improved .
|
References
Comment: Apply proper Harvard referencing style for all your references
Appendices
Appendix A: Help Desk Ticket
Comment: Complete an appropriate Help Desk ticket to illustrate this problem and its relevant features. Replace information below with relevant information from your problem network.
Help Desk Trouble Ticket #190999
| TICKET INFORMATION |
| User name: | Paul Cook | User ID: | pcook
|
| Job title: | Lecturer / Technician
| ||
| Manager: | Phil Lynott | Department: | Business and IT
|
| Ticket category: | Urgent
| ||
| Date and time: | 29 Oct 2019 — 9:30 am | Technician: | John Ritchie
|
| PROBLEM DESCRIPTION | |||
Comment: Insert at least two sentences to describe the problem.
| |||
| TECHNICIAN RESPONSE | |||
Assigned to: John Ritchie Date: 29 October 2019 Time: 10:00am Total time worked:
| |||
Initial action:
| |||
| Follow up action: | |||
Importance: o Mission critical o Slowing user down o Can be scheduled Conclusion: o Resolved o Pending o Unresolved
| |||
| Final notes: | |||
| Trouble Ticket downloaded from: http://techrepublic.com | |||
Expert Answer:
