With the GDPR deadline set for May 25, 2018, many organizations are ill-prepared due to uncertainty about the criteria for compliance. According to a recent WatchGuard survey, a staggering 37% of respondents don't even know if their organization needs to comply with GDPR. Do you?
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/
Active 6 days ago
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
With the GDPR deadline set for May 25, 2018, many organizations are ill-prepared due to uncertainty about the criteria for compliance. According to a recent WatchGuard survey, a staggering 37% of respondents don't even know if their organization needs to comply with GDPR. Do you?
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 errors for MS Exchange Server 2013
I. Certificate error "name on the security certificate is invalid or does not match the name of the site"
II. Out of Office not working
III. Make Internal URLs and Externa…
By default Outlook 2016 displays only one time zone in the Calendar. The following article explains how to display two time zones in one calendar view.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.
Suggested Courses
Course of the Month11 days, 15 hours left to enroll
730 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.