PSA and RMM

Solve any challenge with one platform

Operate more efficiently, reduce complexity, improve EBITDA, and much more with the purpose-built platform for MSPs.

Cybersecurity and Data Protection

Ensure security and business continuity, 24/7

Protect and defend what matters most to your clients and stakeholders with ConnectWise's best-in-class cybersecurity and BCDR solutions.

Automation and Integrations

Integrate and automate to unlock cost savings

Leverage generative AI and RPA workflows to simplify and streamline the most time-consuming parts of IT.

University

University Log-In

Check out our online learning platform, designed to help IT service providers get the most out of ConnectWise products and services.

About Us

Experience the ConnectWise Way

Join hundreds of thousands of IT professionals benefiting from and contributing to a legacy of industry leadership when you become a part of the ConnectWise community.

News and Press

Experience the ConnectWise Way

Join hundreds of thousands of IT professionals benefiting from and contributing to a legacy of industry leadership when you become a part of the ConnectWise community.

ConnectWise

Sonic Windows Zone Not Working [2026]

If the issue persists after all steps, collect NetExtender logs ( C:\Program Files (x86)\SonicWall\NetExtender\logs ) and open a case with SonicWall support.

What Does “Sonic Windows Zone” Mean? When you connect to a corporate network using SonicWall NetExtender (SSL-VPN), the client assigns your computer’s network connection to a specific network zone in Windows. This zone determines the firewall rules applied to your VPN traffic. Typically, the SonicWall client forces the VPN tunnel into the “Public” or “Domain” zone – but sometimes users report that the “Windows Zone” appears as “Not Working,” “Unidentified,” or “No Network Access.” Sonic Windows Zone Not Working

Get-NetConnectionProfile Look for the interface matching your VPN (often named “Unidentified network”). Change its category to (if allowed by security policy): If the issue persists after all steps, collect

Set-NetConnectionProfile -InterfaceAlias "Ethernet X" -NetworkCategory Private Replace "Ethernet X" with the actual interface name from Get-NetConnectionProfile . This zone determines the firewall rules applied to