Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Course Of The Month
Become a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Outlook Anywhere Exchange 2007 Fails to Configure Clients
Posted on 2010-11-24
We're trying to configure outlook anywhere for a client. Currently, exchange 2007 is configured to deliver over HTTP and firewall exceptions have been put in place for 25, 80, and 443 as required. The certificate is configured as well. Our test user can connect to OWA without issue, however when connecting to Outlook Anywhere from an outlook client, we're seeing issues.
heres the process i'm using, perhaps its wrong?
(using outlook 2007) i go to setup the account
setup for exchange, use the internal exchange server name (FQDN), select more options, under the connections tab, check the "Connect to Microsoft Exchange using HTTP" and configure the proxy to point to "remote.$SERVERNAME.org" when i check the name it prompts me for a username and password but will not authenticate.
any help would be appreciated.
heres the process i'm using, perhaps its wrong?
(using outlook 2007) i go to setup the account
setup for exchange, use the internal exchange server name (FQDN), select more options, under the connections tab, check the "Connect to Microsoft Exchange using HTTP" and configure the proxy to point to "remote.$SERVERNAME.org" when i check the name it prompts me for a username and password but will not authenticate.
any help would be appreciated.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
7-
5
2- +1
15 Comments
check that autodiscover.yourdomain.co
It should autoconfigure itself if these are correct.
Also, check this out. https://www.testexchangeconnectivity.com/
It should autoconfigure itself if these are correct.
Also, check this out. https://www.testexchangeconnectivity.com/
I noticed when setting up mine in Exchange 2010, which is quite similar, that at the user/password prompt, we had to use domain\user and pasword or it would not authenticate.
What I meant to say was put that in front of your name in the "Proxy servers with this principal name" box
Have you tried Basic authentication?
What about using the certificate's "Issued To" name as your proxy server URL?
What about using the certificate's "Issued To" name as your proxy server URL?
drpoppers,
thanks for the link, its been very helpful. it appears that the RPC over HTTP is failing to get a ping response from NSPI on port 6004. initially it looks like Microsoft had a problem using IPv6 internally between server 2008 and exchange 2007 which was resolved in SP1 RU4. however i have SP3 installed.
using netstat -apo|findstr i looked to ensure ports 6001,6002,6004 are being listened by the correct processes. but heres what i got
6001 by store.exe for both IPv4 and IPv6
6002 by mad.exe for both IPv4 and IPv6
6004 by mad.exe for both IPv4 and IPv6
note that this is not a DC so lsass.exe is not listening on 6004.
yet i'm still getting the NSPI failure on 6004. ideas?
thanks for the link, its been very helpful. it appears that the RPC over HTTP is failing to get a ping response from NSPI on port 6004. initially it looks like Microsoft had a problem using IPv6 internally between server 2008 and exchange 2007 which was resolved in SP1 RU4. however i have SP3 installed.
using netstat -apo|findstr i looked to ensure ports 6001,6002,6004 are being listened by the correct processes. but heres what i got
6001 by store.exe for both IPv4 and IPv6
6002 by mad.exe for both IPv4 and IPv6
6004 by mad.exe for both IPv4 and IPv6
note that this is not a DC so lsass.exe is not listening on 6004.
yet i'm still getting the NSPI failure on 6004. ideas?
meganuk3,
using "msstd:"in the proxy servers principal name wont work, the msstd: entry is for mutual authentication, which i'm not using here. additionally i'm currently using basic authentication.
using "msstd:"in the proxy servers principal name wont work, the msstd: entry is for mutual authentication, which i'm not using here. additionally i'm currently using basic authentication.
Is the cert "issued to" remote.$servername.org?
Has outlook anywhere ever worked? Have you tested it internally
Has outlook anywhere ever worked? Have you tested it internally
drpoppers,
the autodiscover is not working, it appears we forgot to add an 'A' record with the host for autodiscover.$SERVERNAME.o
meganuk3,
yes thats how the cert is issued. and no Outlook anywhere is a new feature we're setting up. the test fails internally as well at the same location, so i'm fairly confident the network layer is not at issue here.
i'll post back with results once the autodiscover 'A' record propagates. a colleague has informed me that outlook2007 needs the autodiscover features to function normally so perhaps this will help.
the autodiscover is not working, it appears we forgot to add an 'A' record with the host for autodiscover.$SERVERNAME.o
meganuk3,
yes thats how the cert is issued. and no Outlook anywhere is a new feature we're setting up. the test fails internally as well at the same location, so i'm fairly confident the network layer is not at issue here.
i'll post back with results once the autodiscover 'A' record propagates. a colleague has informed me that outlook2007 needs the autodiscover features to function normally so perhaps this will help.
Featured Post
Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
This article will help to fix the below error for MS Exchange server 2010
I. Out Of office not working
II. Certificate error "name on the security certificate is invalid or does not match the name of the site"
III. Make Internal URLs and External…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center.
Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center.
Navigate to the Servers >> Certificates…
CodeTwo Sync for iCloud (http://www.codetwo.com/sync-for-icloud?sts=6554) automatically synchronizes your Outlook 2016, 2013, 2010 or 2007 folders with iCloud folders available via iCloud Control Panel.
This lets you automatically sync them with…
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month6 days, 18 hours left to enroll
623 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.