Solved

Bypass ISA proxy for Outlook Anywhere

Posted on 2014-10-24
8
359 Views
Last Modified: 2014-11-04
Have a network using ISA 2004 as a web proxy.  This is shortly to be removed.

In the meantime, the client has been migrated to a hosted Exchange service and ISA is blocking Outlook Anywhere connections.  I understand that ISA breaks the RPC-over-https protocol and needs to be bypassed, but how is this done?

I have removed the web proxy filter for all HTTPS but still not working
0
Comment
Question by:devon-lad
  • 4
  • 3
8 Comments
 
LVL 6

Expert Comment

by:Flora
ID: 40401253
0
 
LVL 1

Author Comment

by:devon-lad
ID: 40401274
I think this is related to external clients and in-house Exchange.  Our situation is the other way round.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40403184
It may not be an ISA issue at all. It could be DNS related. Do you have any DNS records that are referencing autodiscover and pointing it to the ISA or the old Exchange server directly? Could be A, SRV or even an SCP. If not, may also need to create one if using split-DNS to point to the hosting service. Basically clients may be defaulted to an old internal environment.
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 1

Author Comment

by:devon-lad
ID: 40406079
Gareth,

You may well be right.  We'd been having a lot of account lockout issues which were SCP related.  An I've just realised the test machines setup to bypass the proxy are using external DNS.  The red herring is that one internal machine using internal DNS does not have a problem.

Going to remove Exchange today, so will see if that solves it.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40406848
Awesome. That will likely be the final fix.
0
 
LVL 1

Accepted Solution

by:
devon-lad earned 0 total points
ID: 40412829
Turns out it was proxy settings being applied by a group policy to most but not all workstations.

They have the same internal and external domain name and most of the workstations were set to bypass the proxy for all traffic to *.companydomain.com.  Changed this to the specific internal web hosts used and Outlook started working.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40414562
Awesome. Be sure to accept your own comment as the solution.
0
 
LVL 1

Author Closing Comment

by:devon-lad
ID: 40421143
Found own solution
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create an Address List 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 Organization >> Ad…
how to add IIS SMTP to handle application/Scanner relays into office 365.

820 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question