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

endpoint on different subnet. Installs but will not update.

joea

I have the update server on the main lan subnet and a laptop on a subnet, thru a router. I can browse to the update/install location and run setup, which installs sophos av.   However, update fails.  Cannot find update location.

mrinit.conf shows the explicit IP of the update server. 

Why can update not find it?   I can see the router dropping netbios calls on the subnet.   But why should update need that, when it knows where the update server is?

:39009


This thread was automatically locked due to age.
Parents
  • 0

    Hello joea,

    likely setup.exe has correctly put the IP into the initial configuration. You can check the update location using Configure updating from the client's Sophos GUI and/or View updating log shows you the location it attempted to update from. Now you didn't say whether the client "appeared" in the console and if so, whether it has been put into a specific group.  

    To rephrase the least sentence from my previous post (as some of the information was apparently new to you you might have missed it): Once the client's RMS successfully connects to the management server it configures updating according to the policy - probably the policy contains a name and not an IP.  This would explain the successful install and subsequent updating failure - but it is just a guess.

    If the above does not apply you should check the ALUpdate log in [%ProgramData%|%ProgramFiles%]\Sophos\AutoUpdate\Logs for details of the failure.

    Christian

    :39049
Reply
  • 0

    Hello joea,

    likely setup.exe has correctly put the IP into the initial configuration. You can check the update location using Configure updating from the client's Sophos GUI and/or View updating log shows you the location it attempted to update from. Now you didn't say whether the client "appeared" in the console and if so, whether it has been put into a specific group.  

    To rephrase the least sentence from my previous post (as some of the information was apparently new to you you might have missed it): Once the client's RMS successfully connects to the management server it configures updating according to the policy - probably the policy contains a name and not an IP.  This would explain the successful install and subsequent updating failure - but it is just a guess.

    If the above does not apply you should check the ALUpdate log in [%ProgramData%|%ProgramFiles%]\Sophos\AutoUpdate\Logs for details of the failure.

    Christian

    :39049
Children
No Data