Okay thank you for that clarification!

Okay I did not realize that. The reason I thought that it has to do with DCOM is that I can connect to any server that is not the 2022 version that has the DCOM hardening. This is the only reason that led me to believe that it must be DCOM issues. How is it that the OPC UA connection is not affected by DCOM settings?

What I meant was I set the COM security on application startup for the OPC connection as described in the articles you sent me. I have attached the exception I am getting.

OpcLabs.EasyOpc.UA.OperationModel.UAException: An OPC-UA operation failure with error ID 'OpcLabs.UAEngine=1' occurred, originating from 'Opc.Ua.Core' and with depth of 2. The inner exception, of type "OpcLabs.EasyOpc.UA.Engine.UAEngineException", contains details about the problem.
---> OpcLabs.EasyOpc.UA.Engine.UAEngineException: UA SDK error (Opc.UA.ServiceResult=0x808A0000) in 'DiscoveryClient.GetEndpoints'. OPC UA service result - Error establishing a connection: BadNotConnected.
+ The error occurred when preselecting an endpoint for discovery URL "opc.tcp://StampingScada.ccrnt.ccr:49380".
+ Connection attempt #2; last connected at 1/1/0001 12:00:00 AM (local); unconnected for 00:00:34.3900000.
+ Some possible causes of this error are that the OPC-UA server is not running, or is not configured to listen on the specified port. Also, the network connection may be broken (cable unplugged?).
+ The client method called (or event/callback invoked) was 'DataChangeNotification'.
---> OpcLabs.EasyOpc.UA.UAServiceException: OPC UA service result - Error establishing a connection: BadNotConnected.
at Opc.Ua.Bindings.ChannelAsyncOperation`1.End(Int32 timeout, Boolean throwOnError)
at Opc.Ua.Bindings.UaSCUaBinaryClientChannel.EndSendRequest(IAsyncResult result)
at Opc.Ua.Bindings.UaSCUaBinaryTransportChannel.EndSendRequest(IAsyncResult result)
at Opc.Ua.Bindings.UaSCUaBinaryTransportChannel.SendRequest(IServiceRequest request)
at Opc.Ua.DiscoveryClient.GetEndpoints(RequestHeader requestHeader, String endpointUrl, StringCollection localeIds, StringCollection profileUris, EndpointDescriptionCollection& endpoints)
at OpcLabs.EasyOpc.UA.Toolkit.Sdk.ToolkitDiscoveryClient.OpcLabs.EasyOpc.UA.Toolkit.Client.ISdkDiscoveryClient.GetEndpoints(String endpointUrl, StringCollection sdkProfileUris)
at OpcLabs.EasyOpc.UA.Toolkit.Sdk.ClientUtils.<>c__DisplayClass55_0.<SelectEndpointInternal>b__2()
at OpcLabs.EasyOpc.UA.Toolkit.UAEngineBase.PerformSdkAction(UASdkCallType callType, Func`1 usingFunction, String name, Action sdkAction)
--- End of inner exception stack trace ---

I have set ComManagement.Instance.Configuration.SecurityParameters.UseCustomSecurity to false and set the security initialization. Still cannot connect to new 2022 servers, connection works fine to previous version servers.

I am attmepting to connect to a top server machine that has been upgraded to 2022 version. I am having issues connecting fom the client which is using OPCLabs.QuickOPC(5.63.121). I have configured the component settings on both server and client to use the Packet Integrity authentication level. My question is how to I set the DCOM settings of the UA client in code when creating it? Or does it automatically accept the component services default settings?