DirectAccess Windows 8 Client Won't Connect - Last Error Code: 0x2af9

Question

Hi All
Well I've had 2012 DirectAccess up and running now for about 2/3 weeks (using Win8 client only), it's been "ok" (most problems are client based - like Services not restarting upon resuming from sleep).
Yesterday I spent many hours connected to DirectAccess from my Windows 8 Laptop. When it's working, I love it.
Today, it's a completely different story.
Windows 8 won't damn well connect. At first I started getting prompted to enter proxy credentials (I have no idea why, have never been prompted for this before and the internal TMG proxy shouldn't even be in the loop, given my DA server has it's own
public IP address). The DA server has a completely separate public IP to the proxy's public IP address and the DA is setup with 2x NICs.
The error I'm getting is:
Interface IPHTTPSInterface (Group Policy)  Parameters
Role                       : client
URL                        :
https://da.fqdn:443/IPHTTPS
Last Error Code            : 0x2af9
Interface Status           : failed to connect to the IPHTTPS server. Waiting to reconnect
Where do I find out what 0x2af9 error code means?

Answer 1

Hi,
The information for your errorcode seems to be related to not beeing able to lookup the host (the information from MSDN is pasted below.)
Can you verify that your client can resolve "da.fqdn" to the correct IPv4 address?
http://msdn.microsoft.com/en-us/library/windows/desktop/ms681391.aspx
WSAHOST_NOT_FOUND
11001 (0x2AF9)
No such host is known.
Jonas Blom | Relevo AB |
http://blog.nrpt.se
Hi Jonas
Thanks for your input. I think you might be right.
I suspected IE wasn't resetting my connection settings (even though I had un-ticked 'use a proxy server' - I don't think it had 'applied').
So, I did a reset of IE10, noticed all of the connection settings were gone and DA connected.
There definitely seems to be a gap in the DirectAccess solution in that it refers to the IE proxy/connection settings rather than just goes out to the Internet like Outlook does. When on the Domain, obviously you'll receive GPOs which in most organisations
that use things like Proxies (e.g. TMG) these GPOs will apply the proxy settings, but then when you disconnect from the Domain and you want to roam, those proxy settings need to be disabled - at least until DA has connected, then you're free to apply
the proxy as the gateway again.
It's a bit annoying.