Welcome to ISAserver.org

Simple HTTP Web Publishing issue

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Web Publishing >> Simple HTTP Web Publishing issue

Page: [1]

Message

<< Older Topic Newer Topic >>

Simple HTTP Web Publishing issue - 28.Sep.2007 4:07:16 PM

dougm

Posts: 8
Joined: 17.Apr.2003
Status: offline

To Whom It May Concern,

We are experiencing a very strange problem and require some insight. We have multiple IP's assigned to an external interface and have created an HTTP web listener that is assigned to a specific external IP (listen on IP .....). We then created a rule (using the web publishing wizard) to use that listener and point to an internal web server. The problem seems to be that instead of displaying the web site sitting on the internal server (configured in the rule), it is pointing to the Firewall IIS website. It is like it is ignoring the rule to forward to the internal server - what gives? We have other rules created that utilize the same thing over HTTPS and everthing works okay.

Any ideas?

Feeling Stupid...

Doug

Post #: 1

Featured Links*

RE: Simple HTTP Web Publishing issue - 1.Oct.2007 2:45:18 PM

Rotorblade

Posts: 1002
Joined: 27.Feb.2007
Status: offline

Doug,

quote:

The problem seems to be that instead of displaying the web site sitting on the internal server (configured in the rule), it is pointing to the Firewall IIS website.

Is IIS installed on the ISA server?

If so, what port is it assigned?

How is DNS configured on ISA? (NIC Config's)

Rule order?

RB

(in reply to dougm)

Post #: 2

RE: Simple HTTP Web Publishing issue - 2.Oct.2007 12:00:22 PM

dougm

Posts: 8
Joined: 17.Apr.2003
Status: offline

RB,

Yes, IIS is installed on the ISA server and I did try the following:

Changed the ISA IIS port to 81 then try the listener and when I do that, instead of getting the ISA firewall IIS page, I get "page not found". I didn't try removing IIS altogether but did read on another post that removing IIS will allow the listener to kick in. That doesn't make sense though because the same should apply by changing the IIS port to 81??

Any thoughts?

For DNS we have the following config:

Perimeter: Firewall is joined to our Perimeter Domain and using its DNS
Corporate: no DNS but external domain is using forwarding to this networks DNS
Public: Using ISP DNS

Thanks
Doug

(in reply to Rotorblade)

Post #: 3

RE: Simple HTTP Web Publishing issue - 3.Oct.2007 8:30:21 AM

enricoklein

Posts: 49
Joined: 8.Mar.2005
From: netherlands
Status: offline

Hi Doug,

the best way would indeed be to remove IIS from the ISA server.
Another solution could be to disable socket pooling on IIS (http://support.microsoft.com/kb/888650/en-us)

tip: you can check which process uses port 80 by running "netstat -abn | find ":80" | find /i "listening" from a command line
This gives you the process ID in the most right column, then just check taskmanager for the corresponding process or run "tasklist /FI "PID eq <pidnumber>"

Regards,
Enrico

(in reply to dougm)

Post #: 4