I've mentioned this in passing in other posts but never really dedicated a
post to it:

When our server boots up there seems to be a problem with the boot order of
SBS. The problem manifests itself in a few ways but I think they are all
related. ISA spits out an alert about a server publishing rule configured
incorrectly and if I go to the default web site I have the 3 red X's on
public, Exchange, and Exadmin. A simple stop/start of the default website
clears it all up.

I'd rather it just took care of itself than having to stop/start it. Any
ideas?

Thank you!

The three X's are normal, the result of the order in which certain services
start. The X's are not related to the ISA issue. You can just ignore the
X's completely, since their appearance is the only symptom, and troubleshoot
the ISA error. Can you post the details of your publishing rule?


"IBC" <spamityspam@spam.spam> wrote in message
news:u2yZrFn9DHA.3436@tk2msftngp13.phx.gbl...
> I've mentioned this in passing in other posts but never really dedicated a
> post to it:
>
> When our server boots up there seems to be a problem with the boot order
of
> SBS. The problem manifests itself in a few ways but I think they are all
> related. ISA spits out an alert about a server publishing rule configured
> incorrectly and if I go to the default web site I have the 3 red X's on
> public, Exchange, and Exadmin. A simple stop/start of the default website
> clears it all up.
>
> I'd rather it just took care of itself than having to stop/start it. Any
> ideas?
>
> Thank you!
>
>

We have that error as well. I seem to remember it having something
to do with Exchange taking contol of those folder away from
IIS...but I don't remember specifics. There was a "fix," but it
didn't work for me. I'd like a find resolution as well. Even
though it doesn't really affect ops, I hat seeing errors...even if
they're fake.

"Dave Nickason [SBS MVP]" <gwdibble@NOSPAM.frontiernet.net> wrote
in news:e6tFWYn9DHA.2028@TK2MSFTNGP10.phx.gbl:

> The three X's are normal, the result of the order in which
> certain services start. The X's are not related to the ISA
> issue. You can just ignore the X's completely, since their
> appearance is the only symptom, and troubleshoot the ISA error.
> Can you post the details of your publishing rule?
>
>
> "IBC" <spamityspam@spam.spam> wrote in message
> news:u2yZrFn9DHA.3436@tk2msftngp13.phx.gbl...
>> I've mentioned this in passing in other posts but never really
>> dedicated a post to it:
>>
>> When our server boots up there seems to be a problem with the
>> boot order
> of
>> SBS. The problem manifests itself in a few ways but I think
>> they are all related. ISA spits out an alert about a server
>> publishing rule configured incorrectly and if I go to the
>> default web site I have the 3 red X's on public, Exchange, and
>> Exadmin. A simple stop/start of the default website clears it
>> all up.
>>
>> I'd rather it just took care of itself than having to
>> stop/start it. Any ideas?
>>
>> Thank you!
>>
>>
>
>

I'll post whatever you need, but what in particular are you interested in?
This was working before, but now its not. Works inside, but not out. The web
page error starts with:

The page cannot be displayed
The page you are looking for is currently unavailable. The Web site
might be experiencing technical difficulties, or you may need to adjust your
browser settings.



"Dave Nickason [SBS MVP]" <gwdibble@NOSPAM.frontiernet.net> wrote in message
news:e6tFWYn9DHA.2028@TK2MSFTNGP10.phx.gbl...
> The three X's are normal, the result of the order in which certain
services
> start. The X's are not related to the ISA issue. You can just ignore the
> X's completely, since their appearance is the only symptom, and
troubleshoot
> the ISA error. Can you post the details of your publishing rule?
>
>
> "IBC" <spamityspam@spam.spam> wrote in message
> news:u2yZrFn9DHA.3436@tk2msftngp13.phx.gbl...
> > I've mentioned this in passing in other posts but never really dedicated
a
> > post to it:
> >
> > When our server boots up there seems to be a problem with the boot order
> of
> > SBS. The problem manifests itself in a few ways but I think they are all
> > related. ISA spits out an alert about a server publishing rule
configured
> > incorrectly and if I go to the default web site I have the 3 red X's on
> > public, Exchange, and Exadmin. A simple stop/start of the default
website
> > clears it all up.
> >
> > I'd rather it just took care of itself than having to stop/start it. Any
> > ideas?
> >
> > Thank you!
> >
> >
>
>

