Issues After Disabling IPv6 on Your NIC on SBS 2008
Published Apr 04 2019 02:20 PM 2,917 Views
Microsoft
First published on TechNet on Oct 24, 2008

[Today's post comes to us courtesy of Justin Crosby, Ed Walters, and Doug Boyd]


If you uncheck the IPv6 protocol from your network interface card on your Windows SBS 2008 server you may see the following issues after a reboot:



  • Microsoft Exchange services fail to start

  • Server hangs at "Applying Computer Settings..."  (can eventually logon after 30 - 60 minutes)

  • Network icons show as offline

  • Some or all of the following events


Application Log Events

Source: MSExchange ADAccess
Event ID: 2114
Task Category: Topology
Level: Error

Description:
Process MAD.EXE (PID=2088). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.


----------------------


Source: MSExchange ADAccess
Event ID: 2601
Task Category: General
Level: Warning

Description:
Process MSEXCHANGEADTOPOLOGY (PID=952). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,...> - Error code=80040a01.




The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.


----------------------


Source: MSExchange ADAccess
Event ID: 2102
Task Category: Topology
Level: Error

Description:
Process MAD.EXE (PID=2088). All Domain Controller Servers in use are not responding: SBS.sbs2008.local


----------------------


Source: MSExchange ADAccess
Event ID: 2105
Task Category: Topology
Level: Warning

Description:
Process MAD.EXE (PID=2088). Exchange Active Directory Provider failed to obtain DNS records for domain sbs2008.local. DNS Priority and Weight for the Domain Controllers in this domain will be set to the default values 0 (priority) and 100 (weight).


----------------------


Source: MSExchange ADAccess
Event ID: 2114
Task Category: Topology
Level: Error


Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=952). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.


----------------------



Source: MSExchangeFBPublish
Event ID: 8197
Task Category: General
Level: Error


Description:
Error initializing session for virtual machine SBS. The error number is 0x80040a01. Make sure Microsoft Exchange Store is running. Also, make sure that there is a valid public folder database on the Exchange server.


----------------------


Source: MSExchangeTransportLogSearch
Event ID: 7005
Task Category: General
Level: Error


Description:
Microsoft Exchange couldn't read the configuration from the Active Directory directory service because of error: Failed to load config due to exception: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Exchange Topology service on server localhost did not return a suitable domain controller.



System Log Events

Source: Service Control Manager
Event ID: 7044
Task Category: None
Level: Warning


Description:
The following service is taking more than 16 minutes to start and may have stopped responding: Microsoft Exchange System Attendant


----------------------


Source: Service Control Manager
Event ID: 7022
Task Category: None
Level: Error


Description:
The Microsoft Exchange Transport service hung on starting.


----------------------


Source: Service Control Manager
Event ID: 7024
Task Category: None
Level: Error


Description:
The Microsoft Exchange Information Store service terminated with service-specific error 0 (0x0).




Resolution

To resolve this issue all you have to do is re-check IPv6 in the properties of you NIC and reboot.



NOTE: IPv4 must also be enabled.


Properly Disabling IPv6

SBS 2008 is designed to fully support IPv6 and has IPv6 enabled by default.  Most users should never need to disable IPv6, however if you must disable IPv6 here is how to disable it properly:


Important: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 ( http://support.microsoft.com/kb/322756/ )



  1. Uncheck Internet Protocol Version 6 (TCP/IPv6) on your Network Card.

  2. In Registry Editor, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\

  3. Double-click DisabledComponents to modify the DisabledComponents entry.
    Note If the DisabledComponents entry is unavailable, you must create it. To do this, follow these steps:

    1. In the Edit menu, point to New , and then click DWORD (32-bit) Value .

    2. Type DisabledComponents, and then press ENTER.

    3. Double-click DisabledComponents .


  4. Enter " ffffffff " (eight f’s), and then click OK :


  5. Reboot the SBS 2008 server.


RRAS (VPN) Note: If you plan to enable VPN on your SBS 2008 server, you MUST also Export and then Delete the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemoteAccess\RouterManagers\Ipv6


If you do not delete this key you will get an 20103 Event when trying to start RRAS with IPv6 disabled.  You must reboot after removing this key.


For more information please see:


Version history
Last update:
‎Apr 04 2019 02:20 PM
Updated by: