I see that our clients that i get "failed to connect to the IPHTTPS server. Waiting to reconnect" from command: "netsh interface httpstunnel show interface". This is when the clients is inside the corporate network and the network is working. No issues. From command "Netsh dns show state":
Machine Location : Inside corporate network
Direct Access Settings : Configured and Disabled
I just wonder if something is wrong here, should it really try to connect to the httpstunnel when inside the corporate network? Should it not say that the tunnel is inactive? We have had some strange network issues with laptops where we have Direct Access published so i am thinking it might is connected to this.
Output from "netsh dns show state":
Machine Location: Inside corporate network
Direct Access Settings: Configured and activated!
On the other netsh command my Windows 8 machine starts complaining I should use PowerShell and "Get-netIPHTTPSConfiguration" ;-)
IMHO the beaviour of a machine which realized that it is inside the corporate network should be that it doesn´t try to connect via httpstunnel. This would be more or less senseless.
I checked the commands with a Windows 7 Client and got:
1) netsh interface httpstunnel show Interface:
Last errorcode: 0x0
Interface Status: The IP-HTTPS Interface is active
2) netsh dns Show state:
The same results as yours.
So the behaviour between Win8 and Win7 Clients seems to be different.