Welcome to ISAserver.org

Internal Web Proxy clients cannot see internal web server

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Web Publishing >> Internal Web Proxy clients cannot see internal web server

Page: [1]

Message

<< Older Topic Newer Topic >>

Internal Web Proxy clients cannot see internal web server - 5.Nov.2006 12:24:00 AM

jimmyk

Posts: 37
Joined: 22.Sep.2006
Status: offline

Hello,
I have published an Internal web server to the Internet (external network). My internal clients cannot access this web server. When using IE, they get the following error message when trying to access the default page on the website. This error message is from the ISA server
Error Code 502 Proxy Error. The ISA Server denied the specified URL.
IP Address 10.0.0.1
Date: xxxxx
Server: isa.x.com
Source: proxy

I would not think this would happen because I configured the Internal Network' Web Browser tab to: Directly access computers in the Domains tab (which is includes the domain that both the web server and IE clients are on).
and I also added the same domain to the 'Directly access these servers or domains' box.

Note that when I deselected the web proxy from IE, I was able to access the internal website from internal clients.

Thanks!

Post #: 1

Featured Links*

RE: Internal Web Proxy clients cannot see internal web ... - 5.Nov.2006 7:50:05 AM

spouseele

Posts: 12830
Joined: 1.Jun.2001
From: Belgium
Status: offline

Hi jimmyk,

check out my blog Solving the "Directly access these servers or domains" issue in ISA Server 2004 SP2. Of course, be aware that configuring Direct Access on ISA only works if the Web Proxy clients (IE) use Automatic Configuration. That means, either 'Automatically detect settings' or 'Use automatic configuration script'.

For full details about Automatic Configuration, check out my article Understanding the Web Proxy and Firewall Client Automatic Configuration and related forum topic.

HTH,
Stefaan

(in reply to jimmyk)

Post #: 2

RE: Internal Web Proxy clients cannot see internal web ... - 6.Nov.2006 10:28:17 PM

jimmyk

Posts: 37
Joined: 22.Sep.2006
Status: offline

Thanks for the answer, but Darn! Does that mean I have read all that stuff just to allow internal web proxy clients to access an internal web server, while still using the ISA as a web proxy server?

What are those automatic configuration scripts supposed to do anyway?
Thanks

(in reply to spouseele)

Post #: 3

RE: Internal Web Proxy clients cannot see internal web ... - 6.Nov.2006 10:40:58 PM

jimmyk

Posts: 37
Joined: 22.Sep.2006
Status: offline

Pardon my frustration. Is it just me, or is the learning curve associated with ISA particularly steep? How does a sys admin have the time to learn all this stuff???

(in reply to jimmyk)

Post #: 4

RE: Internal Web Proxy clients cannot see internal web ... - 6.Nov.2006 11:02:42 PM

jimmyk

Posts: 37
Joined: 22.Sep.2006
Status: offline

Hello Spouseele,
I installed the Firewall Client on my pc. I used its "Enable Web Browser Automatic Configuration 'Configure Now' "button to automatically assign the following information to the IE client's 'Use Automatic Configuration Script Address: http://isa.domain.loc:8080/array.dll?Get.Routing.Script '

Should this script be adequate to allow the IE client to bypass the ISA when trying to access internal web servers? It doesn't seem to be working.

Thanks!

(in reply to jimmyk)

Post #: 5

RE: Internal Web Proxy clients cannot see internal web ... - 6.Nov.2006 11:05:44 PM

jimmyk

Posts: 37
Joined: 22.Sep.2006
Status: offline

I finally added an access list that allows 'All Internal to access ALL Internal' to get my internal IE clients to access an internal web server. But I know that is a bandaid, and isn't the proper method.

(in reply to jimmyk)

Post #: 6

RE: Internal Web Proxy clients cannot see internal web ... - 7.Nov.2006 2:42:21 PM

spouseele

Posts: 12830
Joined: 1.Jun.2001
From: Belgium
Status: offline

Hi jimmyk,

yes, you should read all them if you like to understand what you are doing!

This are the minimum configuration steps:

Internal network properties > tab Domains: make sure your internal domain is listed there.
Internal network properties > tab Web Browser: make sure your internal Network ID is listed there (same content as in the Internal network properties > tab Addresses).
Internal network properties > tab Auto Discovery: make sure that Publish automatic discovery information for this network is enabled.
Make sure IE is configured for Automatic Configuration, either Automatically detect settings or Use automatic configuration script.

HTH,
Stefaan

(in reply to jimmyk)

Post #: 7