Click to Rate and Give Feedback
TechNet
TechNet Library
Exchange Server
Troubleshooting
 Outlook Anywhere Client Connectivit...

  Switch on low bandwidth view
Collapse All/Expand All Collapse All
Outlook Anywhere Client Connectivity Issue Because of TCP/IPv6

Applies to: Exchange Server 2007 SP1, Exchange Server 2007 Topic Last Modified: 2009-04-21

This topic explains an Outlook Anywhere connectivity problem that occurs when a client tries to connect over the Internet to an Exchange 2007 SP1 environment that is running on Windows Server 2008, and how to resolve it.

Cc671176.note(en-us,EXCHG.80).gifNote:
This problem was resolved in Update Rollup 4 for Exchange Server 2007 Service Pack 1. If you have installed Update Rollup 4 for Exchange Server 2007 Service Pack 1 or a later version, do not follow the procedure that is described in this topic.

When a client using Outlook Anywhere tries to connect to Exchange 2007 SP1 running on Windows Server 2008, the client cannot connect. This happens because the RPCProxy component on the Client Access server that is running on Windows Server 2008 is unable to connect through port 6004 to the DSProxy component on the Exchange Mailbox server.

Windows Server 2008 has made TCP/IPv6 the default communication protocol stack over which connections are made by clients connecting to the server that is running Microsoft Exchange. The RPCProxy component tries to connect to the DSProxy component through port 6004 over TCP/IPv6. However, the DSProxy component does not listen on the TCP/IPv6 stack, which causes connection requests from the RPCProxy component to fail.

In Exchange 2007 SP1, for clients to connect by using Outlook Anywhere when the Client Access server is running on Windows Server 2008, TCP/IPv6 connectivity must be manually disabled on all Exchange servers that have the Client Access server role installed.

To resolve the issue, perform one of the following procedures on the Client Access server. The procedure you use depends on whether your topology is running the Client Access server role and Mailbox server role on the same Exchange server or on different Exchange servers.

To perform the following procedures, the account you use must be delegated the Exchange Organization Administrator role. For more information about permissions, delegating roles, and the rights that are required to administer Exchange 2007, see Permission Considerations

To disable TCP/IPv6 in a multiple-server topology where the Client Access server role is not running on the same Exchange server as the Mailbox server role
  1. Under Network Connections, select the network adapter, and then click Properties.

  2. In the properties window, click to clear the check box for Internet Protocol Version 6 (IPv6).

    Cc671176.note(en-us,EXCHG.80).gifNote:
    Clearing this check box causes the RPCProxy component on the Client Access server to use TCP/IPv4 to talk to the DSProxy component on the Mailbox server.
  3. Click Start, and then click Run.

  4. Type regedit in the Open box.

  5. Using Registry Editor, locate the following registry key:

    HKEY_Local_Machine\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters

  6. Right-click the Parameters key, click New, and then click DWORD (32-bit) Value. For the key, add the following values:

    Name: DisabledComponents

    Data: 0xFFFFFFFF

  7. Restart the Client Access server.

The preceding procedure does not work for a single-server topology where the Client Access server role is running on the same Exchange server as the Mailbox server role. This is because the loopback interface (an interface that is used when communicating through TCP/IP to a process on the same computer) continues to use TCP/IPv6. In this case, you must perform the following steps to disable TCP/IPv6.

