"Kristijan Marin" <kristijan.marin@hermes-plus.si> wrote in message
news:eeUrUVIrFHA.2804@TK2MSFTNGP10.phx.gbl...
> Does anyone know how to copy files inside network from mashine one to
> mashine2
> if the mashine2 requires user/pass authentication ??
>
> I need this for Windows platform.

William DePalo [MVP VC++] wrote:

>>Does anyone know how to copy files inside network from mashine one to
>>mashine2
>>if the mashine2 requires user/pass authentication ??

> If it is one of NT/2K/XP/2K+3 that you are talking about you should be able
> to use this sequence
>
> LogonUser();
> ImpersonateLoggedOnUser();
> CopyFile();
> RevertToSelf();
> CloseHandle(); // on the token returned by LogonUser()

Willy Denoyette [MVP] wrote:
> The purpose of LogonUser is to obtain an access token specifying the
> credentials of a valid local or domain (remote) account. If you specify a
> remote users credentials, the token obtained can be used to impersonate the
> current thread and access the remote resource. Now, if you use non local
> user credentials, accesses to local FS objects will fail (unless the remote
> user is a shadow account of a local account), this can be solved by:
> - specifying a domain user when calling LogonUser and granting this doamin
> account access to the loacl FS resources, or,
> - by specifying LOGON32_LOGON_NEW_CREDENTIALS as dwLogonType (W2K2 or
> higher).
>
> Willy.

Willy Denoyette [MVP] wrote:
> This is by design, the logontype LOGON32_LOGON_NETWORK returns an access
> token that has NO network access.

> Yep, no need to map shares to local drives anymore

"Tamas Demjen" <tdemjen@yahoo.com> wrote in message
news:ubY1xMhsFHA.3216@TK2MSFTNGP12.phx.gbl...
> William DePalo [MVP VC++] wrote:
>
>>>Does anyone know how to copy files inside network from mashine one to
>>>mashine2
>>>if the mashine2 requires user/pass authentication ??
>
>> If it is one of NT/2K/XP/2K+3 that you are talking about you should be
>> able to use this sequence
>>
>> LogonUser();
>> ImpersonateLoggedOnUser();
>> CopyFile();
>> RevertToSelf();
>> CloseHandle(); // on the token returned by LogonUser()
>
> LogonUser only logs you in to the local computer, and it can't be used to
> log on to a remote computer.

"Tamas Demjen" <tdemjen@yahoo.com> wrote in message
news:ubY1xMhsFHA.3216@TK2MSFTNGP12.phx.gbl...
> William DePalo [MVP VC++] wrote:
>
>>>Does anyone know how to copy files inside network from mashine one to
>>>mashine2
>>>if the mashine2 requires user/pass authentication ??
>
>> If it is one of NT/2K/XP/2K+3 that you are talking about you should be
>> able to use this sequence
>>
>> LogonUser();
>> ImpersonateLoggedOnUser();
>> CopyFile();
>> RevertToSelf();
>> CloseHandle(); // on the token returned by LogonUser()
>
> LogonUser only logs you in to the local computer, and it can't be used to
> log on to a remote computer. The user must exist locally. If the user
> doesn't exist locally, than WNetAddConnection seems to be the only way to
> go, which is not safe, because if the app crashes, the connection remains
> open. I have yet to find a solution that works and is safe. LogonUser is
> totally out of question, because on a typical network a local computer
> only has 1 user, while a file server has numerous others.
>
> Tom

"Tamas Demjen" <tdemjen@yahoo.com> wrote in message
news:us41%23QisFHA.2492@tk2msftngp13.phx.gbl...
> Willy Denoyette [MVP] wrote:
>> The purpose of LogonUser is to obtain an access token specifying the
>> credentials of a valid local or domain (remote) account. If you specify a
>> remote users credentials, the token obtained can be used to impersonate
>> the current thread and access the remote resource. Now, if you use non
>> local user credentials, accesses to local FS objects will fail (unless
>> the remote user is a shadow account of a local account), this can be
>> solved by:
>> - specifying a domain user when calling LogonUser and granting this
>> doamin account access to the loacl FS resources, or,
>> - by specifying LOGON32_LOGON_NEW_CREDENTIALS as dwLogonType (W2K2 or
>> higher).
>>
>> Willy.
>
> Thanks Willy, this seems to be solving a 2-year-old problem to me. The
> following works nicely:
>
> HANDLE token;
> if(LogonUser(
> "Tamas", "\\\\RemoteComputer",
> "password",
> LOGON32_LOGON_NEW_CREDENTIALS,
> LOGON32_PROVIDER_DEFAULT,
> &token))
> {
> if(ImpersonateLoggedOnUser(token))
> {
> CopyFile("c:\\0.txt", "\\\\RemoteComputer\\Share\\0.txt",
> TRUE);
> RevertToSelf();
> }
> CloseHandle(token);
> }
>
> Does the LOGON32_LOGON_NEW_CREDENTIALS flag require the server to be W2k+,
> or the client (local) computer only?
>

> I also tried this:
> BOOL res = LogonUser(
> "Tamas@RemoteComputer", NULL,
> "password",
> LOGON32_LOGON_NETWORK,
> LOGON32_PROVIDER_DEFAULT,
> &token);
>
> and res was TRUE and the token was valid, but after the
> ImpersonateLoggedOnUser call the remote FS was not accessible. Note that
> RemoteComputer is not a true domain, it's just another computer in a
> workgroup. I guess if I knew how to add access to the FS, that would work
> too. <sigh> I'd spent days without success before.
>

> Anyway, LOGON32_LOGON_NEW_CREDENTIALS does the trick, but only on W2k+.
>

> Tom

William DePalo [MVP VC++] wrote:

> I guess that depends on what you mean by "log on to a remote computer".
>
> I can tell you that, just as the docs specify, if on a machine in a domain,
> you specify the credentials of a domain user, then you can certainly get a
> token and use it to impersonate that user.
>
> And of course, you can also use the function to get a token representing a
> user local to the machine.

"Tamas Demjen" <tdemjen@yahoo.com> wrote in message
news:u0PfgdssFHA.2492@tk2msftngp13.phx.gbl...
> LOGON32_LOGON_NEW_CREDENTIALS is not required to impersonate users on the
> local machine, or on a remote machine in the same domain as the local one.
>
> It seems to me that LogonUser was originally designed to support
> impersonation of local and domain users, and later (in W2k) MS has
> introduced the LOGON32_LOGON_NEW_CREDENTIALS logontype to support foreign
> domains and machines not in a domain.