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

Windows Server 2008 R2 SP1 webcid setup

I'm trying to setup a webcid on a Windows Server 2008 R2 SP1 machine.

I've successfully got it working for windows Endpoint clients, but I can't for our Mac clients.

The log on the client only says "Could not contact primary server" error changes between "Server was not available" and "Server could not be found"

The IIS Log has the following

"

2013-03-26 05:34:24 137.166.68.29 GET /Sophos/OSXHomehttp/Sophos+Anti-Virus.mpkg/Contents/Packages/SophosAU.mpkg/Contents/Packages/SophosAUCLI8.0.1.pkg/Contents/Resources/preinstall - 80 - 220.233.4.17 <UA+a="Mac"+u="<domain\username>"+v="8.0.8.1"+/> 401 2 64 93
2013-03-26 05:34:24 137.166.68.29 GET /Sophos/OSXHomehttp/Sophos+Anti-Virus.mpkg/Contents/Packages/SophosAU.mpkg/Contents/Packages/SophosAUCLI8.0.1.pkg/Contents/Resources/preinstall - 80 - 220.233.4.17 <UA+a="Mac"+u="<domain\username>"+v="8.0.8.1"+/> 401 1 2148074254 31
2013-03-26 05:34:24 137.166.68.29 GET /Sophos/OSXHomehttp/Sophos+Anti-Virus.mpkg/Contents/Packages/SophosAU.mpkg/Contents/Packages/SophosAUCLI8.0.1.pkg/Contents/Resources/preinstall - 80 <domain\username>"+ 220.233.4.17 <UA+a="Mac"+u="<domain\username>"+v="8.0.8.1"+/> 404 17 64 93

"

A web browser can connect with no problems.

What setting am I missing?

:38791


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

    I don't have an immediate solution, I'll try to help you with interpreting the log and maybe it gives you some ideas:

    AFAIK Macs try with authentication (as opposed to AU on Windows which always makes an unauthenticated request first) so the request should get a 200 reply. Looking at the substatus code (the number after the 40x) I see 2 (i.e. the detailed code is 401.2 which means logon failed due to server configuration), then 1 (simply logon failed but with a w32 code of 8009030e) and eventually with 404.17 which is rather obscure.

    Also the URL seems quite strange - for managed clients I'd expect both the subscription (Snnn) and ESCOSX in the path. Do you rewrite the URL somewhere? 

    Anyway, it seems that there's an issue with the authentication scheme used. According to Troubleshooting updating from Web CID issues Anonymous, Basic, Digest and Windows Authentication are all known to work correctly.

    HTH

    Christian

    :38803
Reply
  • Hello aburrow,

    I don't have an immediate solution, I'll try to help you with interpreting the log and maybe it gives you some ideas:

    AFAIK Macs try with authentication (as opposed to AU on Windows which always makes an unauthenticated request first) so the request should get a 200 reply. Looking at the substatus code (the number after the 40x) I see 2 (i.e. the detailed code is 401.2 which means logon failed due to server configuration), then 1 (simply logon failed but with a w32 code of 8009030e) and eventually with 404.17 which is rather obscure.

    Also the URL seems quite strange - for managed clients I'd expect both the subscription (Snnn) and ESCOSX in the path. Do you rewrite the URL somewhere? 

    Anyway, it seems that there's an issue with the authentication scheme used. According to Troubleshooting updating from Web CID issues Anonymous, Basic, Digest and Windows Authentication are all known to work correctly.

    HTH

    Christian

    :38803
Children
No Data