To disable TCP/IPv6 in a single-server topology where the Client Access server role is running on the same Exchange server as the Mailbox server role
  1. Open the hosts file located at %SystemRoot%\system32\drivers\etc\ by using an editor such as Notepad.

    Cc671176.note(en-us,EXCHG.80).gifNote:
    In this step, %SystemRoot% refers to the local hard disk where the Windows system files are located.
  2. Search for the line that contains the term "localhost" by using the CTR+F key combination.

  3. Type a number sign (#) at the beginning and end of the line to make the line a comment.

  4. Press ENTER and, on the next line, type the following lines to provide the TCP/IPv4 address, hostname, and FQDN name for the Exchange server that is running both the Client Access and Mailbox server roles:

       <TCP/IPv4 address>   <host name of the computer>

       <TCP/IPv4 address>   <FQDN of the computer>

  5. Click Save, and then close the file.

For more information about TCP/IPv6, see IPv6 Support in Exchange 2007 SP1 and SP2.

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Incorrect Registry Value name      Brad Hughes ... Thomas Lee   |   Edit   |   Show History
The registry value you should create is called DisabledComponents (no spaces) and is documented in the following KB article:
929852 How to disable certain Internet Protocol version 6 (IPv6) components in Windows Vista
http://support.microsoft.com/default.aspx?scid=kb;EN-US;929852
Only remove ipv6 localhost from hosts file      MikeWedderburn-Clarke   |   Edit   |   Show History

The section on editing the hosts file is misleading, only the IPv6 reference to localhosts should be commented out.

Taken from the following blog http://www.buit.org/2008/01/04/outlook-anywhere-is-broken-on-ipv6-in-windows-server-2008/ by Kevin Reeuwijk;

(Corrections in bold)


1. Search for the line that contains the term "::1" by using the CTR+F key combination.

Tags What's this?: Add a tag
Flag as ContentBug
Does not apply to SBS 2008      Susan Bradley   |   Edit   |   Show History
Please be aware that this does not apply to Exchange 2007 running on SBS 2008. Do not disable IPv6 in this environment.
http://blogs.technet.com/sbs/archive/2008/10/24/issues-after-disabling-ipv6-on-your-nic-on-sbs-2008.aspx
Be aware that if you do, there will be significant side effects. Do NOT disable ipv6 on SBS 2008.


Due to the fact that the Mailbox role is running on the DC, you do not need to edit this.
You Had Me At EHLO... : How does Outlook Anywhere work (and not work)?:
http://msexchangeteam.com/archive/2008/06/20/449053.aspx


Also Exchange rollup 4 also includes a fix for this:
You are prompted for your credentials three times and you receive an error message when you use the Outlook Anywhere feature to connect to an Exchange Server 2007 Service Pack 1–based server that is running Windows Server 2008:
http://support.microsoft.com/kb/950138/
Tags What's this?: Add a tag
Flag as ContentBug
Incorrect Registry Data Value for DisabledComponents      CassiusA   |   Edit   |   Show History
The DisabledComponents registry data value mentioned should be 0xffffffff as documented in technet http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx
Problem NOT fixed by RU4      neuf   |   Edit   |   Show History
I was stuck trying to enable Outlook Anywhere on my single-server Exchange 2007 SP1 box, on Windows Server 2008. I was experiencing the "rpc_s_server_unavailable error 0x6ba was thrown by the rpc runtime" error using www.testexchangeconnectivity.com. In initial research of the issue, I found this KB article, but ignored it because it says that RU4 fixes the issue, and RU4 is installed on my server. However, after more hours of troubleshooting, I was still not getting anywhere.

I ruled out other possible issues through and kept coming back to the IPv6 issue. So, I tried doing an NSLookup on my Exchange servers FQDN and NetBIOS name from the Exchange server itself. Lo and behold, it was resolving to an IPv6 address. After applying the hosts fix outlined in this article, it worked perfectly. So don't rule out this issue just because you have installed RU4.
Tags What's this?: Add a tag
Flag as ContentBug
Be carefull      Sebest74   |   Edit   |   Show History
If using SCR onto an exchange 2007 Server, and adding both netbios and fqdn name of these servers into the HOSTS file, as described in this article, for a multiple role server, will broke your ability to enable SCR.
Tags What's this?: Add a tag
Flag as ContentBug
Solved my issue      Joel Austin   |   Edit   |   Show History
Even though the IP6 issue was said to be resolved in rollup 4 I still had to modify the lmhost file to get Outlook Anywhere to function properly. I have rollup 8 currently installed.
Tags What's this?: Add a tag
Flag as ContentBug
RollUp 4 and all other up to RollUp 8 does not fix Outlook Anywhere issue on Windows 2008      Sergey Erin   |   Edit   |   Show History
Rollup 4 and all older up to RollUp 8 does not fix issue with IPv6. mad.exe does not responding on port 6004 by IPv6 protocol.
telnet 127.0.0.1 6004 return
ncacn_http/1.0

telnet ::1 6004 return blank screen and disconnect after pressing any key.

If we disabling IPv6, as was writtng before, than SCR fail! Editing of hosts file couse SCR does not work.

I was found some workaround:
http://social.technet.microsoft.com/Forums/en-US/exchangesoftwareupdate/thread/9bdb72a5-1557-4713-afa8-68c06b9bac7b
Tags What's this?: Add a tag
Flag as ContentBug
Processing
© 2009 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement
Page view tracker