To determine if Windows Firewall is the cause of application failures - With the Firewall logging feature you can check for disabled port openings, dynamic port openings, analyze dropped packets with push and urgent flags and analyze dropped packets on the send path.To verify if newly added firewall rules work properly or to debug them if they do not work as expected.Doing this for several entries will build a picture of what Windows is doing and how it's malfunctioning, and from that you can employ further troubleshooting techniques to determine the specific setting or component of Windows that needs to be fixed. Instead, you will have to find multiple entries that are related to connectivity, then search the internet to find longer explanations of what those mean. Individual log entries you find will likely not point directly at a cause of failure. Scroll down until you find WLAN-Autoconfig. WLAN-Autoconfig: Expand Applications and Services.Scroll down until you find Diagnostics-Networking. Diagnostics-Networking: Expand ApplicationsĪnd Services Logs, then Microsoft, then Windows.You can look up Networking Event IDs online. System: Expand Windows Logs System will be listed underneath.įilter the log for networking entries (for example, for source 'Diagnostics-Networking', or specific Event IDs that apply to wireless, 802.1x, WPA2).

Within Event Viewer, navigate to each log: Alternatively, from the Control Panel, choose Administrative Tools and then Event

To find these logs, search for the Event Viewer. In Windows, you can use the Diagnostics-Networking, WLAN-Autoconfig, and System logs to do advanced and focused troubleshooting. Find logs for troubleshooting Windows connectivity

Tcp log view