Background info: Coming from an Exchange 2003 server with AD installed, recently migrated to an Exchange 2007 server (Hub, Client Access, Mailbox). All mailboxes have been moved to the 2007 box, and mail flow is working fine. When testing Outlook Anywhere from testoutlookconnectivity.com, if I use the old server name (2003), all tests pass. If I use the new server name (2007), All tests pass until the very end where it fails with: "RPC Server Unavailable Error was thrown by the RPC Runtime" I followed the troubleshooting steps, and found that in the registry under RPC\rpcproxy - valid ports - both servers are listed with all ports. Hope this makes sense. Thank you!Here to learn

Does Outlook anywhere for 2007 works internally? Run the Test-Outlookwebservices cmdlet

I get: 1003 Information About to test AutoDiscover with the e-mai... 1007 Information Testing server mail.server.com wi... 1019 Information Found a valid AutoDiscover service connec... 1013 Error When contacting https://mail.server.com... 1006 Error The Autodiscover service could not be con... EDIT- trying to edit the window to view the full results...... Here to learn

Have done the following configure OA? Installed rpc\http component enabled and configured OA A good article http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/

Installed RPC/Http and enabled Outlook anywhere a while ago. For the most part is seems like it is working. It will work when I test Outlook, but is still failing the www.testexchangeconnectivity.com test when I use the new 2007 internal server name. All tests pass when I use the old 2003 internal server name. I am moving several remote offices to Outlook Anywhere and want it working perfectly, so I'm trying to determine what is not configured correctly. Thanks.Here to learn

with testexchangeconnectivity.com you are testing external connections. Why would you expose your internal server name to internet? Are you using self signed certs?

RPC proxy server: using external FQDN (Go Daddy cert pointing to it) Exchange server: using internal name server.domain.com Mutual authentication principal name: msstd:external FQDN Correct? Here to learn

Right. http://technet.microsoft.com/en-us/library/dd439392(EXCHG.80).aspx

Does Outlook anywhere for 2007 works internally? Run the Test-Outlookwebservices cmdlet

Have done the following configure OA? Installed rpc\http component enabled and configured OA A good article http://www.exchange-genie.com/2008/02/configuring-outlook-anywhere-for-exchange-2007-sp1/

with testexchangeconnectivity.com you are testing external connections. Why would you expose your internal server name to internet? Are you using self signed certs?

Right. http://technet.microsoft.com/en-us/library/dd439392(EXCHG.80).aspx

I just realized there is a static DNS setting pointing our internalservername.domain.com to our WAN address ?? This must have been set before I was with the company. I assume this would not EVER be needed would it? Would that cause any kind of strange loops, or cause Outlook Anywhere tests to fail since the internal and external server names point to the same place? GeezHere to learn

If you mean external DNS no its not required whack it. For external it shouldn't really cause issues unless internalservername.domain.com was your CAS array name for example.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Yes, external DNS. I just moved everything over from a 2003 box to a new 2007 box (client access, hub, and mailbox). Also, Exchange services are still running on the 2003 box. I'm very confused why the testexchangeconnectivity.com Outlook Anywhere test works fine when using the older 2003 exchange server name, yet fails (RPC_S_SERVER_UNAVAILABLE error) when using the new 2007 name. There is also 1 client who has been working fine all along using the new 2007 server name for Outlook Anywhere. Thank youHere to learn

To clarify you're doing a migration from 2003 to 2007. Outlook Anywhere continues to work for mailboxes on 2003 but not for users on 2007 except for one user that you said it works for? 1. Is your Exchange 2007 CAS now the "front" end or is your 2003 server the front end and you have the 2007 mailbox server as backend? 2. What do you mean when you change the name to 2003 it works but not 2007 in www.testexchangeconnectivity.com. Exchange 2007 is now mail.company.com correct?James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Yes. No, there are no mailboxes left on the 2003 server. 1. The 2007 server is now the front end. The 2003 server is strictly a DC, but the exchange services are still running on it, and RPC over HTTP. 2. This works: RPC proxy server: using external FQDN (Go Daddy cert pointing to it) Exchange server: 2003server.domain.com Mutual authentication principal name: msstd:external FQDN This doesn't (fails with RPC_S_SERVER_UNAVAILABLE error) RPC proxy server: using external FQDN (Go Daddy cert pointing to it) Exchange server: 2007server.domain.com Mutual authentication principal name: msstd:external FQDN Even though the testoutlookconnectivity.com test fails when using the new 2007 server name, I have tested it (with Outlook externally) and I'm able to send/receive. I have about 30 remote users I'm preparing to switch to Outlook Anywhere but don't want to do anything until I make sure the configuration is perfect. Here to learn

