Troubleshooting

If you place your mouse cursor over the Connect Filter system tray icon, these information pop-ups are available.

Status Description
Connected Connect Filter for Windows is connected and filtering accordingly. There are no known issues.
Smoothwall Filter rejected authentication

The NTLM handshake has failed due to any number of reasons:

  • The Smoothwall Filter isn't signed in to the domain.
  • The Smoothwall Filter only signs in to the Active Directory domain when checking user credentials. It could be that it's unable to sign in. Try running the directory services diagnostics, see our help topic, Managing directories.
  • The user account being used, has either been removed from the domain, or no longer exists.
  • The Smoothwall Filter's session has expired.
  • The user's session has expired.

You should sign back in to the domain. Typically, by logging off of the device and logging back on again.
Unable to connect to the Smoothwall Filter Indicates that the Smoothwall Filter that hosts the Connect Filter proxy server is not responding, or not contactable. We recommend that you check to see if other clients can connect to the Smoothwall Filter first, before rebooting the Smoothwall Filter and Firewall hardware appliance.
Filtering not available The Smoothwall Filter that hosts the Connect Filter proxy server is not responding, or not contactable but, as Failure Mode is set to Open or Continue to requested sites without filtering, browsing is still available.
Unable to contact the Smoothwall Connect Filter service The Connect Filter for Windows client is unable to contact the Connect Filter service running on the local device. Either the service isn't running, or something is blocking the client from seeing the local service.
Captive User Portal detected Connections can't be directed to the Smoothwall Filter as a captive User Portal has been detected. Users must authenticate with the captive User Portal first before continuing.
Unknown problem with Smoothwall Connect Filter system This is a serious issue with the Smoothwall Connect Filter client. We recommend that you contact support.