Getting IP-HTTPS error code 0x643?

We’ve had a couple reports of visitors to this site hitting IP-HTTPS error code 0x643 so I’m going to devote this article to the cause and resolution 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 0x643 and it reports “IPHTTPS interface administratively disabled”

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 0x643 issue!

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

Categories: Troubleshooting DirectAccess

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

  1. Derrick
    July 18, 2014 at 09:10 #

    What would cause the DisabledComponets key to appear in the registry? By default the key isn’t there.

  2. Paddy Tallon
    October 27, 2014 at 11:27 #


    Getting IP-HTTPS error code 0x274c on the Windows 8.1 client. Have read loads of blogs and tried several different fixes but nothing has worked thus far.

    Could you please help me to resolve this issue? I have been working on this for quite a while now!!

    Many thanks,


    • October 29, 2014 at 11:31 #

      Hi Paddy,

      The IP-HTTPS error code 0x274c is pretty common and translates to :

      A connection attempt failed because the connected party did
      not properly respond after a period of time, or established
      connection failed because connected host has failed to

      I’ve seen this many times in the past when TCP/443 was not reachable from the Internet to the DirectAccess server. Are you able to telnet on port 443 to your IP-HTTPS location? You can find this by typing :

      netsh int https sh int

      Thanks for reading!

      – Tom

      • Paddy Tallon
        October 30, 2014 at 01:51 #


        Thanks for your response.

        The output I get from your suggestion is as follows:

        Role: Client


        Last Error Code: 0x274c

        Interface Status: failed to connect to the HTTPS server. Waiting to reconnect

        I’m not sure about where to go from here….

        Best regards,


      • November 4, 2014 at 09:21 #

        Hi Paddy,

        Are you able to telnet to your DA server name externally on port 443? You can use the following syntax :

        telnet 443

        Replace with your actual FQDN



  3. Derrick
    November 7, 2014 at 06:16 #

    I am trying to get SolidWorks 2014 working over DirectAccess 2012. Anyone now how to achieve this?


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

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

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: