Re: Redirect script no longer works after SP1

Hello Jeremy,

Thank you for posting back!

Please understand that the error information relates with your customize
script and coding/programming, so I still strongly suggest you that post
you questions in the Developer newsgroups cuase we do not have similar
issue problem in Public Newsgroup. By posting there, you may get some
pointers from others who may have had similar experience that they can
share with you. The address is:

http://msdn.microsoft.com/newsgroups/default.asp

Here, I can share some general information with you, but please understand
that we cannot guarantee that it is completely fix your issue. You still
need to contact the Developer newsgroups for the most accurate rolution.
Please see:

According to the error message, it seems that the ISA server rejected the
URL which you inputted in the browser. This problem can be caused because
the ISA destination set for the built-in site does not contain the public
IP address of the network. I assume that you inputted a Fully Qualified
Domain Name (FQDN) in the certificate configuration window when you ran the
CEICW to configure the server internet connections. Since the destination
sets are created according to the name which you inputted in CEICW for
certificate, if the URL of the incoming web request does not match the
name, the connection will be rejected. Here, you can try the following
steps:

NOTE: I use the OWA site path as the example. You can do the tests by using
other path such as /remote.

1. If you have a registered FQDN and the name record is pointing to the
public IP address of the SBS server, you can configure the CEICW by using
the FQDN and access the built-in site with the URL: https://FQDN/exchange
to access the site.

2. If you do not have a FQDN and only have a static public IP address, you
can input the public IP address in the certificate configuration window.
Use the URL: https://Publicipaddress/exchange to access the OWA site.

Considering the current status, I suggest you manually modify the
destination set for the OWA site so that you can access the OWA site by
using a public IP address or different FQDN:

1. Open ISA Management console. Navigate to 'Policy Elements'\'Destination
Sets'.

2. In the right panel, double-click 'Small Business Exchange OWA
Destination Set'. In the properties window, click 'Destinations' tab. Click
'Add' button to add the following destinations:

IP Path:
Public IP address or FQDN /Exchange*
Public IP address or FQDN /public*
Public IP address or FQDN /Exchweb*

3. Click 'OK' to close the dialog boxes. Navigate to
'Monitoring'\'Services'. Restart the ISA related services.

You may also modify other destination sets so that you can access the SBS
built-in web sites by using FQDN or public IP.

For more information regarding the SBS network configurations, please refer
to the following KB article:
825763 How to configure Internet access in Windows Small Business Server
2003
http://support.microsoft.com/?id=825763

I am greatly appreciated your time time and understanding!

Best regards,

