Skip to main content
Barracuda MSP Partner Toolkit

How to Resolve an Incorrect Proxy Detection

Before or after installation the Onsite Manager or Device Manager may detect and attempt to connect through a Proxy server which no longer exists on the network regardless of the settings in MWProxyConfigurationTool. 

The TraceExpertSystem.txt log or LpiSetups.log may show errors similar to the following or other errors indicating failures connecting to a proxy

INFO LPI.ExpertSystem.ActionManagers.SCLogManager - Could not post om scanning status to SC - System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.50.12:8080

If the issue occurs during the installation of an Onsite Manager or Device Manager

If the issue occurs during the installation of an Onsite Manager or Device Manager, follow the steps below:

  1. Launch the PowerShell as Administrator and type the following to determine the current logged on username

    Get-WmiObject win32_useraccount | Where-Object {$_.Name -eq $env:USERNAME}

    The output should  appear like the following:
    clipboard_ee41d438ae95382cd3fd70649d9ab41d4.png
  2. Make note of the SID as support will need it to determine the correct path in the Registry
  3. Open the Registry key and expand HKEY-USERS
  4. Expand the Registry key with the name that matches the SID from steps 1-2
  5. Navigate to the following subkey path

    \Software\Microsoft\Windows\CurrentVersion\Internet Settings\
     

  6. Change the REG_DWORD value named ProxyEnable to 0 
  7. Now expand the Internet Settings key and select the Connection key
  8. Delete the REG_BINARY values named DefaultConnectionsSettings and SavedLegacySettings

If the MWEPERTSYSTEM Service fails to connect after a successful installation 

  1. Open the Services.msc snap-in and locate the MWExpertSystem service
  2. Right click on the service tab and choose Properties
  3. Click the Log on tab
  4. Make note of the Log On Settings
    1. If the Service is configured to run as MWService for example, run POwerShell as Administrator and use the following command to determine the SID for the account:

      Get-WmiObject win32_useraccount | Where-Object {$_.Name -eq “MWService”}

      The output should appear like the following:
      clipboard_e536125d69c4237bc08e6e484e0187936.png
      Note: You may need to substitute MWService with a different account name. In the case of a Domain account, you do not need to specify the name in the format of "DOMAIN\MWService"
    2. If the service is configured to run as the Local System Account the SID should be the following:
      S-1-5-18
  5. Expand the Registry key with the name that matches the SID from steps 4.1 or 4.2
  6. Navigate to the following subkey path

    \Software\Microsoft\Windows\CurrentVersion\Internet Settings\
     

  7. Change the REG_DWORD value named ProxyEnable to 0
  8. Expand the Internet Settings key and select the Connections key
  9. Delete the REG_BINARY values named DefaultConnectionSettings and SavedLegacySettings

Additional Information

  • For additional information regarding how to configure client proxy server settings by using a registry file, please click
    here
  • For additional information regarding how to reset your Internet Explorer proxy settings, please click here