Client is not authorized because of anonymous logon

[electric]

I'm recieving the following error in MTS:

Client is not authorized to make the call. User: NT AUTHORITY\ANONYMOUS LOGON (Package: Reserva 20) (ProgId: Broker.Messages) (CLSID: {B8701170-993F-11D4-8D22-0000B4C055E6}) (Interface: Messages) (IID: {052E5C1A-F23B-11D4-9205-0050DAC42F6B}) (Microsoft Transaction Server Internals Information: File: i:\viper\src\runtime\security\csecobj.cpp, Line: 1209)

The client machines are connected to the MTS server through a VPN. The problem is that the majority of the clients are not beign authenticated by the NT server, they appear as anonymous on the network not with their nt logins. All 100 clients have the same nt account and all are always connected to the VPN.

Has anyone seen this or has any suggestions.

Thank You in advance!

 

[zallen]

It seems that MTS works well on a same domain(LAN).

Regards! zallen@cmmail.com
Long live of freedom!

 

[karlp]

1. You could set NT Challenge/Response to ensure all users are identified. This may or may not be possible depending on your configuration.

2. You could disable security checking on the MTS package

3. It could be DCOM authentication. Try using DCOMCNFG to alter Default Properties.Default Authentication Level to None.

Hope this helps.

K

 

[electric]

I actually found what was causing the problem.
The application that uses the MTS components is started by the NT Scheduler. The NT Scheduler service was configured to log on as the System account, so the app was started with the System Account which for "security" reason authenticates as blank ("&quot to other servers, thus the MTS call arrived as anonymous. The problem was resolved by configuring the Scheduler services to log on as a specified user.

E