Unable to Connect to Production Exchange 2007 Server

Under some instances, due to configuration issues or the version of Outlook DLLs used, some customers have been unable to connect to a 2007 Production Exchange Server. We have listed the possible reasons and resolutions below.

Invalid Configuration of Rights Required for Online Database & Mailbox Access

Before connecting to a Production Exchange Server Database / Mailbox you must grant specific rights to the operator. The rights required will differ depending upon the version of Exchange Server you are attempting to connect to. Follow the instructions as outlined in Rights Required for Online Database & Mailbox Access.

Use of Outlook 2003 or Outlook 2003 DLLs for DigiScope® Connection to an Exchange Server Without a Public Folder Fails to Connect

When you installed Exchange 2007, you may have answered "No" to the question "Do you have any client computers running Outlook 2003 and earlier or Entourage in your organization?"  If so, this eliminated the creation of the Public Folder database.  The end result is that Outlook 2003 can only connect to an Exchange 2007 Server if it has a Public Folder database, so at this point you have two options.

  1. Create a Public Store/Database on the Exchange 2007 Server.  For more about this, please reference http://support.microsoft.com/kb/555851

  2. Utilize Outlook 2007 or Outlook 2007 DLLs to bypass this requirement.

DigiScope® Unable to Connect to Online Mailboxes if Installed on Windows 2008 with Exchange 2007

This issue is caused by IPv6 and a bug that Microsoft will hopefully fix in an upcoming service pack, however, this issue only occurs if you have Exchange 2007 installed on a Windows 2008 Server and are attempting to utilize DigiScope® directly on the Windows 2008 server. There are two ways to resolve this issue:

  1. Install and utilize DigiScope® on an alternate machine.

  2. If you are not currently utilizing IPv6, then follow the steps outlined below to disable IPv6.

    1. Unbind IPv6 from the Network Adapter

    2. Open Regedit and navigate to HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters

      WARNING: Before you edit the registry, ALWAYS export the keys in the registry that you plan to edit, or back up the whole registry so that if a mistake is made you have a rapid rollback position. Learn more about the Windows Registry.

    3. Add a DWORD32 named DisabledComponents and give it the following value: 0xff

      NOTE: When installing Exchange 2007 on Server 2008, using Outlook Anywhere requires using this value and you can read more about this in the following MS Exchange Team Article and to refer to the table below for other possible values. We would also suggest that you review the IPv6 Transition Technologies White paper for more details.



      Disable all IPv6 tunnel interfaces, including ISATAP, 6to4, and Teredo tunnels


      Disable all 6to4-based interfaces


      Disable all ISATAP-based interfaces


      Disable all Teredo-based interfaces


      Disable Teredo and 6to4


      Disable IPv6 on non tunnel interfaces including all LAN and PPP interfaces


      Disable IPv6 on all LAN, PPP, and tunnel interfaces


      Prefer IPv4 to IPv6 when attempting connections


      Disable IPv6 over all interfaces and prefer IPv4 to IPv6 when attempting connections


    4. Edit the hosts file (usually located in "C:\Windows\System32\Drivers\etc" ) to comment out the IPv6 "localhost" equivalent.

      1. You will see an entry that looks like this "::1 localhost"

      2. Put a # in front of the entry to comment it out like this "# ::1 localhost"

      3. Also add the Netbios and FQDN of the server that holds the CAS role to the HOSTS file

        ex. rhino.acme.com rhino

    5. Reboot

    6. Run netstat –a –n to confirm that IPv6 is removed.