Welcome to ISAserver.org

Web Publishing works for only 10 minutes???

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 Publishing] >> Web Publishing >> Web Publishing works for only 10 minutes???

Page: [1]

Message

<< Older Topic Newer Topic >>

Web Publishing works for only 10 minutes??? - 22.Feb.2007 5:09:04 AM

markstarmer

Posts: 5
Joined: 21.Feb.2007
Status: offline

Hello,

I've found that when I publish a web site it will work, but only stay up for 10 minutes, then ISA will stop listening on port 80 (I try a telnet, but it hangs), the EventLog gives a message saying that there is a problem with the specified server and another log saying that it has a problem connecting to the Domain Controller. Could this be causing the probelms?

Best Regards,

Mark Starmer

Post #: 1

Featured Links*

RE: Web Publishing works for only 10 minutes??? - 22.Feb.2007 6:42:31 AM

markstarmer

Posts: 5
Joined: 21.Feb.2007
Status: offline

I have since found the internal logging on ISA and it seems that somehow after a certain period of time the requests stop processing and ISA will give the following message

Rule:         Enterprise [Default Rule]
Message:    0xc004000d FWX_E_POLICY_RULES_DENIED
From:         External
To:             Local Host

But when I first apply settings to ISA it will work fine until I get a message in the Application Logs in ISA server, effectivly saying that it is rolling back the configuration due to an error, the message I get before this says that my rule that I created to allow port-80 bound traffic allows traffic in...

(in reply to markstarmer)

Post #: 2

RE: Web Publishing works for only 10 minutes??? - 22.Feb.2007 8:12:15 AM

markstarmer

Posts: 5
Joined: 21.Feb.2007
Status: offline

It seems like I managed to fix the problem, it turns out that our systems admin who installed the ISA server disabled the rule that allowed connection to the Domain Controller and the rule connecting to the Configuration Database and also setup a rule inside it that meant that it couldn't connect to the Local Host where the configuration services was residing. After changing this everything seems to now be working... (It has been up for about 40 minutes so far, so I'm still holding my braces)

Hopefully this is the end of my three day nightmare!

Cheers,

Mark Starmer

(in reply to markstarmer)

Post #: 3