Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Subscribers 3 subscribers
  • Views 5442 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

Work Group computer not updating through UNC in SEC 5.5

company1980 ahmed

Dear All,

I have installed SEC5.5 on my domain server, all my domain PC get updated from this server and working fine. We have some work group PC so we decide to install on these PC. I have manually install endpoint point security through copy the CIDS folder on work group PC and run the sophos setup from there. The installation was successful and the work group client reflect back to enterprise console. but the problem is that when we update the sophos from work group  PC it show the message could not contact the server. Domain system get updated from the folder whose path is "\\sophos-srv\SophosUpdate". But work group client cannot access the path by "UNC", although they can access the path if we specify the IP address instead of name.

My question is that is there an alternate way to update the work group client or anythings else.

Thanks

Furqan Ahmed



This thread was automatically locked due to age.
Parents
  • +1

    Hello Furqan Ahmed,

    they can access the path if we specify the IP address
    it seems that the workgroup endpoint can't resolve the server name (sophos-srv). So you'd have to amend your updating policy - an FQDN that the outside endpoint can resolve (it should work with the domain endpoints as well).
     
    Christian

    ,

  • 0 in reply to QC

    Dear Christan,

    Thanks for the reply, I have set new update policy for workgroup computer and it is working but one warning is shown which is "The primary update location may not contain the selected software subscription recommended do you want to continue anyway"

     

    Regards

    Furqan Ahmed

Reply
  • 0 in reply to QC

    Dear Christan,

    Thanks for the reply, I have set new update policy for workgroup computer and it is working but one warning is shown which is "The primary update location may not contain the selected software subscription recommended do you want to continue anyway"

     

    Regards

    Furqan Ahmed

Children
  • 0 in reply to company1980 ahmed

    Hello Furqan Ahmed,

    one warning is shown
    yes, that's expected - you get it when you use an FQDN or alias in the UNC path or when you use HTTP as Primary. Should have mentioned it.

    Christian

  • 0 in reply to QC

    Dear Christan,

    Sorry I didn't get your point, can you please clarify the above statement.

     

    Regards

    Furqan Ahmed 

  • 0 in reply to company1980 ahmed

    Hello Furqan Ahmed,

    no problem. The update manager (SUM) deploys all subscriptions to the default (\\server\SophosUpdate\) share (Configure update manager, tab Distribution, Update to: pane)). Optionally it can deploy to additional shares. For these the console (the management server to be exact) knows which subscriptions are contained in them.
    The management server can't tell whether \\server.fq.dn\SophosUpdate\ is indeed just another name for \\server\SophosUpdate\ or not, even less when it is a WebCID, i.e. the share published with a web server and accessed via HTTP (theoretically it could try to access the location and compare the catalogs - anyway, it doesn't). Thus it warns you that you are not using a "known" path in your policy.

    Is this clearer?

    Christian   

  • 0 in reply to QC

    Dear Christain,

     

    Thanks for the reply, you want to say that the domain client access the SUM using UNC path, but the work workgroup computer access the same location using the ip address.

    Regards

    Furqan Ahmed

  • 0 in reply to company1980 ahmed

    Hello Furqan Ahmed,

    [sorry, haven't been "in" yesterday]
    the endpoint accesses the update location by standard means. Whether you specify a UNC path or an HTTP URL it has to be able to 1) if a name is used resolve the name to an IP, 2) make a connection to this IP, have sufficient rights to access the share/path with the given credentials. There's nothing special here. It depends on your setup whether a non-doamin endpoint can resolve a simple name like \\server, needs an FQDN like \\server.domain.local, or perhaps can't access a server in the domain at all.

    Christian

  • 0 in reply to QC

    Dear Christain,

    I simply set to the two update policy, the domain client access the share using the UNC path, and the workgroup client access the same path using the ipaddress with the sufficient user rights. Both are working fine.

    Thanks for your support.

     

    Regards

     

    Furqan Ahmed

Unfiltered HTML