Save following to a reg file and double-click on it.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W3SVC]
"DependOnService"=hex(7):49,00,49,00,53,00,41,00,4 4,00,4d,00,49,00,4e,00,00,
00,\

4d,00,53,00,45,00,78,00,63,00,68,00,61,00,6e,00,67 ,00,65,00,49,00,53,00,00,\
00,00,00



"IBC" <spamityspam@spam.spam> wrote in message
news:u2yZrFn9DHA.3436@tk2msftngp13.phx.gbl...
> I've mentioned this in passing in other posts but never really dedicated a
> post to it:
>
> When our server boots up there seems to be a problem with the boot order
of
> SBS. The problem manifests itself in a few ways but I think they are all
> related. ISA spits out an alert about a server publishing rule configured
> incorrectly and if I go to the default web site I have the 3 red X's on
> public, Exchange, and Exadmin. A simple stop/start of the default website
> clears it all up.
>
> I'd rather it just took care of itself than having to stop/start it. Any
> ideas?
>
> Thank you!
>
>

OK, thanks for this information. Unfortunately I have a few problems:

1. I'm a paranoid nutball, and since I can't tell just by looking at that
code what exactly its doing, I'm inclined to NOT put it on my server without
some additional thumbs up from an MVP or 2. Its fairly apparent from the
question and the code that its causing the services to start in a certain
order, but I have no idea what those HEX codes point to or do.
2. I have no idea how to create a Reg. file and prefer not to learn on my
production server. Overwhelming faith in my own abilities, wouldn't you say?

Dave,

I'm still not sure what in particular to post since there is hardly any
information at all, but the rule for Server publishing is as follows:


Enabled
IP of internal Server: 10.0.0.10
IP of External NIC: 1923168.1.101
Mapped Server Protocol HTTPS
Applies to: Any Request.

Thanks!

"Daryl Maunder" <dmaunder.nospam@midnightoil.nospam.com.nospam.a u> wrote in
message news:ekgv85q9DHA.2480@TK2MSFTNGP10.phx.gbl...
> Save following to a reg file and double-click on it.
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W3SVC]
>
"DependOnService"=hex(7):49,00,49,00,53,00,41,00,4 4,00,4d,00,49,00,4e,00,00,
> 00,\
>
>
4d,00,53,00,45,00,78,00,63,00,68,00,61,00,6e,00,67 ,00,65,00,49,00,53,00,00,\
> 00,00,00
>
>
>
> "IBC" <spamityspam@spam.spam> wrote in message
> news:u2yZrFn9DHA.3436@tk2msftngp13.phx.gbl...
> > I've mentioned this in passing in other posts but never really dedicated
a
> > post to it:
> >
> > When our server boots up there seems to be a problem with the boot order
> of
> > SBS. The problem manifests itself in a few ways but I think they are all
> > related. ISA spits out an alert about a server publishing rule
configured
> > incorrectly and if I go to the default web site I have the 3 red X's on
> > public, Exchange, and Exadmin. A simple stop/start of the default
website
> > clears it all up.
> >
> > I'd rather it just took care of itself than having to stop/start it. Any
> > ideas?
> >
> > Thank you!
> >
> >
>
>

Go [url]http://www.smallbizserver.net/DesktopDefault.aspx?tabid=69[/url] Second error
line down. You can download the reg file here. Explanation available here
also.

Dirk-Thomas

