Windows WAN Network Troubleshooting
Jenny1995
Troubleshootingrecomendationchanges.docxRunning Head: Response 7
Windows WAN Network Troubleshooting
by [Name]
Course
Professor
[Name of Institution]
16th September, 2018
Part 1
Troubleshooting process
The data connectivity issues that are faced by the employees at the location A and B are solved by following a process of troubleshooting. Through this process, the IT specialists will be able to know about the problem area and what concrete steps should be taken by them in order to solve this problem by applying troubleshooting tools.
The network troubleshooting steps that are involved in this process are mentioned below:
1. Everything in the power cycle along with other connecting devices must be checked. By rebooting the equipment this problem can be solved. Firstly, reboot the PC along with the modem and router. The modem along with routers caches must be checked and must be wait for 60 seconds before the PC, routers and modem are connected to it. The turning of everything off and again on will help in ensuring that the problem is permanent not temporary (Buseung Cho, 2017). Hence, in the first step it is better to reboot than to wait for 30 minutes that wastes time.
After this rebooting the computer will be restarted to check whether these devices are connected with the network or not. If still they are not connected, then there is an issue with an ISP and its equipment. Antivirus scan must also run that will remove malware interfering from the connection.
2. Check physical connections: If the problem of connectivity after rebooting still exists than the physical contact will be checked. The Ethernet cable will be tested that is connected with the router might be unplugged or damaged. Once the connection is verified, then the equipment related to it must be checked. If the lights of the router are flashing green or regular than it is ok (Dana, Zadeh, Kalantari, & Badie, 2010). If no light comes out, then the reboot defects and if the red light is detected, then the ISP is down.
3. Run the network troubleshooters: By automatically running the troubleshooter the problematic areas will be fixed rather than locating it and then setting it. For the networking problems, the network icon will be selected and then troubleshoot problem will automatically solve the problem. If it can’t fix the problem, this problem will be identified that can be set manually.
4. Check the valid IP address: As all the computer are not working therefore it is important to identify a spot that connect all these computers. In this way, the problematic area will be identified. To check it, the network and sharing center in the menu will be selected. Through this, we get into the properties of IP (Csikor & Pezaros, 2017). The DNS server will be checked automatically. The valid IP address can be obtained from it. The command prompt dialogue box helps in troubleshooting the problem of wireless LAN and Ethernet adapter. Through these two commands the config /release and ipconfig /renew this problem will be solved.
5. Try PING and Trace tools on the route: If the IP address starts working while running the config then we have a valid IP address between the router. Thus, the problem that is between the internet and router will be identified in this way. On the Google DNS, this command will be write in the foam of ping 8.8.8.8 (Shiyong Wang, 2018). This will help in tracing the problem between the computer and the Google DNS server. Through this command, a step by step breakdown will obtained but during this, if the error pops up, then there is a problem with local area network.
6. Contact with your ISP: After the implementation of the steps mentioned above. It is verified that all our equipment is working. In this way, a valid IP address is obtained. This is also identified that the networking problem is occurring outside. Through the ISP the problematic area will be detected.
7. Wait it out: The main issue is with the ISP hence the problem will be fixed at that end. By collaboration with internet service provider, this problem will be further solved.
8. Get connected: After solving the issue of ISP all the interrupted locations will connect again.
Network troubleshooting tools:
For every network administrator, it is necessary that they must know about the troubleshooting tools as they are of great help in solving problems. Below mentioned is a list of troubleshooting tools that are used to solve the problem of networking:
Tracert: This tool is used to determine the connectivity, as it provides more accurate information. It gives precise information about the specific path and the destination host. It also includes information about the packets of routes as it allows for information about the intermediate hosts. This tool is based on Linux/*nix machines (Cziva, 2017). This tool proved to be a great help in solving this problem of networking troubleshooting as it provides accurate information about the issue and also identifies certain points where this problem is present that saves time.
Ping: Ping utility is the most accurate tool. Through this tool, basic connectivity test is conducted between the destination host and requesting host. ICMP, internal control message protocols are used that can send an echo packet to the destination host. Thus, this gives a basic picture of where the problem exists. The ICMP facility of this tools will help in resolving this problem in a limited time.
Path Ping: Through this tool more detail picture of the problem is generated that gives a comprehensive look and identify the host from where the issue of error in connectivity arises. This tools will help me in getting details of the issues so that this problem cannot be occurred in future.
NETSTAT: The connectivity problem that is faced at location C where the network is connected, but the slow speed creates difficulty for the office staff. Hence, active network connection problems are identified through it. It is used to determine which service at the host is not active.
NSLookup: The issue related to the Dynamic Name system (DNS) is resolved by this tool as this is specifically designed for this networking problem (Denney, 2017). It is used by everyone who is using the internet. In solving the problem of networking at the location A and B this tool will be used to identify those IP address where this problem more likely to occur. Through this default, DNS configures are identified.
Nbtstat: This tool is applied at location C, where it figures out the currents state of active network connections. Through this Nbtstat tool, active and non-active posts are identified.
Performance monitor: The performance monitor would be of great help that continuously monitors the problem and before the occurrence of the problem the low-performance areas are identified. So that the issues are rectified before occurring.
The networking performance problems that are identified in this case are due to the lack of implementation of networking troubleshooting tools. Without proper repair and maintenance, as well as lack of adequate monitoring, lead to arise the problem for both locations. The location B faces more issues because they are totally disconnected from the server. While the location C have somehow internet connection but the internet is not working properly.
Part 2
In the identification of the problem that is presented here is the lack of connectivity with the server and second one is bad performance of internal server provider (Richard Cziva, 2017).
The steps that I recommend for solving this problem at both locations are mentioned below:
• Firstly, the rebooting of equipment must be checked in all routers and modems and also at the connected devices or cables. So that, it can be analyzed where the problems are present whether in the equipment or at the end of internet service provider.
• Secondly, the connection of all internet must be checked physically because due to damages to the physical system there is more likely chances that the connectivity problem arises.
• Thirdly, automatically running the troubleshooting option in the PC the problem can also be rectified.
• Fourthly, if the problem does not solve by automatically running the troubleshooting then this can be further rectified by checking the IP address.
• Lastly, by implementing the networking troubleshooting tools, the problem can rectify and settled in the long run.
Before implementing the tools, it is essential that at the central server, the performance monitoring tools, and nslookup must be implemented. Through these tools, long-term problems related to connectivity will be solved. As performance monitoring is the primary tool that will save from any type of problem. With the help of this tool problem will be solved before occurring.
Furthermore, as per the current situation the application of “Tracert,” and “Nbtstat” troubleshooting tools at the server will help in resolving the connectivity problem. By applying the “Tracert,” tool at the problematic area. It will help in solving the problem at the point where it is occurred rather than checking all the points that might be the reason of problem.
Moreover, “Nbtstat” should be implemented that will identify what are the active points of internet connectivity with the server and what are the other inactive points that lack in connectivity. In this way, only those points will be repaired that are not connected rather than checking all the points. The Linux/*nix machines of this tools will help to identify the inactive points.
Concluding the recommendation, in a nutshell, it is important to mention that a combination of tools is used to solve the problem in the long term. These advanced and high technological tools is a perfect solution to networking troubleshooting problem.
References Csikor, L., & Pezaros, D. P. (2017). End-Host Driven Troubleshooting Architecture for Software-Defined Networking. GLOBECOM 2017 - 2017 IEEE. Retrieved from https://ieeexplore.ieee.org/abstract/document/8254759/citations Cziva, R. P. (2017). Container network functions: bringing NFV to the network edge. IEEE Communications Magazine,, 24-31. doi:10.1109/MCOM.2017.1601039. Retrieved from: https://ieeexplore.ieee.org/document/7945849/ Dana, A., Zadeh, A., Kalantari, M., & Badie, K. (2010). A traffic splitting restoration scheme for MPLS network using case-based reasoning. Ultra Modern Telecommunications and Control Systems and Workshops (ICUMT) 2010 International Congress on, 635-641. doi:10.1109/APCC.2003.1274461 Retrieved from: https://ieeexplore.ieee.org/document/1274461/?section=abstract Richard Cziva, D. P. (2017). On the Latency Benefits of Edge NFV. 2017 ACM/IEEE Symposium on Architectures for Networking and Communications Systems (ANCS). doi: 10.1109/ANCS.2017.23. Retrieved from: https://ieeexplore.ieee.org/document/7966908/ Shiyong Wang, J. W. (2018). Knowledge Reasoning with Semantic Data for Real-Time Data Processing in Smart Factory. Sensors , 471. doi:https://doi.org/10.3390/s18020471. Retrieved from: http://www.mdpi.com/1424-8220/18/2/471
