1

Topic: Singularities DCOM security in Windows 10

There is the distributed application on the basis of DCOM, for a long time working on different systems. Works on XP, Windows 7, Server 2008R2 in different combinations. Being installed on Windows 10, it does not start up to itself remote client users. That is, from Windows 10 it is possible to be connected to the service allocated, for example, on 7, and reversely is not present. Access is forbidden. Setting and adjustment DCOM everywhere the identical. On audit it is visible that the remote user normally logs in in system. The failure goes already at attempt to create COM object. Probably, Windows 10 has any else adjustments of safety. On Windows 8 did not check. Somebody already faced it? I rummaged all Internet, found nothing. All already tried.

2

Re: Singularities DCOM security in Windows 10

Hello, john_silver, you wrote: What error is returned to application? What is written to event logs Windows of the client and the server? Under what  works DCOM? I had problems with adjustment of Kerberosa and tickets for this

3

Re: Singularities DCOM security in Windows 10

Hello, mDmitriy, you wrote: D> What error is returned to application? It is refused access. D> that is written to event logs Windows of the client and the server? On the server successful login, then  is visible. D> Under what  works DCOM? With the rights of the manager to both computers. A network without the domain. D> I had problems with adjustment of Kerberosa and tickets for this  I so understand that is by default used NTLMSSP. Here after all the main thing that in other systems all works, with the same parameters. And in Win 10 does not work. That is, there are any differences for this system.

4

Re: Singularities DCOM security in Windows 10

Hello, john_silver, you wrote: _> Hello, mDmitriy, you wrote: D>> What error is returned to application? _> it is refused access. D>> that is written to event logs Windows of the client and the server? _> on the server successful login, then  is visible. In log of system events or applications there are records about response DCOM? I.e., whether it is possible to understand, to which resource access is refused? D>> under what  works DCOM? _> With the rights of the manager to both computers. A network without the domain. D>> I had problems with adjustment of Kerberosa and tickets for this  _> I so understand that is by default used NTLMSSP. I too so thought... But it was clarified, it is necessary to adjust Kerberos - it helped with my case _> Here after all the main thing that in other systems all works, with the same parameters. And in Win 10 does not work. That is, there are any differences for this system. About Win 10 anything cannot tell, did not face, alas. . As well as with operation DCOM in  networks. My problems were solved by system administrators, but it was necessary to them was specific to stick that put in access

5

Re: Singularities DCOM security in Windows 10

Hello, mDmitriy, you wrote: _>> I so understand that is by default used NTLMSSP. D> I too so thought... But it was clarified, it is necessary to adjust Kerberos - it helped with my case That is used - it is possible to clarify explicitly through CoQueryAuthenticationServices.