When our complete network is running on ip v4  ,why  do we need ipv6 enabled on our server  2008 ? let us unselect the ipv6  form  the network adapter properties ……  ho .. wait …wait..! I did it on my exchange server 2010 and ran into problems .

If the windows version is  Windows sbs 2008 (Windows Small Business Server 2008) then we may  encounter some  issues  like

“Exchange server services will fail to start ” and the Microsoft Exchange Active Directory Topology service will fail to start .We can see one or more fallowing errors  in event viwer.

 

Application Log Events

Event ID: 2114 

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.

 

 

 

 

System log events like,

The Microsoft Exchange Address Book service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.

The Microsoft Exchange RPC Client Access service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.

Also Excahnge server installation will fail with error like below .

The execution of: “$error.Clear(); if ($RoleStartTransportService) { start-SetupService -ServiceName MSExchangeTransport }”, generated the following error: “Service ‘MSExchangeTransport’ failed to reach  status ‘Running’ on this server.”

 

Though IP v 6  is supported  fully on windows 2008 server , If we disable ipv6  in network interface card (NIC) , we may run into some problems  especially if we are running exchange services or trying to install exchange server .

So it is better not to unselect the IPv6 .If we really need to disable ip v6 then unselecting the checkbox is not  enough alone. We  should also change registry modification .

method 1:

  1. Uncheck Internet Protocol Version 6 (TCP/IPv6) on 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, we 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:

 

 

 

 

 

 

 

 

Quick method 2:

open command prompt with administrator privilages ( right click on command prompt and select run as administrator)  , and type the command  c:\>reg add hklm\system\currentcontrolset\services\tcpip6\parameters /v DisabledComponents /t REG_DWORD /d 255

 

Now finally ,  If we want to run vpn from the serevr on which we disbaled ipv6, we must delete the fallowing registry key and retsrat the server (make sure to export the key before deleting it). other wise routing and remote access will fail with event id 20103

  Event ID   : 20103
  Source     : Router
  Description: Unable to load c:\winnt\system32\iprtrmgr.dll
 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemoteAccess\RouterManagers\Ipv6


 


 

 

 

 

 

 


2 Comments

Vinod · October 17, 2011 at 2:42 am

Srikanth bro … cool site … missin u 😀

jeevan · September 11, 2011 at 9:21 pm

thanks ! saved me

Leave a Reply

Your email address will not be published.