Hi,
as i found no answer in the old threads, is there an solution for Stats preventing the dcom 10028 errors?
DCOM was unable to communicate with the computer 192.168.xx.xx using any of the configured protocols; requested by PID 22e8 (C:\Program Files (x86)\Sophos\Sophos Transparent Authentication Suite\stas.exe).
regards
Mathias
Hello Mathias,
Thank you for reaching out to the Sophos Community.
While doing some searching, I was able to find the following document. Let me know if you have already gone through this best-practice configuration of STAS. Section "B" corresponds to "DCOM" configurations.
- https://community.sophos.com/sophos-xg-firewall/f/recommended-reads/125318/sophos-xg-firewall-best-practice-for-stas
Let me know if the machine(s) from which these errors are being generated are Windows machines or other types of network devices. If these are not Windows/Domain-joined systems, I recommend checking over the settings on the system where the "Collector" is installed. Try changing the options under the tab "STAS Collector" so that it matches the following.
- Workstation Polling Method: Registry Read Access
Let me know if this resolves the issue. If you continue to experience this issue after implementing the changes, I recommend opening a support case with our team to investigate further.
Hello Mathias,
Thank you for reaching out to the Sophos Community.
While doing some searching, I was able to find the following document. Let me know if you have already gone through this best-practice configuration of STAS. Section "B" corresponds to "DCOM" configurations.
- https://community.sophos.com/sophos-xg-firewall/f/recommended-reads/125318/sophos-xg-firewall-best-practice-for-stas
Let me know if the machine(s) from which these errors are being generated are Windows machines or other types of network devices. If these are not Windows/Domain-joined systems, I recommend checking over the settings on the system where the "Collector" is installed. Try changing the options under the tab "STAS Collector" so that it matches the following.
- Workstation Polling Method: Registry Read Access
Let me know if this resolves the issue. If you continue to experience this issue after implementing the changes, I recommend opening a support case with our team to investigate further.
