I see a sucessful connection listed in the event logs, and in my original
post demonstrated that I could telnet in on the WinRM port, so no firewall
blocking. There is also no proxy or anything in between. I can connect to
over 100 different servers, many on the same subnet as myhost, but this is
the only one giving me trouble.

On Thu, Nov 12, 2015 at 1:19 PM, J Hawkesworth <
[email protected]> wrote:

> try hitting it again with ansible and check the event logs for any
> evidence of a login attempt.
>
> if its not getting that far... is there a proxy between controller and
> windows host (guessing a bit here, not much experience with proxies)?
>
> possibly firewall rules kicking in?  bear in mind different profiles which
> may or may not be affecting connection from controller to windows target
> differently from windows to windows
>
> will try and think of more ideas.
>
>
> On Thursday, November 12, 2015 at 1:58:18 PM UTC, Matt Calhoun wrote:
>>
>> I have verified that PSRemoting seems to be working fine on this host.
>> From another windows box...
>>
>> PS C:\> Invoke-Command -ComputerName myhost -port 5985 -Authentication
>> Kerberos -ScriptBlock { Get-Content c:\windows\system32\drivers\etc\hosts
>>  } -credential myaccount
>> <Prompted for and enter password here>
>>
>> # Copyright (c) 1993-2009 Microsoft Corp.
>> #
>> # This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
>> #
>> # This file contains the mappings of IP addresses to host names. Each
>> # entry should be kept on an individual line. The IP address should
>> # be placed in the first column followed by the corresponding host name.
>> # The IP address and the host name should be separated by at least one
>> # space.
>> #
>> # Additionally, comments (such as these) may be inserted on individual
>> # lines or following the machine name denoted by a '#' symbol.
>> #
>> # For example:
>> #
>> #      102.54.94.97     rhino.acme.com          # source server
>> #       38.25.63.10     x.acme.com              # x client host
>>
>> # localhost name resolution is handled within DNS itself.
>> #       127.0.0.1       localhost
>> #       ::1             localhost
>>
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Ansible Project" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/ansible-project/ZebLwqaxYpo/unsubscribe.
> To unsubscribe from this group and all its topics, 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/0433d886-3b8b-413a-ae39-3c0f1c2b65a3%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/0433d886-3b8b-413a-ae39-3c0f1c2b65a3%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAEw3D2c6SZkGcvCE5APFS_vOhSmKNLbEOW97-RtLHn35o07nmA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to