Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 15 replies
  • Subscribers 1 subscriber
  • Views 8973 views
  • Users 0 members are here
Options
Suggested
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

philrob

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.
  • 0

    Hello Phil,

    you can get this message with the "empty" URL when the proxy settings are incorrect (for example you select "Custom proxy" but do not enter an address)

    Christian

    :3596
  • 0

    Thanks for the swift reply

    The proxy is set to 'No Proxy' on the preferences.

    Phil

    :3597
  • 0

    Did you take a look at the log, this gives the full URL and what type of error occurred (timeout, access denied, ...).

    Christian

    :3599
  • 0

    Thanks, will have a look when I get home

    Regards

    Phil

    :3601
  • 0

    Log isn't much help

    com.sophos.autoupdate: Error:    Could not contact primary server [my server details are here] at 18:07 on 29 June 2010
    com.sophos.autoupdate:     Access was denied
    com.sophos.autoupdate:

    It does show the correct details for the server (which I have replaced).

    Using a browser, I can cut and paste the server details from the log and can browse the website.



                     29 June 2010    17:39        80103 cidsync.upd
                      26 May 2010    15:28        58164 manifest.dat
                     29 June 2010    17:39          114 master.upd
                      26 May 2010    15:28        50553 product.spi
                     29 June 2010    17:39          185 root.upd
                  11 January 2007    18:18         2227 sdf.xml
                    06 March 2007    21:44        <dir> Sophos Anti-Virus.mpkg
                      26 May 2010    15:28          457 svf.xml

    Is there a way to get more detailed logging to find out where the failure is?

    I have tried leaving the credentials blank and also putting in the wrong credentials the error message stays the same. As it does if I switch to system proxy (the default).

    The error message without the address of the server makes me think something isn't being registered somewhere

    Thanks

    Phil

    :3626
  • 0

    Hello Phil,

    it is normal that the pop-up shows only http://. As your log contains the correct server details nothing is wrong with the software. "Access denied" usually means that the server could be reached but gave an error response. The (web)server's logs should show the request and response. As the exchange is in clear text it'd be also simple to trace it (I have a small proxy for this purpose). But anyway I'd take a look at the server's logs first.

    Christian

    :3634
  • 0

    Thanks, will have a look tomorrow

    Regards

    Phil

    :3662
  • 0

    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
  • 0

    Hello Gary,

    you say I can do a Connect to Server and connect to smb://<serverip>/InterChk/ESOSX - have you also configured the serverip in your updating policy or the server name?

    As I said, the client's log shows whether access has been denied, the connection timed out or another error occurred. For http connection problems you should view the webserver's (IIS?) logs.

    Christian

    :4215
  • 0

    Gary,

    I haven't got ot to work yet, but I haven't tried either. For complicated reasons we are going to have to re-install Sophos on the main server, Once that is done I will work my way through clearing all the issues one at a time.

    Once I do get it fixed (and I will, it has to be a configuration issue) I'll post what I did to get it to work

    Regards

    Phil

    :4292
Unfiltered HTML