Issue The SafeGuard Enterprise Client is unable to connect to the SafeGuard Enterprise Server, although the client can contact the server machine (ping via IP address and FQDN). The User Machine Assignment never takes place and the POA resides in autologon mode. Troubleshooting according to KBA 109662 "SafeGuard Enterprise: analyzing client-server communication (Troubleshooting guide)" did not resolve the problem.
Known to apply to the following Sophos product(s) and version(s) SafeGuard Device Encryption
Verify if an outdated or improperly configured WinHTTP Proxy setting was imported to the client. To do so, open the command prompt and type "ProxyCfg.exe" to display the current WinHTTP proxy settings. Hint: With Windows Vista, Windows 7 and Windows Server 2008 the 'ProxyCfg.exe' tool has been replaced by the 'Netsh.exe'. Run "Netsh.exe winhttp show proxy" to show the current configuration.
Netsh.exe winhttp show proxy
On x64 based systems, make sure to execute Netsh.exe from C:\Windows\SysWOW64\ folder
Example on Windows XP Client:
In case that the configured "Proxy Server(s)" would not be valid anymore, please remove it from the WinHTTP proxy configuration or completely switch to direct access mode via "Proxycfg.exe -d" to bypass all configured WinHTTP proxy servers.
Configured WinHTTP proxy settings can also be verified via the following Registry Key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\WinHttpSettings
The SafeGuard Enterprise Client should be able to communicate with the SafeGuard Enterprise Server now.
More information regarding the Proxycfg tool and how to configure a bypass list or direct access can be found at: http://support.microsoft.com/kb/289481
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. If you need technical support please post a question to our community. Alternatively for licensed products open a support ticket.