Network Troubleshooting Tool

How to Run the Tool

1. Download the tool using the button above.
2. Extract the ‘Tech AD Network_Tools Ver 1.0.zip‘
3. Double-click on ‘start.bat‘.
4. Click on the ‘Run Tool‘ button.

What is it?

The Network Troubleshooting Tool is a GUI-based utility designed to help users quickly diagnose and resolve common network connectivity problems. It provides direct access to essential Windows networking commands, allowing both beginners and professionals to analyze and monitor network performance in real time.

Users can input a Host/IP (for example, google.com or 8.8.8.8) and an optional Port number to test network reachability, connectivity paths, and configuration details.

---

Interface Components

Input Fields

• Enter Host/IP
  Enter the hostname or IP address of the target system you want to test (e.g., 192.168.1.1 or example.com).
• Enter Port (Test Port)
  Specify a port number (optional) for operations like Test Port or Port Scan. For instance, you might enter 80 for HTTP or 443 for HTTPS.

---

Function Buttons

1. Ping

Performs a standard ICMP ping to the entered host/IP.

• Purpose: Checks whether the target host is reachable and measures response time (latency).
• Equivalent Command: ping <host/IP>
• Use Case: Verify basic network connectivity.

---

2. Traceroute

Executes a traceroute to the specified destination.

• Purpose: Displays the path packets take from your system to the target host, including all intermediate routers (hops).
• Equivalent Command: tracert <host/IP>
• Use Case: Diagnose where network delays or failures occur.

---

3. Pathping

Combines the features of ping and traceroute.

• Purpose: Measures packet loss and latency across the network route.
• Equivalent Command: pathping <host/IP>
• Use Case: Identify unreliable network segments.

---

4. DNS Lookup

Queries DNS records for the specified domain name.

• Purpose: Resolves the domain to its corresponding IP address and provides DNS response details.
• Equivalent Command: nslookup <domain>
• Use Case: Check DNS resolution and identify potential DNS issues.

---

5. Show IP Config

Displays basic network adapter configuration.

• Purpose: Lists current IP address, subnet mask, gateway, and DNS server.
• Equivalent Command: ipconfig
• Use Case: Verify local network configuration.

---

6. Show IP Config /all

Shows a detailed network configuration report.

• Purpose: Provides extended information including MAC address, DHCP details, lease times, and adapter status.
• Equivalent Command: ipconfig /all
• Use Case: Deep network diagnostics and configuration analysis.

---

7. Flush DNS

Clears the DNS resolver cache.

• Purpose: Removes cached DNS entries to resolve updated or conflicting domain records.
• Equivalent Command: ipconfig /flushdns
• Use Case: Fix issues where domain names resolve incorrectly or not at all.

---

8. ARP Table

Displays the Address Resolution Protocol (ARP) table.

• Purpose: Lists IP-to-MAC address mappings on the local network.
• Equivalent Command: arp -a
• Use Case: Identify connected devices or troubleshoot local network communication.

---

9. Netstat

Displays active network connections and listening ports.

• Purpose: Shows current TCP/UDP connections, ports in use, and associated processes.
• Equivalent Command: netstat -an
• Use Case: Check open ports, identify suspicious connections, or monitor active sessions.

---

10. Routing Table

Displays the local routing table.

• Purpose: Lists how network traffic is directed to different networks or interfaces.
• Equivalent Command: route print
• Use Case: Diagnose incorrect routing or gateway issues.

---

11. Test Port

Tests whether a specific port on a target host is open and responsive.

• Purpose: Validates service availability on a given port.
• Equivalent Command: (Custom implementation or Test-NetConnection <host> -Port <port>)
• Use Case: Check if a web server, mail server, or any other service is reachable.

---

12. Stop Command

Stops any currently running command or test.

• Purpose: Terminates a long-running process (like traceroute or pathping).
• Use Case: Use this if a test hangs or takes too long to complete.

---

Usage Example

1. Enter google.com in the Host/IP field.
2. Click Ping to verify connectivity.
3. If packets are lost, click Traceroute to see where the failure occurs.
4. Use DNS Lookup to verify if the domain resolves properly.
5. Check Show IP Config /all to confirm your local settings.

---

System Requirements

• Operating System: Windows 10 or higher
• Permissions: Administrator privileges may be required for certain commands (e.g., Flush DNS).
• Dependencies: Built-in Windows networking utilities (no external installation needed).

---

Notes

• Use Stop Command to cancel ongoing tests.