Welcome to ISAserver.org

error 500 and proxy chain loop

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Web Publishing >> error 500 and proxy chain loop

Page: [1]

Message

<< Older Topic Newer Topic >>

error 500 and proxy chain loop - 2.Aug.2005 6:01:00 PM

yg_101

Posts: 8
Joined: 8.Jul.2005
Status: offline

Hi, I've got ISA Ent. array with two member servers and 4 networks attached to them. The ISA is behind PIX. I'm publishing 5 web sites (via HTTP and HTTPS) and OWA. All of the web sites are running on dual-node NLB cluster, and OWA is to a single Exchange server in the site. All of the web sites are located on one network (dedicated VIP's), Exchange on another.

Two of my web sites work OK (on https), the other 3, published on the same cluster, don't work at all - http or https (I get the 500 error). All the web sites and OWA work OK from the internal segments, but not via the published addresses from the Internet.

all of the rtfm'ing, recreating the rules (and the sites), checking every single config parameter I could find, didn't help. Any suggestions?
Thank you much,
Joe

P.S. I did try to change from the "requests appear to come from the original client" to the "requests appear to come from ISA" setting. In that case, instead of giving me error 500, it gives the error 12206, which is a proxy chain loop. any ideas on how to solve it?

Post #: 1

Featured Links*

RE: error 500 and proxy chain loop - 3.Aug.2005 8:52:00 AM

tshinder

Posts: 47490
Joined: 10.Jan.2001
From: Texas
Status: offline

Hi Yg,

If you want to use NLB, you must preserve the original client source address.

What are the exact details of the Web Publishing Rules that aren't working?

Thanks!
Tom

(in reply to yg_101)

Post #: 2

RE: error 500 and proxy chain loop - 4.Aug.2005 12:57:00 PM

yg_101

Posts: 8
Joined: 8.Jul.2005
Status: offline

Hi Tom, here're the details:

allow from anywhere ("external") to www.sitename.com

forward original host header

requests appear to come from the original client

protocols: HTTPS, HTTP

link translation - none

all users

bridging: web server: http - 80, ssl - 443, no certificate authentication to the ssl web server

path - same as internal /*

public name - a list of sites: www.sitename.com www.sitename1.com www.sitename2.com + ip address

listener properties: VIP on external interface, enable HTTP on 80, enable HTTPS on 443, certificate - www.sitename.com
authentication - basic and integrated (tried each one separately)
users not required to authenticate

are there any other parameters you'd be looking for?

thanks for your help

(in reply to yg_101)

Post #: 3

RE: error 500 and proxy chain loop - 18.Aug.2005 12:24:00 AM

Guest

I've been experiencing the same issues with ISA 2k on SBS 2k. While searching around I found this thread. It at least sounds helpful. I haven't tried it yet, but I'll post when I do.

http://www.tech-archive.net/Archive/ISA/microsoft.public.isa.publishing/2004-03/0036.html

(in reply to yg_101)

Post #: 4