I have recently deployed a new Exchange 2007 environment for a client. I configured two users at this main location with Outlook Anywhere and successfully connected. They now have 5 additional users at a remote location that they want connected to the Exchange server to get them off of the ISP's POP accounts. My problem is that these folks do not have a VPN connection to the main location. How can I get Outlook 2007 configured for Outlook Anywhere and get them to resolve the server name and user name without first initiating a VPN connection? I know I was able to do this in an Exchange 2003 environment but have had no luck at all with the Exchange 2007 environment. A little background info would probably be helpful here. I have followed steps that found on numerous sites. When configuring the client I select the option to manually configure. I enter the server name and user name. Rather than clicking on "check name" I select "more settings". I click past the warning and then go to the connection tab and proceed to configure Outlook Anywhere. I use the same URL that is used for OWA (exchange.domainname.com), check the boxes for fast and slow networks, then select basic authentication. Once that is complete it takes me back to the server name/user name dialog box. I'm told that once I reach that point I should be able to click on "check name" and it will resolve....but it doesn't. I have tried all possible names for the server name. I used the external FQDN, the internal FQDN, and the netbios name. Autodiscover is working. I have the appropriate names (even autodiscover) on the certificate. I'm just not sure what I'm missing.In a 2007 environment (Exchange and Outlook) is it even possible to configure this remotely without a VPN connection? Like I said previously, I'm sure I was able to pull this off in the Exchange 2003 environment. Since we started deploying Exchange 2007 (some time ago) I have never been able to configure a remote user with Outlook Anywhere without utilizing a VPN connection....but now I have to.

Hi,This is also possible in Exchange 2007.What happens when you rightclick the Outlook icon and select test automatic configuration of e-mail?Leif

Absolutely nothing. I start Outlook. I'm prompted for a logon. I hold the ctrl key down and right click the Outlook icon. I then select the test for automatic configuration and it does nothing. What should I see?

Follow up to your question....the test of the automatic configuration does not start until after you log on to your Outlook Anywhere client. I have 5 or 6 profiles in Outlook. My work account (which is Outlook Anywhere and working great) and I also have a handful of other Outlook Anywhere profiles configured for other clients of mine. They all work great. If I select any of those profiles and successfully logon, then I can run the automatic configuration test. The problem I'm having is that this particular client (or Outlook profile) will not make that initial connection to the Exchange server to resolve the names. Therefore I cannot complete the configuration or successfully logon. IF they had a VPN, i'm confident that I could initiate a VPN connection and successfully create that initial connection. Once that initial connection is made and the server/user names are resolved, the VPN is no longer needed. BUT....no VPN is available in this scenario.

Hi, 1. I suggest you compare the configuration (More Settings->Connection tab->Exchange Proxy Settings) in internal Network Outlook client which can connect to Exchange successfully through Https with the external Outlook Clients which failed to check name. Note: For the internal Outlook Client, please right click Outlook icon and click Connection Status. Please ensure the Outlook connects to Exchange through HTTPS instead of TCP/IP 2. If the configuration of internal Outlook which connects to Exchange through HTTPS is completely same as external Outlook client, please ensure the external Outlook Client is able to resolve the URL specified in the Exchange Proxy Setting to correct IP Address. You can access following URL from external Outlook Client: https://exchange.domainname.com/rpc/rpcproxy.dll Note: I assume the exchange.domainname.com is external host name which you configured for Outlook Anywhere. You should not get any certificate related warning. You should get a blank page after authentication. Mike