I have a question regarding Exchange 2010 and 2007 co-existance specifically with the autodiscover service. Environment consists of Exchange 2007 with all services enabled and working (autodiscover, OA, OWA, activesync, ews). The autodiscoverinternaluriparameter is set to https://webmail.domain.com/autodiscover/autodiscover.asmx We installed 2010, new certificates to enable all services 2007 had. With 2010, we bypassed ISA 2006 so our hardware load balancer routes traffic to our cas array. The autodiscoverinternaluriparameter on 2010 matches that of 2007. When I try to setup a 2010 mailbox outlook profile from a machine NOT on the domain, not on our VPN, autodiscover seems to find the mailbox and successfully set it up. When I try to set up a 2007 mailbox profile on the same machine, outlook hangs and does not create the profile. If I wait long enough, it states the exchange connection is not available, however, a window pops up with the name of the mailbox server, so it seems like autodiscover finds the name of the server but cannot log on. Autodiscover has the correct external and internal DNS records. We configured the legacy url for webmail, and redirection is working properly. We also tried configuring the autodiscoverinternaluri parameter to point to autodiscover.domain.com/.... But that seems to have the same result. Does anyone have any input as to what the issue could be? Testexchangeconnectivity.com also comes up clean with all services. We are pretty stumped at this point. Thank you.
UPDATE:
so testexchangeconnectivity is failing for rpc/http on 2007 mailbox. 2010 comes up clean! i did a telnet to that port on the mailbox server and the port is listening. any help is appreciated!
| Testing the Name Service Provider Interface (NSPI) on the Exchange Mailbox server. | |||||||||||||||
| An error occurred while testing the NSPI RPC endpoint. | |||||||||||||||
|
