# Troubleshooting Windows Host UNREACHABLE! **URL:** \ **Category:** Ansible Project\ **Tags:** windows\ **Created:** [November 11, 2015, 9:47pm UTC](https://forum.ansible.com/t/troubleshooting-windows-host-unreachable/19738 "2015-11-11T21:47:20Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Calhoun\_Matt](https://avatars.discourse-cdn.com/v4/letter/c/ecb155/32.png) [@Calhoun\_Matt](https://forum.ansible.com/u/Calhoun_Matt)\ **Post date:** [November 11, 2015, 9:47pm UTC](https://forum.ansible.com/t/troubleshooting-windows-host-unreachable/19738/1 "2015-11-11T21:47:20Z")
I have many windows hosts that have been configured identically (as far as I can tell) and I can connect to all but one of them. Anyone have an idea of why this may be happening? - Up to date on all windows patches - Have rebooted $ ansible myhost -m win\_ping -o -vvvv Using /Users/[redacted]/Dropbox/Code/[redacted]/[redacted]/ansible.cfg as config file Loaded callback oneline of type stdout, v2.0 ESTABLISH WINRM CONNECTION FOR USER: [redacted]@MYDOMAIN.LOCAL on PORT 5985 TO myhost EXEC Set-StrictMode -Version Latest (New-Item -Type Directory -Path $env:temp -Name “ansible-tmp-1447277903.29-206977271531324”).FullName | Write-Host -Separator ‘’; myhost | UNREACHABLE! $ telnet myhost 5985 Trying 10.159.15.11… Connected to myhost.mydomain.local. Escape character is ‘^]’. C:\Windows\system32\>hostname myhost C:\Windows\system32\>winrm get winrm/config/service Service RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)(A;;GR;;;IU)S:P(AU;FA;GA;;;WD)(AU;SA;GXGW;;;WD) MaxConcurrentOperations = 4294967295 MaxConcurrentOperationsPerUser = 1500 EnumerationTimeoutms = 240000 MaxConnections = 300 MaxPacketRetrievalTimeSeconds = 120 AllowUnencrypted = true [Source=“GPO”] Auth Basic = true [Source=“GPO”] Kerberos = true Negotiate = true Certificate = false CredSSP = false CbtHardeningLevel = Relaxed DefaultPorts HTTP = 5985 HTTPS = 5986 IPv4Filter = \* [Source=“GPO”] IPv6Filter = \* [Source=“GPO”] EnableCompatibilityHttpListener = false EnableCompatibilityHttpsListener = false CertificateThumbprint ---
**Author:** ![Trond\_Hindenes](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@Trond\_Hindenes](https://forum.ansible.com/u/Trond_Hindenes)\ **Post date:** [November 11, 2015, 11:06pm UTC](https://forum.ansible.com/t/troubleshooting-windows-host-unreachable/19738/2 "2015-11-11T23:06:47Z")
Can you test regular psremoting from another windows host to the problematic machine using the same port (5985) and the same auth scheme (Kerberos) that you are (seemlingly) using in your Ansible config? ---
**Author:** ![j.r.hawkesworth](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@j.r.hawkesworth](https://forum.ansible.com/u/j.r.hawkesworth)\ **Post date:** [November 12, 2015, 5:20am UTC](https://forum.ansible.com/t/troubleshooting-windows-host-unreachable/19738/3 "2015-11-12T05:20:11Z")
Worth checking if Window Remote Management service is running and if using a domain user that the domain user a member of the WinRMRemoteWMIUsers\_\_ group too. Jon ---
**Author:** ![Calhoun\_Matt](https://avatars.discourse-cdn.com/v4/letter/c/ecb155/32.png) [@Calhoun\_Matt](https://forum.ansible.com/u/Calhoun_Matt)\ **Post date:** [November 12, 2015, 1:58pm UTC](https://forum.ansible.com/t/troubleshooting-windows-host-unreachable/19738/4 "2015-11-12T13:58:18Z")
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 # Copyright (c) 1993-2009 Microsoft Corp. ---
**Author:** ![j.r.hawkesworth](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@j.r.hawkesworth](https://forum.ansible.com/u/j.r.hawkesworth)\ **Post date:** [November 12, 2015, 6:19pm UTC](https://forum.ansible.com/t/troubleshooting-windows-host-unreachable/19738/5 "2015-11-12T18:19:36Z")
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. ---
**Author:** ![Calhoun\_Matt](https://avatars.discourse-cdn.com/v4/letter/c/ecb155/32.png) [@Calhoun\_Matt](https://forum.ansible.com/u/Calhoun_Matt)\ **Post date:** [November 12, 2015, 7:04pm UTC](https://forum.ansible.com/t/troubleshooting-windows-host-unreachable/19738/6 "2015-11-12T19:04:17Z")
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. ---
**Author:** ![j.r.hawkesworth](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@j.r.hawkesworth](https://forum.ansible.com/u/j.r.hawkesworth)\ **Post date:** [November 12, 2015, 11:04pm UTC](https://forum.ansible.com/t/troubleshooting-windows-host-unreachable/19738/7 "2015-11-12T23:04:46Z")
Is this machine Server 2008 R2 by any chance? WMF 3.0 had an irritating bug where it would allocate a tiny memory quota for winrm so things would fail a lot. Hotfix for the fix as described in the blue box here: [http://docs.ansible.com/ansible/intro\_windows.html#windows-system-prep](http://docs.ansible.com/ansible/intro_windows.html#windows-system-prep) Just comparing my winrm get winrm/config/service with yours and my last line states ‘AllowRemoteAccess = true’ - do you have that? Jon