Getting IP-HTTPS error code 0x32?

Good Afternoon! So after encountering this error a couple of times myself and just recently having a poster report this issue, I’m going to be covering the cause for IP-HTTPS error code 0x32. Luckily this is a pretty simple one so I’ll keep it short today!

If your client is trying to connect using IP-HTTPS, you will encounter this error code if the IP-HTTPS adapter on your DirectAccess client/server has been disabled.

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

Now on a system that is having the issue, you will see the error code 0x32 and it reports “IPHTTPS interface administratively disabled” just like below :

IP-HTTPS error code 0x32

IP-HTTPS error code 0x32

So now we need to determine why the IPHTTPS interface is administratively disabled. So the most common cause of this occurrence would be a registry key that disables either part or the entire IPv6 stack. DirectAccess requires that the IPv6 stack is enabled (at least for the IPHTTPS adapter) in order to function correctly. To check and see if you’ve disabled the IPv6 stack, check the following registry key location :


DisabledComponents Registry Key

DisabledComponents Registry Key

Look for a value called DisabledComponents as this can disable part of the IPv6 network stack used by DirectAccess. In my example, the registry value of 142 in decimal. This was disabling the IPHTTPS adapter on my machine. The value should either be 0 or not exist entirely for the IPv6 stack to be properly enabled for DirectAccess. If you do remove this registry key, you do need to reboot for this to go into effect. Just for reference, you can read more about the disabledcomponents registry key here on the Microsoft website :

Please leave a comment below if this doesn’t solve your IP-HTTPS error code 0x32 issue!

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

Categories: Troubleshooting DirectAccess

7 Comments on “Getting IP-HTTPS error code 0x32?”

  1. May 28, 2014 at 06:39 #

    I’ve also seen a 0x643 error (IPHTTPS interface creation failure) caused by the exact same registry setting – fix was to delete that registry value then restart the IP Helper Service, which brought everything back to life.

    • May 28, 2014 at 07:34 #

      Thanks for the information Sean! I’ll be sure to add this one to the list of IP-HTTPS error codes on my site.

  2. Derrick
    June 9, 2014 at 08:56 #

    I also was receiving 0x643 and removing DisabledComponents registry key fixed the issue.

    • Derrick
      July 18, 2014 at 08:10 #

      I have another computer that is having 0x643 error but the DisabledComponents registry key is not in the registry. Any other recommendations?

      • Derrick
        July 18, 2014 at 08:35 #

        reset ipv6 fixed

  3. Robert Rigdon
    March 25, 2015 at 11:19 #

    We are using this fix for our network but this registry key keeps returning to our users systems. Does anyone have an idea of what would be recreating this registry key?


  1. DirectAccess Client Troubleshooting Guide | The DirectAccess Guide - April 11, 2014

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

Leave a Reply

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

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

Google photo

You are commenting using your Google 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 )

Connecting to %s

%d bloggers like this: