I think what you describe is basically second hop issue then..

I just found 
this https://msdn.microsoft.com/en-us/library/ee309365(v=vs.85).aspx 
regarding multi-hop configuration for winrm - I suggest working through it 
and seeing if it is any help.

Jon 

On Friday, June 19, 2015 at 8:16:23 AM UTC+1, [email protected] wrote:
>
> Both servers are domain members and i am using domain administrator 
> account.
> Following scheme doesn't work neither:
>
> Ansible ---> srv01 ---> srv01   works
>                            |
>                            ---> srv02  doesn't work
>
> Ansible ---> srv02  ---> srv02  works
>                             |
>                             ---> srv01  doesn't work
>
> This issue is quite critical for me as i really need to deploy windows 
> machines the same way i do linux.
>
> On Friday, June 19, 2015 at 2:13:19 AM UTC+2, Trond Hindenes wrote:
>>
>> So just to sum up:
>> Ansible-->srv01: You can list stuff in \\srv01\ but not \\srv02
>>
>> Are you connecting to srv01 from ansible using a domain account or a 
>> local account? If local it's pretty logical that you have this issue: The 
>> user doesn't have any permissions outside srv01, so that's the only thing 
>> you can see.
>>
>> For cross-machine boundaries you need to connect using a domain account. 
>> Or you can write an Ansible module which takes username/password as a 
>> parameter and pass that in (look at the PR for win_package in the 
>> "ansible-modules-extras" repo on githug, it has the functionality to get 
>> files from a unc share using explicitly defined credentials.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/e4e6b42e-a6ea-402e-83e1-0c03fc197b2b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to