Call security can most easily be turned off by using Dcomcnfg.exe to modify the registry. However, using Dcomcnfg.exe to turn security off will only work if both the client and the server do not call CoInitializeSecurity. The reason for this is that when CoInitializeSecurity is called, DCOM ignores the registry settings and using the values supplied to CoInitializeSecurity instead.
To turn security off with Dcomcnfg.exe, both the client and the server must set their Authentication Levels to None. The following steps must be completed:
If the client is not on the list, then you have two choices. You can either set the client's Authentication Level to None on a machine-wide basis using Dcomcnfg.exe, or you can set the client's authentication level to None programmatically. To use the first method, follow the step-by-step procedure below. (For more information about the second method, see Turning Off Call Security Programmatically).
Warning Setting the machine-wide Authentication Level to None is extremely unsecure.