RE: LogOn User Fails with 1327
From: Rhett Gong [MSFT] (v-raygon_at_online.microsoft.com)
Date: 10/06/04
- Next message: Help: "Certificates and key containers"
- Previous message: Craig: "Certificates: Which store to add to?"
- In reply to: Chuck P: "RE: LogOn User Fails with 1327"
- Next in thread: Chuck P: "RE: LogOn User Fails with 1327"
- Reply: Chuck P: "RE: LogOn User Fails with 1327"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 06 Oct 2004 08:39:14 GMT
>What APIs are used when I am on an AD domain and I map a network drive to
an
>untrusted NT domain?
You may use NetShareAdd.
>I can't change the trusts and the ADSI provider shouldn't be used for NT
>domains(kbid=218497).
>I really don't need a token, just whether the user is who they say they
are.
Could you details your test domain environment (how did you build your nt
domain and what you make to have the test computer joined in the ad domain)
so that I can build a similar env to see if it is possible to workaround
this problem?
Also, could you try to logon the test computer as the admin of ad domain,
then call LogonUser api with the admin account of the NT domain and let me
know what you get please?
Thanks,
Rhett Gong [MSFT]
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Please reply to newsgroups only. Thanks.
- Next message: Help: "Certificates and key containers"
- Previous message: Craig: "Certificates: Which store to add to?"
- In reply to: Chuck P: "RE: LogOn User Fails with 1327"
- Next in thread: Chuck P: "RE: LogOn User Fails with 1327"
- Reply: Chuck P: "RE: LogOn User Fails with 1327"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]