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

Auto Update config problem on MAC

Now have a MAC at home, so have setup a web share at work and installed Sophos on the MAC and set enterprise console to update the MAC signatures as well as windows.

The mac doesn't seem to be accepting the auto-update address. Error message is

  "Could not contact primary server http://"

with nothing after the http:// in the error message.Preferences have 'Company web server' and the full url of the folder.

The settings (with the full URL) are correct in the preferences. This I have tested by cutting and pasting the URL into a web browser. I get prompted for a username and password and,once these are entered, can browse the folder.

It seems as if sophos is not registering the URL and so can't connect.

incidentally Windows clients can update without any problems (though to a separate subfolder).

Any Ideas?

Thanks

Phil

:3591


This thread was automatically locked due to age.
Parents
  • Phil,

    I'm having the same problem - did you ever get this resolved?

    Going from a Windows 2003 Server hosting Sophos Data to a Mac client (version 7.1.9).  The odd thing is that our clients running version 4.9.37 WILL contact the server, but machines running the newer version WILL NOT.

    I've tried connecting via smb and http - but they refuse to connect to the server.  The server's Event Viewer lists no outright refusals or errors.  From the client, I can do a Connect to Server and connect to smb://<serverip>/InterChk/ESOSX without an issue.  I can also navigate to http://<serverip>/InterChk/ESOSX inside Safari and view a virtual listing of files.  Sophos doesn't want to connect, however.

    Any suggestions?

    -Gary

    :4187
Reply
  • Phil,

    I'm having the same problem - did you ever get this resolved?

    Going from a Windows 2003 Server hosting Sophos Data to a Mac client (version 7.1.9).  The odd thing is that our clients running version 4.9.37 WILL contact the server, but machines running the newer version WILL NOT.

    I've tried connecting via smb and http - but they refuse to connect to the server.  The server's Event Viewer lists no outright refusals or errors.  From the client, I can do a Connect to Server and connect to smb://<serverip>/InterChk/ESOSX without an issue.  I can also navigate to http://<serverip>/InterChk/ESOSX inside Safari and view a virtual listing of files.  Sophos doesn't want to connect, however.

    Any suggestions?

    -Gary

    :4187
Children
No Data