Brandy Nee

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
>From: "Jeremy Gollehon" <j_gollehonBLAMSPAM@xxxxxxxxxxx>
>References: <emv2yhMrFHA.2588@xxxxxxxxxxxxxxxxxxxx>
<8u3MtTRrFHA.472@xxxxxxxxxxxxxxxxxxxxx>
<OyKr$1XrFHA.2588@xxxxxxxxxxxxxxxxxxxx>
<nWdU9ShrFHA.472@xxxxxxxxxxxxxxxxxxxxx>
>Subject: Re: Redirect script no longer works after SP1
>Date: Fri, 2 Sep 2005 16:38:23 -0700
>Lines: 135
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
>X-RFC2646: Format=Flowed; Original
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
>Message-ID: <#S2xjeBsFHA.3352@xxxxxxxxxxxxxxxxxxxx>
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: 66-224-14-74.atgi.net 66.224.14.74
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:150384
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Brandy,
>I remembered how I did this before (I think).
>I believe I replaced the 403 error page with my .asp page.
>However, it seems that it was a 403.6 error page before (which I can find
to
>replace), but I can't figure out where this new 403 error page is served
>from.
>
>It's this one:
>Technical Information (for support personnel)
>
> a.. Error Code: 403 Forbidden. The server denied the specified Uniform
>Resource Locator (URL). Contact the server administrator. (12202)
>
>If I could figure out where that is, I could replace it with my script and
>everything would be all good. Thanks for any help!
>-Jeremy
>
>
>""Brandy Nee [MSFT]"" <v-branee@xxxxxxxxxxxxxxxxxxxx> wrote in message
>news:nWdU9ShrFHA.472@xxxxxxxxxxxxxxxxxxxxxxxx
>> Hello Jeremy,
>>
>> Thank you for posting back!
>>
>> I understand that you host this website offsite, and I have performed a
>> lot
>> of research and testing for your case, unfortunately, there is no nature
>> way on the SBS 2K3 server.
>>
>> As this issue includes custom coding/programming, scripting, I suggest
you
>> that post you questions in the Developer newsgroups. By posting there,
you
>> may get some pointers from others who may have had similar experience
that
>> they can share with you.
>>
>> http://msdn.microsoft.com/newsgroups/default.asp
>>
>> I am greatly appreciated your time and understanding! If you need any
>> assistance regarding SBS server in the future, please feel free to post
>> back. I am glad to be working with you again!
>>
>>
>> Best regards,
>>
>> Brandy Nee
>>
>> Microsoft CSS Online Newsgroup Support
>>
>> Get Secure! - www.microsoft.com/security
>> ======================================================
>> This newsgroup only focuses on SBS technical issues. If you have issues
>> regarding other Microsoft products, you'd better post in the
corresponding
>> newsgroups so that they can be resolved in an efficient and timely
manner.
>> You can locate the newsgroup here:
>> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>>
>> When opening a new thread via the web interface, we recommend you check
>> the
>> "Notify me of replies" box to receive e-mail notifications when there are
>> any updates in your thread. When responding to posts via your newsreader,
>> please "Reply to Group" so that others may learn and benefit from your
>> issue.
>>
>> Microsoft engineers can only focus on one issue per thread. Although we
>> provide other information for your reference, we recommend you post
>> different incidents in different threads to keep the thread clean. In
>> doing
>> so, it will ensure your issues are resolved in a timely manner.
>>
>> For urgent issues, you may want to contact Microsoft CSS directly. Please
>> check http://support.microsoft.com for regional support phone numbers.
>>
>> Any input or comments in this thread are highly appreciated.
>> ======================================================
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>>
>> --------------------
>>>From: "Jeremy Gollehon" <j_gollehonBLAMSPAM@xxxxxxxxxxx>
>>>References: <emv2yhMrFHA.2588@xxxxxxxxxxxxxxxxxxxx>
>> <8u3MtTRrFHA.472@xxxxxxxxxxxxxxxxxxxxx>
>>>Subject: Re: Redirect script no longer works after SP1
>>>Date: Tue, 30 Aug 2005 09:11:38 -0700
>>>Lines: 31
>>>X-Priority: 3
>>>X-MSMail-Priority: Normal
>>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
>>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
>>>X-RFC2646: Format=Flowed; Original
>>>Message-ID: <OyKr$1XrFHA.2588@xxxxxxxxxxxxxxxxxxxx>
>>>Newsgroups: microsoft.public.windows.server.sbs
>>>NNTP-Posting-Host: 66-224-14-74.atgi.net 66.224.14.74
>>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:149182
>>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>>
>>>Brandy,
>>>
>>>Thanks for the response.
>>>Because my public facing website (http://www.fqdn.com) is hosted offsite,
>>>far away from the small business server, I set up http://remote.fqdn.com
>> to
>>>point at RWW (the SBS's external IP address). To make it easy for my
>> users
>>>when they're traveling, I want them to be able to type in that address
and
>>>get redirected to RWW at https://remote.fqdn.com/Remote (which my script
>>>used to do).
>>>
>>>To sum it up:
>>>Redirect
>>>http://remote.fqdn.com
>>>to
>>>https://remote.fqdn.com/Remote
>>>
>>>Now that I think about it, opening up port 80 might have been how I did
>> this
>>>before. Probably not a good idea. Hopefully someone has a different
>>>solution.
>>>
>>>Thanks again,
>>>-Jeremy
>>>
>>>
>>>""Brandy Nee [MSFT]"" <v-branee@xxxxxxxxxxxxxxxxxxxx> wrote in message
>>>news:8u3MtTRrFHA.472@xxxxxxxxxxxxxxxxxxxxxxxx
>>>
>>>
>>><snip>
>>>
>>>
>>>
>>
>
>
>

.

Loading