"IBC" <spamityspam@spam.spam> wrote in message
news:O$kCfyw9DHA.548@TK2MSFTNGP11.phx.gbl...
> OK, thanks for this information. Unfortunately I have a few problems:
>
> 1. I'm a paranoid nutball, and since I can't tell just by looking at that
> code what exactly its doing, I'm inclined to NOT put it on my server
without
> some additional thumbs up from an MVP or 2. Its fairly apparent from the
> question and the code that its causing the services to start in a certain
> order, but I have no idea what those HEX codes point to or do.
> 2. I have no idea how to create a Reg. file and prefer not to learn on my
> production server. Overwhelming faith in my own abilities, wouldn't you
say?
>
> Dave,
>
> I'm still not sure what in particular to post since there is hardly any
> information at all, but the rule for Server publishing is as follows:
>
>
> Enabled
> IP of internal Server: 10.0.0.10
> IP of External NIC: 1923168.1.101
> Mapped Server Protocol HTTPS
> Applies to: Any Request.
>
> Thanks!
>
> "Daryl Maunder" <dmaunder.nospam@midnightoil.nospam.com.nospam.a u> wrote
in
> message news:ekgv85q9DHA.2480@TK2MSFTNGP10.phx.gbl...
> > Save following to a reg file and double-click on it.
> >
> > Windows Registry Editor Version 5.00
> >
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W3SVC]
> >
>
"DependOnService"=hex(7):49,00,49,00,53,00,41,00,4 4,00,4d,00,49,00,4e,00,00,
> > 00,\
> >
> >
>
4d,00,53,00,45,00,78,00,63,00,68,00,61,00,6e,00,67 ,00,65,00,49,00,53,00,00,\
> > 00,00,00
> >
> >
> >
> > "IBC" <spamityspam@spam.spam> wrote in message
> > news:u2yZrFn9DHA.3436@tk2msftngp13.phx.gbl...
> > > I've mentioned this in passing in other posts but never really
dedicated
> a
> > > post to it:
> > >
> > > When our server boots up there seems to be a problem with the boot
order
> > of
> > > SBS. The problem manifests itself in a few ways but I think they are
all
> > > related. ISA spits out an alert about a server publishing rule
> configured
> > > incorrectly and if I go to the default web site I have the 3 red X's
on
> > > public, Exchange, and Exadmin. A simple stop/start of the default
> website
> > > clears it all up.
> > >
> > > I'd rather it just took care of itself than having to stop/start it.
Any
> > > ideas?
> > >
> > > Thank you!
> > >
> > >
> >
> >
>
>

So you're publishing a web site to the Internet with HTTPS, and the
publishing rule previously worked? If you didn't change anything, I'm
wondering if a security patch or something caused this. 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). How about if you delete and recreate the
rule?

What's the source and event ID of the error? Have you tried searching them
at support.microsoft.com?

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.

I'm pretty sure the info Dirk-Thomas refers you to was written by Steve
Foster and will work fine.

"IBC" <spamityspam@spam.spam> wrote in message
news:O$kCfyw9DHA.548@TK2MSFTNGP11.phx.gbl...
> OK, thanks for this information. Unfortunately I have a few problems:
>
> 1. I'm a paranoid nutball, and since I can't tell just by looking at that
> code what exactly its doing, I'm inclined to NOT put it on my server
without
> some additional thumbs up from an MVP or 2. Its fairly apparent from the
> question and the code that its causing the services to start in a certain
> order, but I have no idea what those HEX codes point to or do.
> 2. I have no idea how to create a Reg. file and prefer not to learn on my
> production server. Overwhelming faith in my own abilities, wouldn't you
say?
>
> Dave,
>
> I'm still not sure what in particular to post since there is hardly any
> information at all, but the rule for Server publishing is as follows:
>
>
> Enabled
> IP of internal Server: 10.0.0.10
> IP of External NIC: 1923168.1.101
> Mapped Server Protocol HTTPS
> Applies to: Any Request.
>
> Thanks!
>
> "Daryl Maunder" <dmaunder.nospam@midnightoil.nospam.com.nospam.a u> wrote
in
> message news:ekgv85q9DHA.2480@TK2MSFTNGP10.phx.gbl...
> > Save following to a reg file and double-click on it.
> >
> > Windows Registry Editor Version 5.00
> >
> > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W3SVC]
> >
>
"DependOnService"=hex(7):49,00,49,00,53,00,41,00,4 4,00,4d,00,49,00,4e,00,00,
> > 00,\
> >
> >
>
4d,00,53,00,45,00,78,00,63,00,68,00,61,00,6e,00,67 ,00,65,00,49,00,53,00,00,\
> > 00,00,00
> >
> >
> >
> > "IBC" <spamityspam@spam.spam> wrote in message
> > news:u2yZrFn9DHA.3436@tk2msftngp13.phx.gbl...
> > > I've mentioned this in passing in other posts but never really
dedicated
> a
> > > post to it:
> > >
> > > When our server boots up there seems to be a problem with the boot
order
> > of
> > > SBS. The problem manifests itself in a few ways but I think they are
all
> > > related. ISA spits out an alert about a server publishing rule
> configured
> > > incorrectly and if I go to the default web site I have the 3 red X's
on
> > > public, Exchange, and Exadmin. A simple stop/start of the default
> website
> > > clears it all up.
> > >
> > > I'd rather it just took care of itself than having to stop/start it.
Any
> > > ideas?
> > >
> > > Thank you!
> > >
> > >
> >
> >
>
>

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 the
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!!!

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!!!
>
>
>

