This seems likely to be related to the ISA error about the server publishing
rule, so I'd figure that out first. If recreating the rule doesn't help,
I'd search support.microsoft.com for the relevant text from the error
message.

The red X's don't effect the operation of anything as far as I've ever seen.
I used to be in the camp where everything had to work error-free. Now, with
the exception of security and performance issues, I'm on the side of not
fixing things that don't need to be fixed. A classic example of this is one
time I upgraded our accounting software for no reason other than that a free
upgrade was available. Come to find out a bug in the new program prevented
printing to certain printers, which was a giant hassle for the two weeks it
took them to fix it. I don't make those mistakes any more - to paraphrase
Mariette and Marina, if it ain't broke, don't fix it.

"IBC" <spamityspam@spam.spam> wrote in message
news:eeIgqwx9DHA.888@tk2msftngp13.phx.gbl...
> In line:
>
>
> > So you're publishing a web site to the Internet with HTTPS, and the
> > publishing rule previously worked?
>
> Yes.
>
> > If you didn't change anything, I'm
> > wondering if a security patch or something caused this.
>
> I don't know exactly when it broke, but I'm fairly positive the only patch
> added since it last worked is our beloved 828028. I haven't heard anybody
> else have problems with OWA though, so I'm inclined to pray thats not it.
>
> >When viewing the
> > rule in ISA mgr. all the settings look OK? (Your external IP is wrong
> below
> > but I'm asuming that's a typo).
>
> Rypo...er....Tupo....uh....yeah. 192.168.1.101
>
> > How about if you delete and recreate the
> > rule?
> >
>
> I'll try that.
>
> > What's the source and event ID of the error? Have you tried searching
> them
> > at support.microsoft.com?
> >
>
> There are no error in the event log, you can't even get tot the site. It
> works on the inside, but if you try to hit it from the outside it gives t
he
> message I posted in an above thread.
>
> > REG files are just text files configured to insert (or delete) certain
> info
> > in the registry. If you open a registry editor and export a key, then
> open
> > that file in notepad, you'll see an example. If you dbl-click a .reg
> file,
> > it'll install the code in the registry, so you should rename them .txt
if
> > that's not your goal. You're right to be cautious about these files
since
> a
> > typo or other problem can leave you in a mess. Always have a backup or
> > system restore point for these.
> >
>
> Ah. That makes sense. Usually if I'm FORCED to do a regedit, I did it by
> hand. One of the few things I still try to keep my fingers out of since I
> know what a catastrophe it can end up being.....
>
> > I'm pretty sure the info Dirk-Thomas refers you to was written by Steve
> > Foster and will work fine.
> >
>
> From the little I've read, does the default web site actually start then
> without fixing this or do you need to stop/restart to get that going? Our
> default website is accessible via https, but it redirects back out to our
> normal site. I use it to troubleshoot, if I can get to
[url]https://mydomain.com[/url]
> but not [url]https://mydomain.com/exchange[/url] then I know I have an OWA problem.
>
> Is it worth 'patching' this?
>
> Thank again!!!
>
>
>