Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 15 replies
  • Subscribers 1 subscriber
  • Views 8577 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

    We are also having a Similar Problem, Our Mac Clients Log always say "Server Could not be found" but a normal smb connection through the OS allows us to connect to the network share. I am doing it analot to Windows, so I assume that when I set the path it should be like this:

    smb://[Servername]/SOPHOS-VAV-01/SophosUpdate/CIDs/S000/ESCOSX

    Can anyone help me? Also when will EC 4.5 see the system as having it installed? Up till now we can't see it yet, and the Mac is "Domain Joined" Running Mac OS X 10.6.4

    :4657
  • 0

    Just checked - for smb: all you get is Server Could not be found  for incorrect server or credentials. If the path is incorrect you get not available. BTW: what's the SOPHOS-VAV-01 in the path?

    The client usually contacts the server shortly after install. Open the following location in your favourite browser: file:///Library/Logs/SophosMessageRouter/NetworkReport/ReportData.xml - it's the same information as on windows. You'll find the Router logs in the SophosMessageRouter folder which may contain error details.

    Christian

    P.S.: the spellchecker suggests that I replace SophosMessageRouter with Sphygmomanometer :smileyvery-happy:

    :4662
  • 0

    This may be similar to an issue I had when moving to Sophos 7.x for Mac OS X.

    I use IIS servers and I learned through working with Sophos tech support, I had to change the configuration of the IIS servers to support the new Sophos 7.x for Mac OS X. This configuration change was not required for any other Sophos products and was not documented anywhere by Sophos. I have tried to locate my notes on what was needed but could not find them. Once I get to the work of getting SUM to provide Sophos 7.x to Mac OS X I will have to revisit this again.

    You could try contacting Sophos tech support and cover the issue is updating Sophos 7.x on Mac OS X from IIS server. There is a configuration change needed to the default security settings in IIS to allow Sophos 7.x to update on Mac OS X.

    Good luck,

    VCU

    :4668
  • 0

    Ok I figured it out after long trying and logging. Apperently Mac can't support the new style of login (username@domain) when I changed it back to (domain\username) it finally worked. Now on to the issue that it isn't going to it's AD Synced group in EM like it should yet resides in the Unassigned folder.

    :4673
  • 0

    Now on to the issue that it isn't going to it's AD Synced group in EM

    Ah, that's not a problem with the client I assume. As I don't have any MACs in AD I can't say how it should behave. Do the MACs appear as unmanaged in the AD group and disappear (and re-appear in the Unassigned group) after install or don't they show up at all?

    Christian

    :4678