How To: Disable Windows Firewall via Command Prompt

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected: All

     

    Overview

    This article explains how to disable Windows Firewall from the command prompt. Disabling it from the Windows Firewall GUI does not always work, since the GUI reflects Group Policy settings pushed down from the domain controller — using the command prompt instead changes the local server's firewall settings directly.

     

    Disable Windows Firewall via Command Prompt

    1. Open Command Prompt as Administrator and run the following command to show the current state of each firewall profile:
      netsh advfirewall show allprofiles

    Command Prompt window showing the output of netsh advfirewall show allprofiles, with the Domain, Private, and Public Profile Settings each showing State: ON.

    1. To turn off every profile at once, run:
      netsh advfirewall set allprofiles state off

    Command Prompt window showing the output of netsh advfirewall set allprofiles state off, followed by netsh advfirewall show allprofiles confirming all three profiles now show State: OFF.

    1. To view or turn off a single profile instead of all of them, specify that profile by name — for example, for the Public profile:
      netsh advfirewall show public
      netsh advfirewall set public state off

    Command Prompt window showing netsh advfirewall set public state off, followed by netsh advfirewall show allprofiles confirming only the Public profile now shows State: OFF while Domain and Private remain ON.

     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.