

Right click the Wireshark entry showing the 407 error, then select "Follow TCP Stream".If the issue is with proxy authentication, you will see entries here indicating 407 Proxy Authentication Required responses from the Barracuda Web Filter.Within Wireshark, find the Filter field, and enter the following string: = 407.Click the Capture menu again, and select Stop.Run the application that is causing the issue, and reproduce the issue.Select the appropriate network interface for your web traffic, then click Start.Open Wireshark, click the Capture menu, then select Interfaces.In this case, the only option to resolve this issue is to configure the Barracuda Web Filter to exempt that applications traffic from proxy authentication requirements, then whitelist any domains it accesses for unauthenticated users.įollow these steps to determine the traffic the application is sending, then exempt that traffic: These applications will collect this information automatically from Internet Options.


This may not always be an option, particularly with applications that do not offer the option to disable proxying. The simplest resolution to this situation is to disable proxying for applications that are experiencing errors when forwarding to the Barracuda Web Filter. Applications without NTLM/Kerberos support will not pass on a user?s authentication to the Barracuda Web Filter, and in turn their web traffic will be rejected without a block page. Typical symptoms include authentication prompts, cache access denied messages, and 407 errors. If you notice a particular application is not working with an upstream Barracuda Web Filter, the source of the problem may involve proxy authentication incompatibility. However, using this scheme typically requires some advanced configuration, particularly for applications that do not explicitly support NTLM/Kerberos authentication. Using Kerberos or NTLM authentication schemes allows multiple users from the same IP address to be identified for logging and policy application. Devices installed in a forward proxy configuration with NTLM or Kerberos authentication.Back to Knowledgebase How can I troubleshoot and resolve issues with proxy authentication required errors?Īpplies where all of the following applies:
