WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!
Outlook Anywhere Exchange 2007 Fails to Configure Clients
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.
Asked:
7-
5
2- +1
2 Solutions
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.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
It should autoconfigure itself if these are correct.
Also, check this out. https://www.testexchangeconnectivity.com/