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

Download of Sophos AutoUpdate Failed from server \\SUM\share - 6b

JoshMcCracken

I'm having issues with 1 SUM. This is the only SUM that clients are getting this error message from.

The SUM is recieving updates in line with the other 3 SUMs and no error messages are reporting on the SUM.

This is what I tried:

1. Stop services (Sophos Agent, Sophos Message Router, Sophos Update Manager)

2. Delete the folders \\ksrcandc-b\SophosUpdate\CIDs & \\ksrcandc-b\SophosUpdate\Warehouse - as these folders might be corrupt and a re-download will fix

3. Start the services back up

4. OPen the SEC and update now - binaries download etc... folders/files reappear

5. Go to the clients with the error and update now/comply with configuration -- nothing

-View computer details each client shows the error detailed in the subject of this post

6. Go to a few of the clients (mix of xp and windows 7) look in the Update settings, verify the correct credentials are used - yes.

7. Go to the log and see after updating:

-Could not connect to the Server. Check that this computer is connected to the network and that Sophos AutoUpdate is configured to update from the correct location with the correct credentials and proxy details. - Yes as said before credentials look correct and there are no proxy configuration needed.

Stuck, not sure what else to try.

Any suggestions would be great.

:53263


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

    Hello Josh,

    I am able to get to the share

    from where (i.e. one of the affected computers) and how (net use ... or Explorer's Map network drive ...)? Thinking about it - wrong credentials usually result in error 1326, not 86 (although the latter specifically means incorrect password). The "small number" code suggests an issue with the LAN Manager authentication level (the use of LM, NTLM and NTLMv2). This is most often (due to the default policy settings) seen when a Windows Version 6.x+ client tries to access an older server (e.g. Win7 to W2k) - as XP endpoints suffer as well this might not apply.   

    So, dunno if this helps. One more thing - have a look at the Security Event logs.

    Christian

    :53303
Reply
  • 0

    Hello Josh,

    I am able to get to the share

    from where (i.e. one of the affected computers) and how (net use ... or Explorer's Map network drive ...)? Thinking about it - wrong credentials usually result in error 1326, not 86 (although the latter specifically means incorrect password). The "small number" code suggests an issue with the LAN Manager authentication level (the use of LM, NTLM and NTLMv2). This is most often (due to the default policy settings) seen when a Windows Version 6.x+ client tries to access an older server (e.g. Win7 to W2k) - as XP endpoints suffer as well this might not apply.   

    So, dunno if this helps. One more thing - have a look at the Security Event logs.

    Christian

    :53303
Children
No Data