actually, at the moment it appears that the .reg file is not available from
Mariette's site. I wonder if this has anything to do with the fact that
implementing the dependency change has a habit of breaking the ICW?

--
Mick Malloy
[url]http://www.micropol.com.au[/url]

"Dirk-Thomas Brown" <youhadtoask@hotmail.com> wrote in message
news:eTapeBx9DHA.3452@TK2MSFTNGP09.phx.gbl...
> Go [url]http://www.smallbizserver.net/DesktopDefault.aspx?tabid=69[/url] Second error
> line down. You can download the reg file here. Explanation available here
> also.
>
> Dirk-Thomas
>
> "IBC" <spamityspam@spam.spam> wrote in message
> news:O$kCfyw9DHA.548@TK2MSFTNGP11.phx.gbl...
> > OK, thanks for this information. Unfortunately I have a few problems:
> >
> > 1. I'm a paranoid nutball, and since I can't tell just by looking at
that
> > code what exactly its doing, I'm inclined to NOT put it on my server
> without
> > some additional thumbs up from an MVP or 2. Its fairly apparent from the
> > question and the code that its causing the services to start in a
certain
> > order, but I have no idea what those HEX codes point to or do.
> > 2. I have no idea how to create a Reg. file and prefer not to learn on
my
> > production server. Overwhelming faith in my own abilities, wouldn't you
> say?
> >
> > Dave,
> >
> > I'm still not sure what in particular to post since there is hardly any
> > information at all, but the rule for Server publishing is as follows:
> >
> >
> > Enabled
> > IP of internal Server: 10.0.0.10
> > IP of External NIC: 1923168.1.101
> > Mapped Server Protocol HTTPS
> > Applies to: Any Request.
> >
> > Thanks!
> >
> > "Daryl Maunder" <dmaunder.nospam@midnightoil.nospam.com.nospam.a u> wrote
> in
> > message news:ekgv85q9DHA.2480@TK2MSFTNGP10.phx.gbl...
> > > Save following to a reg file and double-click on it.
> > >
> > > Windows Registry Editor Version 5.00
> > >
> > > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W3SVC]
> > >
> >
>
"DependOnService"=hex(7):49,00,49,00,53,00,41,00,4 4,00,4d,00,49,00,4e,00,00,
> > > 00,\
> > >
> > >
> >
>
4d,00,53,00,45,00,78,00,63,00,68,00,61,00,6e,00,67 ,00,65,00,49,00,53,00,00,\
> > > 00,00,00
> > >
> > >
> > >
> > > "IBC" <spamityspam@spam.spam> wrote in message
> > > news:u2yZrFn9DHA.3436@tk2msftngp13.phx.gbl...
> > > > I've mentioned this in passing in other posts but never really
> dedicated
> > a
> > > > post to it:
> > > >
> > > > When our server boots up there seems to be a problem with the boot
> order
> > > of
> > > > SBS. The problem manifests itself in a few ways but I think they are
> all
> > > > related. ISA spits out an alert about a server publishing rule
> > configured
> > > > incorrectly and if I go to the default web site I have the 3 red X's
> on
> > > > public, Exchange, and Exadmin. A simple stop/start of the default
> > website
> > > > clears it all up.
> > > >
> > > > I'd rather it just took care of itself than having to stop/start it.
> Any
> > > > ideas?
> > > >
> > > > Thank you!
> > > >
> > > >
> > >
> > >
> >
> >
>
>

I think I'm just fine with lil stop signs for now....as long as everything
is working other than the pretty pictures, I'm fine.

Thanks for the heads up!

