3

We have some users who work remotely and they access their e-mail in Outlook 2003 using RPC over HTTP. We just hired another sales guy and the laptop we bought for him came with Office 2010, so I decided to give it a whirl. I set it up the same as I normally would for Outlook 2003 and sent him on his merry way. Now he's back home several thousand miles away and can't get to his e-mail. He is able to access his e-mail using Outlook Web Access.

Searching around on Google, lots of people were pointing to https://testexchangeconnectivity.com/ so I gave that a try. Most of the steps are successful, but it fails on "Attempting to ping RPC endpoint 6001 (Exchange Information Store)". I'd like to fix this, though I suspect fixing it may not automatically fix the outlook 2010 issue.

I checked the registry setting for ValidPorts, and it's configured correctly. I have ports 80, 443, and 6001-6004 being forwarded on the router to the Exchange server.

If Outlook 2010 just won't work with Exchange 2003, I can accept that, though trying to rectify it will be interesting because I don't expect this guy will be back in the office for a long time. Has anybody got Outlook 2010 working with Exchange 2003 using RPC over HTTP?

If you have a solution, or something you want me to do to help investigate the problem, please give specific steps. Exchange Server is slightly outside my area of expertise.

Community
  • 1
Scott
  • 1,173
  • 3
  • 13
  • 25
  • I do not know the answer to your issue but I am working with Outlook 2010 RPC/HTTP on exchange 2003. – pablo Feb 15 '11 at 20:26

3 Answers3

1

The Office 2010 user showed up in my office today, so I downgraded him to Outlook 2003.

Scott
  • 1,173
  • 3
  • 13
  • 25
0

Outlook 2010 works with Exchange 2003, that's 100% true. I have at least 3 clients environments working with this config. Please note, except ports 80 and 443 you don't need to open ANYTHING in the firewall. I can give you some advice on the matter and help in configuring the settings correctly. Where are you located?

Vick Vega
  • 2,398
  • 16
  • 22
  • 5
    For the benefit of the community, I'd prefer if you could explain on here what I should be checking. – Scott Feb 17 '11 at 20:13
0

I had the exact same problem, and finally solved it after a day and a half of investigation. The problem IS the ValidPorts registry key. You need to make sure it references the precise domain name that the mobile Outlook client uses to access it, it's very easy to overlook since the key is already populated with other names. Take a look at my answer and update accordingly.

If you pass the testexchangeconnectivity.com test, I'd appreciate stealing that green checkmark from you ;)

Community
  • 1
Bigbio2002
  • 2,763
  • 11
  • 34
  • 51
  • I double-checked ValidPorts and the port numbers are set up for both the internal AND external host names, so I don't think that's the solution to my problem. – Scott Nov 10 '11 at 17:17
  • Triple-check it. It took me about 5 times before I finally noticed what the problem was. Check to make sure the RPC proxy is configured correctly also. The testexchangeconnectivity.com results that you had indicate that the server can't proxy requests from the front-end to the back-end services, so the problem lies somewhere there. – Bigbio2002 Nov 10 '11 at 19:20