Arno Garrels wrote: > >> From MSDN: > > "lpszUsername > [in] A pointer to a null-terminated string that specifies the name of the > user. This is the name of the user account to log on to. If you use the > user principal name (UPN) format, [EMAIL PROTECTED], the lpszDomain > parameter must be NULL. > lpszDomain > [in] A pointer to a null-terminated > string that specifies the name of the domain or server whose account > database contains the lpszUsername account. If this parameter is NULL, > the user name must be specified in UPN format. If this parameter is ".", > the function validates the account by using only the local account > database."
To complete this for older Windows-versions: lpszUsername Pointer to a null-terminated string that specifies the user name. This is the name of the user account to log on to. lpszDomain Pointer to a null-terminated string that specifies the domain or server to log on to. If this parameter is ".", LogonUser searches only the local account database for the account specified in lpszUsername. If this parameter is NULL, LogonUser searches the local account database, and then searches trusted domain account databases, until it finds the lpszUsername account or the search is exhausted without finding the account name. > > Arno garrels > > >> If a new domain property is added, nothing prevent the component user >> from ignoring it and still provide domain name and user name in the user >> name part as today, and to rely on the smart proxy to handle that >> situation. It is not worse than today and even provide an enhancement. >> >> -- >> [EMAIL PROTECTED] >> http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be