• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 312
  • Last Modified:

Exchange 2007- outlook anywhere

I have configured exchange 2007 outlook anywhere.  If I connect a laptop to exchange 2007 and configure the mailbox, I can then go out of the network, and connect using outlook anywhere.  If I have not already configured the mailbox inside the network, and resolved the mailbox name, then I cannot connect to the mailbox using outlook anywhere.

Essentially, when setting up a new connection to exchange using oultook anywhere from outside the network, it does not resolve the mailbox.  Any ideas, please.
0
jfeucht
Asked:
jfeucht
  • 7
  • 6
1 Solution
 
MesthaCommented:
The first thing I would suggest is use a test account with the Microsoft test site and see whether that flags anything:
https://www.testexchangeconnectivity.com

Simon.
0
 
jfeuchtAuthor Commented:
that has been a very useful site.  It was very helpful in illuminating the problems, but not so good at providing solution.  However, its an excellent tool..  You definitely get some points when this case is closed.

My current situatino is this:  I have a cert installed that I generated with the following:

New-ExchangeCertificate -GenerateRequest -Path c:\mail_xxxx_com.csr -KeySize 2048 -SubjectName "c=US, s=Texas, l=Houston, o=xxxxx Industries Inc, ou=Information Technology, cn=mail.xxxxxx.com" -DomainName houcorpexch01.yyyyyy.corp, autodiscover.yyyyyy.corp, mail.xxxxx.com, yyyyy.corp, autodiscover.xxxxxxx.com -PrivateKeyExportable $True

where xxxxx is the public name and yyyyy is the internal name

Inside the network, I can configure mail account, and then take it outside the network and connect via outlook anywhere.  I take it outside the network, and remove the profile.  Then when trying to create the profile over outlook anywhere, it fails.
0
 
MesthaCommented:
Starting with the obvious - does autodiscover.example.com resolve externally correctly?
How far did the test site get? Which element did it fail on?

Simon.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
jfeuchtAuthor Commented:
yes autodiscover resolves as it should.  I created an external dns record to ensure that it does.
0
 
MesthaCommented:
So which element did the autodiscover test fail on?

Simon.
0
 
jfeuchtAuthor Commented:
it fails in a few places, but I expect these failures to happen, since the current messaging environment is a hosted exchange provider, and thus dns records point to their MX records.

its a mess
0
 
MesthaCommented:
From memory, autodiscovery process goes

example.com/autodiscover
autodiscover.example.com
mail.example.com/autodiscover

Therefore to get one or two failures is expected.
Where the MX records point shouldn't be a problem, as autodiscover doesn't use the MX records to my knowledge.

However one of the above three should be accepted and then a connect attempt made, which may then fail at a latter step.

Simon.

0
 
jfeuchtAuthor Commented:
I did some testing w/ rpcdiag, and found the following:

all connections of type "directory" have a status of connecting.  They never become "established".  After a few minutes, the attempts time out, and they become "disconnected".

Any help?
0
 
MesthaCommented:
Is that inside or outside the network?

Simon.
0
 
jfeuchtAuthor Commented:
outside.     Inside works fine, but its using tcp/ip.  I can't seem to force to https to test https.
0
 
jfeuchtAuthor Commented:
more...........rpcping to 6001 succeeds, 6002 succeeds, 6004 FAILS
0
 
MesthaCommented:
If Outlook Anywhere is configured by autodiscover then it will always use TCP/IP inside, as that is the preferred connection method. If you look at the Outlook Anywhere configuration in Outlook you will see that it sets only the "on slow connections", which basically means it falls back to HTTP, rather than using it from the start.

Have you tried resetting the Outlook Anywhere configuration?

Disable Outlook Anywhere
Wait 20 minutes
Remove the RPC Proxy component from Windows Components.
Then in IIS manager remove the RPC and RPC-WITH-CERT virtual directories and then run IISRESET to write the change to the IIS metabase.
Reinstall the RPC Proxy component from Windows Components
Finally enable Outlook Anywhere in Exchange 2007 again, and wait 20 minutes before testing again.

Simon.
0
 
jfeuchtAuthor Commented:
thanks for sticking with me.  In the end, it was disableing of IPv6 and modifying the hosts file that fixed the issue.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now