<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Firewall on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/firewall/</link>
		<description>Recent content in Firewall on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Thu, 16 Jul 2026 18:05:29 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/firewall/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Investigate Windows Firewall Traffic with PowerShell</title>
				<link>https://www.compilemymind.com/posts/investigate-windows-firewall-traffic-powershell/</link>
				<pubDate>Thu, 16 Jul 2026 18:05:29 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/investigate-windows-firewall-traffic-powershell/</guid>
				<description>&lt;h2 id=&#34;direct-answer&#34;&gt;Direct answer&lt;/h2&gt;&#xA;&lt;p&gt;Windows Firewall troubleshooting should distinguish the active profile, the rule that may apply, and the port or protocol being tested. Inspect those boundaries with read-only queries before creating an exception, disabling a profile, or assuming that the application is listening on the expected address. Start with evidence already available to the operator and use the referenced documentation to verify the behavior of the component in scope.&lt;/p&gt;&#xA;&lt;h2 id=&#34;prepare-a-safe-investigation&#34;&gt;Prepare a safe investigation&lt;/h2&gt;&#xA;&lt;p&gt;Record the host, active network connection, application or service, direction of the traffic, protocol, port, remote endpoint, and the time of the failure. Confirm the investigation is authorized and avoid disabling a firewall profile as a diagnostic shortcut. Preserve the observed state so a later change can be compared with the original configuration. Record the evidence in the incident before making a change; preserve values and timestamps exactly as observed.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
