Issues with updating from a Web CID can have a number of causes. The most common can be resolved by working through the following.
Known to apply to the following Sophos product and version Sophos Update Manager
This is suggested first as it will show the direct result of the HTTP transactions initiated by Sophos Auto Update. This event data is very useful in determining the failure reasons on why Endpoints cannot update.
If you don't know the address of your web CID, you can usually find it in the updating details. It will usually take the form http://servername/sharename/
If you have added a new site to IIS with a Physical Path of the following:
This will result in an updating location similar to the following:
If you have added a Virtual Directory (Or through a Web Share on IIS 6.0) to an existing Site in IIS, then you must include the Alias in the updating URL.
This Microsoft article details how to change the binding, in this case we only need to note the binding used on the site hosting the Sophos updating location. Each site will require a unique TCP/IP port, be default the first site wil use Port 80, additional sites will use additional ports.
For example an additional site is added called SophosUpdate it is bound to Port 81:
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. If you need technical support please post a question to our community. Alternatively for licensed products open a support ticket.