Getting IP-HTTPS error code 0x34?

I’ve had a few reports recently from some visitors about IP-HTTPS error code 0x34 on Windows 8 and Windows 8.1 systems. As reference, you can run the following command on your DirectAccess client to check the state of the IP-HTTPS adapter :

netsh int https show int

You will get an output that will show the current state of the connection. A good connection should show error code 0×0 like below :

Good IP-HTTPS connection

Good IP-HTTPS connection

If you are getting a 0x34 error code, this means the OS encountered an issue with a duplicate name. The OS thinks there is a stale IP-HTTPS adapter present in the registry and gets into this state. The root cause is being investigated and I’ll be sure to post more details once they become available.

We now have a public hotfix available to address this issue for any Windows 8.1 and 2012 R2 DirectAccess clients.  You can grab the hotfix here :

http://support.microsoft.com/kb/2966087

This hotfix should be rolled out into a monthly update for Windows 8.1 and 2012 R2 systems in a couple of months.  If you are keeping up-to-date with your monthly updates, then you should no longer encounter this IP-HTTPS error.

As a workaround without the hotfix, you can follow the steps below although I would highly recommend just installing the above hotfix. First make a backup of the following registry keys on one of your DA clients encountering this issue :

HKLM\System\CCS\Control\Network\{4d36e972-e325-11ce-bfc1-08002be10318}\
HKLM\System\CCS\Control\Network\Uninstalled\
HKLM\System\CCS\Services\iphlpsvc\Parameters\IPHTTPS\

After you’ve backed up these keys, then delete all of the GUID values under each of the folders (the GUID values start with a squiggly bracket “{” ). Then try to reboot and see if the DA client will rebuild a new working IP-HTTPS adapter. If this doesn’t work for anyone, please leave a comment in the box below.

Tags: , , , , , , , , , , , , , , , , ,

Categories: Troubleshooting DirectAccess

9 Comments on “Getting IP-HTTPS error code 0x34?”

  1. Richard Knight
    May 6, 2014 at 04:06 #

    Hi,
    Just came across this issue on a customers site. your fix worked.

    Looking forward to finding out the route cause.

    Regards

  2. Mark Lillywhite
    May 20, 2014 at 02:19 #

    Hi – tried your fix but it just regenerated the same keys after the reboot (with the same error) – will update if we figure out the Root cause

  3. John Gilbert
    June 10, 2014 at 13:00 #

    Tough problem to t-shoot. Workaround worked. Very hard to find this blog entry. To make it easier, Need to add “iphttps” vs ip-https, and other keywords. The 0x34 error code is not evident until you find out to use netsh to further isolate the problem.

    • June 10, 2014 at 14:52 #

      Hi John,

      Thanks for the feedback! I’ve added a bunch of additional tags to the article so hopefully it will be easier to find in an Internet search in the near future.

Trackbacks/Pingbacks

  1. DirectAccess Client Troubleshooting Guide | The DirectAccess Guide - May 2, 2014

    […] Getting IP-HTTPS error code 0×34? […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: