About this tag
The packetprivacy tag on WindowsForum.com covers discussions about the Packet Privacy authentication level in Windows, particularly in the context of DCOM and RPC security settings. Users explore how to configure the Default Authentication Level in the Component Services administrative tool, with Packet Privacy being the highest security level (value 6). Topics include troubleshooting Lsass.exe registry reads for the DefaultAuthLevel key and applying workarounds to enforce outbound RPC connections with packet privacy. The tag is relevant for IT professionals and advanced users managing Windows security policies, authentication protocols, and system hardening.
-
J
Lsass.exe constantly reading registry for DefaultAuthLevel (NAME NOT FOUND - in Process Monitor)
I see it relates to DCOM Default Authentication Level, which has in total, 7 fields in the Component Services Windows admin tool. That is in this order, from top of the list to the bottom as it appears; Default, None, Call, Connect, Packet, Packet integrity and Packet Privacy. I only see one...- jonnyc55
- Thread
- authentication component services dcom defaultauthlevel dword hkey_local_machine key lsass packetprivacy process monitor query registry rpc security services settings troubleshooting value windows administration workaround
- Replies: 2
- Forum: Windows Help and Support