Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 0 subscribers
  • Views 13860 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

Sophos Update Server

KeithMurrey

So I thought I would be cool and create a Windows Server called SOPHOS.


So I installed all the users, etc.  And it updated fine.


But just for a day - as when you choose SOPHOS for the update and the login credentials - its not going out to the web - its hitting hitself trying to get the update.

So how in the world do I fix this.

is there another update that I can use that isn't called SOPHOS?  Or do I need to rename the server - reinstall the software - and all users?

Keith



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to KeithMurrey

    Hello Keith,

    I believe the update is trying
    this is not a question of belief - neither message indicates that it is trying to connect to itself. The SUMTrace log should name the failing source location though it doesn't give the actual name or IP but either the symbolic name SOPHOS or the value from C:\Program Files (x86)\Sophos\Update Manager\config.xml (tag <UpdateSource><Path> which ends in Warehouse). So - what makes you think it's trying to connect back to itself?

    Christian

Unfiltered HTML