CompTIA® Server+ : Troubleshooting The Problems
Identify the problem and determine the scope
Question users/stakeholders and identify changes to the server / environment : This requires you to ask questions to the person who was using the server at the time problem occurred. These questions include what happened , if it is a frequent problem, if any specific error message was displayed.
Collect additional documentation / logs : Event logs should be checked for any error messages.
If possible, replicate the problem as appropriate : Try to replicate the problem yourself or with the help of the person who reported the problem.
If possible, perform backups before making changes : A backup should be taken before you start making changes to system to ensure if anything goes wrong there will be no data loss and possibilty of restoration.
Establish a theory of probable cause (question the obvious)
Test the theory to determine cause
Establish a plan of action to resolve the problem and notify impacted users
||Ping: This command can be used to verify whether the target ip address or host name is present. You need to specify the target IP address or host name. You can ping the loop back address at 127.0.0.1. A response ensures that the TCP/IP stack is installed properly on your computer.
||Determines the route packets take to reach the specified destination.
||Displays TCP/IP configuration values, including IP address, subnet mask, and default gateway
||nslookup provides the IP address of the remote computer after querying the DNS server for the IP config information.
||net use can control drive mapping: mounting ("mapping" in Microsoft terminology) drive shares in a network environment. This command makes use of the SMB (server message block) and the NetBios protocol on port 139 or 445.
||Displays and manipulates route information.
|| This utility displays current NetBIOS over TCP/IP connections, and display
NetBIOS name cache.
|| Displays protocol statistics and current TCP/IP connections since the server was last booted.