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
  • I don't like "unclosed threads" - not knowing whether a problem has been solved or worked around (and if, then how).

    I can add a potential solution to this one as I've encountered this problem just a few days ago. Server admins had applied some updates, a few days later a Mac user reported persisting update problems when outside (updates are internally over UNC/smb - furthermore the issue doesn't surface for IDE only updates). Turned out that a request for an extensionless file resulted in a 500 error. As it had worked before for quite some time and the configuration hadn't been touched I was somewhat miffed. Took a look at the Handler Mappings, suspected the ExtensionlessUrlHandler-Integrated-4.0. Restricting it to not handle GET requests made the 404.17 appear.

    For whatever reason I couldn't get the mentioned hotfix (it's available again today, must've been a glitch) so I searched for another solution. I was able to add a MIME Type with an empty extension but this didn't help. Eventually I stumbled over a forum thread where using just a dot for the extension is suggested - indeed, this solved the problem (dunno how long until another patch will break it again but for now it works).

    Christian

    :40325
Reply
  • I don't like "unclosed threads" - not knowing whether a problem has been solved or worked around (and if, then how).

    I can add a potential solution to this one as I've encountered this problem just a few days ago. Server admins had applied some updates, a few days later a Mac user reported persisting update problems when outside (updates are internally over UNC/smb - furthermore the issue doesn't surface for IDE only updates). Turned out that a request for an extensionless file resulted in a 500 error. As it had worked before for quite some time and the configuration hadn't been touched I was somewhat miffed. Took a look at the Handler Mappings, suspected the ExtensionlessUrlHandler-Integrated-4.0. Restricting it to not handle GET requests made the 404.17 appear.

    For whatever reason I couldn't get the mentioned hotfix (it's available again today, must've been a glitch) so I searched for another solution. I was able to add a MIME Type with an empty extension but this didn't help. Eventually I stumbled over a forum thread where using just a dot for the extension is suggested - indeed, this solved the problem (dunno how long until another patch will break it again but for now it works).

    Christian

    :40325
Children
No Data