Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 27 subscribers
  • Views 2554 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

DistributedCOM Errors in Windows Server event logs after STAS integration

Can carmack

Hi Community,

For Active Directory Users integration with Sophos XG Firewall our we installed STAS in our AD Server.
Is this the right choice for syncing our local users with XG ?

After integration i saw lots of ( more than 16K) error logs when we're doing server maintanance routine. This events just appeared after Stas installation.
DistributedCOM ID: 10028 "DCOM was unable to communicate with the computer 192.168.2.54 using any of the configured protocols; requested by PID PID: 1b2c (C:\Program Files (x86)\Sophos\Sophos Transparent Authentication Suite\stas.exe)."

Is there any precaution for this.



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

    Hi  : Is IP Address 192.168.2.54 belongs to monitored network specified in the STAS?

    If No then as of now it is known behavior where STAS Sends WMI query to Network Not Monitored by Agent. This will be taken care in future release of STAS.

    If yes, then is the device 192.168.2.54 Windows machine or non windows OS machine? May required to work on other possibilities to confirm more.

  • 0 in reply to Vishal_R

    Any progress? STAS is bombarding our servers with WMI error logs. Is there any other way to sync AD users with XG Firewall? Gonna uninstall STAS. Help please.

Reply Children
No Data