Users can still connect to the client VPN and AD Auth is working fine on my MX devices.
The error itself isn't causing any issues that I am aware of. I posted this on the Meraki forms as well, but haven't got any hits on it. "Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application." As the client for this is my MX devices.
EVENT ID 1000 APPLICATION ERROR WINDOWS 2012 UPDATE
This only started happening since last Tuesday after the MS update on my DCs. Mostly just posts about 10016, DistributedCOM.Īt this point, I'm kind of at a loss of what to do. When I search for 10036, DistributedCOM I can't find anything on it. I also tried the registry fix, but that did not work either. One thing I noticed that caused the error to stop occurring was by disabling Active Directory Authentication on my MX appliance.
The server in question is a fresh build of spiceworks. 0x00000001 = enabled.īefore trying this, I wanted to check on here first.ĭid you get this sorted out? I am also seeing it on my DCs.
When it say's "Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application." I'm guessing I need to raise the authentication level on the DC? I don't see how this could be done on Meraki MX. This error is occurring for all 3 of my sites displaying the IP of all 3 MXs devices. The address you see above ( 10.0.100.254) is the MX IP, and the domain\User is the domain admin account I'm using in the Meraki dashboard for AD Authentication. I'm using Cisco Meraki MX devices, and they are set up for Active Directory Authentication. The server-side authentication level policy does not allow the user domain\User SID (X-X-X-XX-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXX-XXXXX) from address 10.0.100.254 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. After installing Microsoft updates, I began to receive the following error I got a weird issue that just started to occur on Tuesday, September 14th, on both my DCs.