How to enable a SafeGuard Enterprise Client to connect to the SafeGuard Enterprise server via FQDN or IP address

  • Article ID: 108260
  • Rating:
  • 3 customers rated this article 2.7 out of 6
  • Updated: 01 Dec 2014

After installing SafeGuard Enterprise, the client cannot connect to the SafeGuard Enterprise Server. The Client is located on a different network segment to the SafeGuard Enterprise Server.

Known to apply to the following Sophos product(s) and version(s)

SafeGuard Management Center / Local Policy Editor
SafeGuard Device Encryption

Operating systems
All supported operating systems

What To Do

In order to connect to the Server it is necessary to connect using the FQDN name or via IP address.

The configuration requires you to register the SGN server a second time, using the FQDN name or the IP address. Please follow these steps:

  1. Open the SGN Management Center
  2. Go to Tools -> SGN Server Tools...
  3. Click on "Add Server"

    The Server Registration Window is displayed.
  4. Browse to the machine certificate of the Server (1 in screen shot below) -> The server certificate is stored under C:\Program Files\Utimaco\SafeGuard Enterprise\MachCert\

    Do not use the MSO certificate!

  5. After selecting the certificate the "Server name" field will now be filled up with the FQDN name. If you normally set up your system with the button "Make this computer a SGN Server" the short name will be entered here.

    The dialog should look similar to this after importing the certificate:

    Hint: You can also enter the IP address of the Server here.

    In order to test this, open a web browser on the Client and try to connect the SafeGuard Server web page.

    For example: "" or ""
    Finally, you must create a Client configuration package that points to the FQDN Server name, as in the picture below.

    On those machines that don't work you can simply uninstall the Client Configuration package and install the new one after that again. No decryption process will take place!



If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent