Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Safeguard 5.5 client failing to contact server

The title pretty much says it all really.

I've even resorted to using the server ip address in the config package but still no luck!!

Any ideas?

Cheers

:3294


This thread was automatically locked due to age.
  • Hi,

    On a client machine, have you tried contacting the following through an internet browser:-

    yoursgnservername/SGNSRV

    If you cannot contact this address it would point to an IIS issue on the server.

    :3301

  • HercFeend wrote:

    The title pretty much says it all really.

    I've even resorted to using the server ip address in the config package but still no luck!!

    Any ideas?

    Cheers


    Hi HercFeend,

    Thank you for posting your question in the SophosTalk community.

    This may be obvious but did you check your web server's connection to the database?

    When troubleshooting these types of errors, it always help to start testing close to the database and then move down the path to the SGN Client. This KBA describes how to test the client connection.

    Let us know if the <dbauth> response is OK or FAILED.

    :3349
  • I have the same issue which i am struggling to figure out for the last few days.

    I wonder if you find the solution .

    My connection test says <DBAuth>faild

    My problem starts after few changes we did on the server, This server used to be Domain Controller which we demoted and also we've installed new deployment application, Web based.

    We say ok lets leave this server as is and lets install new server just for the SGNServer, as you know in this wonderful days when you have Virtual environment this task is easy. so --> right click on the W2K3 template --> duplicate and we have new server.

    First we install the sqlexpress and restored the exported db on it, then we installed  SGNServer.msi then we went to the Management Center to add the new server using the new MatchCert , create new server package, install over the new server and run the connection test...... well done the connection test invoke show OK on both Web and DBAuth, good news for us, we went to one of our client machines , right click on the Safeguard enterprise icon  choose SYNC....... our well done was to early!

    The problem still exist on the clients.

    I hope i dont need to recreate new package for the clients stations and to reinstall it manually - thats make me wonder what is the correct steps to replace the SGNServer - didnt find it on the manuall's i'll be glad to know.

    second i am still trying to figure out how can i bring back to life the old sgnserver as it looks like the best solution for me.

    Hope someone here can assist.

    Thanks for reading.

    :3501
  • Hello HercFeend

    Having had the same kind of problems before, I found it extremely useful to check if the client is configured correctly, and is contacting the server the way you want it to.

    For that, use sgnstate, which is a tool that will show you exactly that (see http://www.sophos.com/support/knowledgebase/article/108839.html for an example).

    Hope this helps,

    Vincent

    :3605
  • Hello Harush,

    In theory you shouldn't need to create and distribute a new package, as long as the address to reach the server has not changed. It is not important if it is on another machine or not, but the server needs to be accessible the same way.

    So, for you too, first check the server address used on the client using SGNState. If that is not correct, and you don't want to update the clients, you'll have to play with websites/hostnames/IP addresses.

    Good luck,

    Vincent

    :3606
  • Simple fix for this ... Reinstall Safeguard on your Server.

    I had no prior experience to this. I was having great difficulites getting a resolution from Sophos so in the end I just removed the installations from the Server via Windows Uninstaller and reinstalled, because all the Database information already existed it was easy to get the Safeguard Software back to it working state.

    :21949