gopher_49
asked on
Outlook 2007 connecting via Outlook Anywhere - Exchange 2010 SP1
I'm having issues connecting an Outlook 2007 instance to my Exchange 2010 server.. I added my local exchange server name, I went to Outlook anywhere and filled in my OWA public DNS records, I put in msstd:smtp.mydomain.com in the use only SSL field.. I out in username@domain.com like I always do.. And.. It keeps on coming back for me to enter in the PW again.. I tested the exact same settings on Outlook 2010 and it works just fine. Both are not domain members and remote computer.. Outlook 2010 works perfectly..
Adam Brown
Have you configured Autodiscover for your environment yet? Using autodiscover greatly simplifies things.
ASKER
Yes.. But in this particular install I can't do autodiscovery for the email address being used has a local exchange server still present.. so, it will try to discovery via the local MX /host record which we don't want to mess with right now.. I need to manually setup Outlook 2007 profile for this particular install... So, what could be wrong?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
never mind.. I was wrong. still won't work.
ASKER
I was wrong.. Please take away the objection.. I want to re-open
When it prompts for password try this
Alter username from user@domain.com
To domain\username then enter password
"Tick remember password box "
Alter username from user@domain.com
To domain\username then enter password
"Tick remember password box "
Primary reason for connection failures is SSL certificate problems.
Do you have a trusted SSL certificate?
You said there is an existing Exchange server? What version of Exchange is it? Autodiscover isn't an optional thing, Outlook will try and use it, so the problem may well be that you have a confused client.
Simon.
Do you have a trusted SSL certificate?
You said there is an existing Exchange server? What version of Exchange is it? Autodiscover isn't an optional thing, Outlook will try and use it, so the problem may well be that you have a confused client.
Simon.
ASKER
Because I answered it.