STAS DCOM errors 10028 spamming my PDC

Hi John,

Have you configured the Network IP addresses of these devices in the Monitored Network section of STAS?

Thanks,

Hi Thanks for your reply.

Yes i have on both pdc/bdc.

The strange thing is however, some of the IP addresses don't fall within the scope of of the defined ;

PDC

BDC

ERROR 10028 outside of define IP range;

FYI: We use a SOPHOS XG with the managed wifi. The "other" ip addresses in event view that aren't 10.15.20.x match defined wifi network ranges in the DHCP and network sections of the XG for the WIFI. With the exceptions of a couple of the 10.15.20.x that are printers.

Thanks again

Hi Sachingurung,

when will this be fixed?

I can not find this NC-27245 fix in any release notes

Are you also fixing the Logoff detection in STAS?

I'd also like to know an ETA for this. The event logs are full with this and it's really annoying when troubleshooting other issues and trying to review the event log.

Any new ideas or fixes yet?

We are also seeing hundreds of 10028 dcom errors in server 2016 where we have installed the STAS.

kindly share ETA when this will going to sort?

I support 3 sites and since moving to Sophos AV & XG, each one has hundreds of these error referring STAS. It's filling up EV making it a task to spot other issues. It would seem that this problem has been known about for a very long time and a solution is long overdue.

But I guess once they've got your money ........................

Just curious to see if people are still having this issue.....

We are now running 17.5 and are planning on removing STAS in favour of purely using heartbeat for windows client authentication.... 

Most of our machines are using heartbeat to authenticate now..... so removing stas shouldn't be an issue for us.

Looking forward to be able to read my DCs event logs!

Just updated STAS to 2.5.0.0

aren't we able to define exclusion "ranges" yet?

Hello JohnHilton,

At the moment we do have an option to add a IP range for STAS exclusions, you can manage the range in your subnet and assign them to a smaller subnet range.

e.g. Network Range 192.168.0.1/24 by adding the range of IP not to be managed by STAS you can assign a Static DHCP and determine that last 14 IP will be added in exclusion so you can add 192.168.0.240/28.

Just setup STAS 2.5.0.0 on Server 2019 DC and SAME thing.. tons of events logged for my GuestWiFi network which is on a separate subnet and in the firewall rule doesn't match users.  It's killinh my event logs and hung up my DC, wth.

It's even showing active stas login for my domain admin which I even added to the exclusion user name list. What is going on?

Any news about this mistake ?

Any news about this mistake ?

Nope still have this issue

Hi,