FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
nithincs
Staff & Editor
Staff & Editor
Article Id 415584
Description This article is a detailed, comprehensive guide for collecting network troubleshooting information from a Windows client machine using the command prompt.
Scope FortiGate.
Solution

Step 1: Open Command Prompt:

Select the Start button or press the Windows key, type 'cmd' or 'Command Prompt' into the search bar, and select Command Prompt in the search results.

Step 2: Execute Network Diagnostic Commands:

 

C:\Users\System32>ipconfig
C:\Users\System32>ipconfig /all
C:\Users\System32>arp -a
C:\Users\System32>ping <pc gateway>
C:\Users\System32>getmac /v
C:\Users\System32>ping 1.1.1.1
C:\Users\System32>ping 1.1.1.1 -l 1472 -f -n 4

C:\Users\System32>pathping 1.1.1.1
C:\Users\System32>netsh winhttp show proxy
C:\Users\System32>tracert -d -w 500 1.1.1.1

C:\Users\System32>tracert -4 www.google.com
C:\Users\System32>tracert -6 www.google.com
C:\Users\System32>nslookup www.fortinet.com 8.8.8.8
C:\Users\System32>nslookup www.fortinet.com
C:\Users\System32>query user
C:\Users\System32>route print
C:\Users\System32>ipconfig /displaydns
C:\Users\System32>netstat -ano

C:\Users\System32>netsh interface ipv4 show subinterfaces

C:\Users\System32>netsh interface ipv4 show route

 

Step 3: Run the typeperf Command (Performance Data): This command collects performance data, specifically the send/receive rates for a network adapter.

 

  • Identify the Adapter Name: Review the output from ipconfig /all in the log file. Find the active adapter (e.g., 'Wireless LAN adapter Wi-Fi'). The required name is the exact string value next to Description.

 

Example :

Adapter Name: Intel(R) Wi-Fi 6E AXxxx 160MHz

 

C:\Windows\System32>ipconfig /all

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Wi-Fi 6E AXxxx 160MHz <<<<<<< this is network adapter name
Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.29.245(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 19 October 2025 08:59:36
Lease Expires . . . . . . . . . . : 20 October 2025 08:59:37
Default Gateway . . . . . . . . . : 192.168.29.1
DHCP Server . . . . . . . . . . . : 192.168.29.1
DNS Servers . . . . . . . . . . . : 8
192.168.29.1
NetBIOS over Tcpip. . . . . . . . : Enabled

  • Execute typeperf: Run the command, replacing <THEAdapterName> with the exact name found in the step above. The commands need to run as:

 

C:\Users\System32>typeperf "\Network Interface(Intel(R) Wi-Fi 6E AXxxx 160MHz)\Bytes Sent/sec" "\Network Interface(Intel(R) Wi-Fi 6E AXxxx 160MHz)\Bytes Received/sec"

 

Manually execute the command below, and press Ctrl+C after 15 seconds. Copy all executed commands' output for the affected PC to a file.

 

Related documents:
Performing a sniffer trace or packet capture

Troubleshooting Tip: First steps to troubleshoot connectivity problems