Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 13 replies
  • Answers 3 answers
  • Subscribers 32 subscribers
  • Views 71283 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 Transparent Authentication Suite (STAS) with Windows server 2012

RamyAjamieh

Hi,

I don't know if anyone face a problem wit STAS agent we have the DC it was running on Server 2008 and the STAS agent was installed and working without any problem  we upgrade the OS to Win Server 2012 after the upgrading the STAS can successfully connect the XG but when Im testing the STAS collector it showing test connection failed.

anyone have any idea about this issue

Sophos Test:

 

STAS collector Test:



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

    I had a bit of a nightmare with this to get it going. But I do have it successfully running with 4x 2012r2 dc's.

    My setup has 1x STAS suite on 1 dc with 3x agents on the other.

    That bit was easy. What I was finding was that my auditing was being overwrote by something after a couple of minutes. I checked the DC's group policy as well as the domain policy and there was nothing in them to do this and I never quite got to the bottom of why this was happening despite checking all the policies with a fine tooth-comb.

    So first I would check your dc to see that the audit policies are set. In the end, I had to go into advanced local policy and set the auditing from there, specifically the logon/logoff with kerberos. Once I'd done that (on the 4x dc's), everything flowed and I now have 600 users registered on my UTM's

Reply
  • 0

    I had a bit of a nightmare with this to get it going. But I do have it successfully running with 4x 2012r2 dc's.

    My setup has 1x STAS suite on 1 dc with 3x agents on the other.

    That bit was easy. What I was finding was that my auditing was being overwrote by something after a couple of minutes. I checked the DC's group policy as well as the domain policy and there was nothing in them to do this and I never quite got to the bottom of why this was happening despite checking all the policies with a fine tooth-comb.

    So first I would check your dc to see that the audit policies are set. In the end, I had to go into advanced local policy and set the auditing from there, specifically the logon/logoff with kerberos. Once I'd done that (on the 4x dc's), everything flowed and I now have 600 users registered on my UTM's

Children