sbs2000 - roll back

Is there any way of rolling back sbs2000 to a previous
working configuration. We had somebody in working on our
systems who changed a few bits in ISA - now if we try to
use OWA all we get is error 12206 - Proxy chain loop. Any
help greatfully received.

Marina
Wed Jul 30 18:26:30 CDT 2003

Have you tried rerunning the ICW-wizard? Make sure you check that it will
change the ISA-configuration.
ISA will return to its defaults.

Marina

"Hans" <Hansd@nospam.the-beaches.co.uk> schreef in bericht
news:52fc01c356ee$ea34cd40$a001280a@phx.gbl...
> Is there any way of rolling back sbs2000 to a previous
> working configuration. We had somebody in working on our
> systems who changed a few bits in ISA - now if we try to
> use OWA all we get is error 12206 - Proxy chain loop. Any
> help greatfully received.

Jeff
Wed Jul 30 23:07:20 CDT 2003

Marina has a wise suggestion. Rollback on a domain controller is a pretty
broad idea, its a system state restore. Your problem is probably pretty
trivial.


"Marina Roos" <marina@roos.nodontwantspam.nl.com> wrote in message
news:GuYVa.87581$506.77884@typhoon.bart.nl...
> Have you tried rerunning the ICW-wizard? Make sure you check that it will
> change the ISA-configuration.
> ISA will return to its defaults.
>
> Marina
>
> "Hans" <Hansd@nospam.the-beaches.co.uk> schreef in bericht
> news:52fc01c356ee$ea34cd40$a001280a@phx.gbl...
> > Is there any way of rolling back sbs2000 to a previous
> > working configuration. We had somebody in working on our
> > systems who changed a few bits in ISA - now if we try to
> > use OWA all we get is error 12206 - Proxy chain loop. Any
> > help greatfully received.
>
>

danabeckonline
Thu Jul 31 13:52:20 CDT 2003

Hello Hans,

As pointed out previously, the first thing to do is to run the Internet
Connection Wizard and make sure you have the appropriate packet filters
enabled. Please note that if you have any custom packet filters that they
will be disabled. (not deleted)

If running the ICW does not fix the issue, there are a few things that
commonly cause the proxy chain loop errors.

The first thing to check is to make sure the default web site is running.
Assuming it is, continue below.

In ISA, check the following:

1. In the ISA Manager look at the properties of the Web Publishing rule
created
for OWA. (this could also be the default web publishing rule that the ICW
creates)
2. On the Action tab see what is listed for "Redirect request to this
internal Web Server".
3. Type the internal IP address of the server or the server name in the
box under Redirect request to this internal Web Server".

Another thing to verify is:

1. In ISA Management, go to the Properties of the ISA Server.
2. Go to the Incoming Web Requests tab.
3. Make sure the web listener is set to listen only on the external network
adapter's IP address, and not "all unassigned".

Let us know how this works out!

Best Regards,

Dana Becker
Microsoft Small Business Server Support

This posting is provided "AS IS" with no warranties, and confers no rights.





|
| Is there any way of rolling back sbs2000 to a previous
| working configuration. We had somebody in working on our
| systems who changed a few bits in ISA - now if we try to
| use OWA all we get is error 12206 - Proxy chain loop. Any
| help greatfully received.
|

rayfong
Fri Aug 01 21:56:38 CDT 2003

Besides running ICW per Dana's suggestion, please also run Configure IIS
Wizard from the Do To List. Sometimes, socket pooling will create the proxy
chain loop error. By running the IIS wizard, socket pooling is disabled and
default website is set to bind to the internal nic only.

Ray Fong
Microsoft SBS Product Support

This posting is provided "AS IS" with no warranties, and confers no rights.


>
>Hello Hans,
>
>As pointed out previously, the first thing to do is to run the Internet
>Connection Wizard and make sure you have the appropriate packet filters
>enabled. Please note that if you have any custom packet filters that they
>will be disabled. (not deleted)
>
>If running the ICW does not fix the issue, there are a few things that
>commonly cause the proxy chain loop errors.
>
>The first thing to check is to make sure the default web site is running.
>Assuming it is, continue below.
>
>In ISA, check the following:
>
>1. In the ISA Manager look at the properties of the Web Publishing rule
>created
>for OWA. (this could also be the default web publishing rule that the ICW
>creates)
>2. On the Action tab see what is listed for "Redirect request to this
>internal Web Server".
>3. Type the internal IP address of the server or the server name in the
>box under Redirect request to this internal Web Server".
>
>Another thing to verify is:
>
>1. In ISA Management, go to the Properties of the ISA Server.
>2. Go to the Incoming Web Requests tab.
>3. Make sure the web listener is set to listen only on the external
network
>adapter's IP address, and not "all unassigned".
>
>Let us know how this works out!
>
>Best Regards,
>
>Dana Becker
>Microsoft Small Business Server Support
>
>This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>

Hans
Tue Aug 05 13:42:55 CDT 2003

Many thanks, it needed both to work properly again, but
everything is back to normal.

>-----Original Message-----
>Besides running ICW per Dana's suggestion, please also
run Configure IIS
>Wizard from the Do To List. Sometimes, socket pooling
will create the proxy
>chain loop error. By running the IIS wizard, socket
pooling is disabled and
>default website is set to bind to the internal nic only.
>
>Ray Fong
>Microsoft SBS Product Support
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>>
>>Hello Hans,
>>
>>As pointed out previously, the first thing to do is to
run the Internet
>>Connection Wizard and make sure you have the appropriate
packet filters
>>enabled. Please note that if you have any custom packet
filters that they
>>will be disabled. (not deleted)
>>
>>If running the ICW does not fix the issue, there are a
few things that
>>commonly cause the proxy chain loop errors.
>>
>>The first thing to check is to make sure the default web
site is running.
>>Assuming it is, continue below.
>>
>>In ISA, check the following:
>>
>>1. In the ISA Manager look at the properties of the Web
Publishing rule
>>created
>>for OWA. (this could also be the default web publishing
rule that the ICW
>>creates)
>>2. On the Action tab see what is listed for "Redirect
request to this
>>internal Web Server".
>>3. Type the internal IP address of the server or the
server name in the
>>box under Redirect request to this internal Web Server".
>>
>>Another thing to verify is:
>>
>>1. In ISA Management, go to the Properties of the ISA
Server.
>>2. Go to the Incoming Web Requests tab.
>>3. Make sure the web listener is set to listen only on
the external
>network
>>adapter's IP address, and not "all unassigned".
>>
>>Let us know how this works out!
>>
>>Best Regards,
>>
>>Dana Becker
>>Microsoft Small Business Server Support
>>
>>This posting is provided "AS IS" with no warranties, and
confers no rights.
>>
>>
>>
>
>.
>