What service pack are you on for 2007 should be 2007 SP3 RU3. Just making sure you didn't update to the latest since there were incompatibility issues with IPv6. Also you mentioned that the validports reg key has both servers listed? Can you post the values? ServerNETBIOSName:6001-6002;ServerFQDN:6001-6002;ServerNetBIOSName:6004;ServerFQDN:6004James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Hello, Make sure the Exchange 2007 MBX server is in the list of the validports key: [Check the RpcProxy ValidPorts] ======================= 1. On the RPC proxy server, start Registry Editor (Regedit). 2. In the console tree, locate the following registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy 3. In the details pane, right-click the ValidPorts subkey, and then click Modify. 4. In Edit String, in the Value data box, type the following information: ExchangeServer :6001-6002; ExchangeServerFQDN :6001-6002; ExchangeServer :6004; ExchangeServerFQDN :6004 Thanks, Simon

Thanks for the reply. Current subkey value: Exchange03:6001-6002;Exchange03:6004;Exchange03.domain.com:6001-6002;Exchange03.domain.com:6004;Exchange07:6001-6002;Exchange07:6004;Exchange07.domain.com:6001-6002;Exchange07.domain.com:6004Here to learn

Hmmm not sure why the Exchange03 server would need to be there. This is the reg key on the 2007 server right?James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Correct. Before the 2007 migration, Outlook Anywhere was running on the 2003 box. I just don't want to blindly start removing links to the 2003 box and break something. That's why I'm so confused about why the "test exchange connectivity" test works when using the old Exchange 2003 server name. I'm wondering if it is acting as a front end and accessing mailboxes on the Exchange 2007 box. If I can't get this figured out soon, I may call Microsoft and open a support ticket. Thank youHere to learn

As far as the validports key did you manually enter all those values in including the 2003 server? I would remove the 2003, however if you're paranoid try this, instead of removing the 2003 entries, put the 2007 entries before the 2003 entries. Entries in the ValidPorts key must be an exact match of the RPC over HTTP server asked for by the client (it is not case-sensitive). To streamline processing, the RPC proxy does not perform canonicalization of the name provided by the RPC over HTTP client. Therefore, if the client asks for Rosco.microsoft.com, and in ValidPorts contain Rosco only, the RPC proxy will not match the names, even though both names may refer to the same machine. Additionally, if the IP address of Rosco is 66.77.88.99, and the client asks for 66.77.88.99 but the ValidPorts key contains Rosco only, the RPC proxy will refuse the connection. If a client may ask for the RPC over HTTP server by name, or by IP address, insert both in the ValidPorts key.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

95m3 Although I am having a problem with Outlook Anywhere right now, it DID work despite the ExRCA Outlook Anywhere error message. Otherwise, to format PS output this can help: Test-Outlookwebservices | ft -auto -wrap or Test-Outlookwebservices | fl

Ran test-outlookwebservices | ft -auto -wrap (thank you for the wrap command !!) Id Type Message -- ---- ------- 1003 Information About to test AutoDiscover with the e-mail address user@domain.com. 1007 Information Testing server server07.domain.com with the published name https://mail.domain.com/ews/exchange.asmx & https://mail.domain/ews/exchange.asmx. 1019 Information Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://mail.domain.com/autodiscover/autodiscover.xml. 1013 Error When contacting https://mail.domain.com/autodiscover/autodiscover.xml received the error The remote server returned an error: (401) Unauthorized. 1006 Error The Autodiscover service could not be contacted. Here to learn

Something else strange that is happening: When setting up a test Outlook Anywhere profile (outside), if I use the new server name, it give me an error and cannot resolve the username. If I enter the old server name and hit check name, it automatically changes the server name to the new 2007 server, and resolves the user name. I'm lost.Here to learn

DNS maybe? How do you have that setup? Transitioning from E2K3 to E2K10, there's a number of things to change at the name resolution level (all that "legacy" business) and that - or something comparable - may apply to E2K7.

Hello, The validport value is correct since it previously worked with the Exchange 2003 server so that the legacy server name is in the list. It will not cause confliction and the value only provide a access list of the MBX server which can be accessed by the CAS server. Due to the current situation, since the Outlook Anywhere works properly, I think we can safely ignore the error on the testoutlookconnectivity web site. Thanks, Simon

Thank you to everyone that helped with my issue. After working with a Microsoft tech, we did the following: From CMD> Ran netstat -ano > c:\netstat.txt The file showed [::] :6004 The fix: 1. Under the network adapter properties, uncheck IPv6. THEN: In Registry Editor, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ 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: a. In the Edit menu, point to New, and then click DWORD (32-bit) Value. b. Type DisabledComponents, and then press ENTER. c. Double-click DisabledComponents. 5. Type any one of the following values to configure the IPv6 protocol, and then click OK: a. Type 0xffffffff to disable all IPv6 components, except the IPv6 loopback interface. ** instead of typing 0xffffffff, you can just type "f" eight times and it will change to 0xffffffff. THEN: browse to: C:\windows\system32\drivers\etc and edit the "hosts" file in notepad Make the following changes: FROM: 127.0.0.1 localhost ::1 localhost TO: 127.0.0.1 localhost # ::1 localhost **comment out the IPv6 local host entry. IP Server07 IP Server07.domain.local REBOOT. Outlook Anywhere tests all passed from www.testoutlookconnectivity.com. Here to learn