?
Solved

Exchange 2007 Autodiscover works inside, not outside

Posted on 2009-04-30
4
Medium Priority
?
319 Views
Last Modified: 2012-05-06
Experts,

I am currently running both Exchange 2003 (1 server) and Exchange 2007 (1 server).  My internal domain is domain01.com and external domain.com.  Most of the users' mailboxes are still on the 03 box until the 07 has been tested and configured properly.

With a test user on the 07 box, I'm having trouble to get the Autodiscover working from outside.  Inside, it works ok without an issue.  

When trying to configure an Outlook 07 profile with Autodiscover from outside, I get the following error message.
"The action cannot be completed.  The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action.

I do have an A record for autodiscover.domain.com on my external DNS to point to my mail server.
I also have a SRV record on my external DNS -
Service: _autodiscover
Protocol: _tcp
Port Number: 443
Host: email.domain.com

I have ran the https://www.testexchangeconnectivity.com/ tool and it fails on the last step -
      Testing NSPI Interface on Exchange Mailbox Server
          An error occured while testing the NSPI Interface.
           Attempting to ping RPC Endpoint 6004 (NSPI Proxy Interface) on server PRO4IAEX02.pro4ia01.com
            Failed to ping Endpoint

Any ideas?  Thanks in advance!
0
Comment
Question by:Pro4ia
  • 2
  • 2
4 Comments
 
LVL 9

Expert Comment

by:esmith69
ID: 24272622
What version of Windows is running on the Exchange 2007 server?
0
 
LVL 4

Author Comment

by:Pro4ia
ID: 24272649
Server Enterprise 08 64bit
0
 
LVL 9

Accepted Solution

by:
esmith69 earned 2000 total points
ID: 24272719
Check out some of the suggestions in this thread, starting at the top of the page:

http://blog.aaronmarks.com/?p=65
0
 
LVL 4

Author Closing Comment

by:Pro4ia
ID: 31576641
Thanks.  That helped.  I wonder why internally I didn't have the issue.  I was hesitant on removing IPv6 at first but looks like there is no way around it right now.  Hopefully Microsoft will fix the bug in the future rollups.
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
Exchange administrators are always vigilant about Exchange crashes and disasters that are possible any time. It is quite essential to identify the symptoms of a possible Exchange issue and be prepared with a proper recovery plan. There are multiple…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses

862 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question