"SuperGumby [SBS MVP]" <not@your.nellie> wrote in message
news:ujlKfKy9DHA.2392@TK2MSFTNGP11.phx.gbl...
> actually, at the moment it appears that the .reg file is not available
from
> Mariette's site. I wonder if this has anything to do with the fact that
> implementing the dependency change has a habit of breaking the ICW?
>
> --
> Mick Malloy
> [url]http://www.micropol.com.au[/url]
>
> "Dirk-Thomas Brown" <youhadtoask@hotmail.com> wrote in message
> news:eTapeBx9DHA.3452@TK2MSFTNGP09.phx.gbl...
> > Go [url]http://www.smallbizserver.net/DesktopDefault.aspx?tabid=69[/url] Second
error
> > line down. You can download the reg file here. Explanation available
here
> > also.
> >
> > Dirk-Thomas
> >
> > "IBC" <spamityspam@spam.spam> wrote in message
> > news:O$kCfyw9DHA.548@TK2MSFTNGP11.phx.gbl...
> > > OK, thanks for this information. Unfortunately I have a few problems:
> > >
> > > 1. I'm a paranoid nutball, and since I can't tell just by looking at
> that
> > > code what exactly its doing, I'm inclined to NOT put it on my server
> > without
> > > some additional thumbs up from an MVP or 2. Its fairly apparent from
the
> > > question and the code that its causing the services to start in a
> certain
> > > order, but I have no idea what those HEX codes point to or do.
> > > 2. I have no idea how to create a Reg. file and prefer not to learn on
> my
> > > production server. Overwhelming faith in my own abilities, wouldn't
you
> > say?
> > >
> > > Dave,
> > >
> > > I'm still not sure what in particular to post since there is hardly
any
> > > information at all, but the rule for Server publishing is as follows:
> > >
> > >
> > > Enabled
> > > IP of internal Server: 10.0.0.10
> > > IP of External NIC: 1923168.1.101
> > > Mapped Server Protocol HTTPS
> > > Applies to: Any Request.
> > >
> > > Thanks!
> > >
> > > "Daryl Maunder" <dmaunder.nospam@midnightoil.nospam.com.nospam.a u>
wrote
> > in
> > > message news:ekgv85q9DHA.2480@TK2MSFTNGP10.phx.gbl...
> > > > Save following to a reg file and double-click on it.
> > > >
> > > > Windows Registry Editor Version 5.00
> > > >
> > > > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W3SVC]
> > > >
> > >
> >
>
"DependOnService"=hex(7):49,00,49,00,53,00,41,00,4 4,00,4d,00,49,00,4e,00,00,
> > > > 00,\
> > > >
> > > >
> > >
> >
>
4d,00,53,00,45,00,78,00,63,00,68,00,61,00,6e,00,67 ,00,65,00,49,00,53,00,00,\
> > > > 00,00,00
> > > >
> > > >
> > > >
> > > > "IBC" <spamityspam@spam.spam> wrote in message
> > > > news:u2yZrFn9DHA.3436@tk2msftngp13.phx.gbl...
> > > > > I've mentioned this in passing in other posts but never really
> > dedicated
> > > a
> > > > > post to it:
> > > > >
> > > > > When our server boots up there seems to be a problem with the boot
> > order
> > > > of
> > > > > SBS. The problem manifests itself in a few ways but I think they
are
> > all
> > > > > related. ISA spits out an alert about a server publishing rule
> > > configured
> > > > > incorrectly and if I go to the default web site I have the 3 red
X's
> > on
> > > > > public, Exchange, and Exadmin. A simple stop/start of the default
> > > website
> > > > > clears it all up.
> > > > >
> > > > > I'd rather it just took care of itself than having to stop/start
it.
> > Any
> > > > > ideas?
> > > > >
> > > > > Thank you!
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

OK, here's the update:

If I stop/restart the IIS Admin Service it brings OWA back up, but it
appears my certificate is no longer my certificate. Its Issued from "web11".
I didn't proceed until I find out whats going on with that certificate.

Sound like trouble to me, but I'm trying to get to it from inside...maybe
thats throwing a wrench into it.

OK, had somebody run a check from the outside and it looks good. So now the
question is what is wrong with the publishing rule that causes this to fail
until I restart IIS Admin?


"Dave Nickason [SBS MVP]" <gwdibble@NOSPAM.frontiernet.net> wrote in message
news:uW#Og7x9DHA.1128@tk2msftngp13.phx.gbl...
> 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!!!
> >
> >
> >
>
>