After applying SP2 to ISA 2004, all Web Publishing rules which use Web Listener listening on Port 80 stop functioning. After removing SP2, everything starts working again.
I'm sure its a BUG. I'm just want to know if there is a fix already on the market for it?
I'm sure it's not a bug - I've got 8 production ISA 2004 systems with SP2 installed and using a port 80 listener with no problems. You'll have to diagnose the problem more...
As a Microsft Consultant, once one of my clients approved an update for Office 2000 from SUS. After that, when users open a new document on word, it crashes. The same update has been applied to other clients without problems.
Microsoft said it was a problems with a very specific environment. Solution? Reinstall office on all machines which had the problem (over 700!!!) and that's it!
When this kind of problem happens I cannot say anything else than Microsoft sucks. That's why I'm pretty confidence it's a bug with SP2 when ISA runs on "a very specific environment".
So due to a bug in Office, you make the incredible leap that any problem with your ISA Server is indeed a bug. That's... interesting.
It's not a very efficient way of troubleshooting problems, but that's just me. If it were me, before I posted something to a newsgroup claiming a problem with a piece of software was a bug, I'd want to investigate the logs of that piece of software (under the ISA console under Monitoring\Logging) to see if a specific rule is denying the request, or possibly take a network capture.
Office case was just an example... Other people have been posted here regarding the same problem I´ve got. Everything has been investigated, no Rule was denying the connection. It just showed an error while processing the Publishing Rule.
By the way, I uninstalled the SP2 and everything gets back online again.
We all know microsoft is trying to make their softwares better everyday. But their products still contains thousaund of bugs. Some of them has not been found yet.
I'm confidence this problem relies on a bad piece of SP2 code. I was wondering if there is any patch for this issue out on the market...
Let's be clear about this - the SP2 issue you're referring to doesn't cause all rules to stop functioning on port 80.
quote:
After applying SP2 to ISA 2004, all Web Publishing rules which use Web Listener listening on Port 80 stop functioning
But since you haven't chosen to investigate the problem further than "install SP2, hmm... things are broke, uninstall SP2, hmm things work now, SP2 is a buggy piece of crap software" we'll never know.
You're not requiring basic authentication over HTTP, are you? I believe the release notes say that's now blocked, as it should be. Credentials must be sent over HTTPS.
I have to applaud Microsoft over this decision (even if it's not the cause of your problem) because it shows they are prohibiting dangerous behavior by their clients by default.
Posts: 2187
Joined: 10.Aug.2004
From: fort frances.on.ca
Status: offline
We could try to guess what the problem is until the cows come home, but since Rodrigo chooses to trash MS rather than provide details, it is nothing but conjecture. I generally provide a reply that is commensurate to the detail.
When I saw the "BUG" word, I must confess that I started watching this thread like a sordid voyeur at a blood sport.
_____________________________
The School of Hard Knocks is a mean teacher. She gives the exam before the lesson.
It's good to hear from you that SP2 worked at most places. So, what i'm going to do is to deploy SP2 again in the next weekend than I'll get back here with the problems If I found any.
This way, I'm sure wverybody could help me, right?
Ligetfa, just one question, no offense at all, Have you ever read on Microsft KBs a phrase saying "Microsoft confirms it is a bug in the products mentioned above"? So, It is more usual than we ever think.
I too have installed ISA SP2 on dozens of systems and haven't had problems with publishing.
Pay special attention to the issue related to basic auth and non-secured connections. Create separate listeners for SSL and HTTP communications (that's an ISA firewall best practice).
I have the same problem. But I have only problems with the homepages with .asp code. My static .html pages do not have this problem. I have solved the problem by setting the option "All request should appear to come from ISA" instead of original host. I am not happy with this solution but it works.
In order to use the option "Requetss appear to come from the original client" the published web server must point to ISA as the default gateway. How is the web servers TCP/IP stack configured?
With you specifiying "Requests appear to come from the ISA Server", the published web server only needs to know how to get back to ISA, on it's local subnet most likely).
If someone (me!) has Kai's "multiple listeners on a single IP" trick working like a charm, would the installation of ISA 2K4 SP2 break the settings like you talk about here?
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [ISA Server 2004 General ] >> Web Publishing >> Service Pack 2 blows UP HTTP Publishing 
Service Pack 2 blows UP HTTP Publishing - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread