Netopia 3347NWG with Remote Desktop and Remote Web Workplace

I currently have a Netopia 3347NWG, using PPOE to connect to Deltacom (a
local DSL), which is connected to the WAN Ethernet Adapter of an SBS 2003
Premium R1 (ISA not installed). The LAN Ethernet Adapter (of the SBS) is set
to 192.168.16.2 and is connected to a switch into which is connected the rest
of the office network.

IP passthrough is enabled in the Netopia's Expert - Configuration section to
User Configured PC, and the WAN Ethernet Adapter has the static IP address
(72.xxx.xxx.xxx).

Despite that, external ping and RWW and RDP will not work.

Internally, I can use Remote Desktop from a workstation to access the server
(via Remote Desktop Connection). I can also ping the server, on either the
WAN or LAN adapter.

If I try to access RWW from the workstation via https://sbs2003/Remote, I
get "Internet Explorer cannot display this webpage".

If I try to access RWW from a workstation in the LAN via
https://192.168.16.2/Remote, I get "There is a problem with this website's
security certificate", and if I then click "Continue to this website (not
recommended)", I get "The page cannot be found" (HTTP error 404).

In IIS Admin, Default Website is running and can be browsed; companyweb also
is running and can be browsed.

Remote Access directly into the Netopia setup works, via
http://72.xxx.xxx.xxx:8080.

Obviously, this needs to be changed, but prior message strings refer to
configuration settings which do not seem to be present on this Netopia model.

There is a telnet access available to this Netopia, from a local
workstation, which seems to provide a lot more options -- with little helpful
instruction. The userguide for the 3300 series models refers to nice menus
appearing in the telnet session, but all I see are line-by-line responses.

Hi Greg,

Any help here?

Port Forwarding for the Netopia 3347NWG
http://portforward.com/english/route.../SuperSync.htm

You will need to forward ports 443, 4125 (both relating to RWW) and 3389
(for RDP use) to your SBS external NIC. Then re-run CEICW, enable the
firewall, select your services, complete the Web Server Certificate screen
and finish the rest of CEICW.

IMO, discarding external ping (not being able to ping the router) is a good
thing since it makes you a smaller target on the Internet.

--
Merv Porter [SBS-MVP]
============================

"Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
message news:960F5D02-CBEF-4A02-A2A7-386BA3525606@microsoft.com...
>I currently have a Netopia 3347NWG, using PPOE to connect to Deltacom (a
> local DSL), which is connected to the WAN Ethernet Adapter of an SBS 2003
> Premium R1 (ISA not installed). The LAN Ethernet Adapter (of the SBS) is
> set
> to 192.168.16.2 and is connected to a switch into which is connected the
> rest
> of the office network.
>
> IP passthrough is enabled in the Netopia's Expert - Configuration section
> to
> User Configured PC, and the WAN Ethernet Adapter has the static IP address
> (72.xxx.xxx.xxx).
>
> Despite that, external ping and RWW and RDP will not work.
>
> Internally, I can use Remote Desktop from a workstation to access the
> server
> (via Remote Desktop Connection). I can also ping the server, on either
> the
> WAN or LAN adapter.
>
> If I try to access RWW from the workstation via https://sbs2003/Remote, I
> get "Internet Explorer cannot display this webpage".
>
> If I try to access RWW from a workstation in the LAN via
> https://192.168.16.2/Remote, I get "There is a problem with this website's
> security certificate", and if I then click "Continue to this website (not
> recommended)", I get "The page cannot be found" (HTTP error 404).
>
> In IIS Admin, Default Website is running and can be browsed; companyweb
> also
> is running and can be browsed.
>
> Remote Access directly into the Netopia setup works, via
> http://72.xxx.xxx.xxx:8080.
>
> Obviously, this needs to be changed, but prior message strings refer to
> configuration settings which do not seem to be present on this Netopia
> model.
>
> There is a telnet access available to this Netopia, from a local
> workstation, which seems to provide a lot more options -- with little
> helpful
> instruction. The userguide for the 3300 series models refers to nice
> menus
> appearing in the telnet session, but all I see are line-by-line responses.

I changed IP of the WAN Ethernet adapter in the SBS 2003 to 192.168.1.10, and
set the Gateway to the Netopia's IP of 192.168.1.254. I reran CEICW as
suggested, including Web Server Certificate.

I changed the Netopia 3347NWG, so IP Passthrough is disabled, and I rebooted
it. I then defined these new services in the Netopia's Expert Mode /
Configure / NAT -- SSL (port 443), Terminal Services (port 3389), and Remote
Web Workplace (port 4125). I enabled each of these services there, pointing
them to 192.168.1.10.

Remote Desktop Connection is now working to sbs2003.domain.com.

However, when I attempt externally to go to
http://sbs2003.domain.com/Remote, I get "You are not authorized to view this
page". Obviously, it is making a connection, but something is wrong for RWW
in the server.

"Merv Porter [SBS-MVP]" wrote:

> Hi Greg,
>
> Any help here?
>
> Port Forwarding for the Netopia 3347NWG
> http://portforward.com/english/route.../SuperSync.htm
>
> You will need to forward ports 443, 4125 (both relating to RWW) and 3389
> (for RDP use) to your SBS external NIC. Then re-run CEICW, enable the
> firewall, select your services, complete the Web Server Certificate screen
> and finish the rest of CEICW.
>
> IMO, discarding external ping (not being able to ping the router) is a good
> thing since it makes you a smaller target on the Internet.
>
> --
> Merv Porter [SBS-MVP]
> ============================
>
> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
> message news:960F5D02-CBEF-4A02-A2A7-386BA3525606@microsoft.com...
> >I currently have a Netopia 3347NWG, using PPOE to connect to Deltacom (a
> > local DSL), which is connected to the WAN Ethernet Adapter of an SBS 2003
> > Premium R1 (ISA not installed). The LAN Ethernet Adapter (of the SBS) is
> > set
> > to 192.168.16.2 and is connected to a switch into which is connected the
> > rest
> > of the office network.
> >
> > IP passthrough is enabled in the Netopia's Expert - Configuration section
> > to
> > User Configured PC, and the WAN Ethernet Adapter has the static IP address
> > (72.xxx.xxx.xxx).
> >
> > Despite that, external ping and RWW and RDP will not work.
> >
> > Internally, I can use Remote Desktop from a workstation to access the
> > server
> > (via Remote Desktop Connection). I can also ping the server, on either
> > the
> > WAN or LAN adapter.
> >
> > If I try to access RWW from the workstation via https://sbs2003/Remote, I
> > get "Internet Explorer cannot display this webpage".
> >
> > If I try to access RWW from a workstation in the LAN via
> > https://192.168.16.2/Remote, I get "There is a problem with this website's
> > security certificate", and if I then click "Continue to this website (not
> > recommended)", I get "The page cannot be found" (HTTP error 404).
> >
> > In IIS Admin, Default Website is running and can be browsed; companyweb
> > also
> > is running and can be browsed.
> >
> > Remote Access directly into the Netopia setup works, via
> > http://72.xxx.xxx.xxx:8080.
> >
> > Obviously, this needs to be changed, but prior message strings refer to
> > configuration settings which do not seem to be present on this Netopia
> > model.
> >
> > There is a telnet access available to this Netopia, from a local
> > workstation, which seems to provide a lot more options -- with little
> > helpful
> > instruction. The userguide for the 3300 series models refers to nice
> > menus
> > appearing in the telnet session, but all I see are line-by-line responses.
>
>
>

I have temporarily changed the IP address restrictions for Default WebSite in
IIS Admin, so all are now Granted Access. It is now possible to navigate to
http:\\sbs2003.domain.com, and the default website appears.

However, companyweb (My internal website) goes to http:\\companyweb, which
of course results in "Internet Explorer cannot display the webpage".

All other links (Network Configuration Wizard, Remote Web Workplace, and
Information and Answers) bring up "The page cannot be found".

Directly going to https://sbs2003.domain.com/Remote now results in "The page
cannot be found" instead of the previous "You are not authorized to view this
page".


"Greg Kirkpatrick" wrote:

> I changed IP of the WAN Ethernet adapter in the SBS 2003 to 192.168.1.10, and
> set the Gateway to the Netopia's IP of 192.168.1.254. I reran CEICW as
> suggested, including Web Server Certificate.
>
> I changed the Netopia 3347NWG, so IP Passthrough is disabled, and I rebooted
> it. I then defined these new services in the Netopia's Expert Mode /
> Configure / NAT -- SSL (port 443), Terminal Services (port 3389), and Remote
> Web Workplace (port 4125). I enabled each of these services there, pointing
> them to 192.168.1.10.
>
> Remote Desktop Connection is now working to sbs2003.domain.com.
>
> However, when I attempt externally to go to
> http://sbs2003.domain.com/Remote, I get "You are not authorized to view this
> page". Obviously, it is making a connection, but something is wrong for RWW
> in the server.
>
> "Merv Porter [SBS-MVP]" wrote:
>
> > Hi Greg,
> >
> > Any help here?
> >
> > Port Forwarding for the Netopia 3347NWG
> > http://portforward.com/english/route.../SuperSync.htm
> >
> > You will need to forward ports 443, 4125 (both relating to RWW) and 3389
> > (for RDP use) to your SBS external NIC. Then re-run CEICW, enable the
> > firewall, select your services, complete the Web Server Certificate screen
> > and finish the rest of CEICW.
> >
> > IMO, discarding external ping (not being able to ping the router) is a good
> > thing since it makes you a smaller target on the Internet.
> >
> > --
> > Merv Porter [SBS-MVP]
> > ============================
> >
> > "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
> > message news:960F5D02-CBEF-4A02-A2A7-386BA3525606@microsoft.com...
> > >I currently have a Netopia 3347NWG, using PPOE to connect to Deltacom (a
> > > local DSL), which is connected to the WAN Ethernet Adapter of an SBS 2003
> > > Premium R1 (ISA not installed). The LAN Ethernet Adapter (of the SBS) is
> > > set
> > > to 192.168.16.2 and is connected to a switch into which is connected the
> > > rest
> > > of the office network.
> > >
> > > IP passthrough is enabled in the Netopia's Expert - Configuration section
> > > to
> > > User Configured PC, and the WAN Ethernet Adapter has the static IP address
> > > (72.xxx.xxx.xxx).
> > >
> > > Despite that, external ping and RWW and RDP will not work.
> > >
> > > Internally, I can use Remote Desktop from a workstation to access the
> > > server
> > > (via Remote Desktop Connection). I can also ping the server, on either
> > > the
> > > WAN or LAN adapter.
> > >
> > > If I try to access RWW from the workstation via https://sbs2003/Remote, I
> > > get "Internet Explorer cannot display this webpage".
> > >
> > > If I try to access RWW from a workstation in the LAN via
> > > https://192.168.16.2/Remote, I get "There is a problem with this website's
> > > security certificate", and if I then click "Continue to this website (not
> > > recommended)", I get "The page cannot be found" (HTTP error 404).
> > >
> > > In IIS Admin, Default Website is running and can be browsed; companyweb
> > > also
> > > is running and can be browsed.
> > >
> > > Remote Access directly into the Netopia setup works, via
> > > http://72.xxx.xxx.xxx:8080.
> > >
> > > Obviously, this needs to be changed, but prior message strings refer to
> > > configuration settings which do not seem to be present on this Netopia
> > > model.
> > >
> > > There is a telnet access available to this Netopia, from a local
> > > workstation, which seems to provide a lot more options -- with little
> > > helpful
> > > instruction. The userguide for the 3300 series models refers to nice
> > > menus
> > > appearing in the telnet session, but all I see are line-by-line responses.
> >
> >
> >

You should not have to play with the IP address restrictions for Default
WebSite. You need to forward the proper ports in the router to your
external SBS NIC. The access RWW via
https://<YourServersFullInternetNameAsInputOnYourWebServerCert>/remote

Example:
https://mail.mycompany.com/remote

--
Merv Porter [SBS-MVP]
============================

"Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
message news:555A1A7E-56E2-48A8-B9B1-38A948D064AC@microsoft.com...
>I have temporarily changed the IP address restrictions for Default WebSite
>in
> IIS Admin, so all are now Granted Access. It is now possible to navigate
> to
> http:\\sbs2003.domain.com, and the default website appears.
>
> However, companyweb (My internal website) goes to http:\\companyweb, which
> of course results in "Internet Explorer cannot display the webpage".
>
> All other links (Network Configuration Wizard, Remote Web Workplace, and
> Information and Answers) bring up "The page cannot be found".
>
> Directly going to https://sbs2003.domain.com/Remote now results in "The
> page
> cannot be found" instead of the previous "You are not authorized to view
> this
> page".
>
>
> "Greg Kirkpatrick" wrote:
>
>> I changed IP of the WAN Ethernet adapter in the SBS 2003 to 192.168.1.10,
>> and
>> set the Gateway to the Netopia's IP of 192.168.1.254. I reran CEICW as
>> suggested, including Web Server Certificate.
>>
>> I changed the Netopia 3347NWG, so IP Passthrough is disabled, and I
>> rebooted
>> it. I then defined these new services in the Netopia's Expert Mode /
>> Configure / NAT -- SSL (port 443), Terminal Services (port 3389), and
>> Remote
>> Web Workplace (port 4125). I enabled each of these services there,
>> pointing
>> them to 192.168.1.10.
>>
>> Remote Desktop Connection is now working to sbs2003.domain.com.
>>
>> However, when I attempt externally to go to
>> http://sbs2003.domain.com/Remote, I get "You are not authorized to view
>> this
>> page". Obviously, it is making a connection, but something is wrong for
>> RWW
>> in the server.
>>
>> "Merv Porter [SBS-MVP]" wrote:
>>
>> > Hi Greg,
>> >
>> > Any help here?
>> >
>> > Port Forwarding for the Netopia 3347NWG
>> > http://portforward.com/english/route.../SuperSync.htm
>> >
>> > You will need to forward ports 443, 4125 (both relating to RWW) and
>> > 3389
>> > (for RDP use) to your SBS external NIC. Then re-run CEICW, enable the
>> > firewall, select your services, complete the Web Server Certificate
>> > screen
>> > and finish the rest of CEICW.
>> >
>> > IMO, discarding external ping (not being able to ping the router) is a
>> > good
>> > thing since it makes you a smaller target on the Internet.
>> >
>> > --
>> > Merv Porter [SBS-MVP]
>> > ============================
>> >
>> > "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
>> > message news:960F5D02-CBEF-4A02-A2A7-386BA3525606@microsoft.com...
>> > >I currently have a Netopia 3347NWG, using PPOE to connect to Deltacom
>> > >(a
>> > > local DSL), which is connected to the WAN Ethernet Adapter of an SBS
>> > > 2003
>> > > Premium R1 (ISA not installed). The LAN Ethernet Adapter (of the
>> > > SBS) is
>> > > set
>> > > to 192.168.16.2 and is connected to a switch into which is connected
>> > > the
>> > > rest
>> > > of the office network.
>> > >
>> > > IP passthrough is enabled in the Netopia's Expert - Configuration
>> > > section
>> > > to
>> > > User Configured PC, and the WAN Ethernet Adapter has the static IP
>> > > address
>> > > (72.xxx.xxx.xxx).
>> > >
>> > > Despite that, external ping and RWW and RDP will not work.
>> > >
>> > > Internally, I can use Remote Desktop from a workstation to access the
>> > > server
>> > > (via Remote Desktop Connection). I can also ping the server, on
>> > > either
>> > > the
>> > > WAN or LAN adapter.
>> > >
>> > > If I try to access RWW from the workstation via
>> > > https://sbs2003/Remote, I
>> > > get "Internet Explorer cannot display this webpage".
>> > >
>> > > If I try to access RWW from a workstation in the LAN via
>> > > https://192.168.16.2/Remote, I get "There is a problem with this
>> > > website's
>> > > security certificate", and if I then click "Continue to this website
>> > > (not
>> > > recommended)", I get "The page cannot be found" (HTTP error 404).
>> > >
>> > > In IIS Admin, Default Website is running and can be browsed;
>> > > companyweb
>> > > also
>> > > is running and can be browsed.
>> > >
>> > > Remote Access directly into the Netopia setup works, via
>> > > http://72.xxx.xxx.xxx:8080.
>> > >
>> > > Obviously, this needs to be changed, but prior message strings refer
>> > > to
>> > > configuration settings which do not seem to be present on this
>> > > Netopia
>> > > model.
>> > >
>> > > There is a telnet access available to this Netopia, from a local
>> > > workstation, which seems to provide a lot more options -- with little
>> > > helpful
>> > > instruction. The userguide for the 3300 series models refers to nice
>> > > menus
>> > > appearing in the telnet session, but all I see are line-by-line
>> > > responses.
>> >
>> >
>> >

My server's FQDN (as stated on its Web Server Certificiate and in the A
record of the hosting company's DNS entries) is
sbs2003.thenameofthecompanygoeshere.com, so the address that I have been
using to try to get to RWW is
https://sbs2003.thenameofthecompanygoeshere.com/remote. However, if the IP
address restriction for the Default Website is changed back to normal, when
trying to use RWW, I get "You are not authorized to view this page"; with the
restrictions lifted, I get "Page cannot be found". Pinging
"sbs2003.thenameofthecompanygoeshere.com" results in the static IP assigned
by the ISP, 72.xxx.xxx.xxx, and (JUST AS A TEMPORARY TEST) with the
permission restrictions lifted on Default Website,
http://sbs2003.thenameofthecompanygoeshere.com brings up the Default Website
externally. This proves that the issue is not DNS related.

These ports are properly forwarded to the server's External (WAN) Ethernet
adapter (192.168.1.10): 443, 444, 3389, and 4125. Per Susan Bradley's blog,
443 and 4125 are needed for RWW, 444 allows Sharepoint (companyweb) to be
reached externally, and 3389 allows Terminal Services (Remote Desktop
Connection) externally. As soon as I forwarded 3389, RDC started working to
that server from my office laptop.

From an internal (LAN) workstation, when trying to go to
https://sbs2003/remote, I also get the same results; and on that workstation,
while http://companyweb will appear, clicking "Remote Server Management also
results in "Page cannot be found". Pinging "sbs2003" from the workstation
provides responses from 192.168.16.2 -- the server's LAN address. Opening
http://companyweb on the server itself gives the same results.


"Merv Porter [SBS-MVP]" wrote:

> You should not have to play with the IP address restrictions for Default
> WebSite. You need to forward the proper ports in the router to your
> external SBS NIC. The access RWW via
> https://<YourServersFullInternetNameAsInputOnYourWebServerCert>/remote
>
> Example:
> https://mail.mycompany.com/remote
>
> --
> Merv Porter [SBS-MVP]
> ============================
>
> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
> message news:555A1A7E-56E2-48A8-B9B1-38A948D064AC@microsoft.com...
> >I have temporarily changed the IP address restrictions for Default WebSite
> >in
> > IIS Admin, so all are now Granted Access. It is now possible to navigate
> > to
> > http:\\sbs2003.domain.com, and the default website appears.
> >
> > However, companyweb (My internal website) goes to http:\\companyweb, which
> > of course results in "Internet Explorer cannot display the webpage".
> >
> > All other links (Network Configuration Wizard, Remote Web Workplace, and
> > Information and Answers) bring up "The page cannot be found".
> >
> > Directly going to https://sbs2003.domain.com/Remote now results in "The
> > page
> > cannot be found" instead of the previous "You are not authorized to view
> > this
> > page".
> >
> >
> > "Greg Kirkpatrick" wrote:
> >
> >> I changed IP of the WAN Ethernet adapter in the SBS 2003 to 192.168.1.10,
> >> and
> >> set the Gateway to the Netopia's IP of 192.168.1.254. I reran CEICW as
> >> suggested, including Web Server Certificate.
> >>
> >> I changed the Netopia 3347NWG, so IP Passthrough is disabled, and I
> >> rebooted
> >> it. I then defined these new services in the Netopia's Expert Mode /
> >> Configure / NAT -- SSL (port 443), Terminal Services (port 3389), and
> >> Remote
> >> Web Workplace (port 4125). I enabled each of these services there,
> >> pointing
> >> them to 192.168.1.10.
> >>
> >> Remote Desktop Connection is now working to sbs2003.domain.com.
> >>
> >> However, when I attempt externally to go to
> >> http://sbs2003.domain.com/Remote, I get "You are not authorized to view
> >> this
> >> page". Obviously, it is making a connection, but something is wrong for
> >> RWW
> >> in the server.
> >>
> >> "Merv Porter [SBS-MVP]" wrote:
> >>
> >> > Hi Greg,
> >> >
> >> > Any help here?
> >> >
> >> > Port Forwarding for the Netopia 3347NWG
> >> > http://portforward.com/english/route.../SuperSync.htm
> >> >
> >> > You will need to forward ports 443, 4125 (both relating to RWW) and
> >> > 3389
> >> > (for RDP use) to your SBS external NIC. Then re-run CEICW, enable the
> >> > firewall, select your services, complete the Web Server Certificate
> >> > screen
> >> > and finish the rest of CEICW.
> >> >
> >> > IMO, discarding external ping (not being able to ping the router) is a
> >> > good
> >> > thing since it makes you a smaller target on the Internet.
> >> >
> >> > --
> >> > Merv Porter [SBS-MVP]
> >> > ============================
> >> >
> >> > "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
> >> > message news:960F5D02-CBEF-4A02-A2A7-386BA3525606@microsoft.com...
> >> > >I currently have a Netopia 3347NWG, using PPOE to connect to Deltacom
> >> > >(a
> >> > > local DSL), which is connected to the WAN Ethernet Adapter of an SBS
> >> > > 2003
> >> > > Premium R1 (ISA not installed). The LAN Ethernet Adapter (of the
> >> > > SBS) is
> >> > > set
> >> > > to 192.168.16.2 and is connected to a switch into which is connected
> >> > > the
> >> > > rest
> >> > > of the office network.
> >> > >
> >> > > IP passthrough is enabled in the Netopia's Expert - Configuration
> >> > > section
> >> > > to
> >> > > User Configured PC, and the WAN Ethernet Adapter has the static IP
> >> > > address
> >> > > (72.xxx.xxx.xxx).
> >> > >
> >> > > Despite that, external ping and RWW and RDP will not work.
> >> > >
> >> > > Internally, I can use Remote Desktop from a workstation to access the
> >> > > server
> >> > > (via Remote Desktop Connection). I can also ping the server, on
> >> > > either
> >> > > the
> >> > > WAN or LAN adapter.
> >> > >
> >> > > If I try to access RWW from the workstation via
> >> > > https://sbs2003/Remote, I
> >> > > get "Internet Explorer cannot display this webpage".
> >> > >
> >> > > If I try to access RWW from a workstation in the LAN via
> >> > > https://192.168.16.2/Remote, I get "There is a problem with this
> >> > > website's
> >> > > security certificate", and if I then click "Continue to this website
> >> > > (not
> >> > > recommended)", I get "The page cannot be found" (HTTP error 404).
> >> > >
> >> > > In IIS Admin, Default Website is running and can be browsed;
> >> > > companyweb
> >> > > also
> >> > > is running and can be browsed.
> >> > >
> >> > > Remote Access directly into the Netopia setup works, via
> >> > > http://72.xxx.xxx.xxx:8080.
> >> > >
> >> > > Obviously, this needs to be changed, but prior message strings refer
> >> > > to
> >> > > configuration settings which do not seem to be present on this
> >> > > Netopia
> >> > > model.
> >> > >
> >> > > There is a telnet access available to this Netopia, from a local
> >> > > workstation, which seems to provide a lot more options -- with little
> >> > > helpful
> >> > > instruction. The userguide for the 3300 series models refers to nice
> >> > > menus
> >> > > appearing in the telnet session, but all I see are line-by-line
> >> > > responses.
> >> >
> >> >
> >> >
>
>
>

Any help here?

Error message when you try to access the Remote Web Workplace in Windows
Small Business Server 2003: "You are not authorized to view this page"
http://support.microsoft.com/kb/925653

--
Merv Porter [SBS-MVP]
============================

"Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
message news:79148A29-E272-4BA8-BE8E-EE0C09E9CA11@microsoft.com...
> My server's FQDN (as stated on its Web Server Certificiate and in the A
> record of the hosting company's DNS entries) is
> sbs2003.thenameofthecompanygoeshere.com, so the address that I have been
> using to try to get to RWW is
> https://sbs2003.thenameofthecompanygoeshere.com/remote. However, if the
> IP
> address restriction for the Default Website is changed back to normal,
> when
> trying to use RWW, I get "You are not authorized to view this page"; with
> the
> restrictions lifted, I get "Page cannot be found". Pinging
> "sbs2003.thenameofthecompanygoeshere.com" results in the static IP
> assigned
> by the ISP, 72.xxx.xxx.xxx, and (JUST AS A TEMPORARY TEST) with the
> permission restrictions lifted on Default Website,
> http://sbs2003.thenameofthecompanygoeshere.com brings up the Default
> Website
> externally. This proves that the issue is not DNS related.
>
> These ports are properly forwarded to the server's External (WAN) Ethernet
> adapter (192.168.1.10): 443, 444, 3389, and 4125. Per Susan Bradley's
> blog,
> 443 and 4125 are needed for RWW, 444 allows Sharepoint (companyweb) to be
> reached externally, and 3389 allows Terminal Services (Remote Desktop
> Connection) externally. As soon as I forwarded 3389, RDC started working
> to
> that server from my office laptop.
>
> From an internal (LAN) workstation, when trying to go to
> https://sbs2003/remote, I also get the same results; and on that
> workstation,
> while http://companyweb will appear, clicking "Remote Server Management
> also
> results in "Page cannot be found". Pinging "sbs2003" from the workstation
> provides responses from 192.168.16.2 -- the server's LAN address. Opening
> http://companyweb on the server itself gives the same results.
>
>
> "Merv Porter [SBS-MVP]" wrote:
>
>> You should not have to play with the IP address restrictions for Default
>> WebSite. You need to forward the proper ports in the router to your
>> external SBS NIC. The access RWW via
>> https://<YourServersFullInternetNameAsInputOnYourWebServerCert>/remote
>>
>> Example:
>> https://mail.mycompany.com/remote
>>
>> --
>> Merv Porter [SBS-MVP]
>> ============================
>>
>> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
>> message news:555A1A7E-56E2-48A8-B9B1-38A948D064AC@microsoft.com...
>> >I have temporarily changed the IP address restrictions for Default
>> >WebSite
>> >in
>> > IIS Admin, so all are now Granted Access. It is now possible to
>> > navigate
>> > to
>> > http:\\sbs2003.domain.com, and the default website appears.
>> >
>> > However, companyweb (My internal website) goes to http:\\companyweb,
>> > which
>> > of course results in "Internet Explorer cannot display the webpage".
>> >
>> > All other links (Network Configuration Wizard, Remote Web Workplace,
>> > and
>> > Information and Answers) bring up "The page cannot be found".
>> >
>> > Directly going to https://sbs2003.domain.com/Remote now results in "The
>> > page
>> > cannot be found" instead of the previous "You are not authorized to
>> > view
>> > this
>> > page".
>> >
>> >
>> > "Greg Kirkpatrick" wrote:
>> >
>> >> I changed IP of the WAN Ethernet adapter in the SBS 2003 to
>> >> 192.168.1.10,
>> >> and
>> >> set the Gateway to the Netopia's IP of 192.168.1.254. I reran CEICW
>> >> as
>> >> suggested, including Web Server Certificate.
>> >>
>> >> I changed the Netopia 3347NWG, so IP Passthrough is disabled, and I
>> >> rebooted
>> >> it. I then defined these new services in the Netopia's Expert Mode /
>> >> Configure / NAT -- SSL (port 443), Terminal Services (port 3389), and
>> >> Remote
>> >> Web Workplace (port 4125). I enabled each of these services there,
>> >> pointing
>> >> them to 192.168.1.10.
>> >>
>> >> Remote Desktop Connection is now working to sbs2003.domain.com.
>> >>
>> >> However, when I attempt externally to go to
>> >> http://sbs2003.domain.com/Remote, I get "You are not authorized to
>> >> view
>> >> this
>> >> page". Obviously, it is making a connection, but something is wrong
>> >> for
>> >> RWW
>> >> in the server.
>> >>
>> >> "Merv Porter [SBS-MVP]" wrote:
>> >>
>> >> > Hi Greg,
>> >> >
>> >> > Any help here?
>> >> >
>> >> > Port Forwarding for the Netopia 3347NWG
>> >> > http://portforward.com/english/route.../SuperSync.htm
>> >> >
>> >> > You will need to forward ports 443, 4125 (both relating to RWW) and
>> >> > 3389
>> >> > (for RDP use) to your SBS external NIC. Then re-run CEICW, enable
>> >> > the
>> >> > firewall, select your services, complete the Web Server Certificate
>> >> > screen
>> >> > and finish the rest of CEICW.
>> >> >
>> >> > IMO, discarding external ping (not being able to ping the router) is
>> >> > a
>> >> > good
>> >> > thing since it makes you a smaller target on the Internet.
>> >> >
>> >> > --
>> >> > Merv Porter [SBS-MVP]
>> >> > ============================
>> >> >
>> >> > "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote
>> >> > in
>> >> > message news:960F5D02-CBEF-4A02-A2A7-386BA3525606@microsoft.com...
>> >> > >I currently have a Netopia 3347NWG, using PPOE to connect to
>> >> > >Deltacom
>> >> > >(a
>> >> > > local DSL), which is connected to the WAN Ethernet Adapter of an
>> >> > > SBS
>> >> > > 2003
>> >> > > Premium R1 (ISA not installed). The LAN Ethernet Adapter (of the
>> >> > > SBS) is
>> >> > > set
>> >> > > to 192.168.16.2 and is connected to a switch into which is
>> >> > > connected
>> >> > > the
>> >> > > rest
>> >> > > of the office network.
>> >> > >
>> >> > > IP passthrough is enabled in the Netopia's Expert - Configuration
>> >> > > section
>> >> > > to
>> >> > > User Configured PC, and the WAN Ethernet Adapter has the static IP
>> >> > > address
>> >> > > (72.xxx.xxx.xxx).
>> >> > >
>> >> > > Despite that, external ping and RWW and RDP will not work.
>> >> > >
>> >> > > Internally, I can use Remote Desktop from a workstation to access
>> >> > > the
>> >> > > server
>> >> > > (via Remote Desktop Connection). I can also ping the server, on
>> >> > > either
>> >> > > the
>> >> > > WAN or LAN adapter.
>> >> > >
>> >> > > If I try to access RWW from the workstation via
>> >> > > https://sbs2003/Remote, I
>> >> > > get "Internet Explorer cannot display this webpage".
>> >> > >
>> >> > > If I try to access RWW from a workstation in the LAN via
>> >> > > https://192.168.16.2/Remote, I get "There is a problem with this
>> >> > > website's
>> >> > > security certificate", and if I then click "Continue to this
>> >> > > website
>> >> > > (not
>> >> > > recommended)", I get "The page cannot be found" (HTTP error 404).
>> >> > >
>> >> > > In IIS Admin, Default Website is running and can be browsed;
>> >> > > companyweb
>> >> > > also
>> >> > > is running and can be browsed.
>> >> > >
>> >> > > Remote Access directly into the Netopia setup works, via
>> >> > > http://72.xxx.xxx.xxx:8080.
>> >> > >
>> >> > > Obviously, this needs to be changed, but prior message strings
>> >> > > refer
>> >> > > to
>> >> > > configuration settings which do not seem to be present on this
>> >> > > Netopia
>> >> > > model.
>> >> > >
>> >> > > There is a telnet access available to this Netopia, from a local
>> >> > > workstation, which seems to provide a lot more options -- with
>> >> > > little
>> >> > > helpful
>> >> > > instruction. The userguide for the 3300 series models refers to
>> >> > > nice
>> >> > > menus
>> >> > > appearing in the telnet session, but all I see are line-by-line
>> >> > > responses.
>> >> >
>> >> >
>> >> >
>>
>>
>>

Yes, that helped somewhat, as I found that the "Remote" Web Site (under
Default Web Site) is missing. That might explain the "Page cannot be found"
errors. How can I get this created?

"Merv Porter [SBS-MVP]" wrote:

> Any help here?
>
> Error message when you try to access the Remote Web Workplace in Windows
> Small Business Server 2003: "You are not authorized to view this page"
> http://support.microsoft.com/kb/925653
>
> --
> Merv Porter [SBS-MVP]
> ============================
>
> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
> message news:79148A29-E272-4BA8-BE8E-EE0C09E9CA11@microsoft.com...
> > My server's FQDN (as stated on its Web Server Certificiate and in the A
> > record of the hosting company's DNS entries) is
> > sbs2003.thenameofthecompanygoeshere.com, so the address that I have been
> > using to try to get to RWW is
> > https://sbs2003.thenameofthecompanygoeshere.com/remote. However, if the
> > IP
> > address restriction for the Default Website is changed back to normal,
> > when
> > trying to use RWW, I get "You are not authorized to view this page"; with
> > the
> > restrictions lifted, I get "Page cannot be found". Pinging
> > "sbs2003.thenameofthecompanygoeshere.com" results in the static IP
> > assigned
> > by the ISP, 72.xxx.xxx.xxx, and (JUST AS A TEMPORARY TEST) with the
> > permission restrictions lifted on Default Website,
> > http://sbs2003.thenameofthecompanygoeshere.com brings up the Default
> > Website
> > externally. This proves that the issue is not DNS related.
> >
> > These ports are properly forwarded to the server's External (WAN) Ethernet
> > adapter (192.168.1.10): 443, 444, 3389, and 4125. Per Susan Bradley's
> > blog,
> > 443 and 4125 are needed for RWW, 444 allows Sharepoint (companyweb) to be
> > reached externally, and 3389 allows Terminal Services (Remote Desktop
> > Connection) externally. As soon as I forwarded 3389, RDC started working
> > to
> > that server from my office laptop.
> >
> > From an internal (LAN) workstation, when trying to go to
> > https://sbs2003/remote, I also get the same results; and on that
> > workstation,
> > while http://companyweb will appear, clicking "Remote Server Management
> > also
> > results in "Page cannot be found". Pinging "sbs2003" from the workstation
> > provides responses from 192.168.16.2 -- the server's LAN address. Opening
> > http://companyweb on the server itself gives the same results.
> >
> >
> > "Merv Porter [SBS-MVP]" wrote:
> >
> >> You should not have to play with the IP address restrictions for Default
> >> WebSite. You need to forward the proper ports in the router to your
> >> external SBS NIC. The access RWW via
> >> https://<YourServersFullInternetNameAsInputOnYourWebServerCert>/remote
> >>
> >> Example:
> >> https://mail.mycompany.com/remote
> >>
> >> --
> >> Merv Porter [SBS-MVP]
> >> ============================
> >>
> >> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
> >> message news:555A1A7E-56E2-48A8-B9B1-38A948D064AC@microsoft.com...
> >> >I have temporarily changed the IP address restrictions for Default
> >> >WebSite
> >> >in
> >> > IIS Admin, so all are now Granted Access. It is now possible to
> >> > navigate
> >> > to
> >> > http:\\sbs2003.domain.com, and the default website appears.
> >> >
> >> > However, companyweb (My internal website) goes to http:\\companyweb,
> >> > which
> >> > of course results in "Internet Explorer cannot display the webpage".
> >> >
> >> > All other links (Network Configuration Wizard, Remote Web Workplace,
> >> > and
> >> > Information and Answers) bring up "The page cannot be found".
> >> >
> >> > Directly going to https://sbs2003.domain.com/Remote now results in "The
> >> > page
> >> > cannot be found" instead of the previous "You are not authorized to
> >> > view
> >> > this
> >> > page".
> >> >
> >> >
> >> > "Greg Kirkpatrick" wrote:
> >> >
> >> >> I changed IP of the WAN Ethernet adapter in the SBS 2003 to
> >> >> 192.168.1.10,
> >> >> and
> >> >> set the Gateway to the Netopia's IP of 192.168.1.254. I reran CEICW
> >> >> as
> >> >> suggested, including Web Server Certificate.
> >> >>
> >> >> I changed the Netopia 3347NWG, so IP Passthrough is disabled, and I
> >> >> rebooted
> >> >> it. I then defined these new services in the Netopia's Expert Mode /
> >> >> Configure / NAT -- SSL (port 443), Terminal Services (port 3389), and
> >> >> Remote
> >> >> Web Workplace (port 4125). I enabled each of these services there,
> >> >> pointing
> >> >> them to 192.168.1.10.
> >> >>
> >> >> Remote Desktop Connection is now working to sbs2003.domain.com.
> >> >>
> >> >> However, when I attempt externally to go to
> >> >> http://sbs2003.domain.com/Remote, I get "You are not authorized to
> >> >> view
> >> >> this
> >> >> page". Obviously, it is making a connection, but something is wrong
> >> >> for
> >> >> RWW
> >> >> in the server.
> >> >>
> >> >> "Merv Porter [SBS-MVP]" wrote:
> >> >>
> >> >> > Hi Greg,
> >> >> >
> >> >> > Any help here?
> >> >> >
> >> >> > Port Forwarding for the Netopia 3347NWG
> >> >> > http://portforward.com/english/route.../SuperSync.htm
> >> >> >
> >> >> > You will need to forward ports 443, 4125 (both relating to RWW) and
> >> >> > 3389
> >> >> > (for RDP use) to your SBS external NIC. Then re-run CEICW, enable
> >> >> > the
> >> >> > firewall, select your services, complete the Web Server Certificate
> >> >> > screen
> >> >> > and finish the rest of CEICW.
> >> >> >
> >> >> > IMO, discarding external ping (not being able to ping the router) is
> >> >> > a
> >> >> > good
> >> >> > thing since it makes you a smaller target on the Internet.
> >> >> >
> >> >> > --
> >> >> > Merv Porter [SBS-MVP]
> >> >> > ============================
> >> >> >
> >> >> > "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote
> >> >> > in
> >> >> > message news:960F5D02-CBEF-4A02-A2A7-386BA3525606@microsoft.com...
> >> >> > >I currently have a Netopia 3347NWG, using PPOE to connect to
> >> >> > >Deltacom
> >> >> > >(a
> >> >> > > local DSL), which is connected to the WAN Ethernet Adapter of an
> >> >> > > SBS
> >> >> > > 2003
> >> >> > > Premium R1 (ISA not installed). The LAN Ethernet Adapter (of the
> >> >> > > SBS) is
> >> >> > > set
> >> >> > > to 192.168.16.2 and is connected to a switch into which is
> >> >> > > connected
> >> >> > > the
> >> >> > > rest
> >> >> > > of the office network.
> >> >> > >
> >> >> > > IP passthrough is enabled in the Netopia's Expert - Configuration
> >> >> > > section
> >> >> > > to
> >> >> > > User Configured PC, and the WAN Ethernet Adapter has the static IP
> >> >> > > address
> >> >> > > (72.xxx.xxx.xxx).
> >> >> > >
> >> >> > > Despite that, external ping and RWW and RDP will not work.
> >> >> > >
> >> >> > > Internally, I can use Remote Desktop from a workstation to access
> >> >> > > the
> >> >> > > server
> >> >> > > (via Remote Desktop Connection). I can also ping the server, on
> >> >> > > either
> >> >> > > the
> >> >> > > WAN or LAN adapter.
> >> >> > >
> >> >> > > If I try to access RWW from the workstation via
> >> >> > > https://sbs2003/Remote, I
> >> >> > > get "Internet Explorer cannot display this webpage".
> >> >> > >
> >> >> > > If I try to access RWW from a workstation in the LAN via
> >> >> > > https://192.168.16.2/Remote, I get "There is a problem with this
> >> >> > > website's
> >> >> > > security certificate", and if I then click "Continue to this
> >> >> > > website
> >> >> > > (not
> >> >> > > recommended)", I get "The page cannot be found" (HTTP error 404).
> >> >> > >
> >> >> > > In IIS Admin, Default Website is running and can be browsed;
> >> >> > > companyweb
> >> >> > > also
> >> >> > > is running and can be browsed.
> >> >> > >
> >> >> > > Remote Access directly into the Netopia setup works, via
> >> >> > > http://72.xxx.xxx.xxx:8080.
> >> >> > >
> >> >> > > Obviously, this needs to be changed, but prior message strings
> >> >> > > refer
> >> >> > > to
> >> >> > > configuration settings which do not seem to be present on this
> >> >> > > Netopia
> >> >> > > model.
> >> >> > >
> >> >> > > There is a telnet access available to this Netopia, from a local
> >> >> > > workstation, which seems to provide a lot more options -- with
> >> >> > > little
> >> >> > > helpful
> >> >> > > instruction. The userguide for the 3300 series models refers to
> >> >> > > nice
> >> >> > > menus
> >> >> > > appearing in the telnet session, but all I see are line-by-line
> >> >> > > responses.
> >> >> >
> >> >> >
> >> >> >
> >>
> >>
> >>
>
>
>

Try this...

Reinstall Remote Web
http://groups.google.com/group/micro...0a07e39aca4540

--
Merv Porter [SBS-MVP]
============================

"Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
message news:465CE79D-647C-4E8F-826D-85C5765D89DB@microsoft.com...
> Yes, that helped somewhat, as I found that the "Remote" Web Site (under
> Default Web Site) is missing. That might explain the "Page cannot be
> found"
> errors. How can I get this created?
>
> "Merv Porter [SBS-MVP]" wrote:
>
>> Any help here?
>>
>> Error message when you try to access the Remote Web Workplace in Windows
>> Small Business Server 2003: "You are not authorized to view this page"
>> http://support.microsoft.com/kb/925653
>>
>> --
>> Merv Porter [SBS-MVP]
>> ============================
>>
>> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
>> message news:79148A29-E272-4BA8-BE8E-EE0C09E9CA11@microsoft.com...
>> > My server's FQDN (as stated on its Web Server Certificiate and in the A
>> > record of the hosting company's DNS entries) is
>> > sbs2003.thenameofthecompanygoeshere.com, so the address that I have
>> > been
>> > using to try to get to RWW is
>> > https://sbs2003.thenameofthecompanygoeshere.com/remote. However, if
>> > the
>> > IP
>> > address restriction for the Default Website is changed back to normal,
>> > when
>> > trying to use RWW, I get "You are not authorized to view this page";
>> > with
>> > the
>> > restrictions lifted, I get "Page cannot be found". Pinging
>> > "sbs2003.thenameofthecompanygoeshere.com" results in the static IP
>> > assigned
>> > by the ISP, 72.xxx.xxx.xxx, and (JUST AS A TEMPORARY TEST) with the
>> > permission restrictions lifted on Default Website,
>> > http://sbs2003.thenameofthecompanygoeshere.com brings up the Default
>> > Website
>> > externally. This proves that the issue is not DNS related.
>> >
>> > These ports are properly forwarded to the server's External (WAN)
>> > Ethernet
>> > adapter (192.168.1.10): 443, 444, 3389, and 4125. Per Susan Bradley's
>> > blog,
>> > 443 and 4125 are needed for RWW, 444 allows Sharepoint (companyweb) to
>> > be
>> > reached externally, and 3389 allows Terminal Services (Remote Desktop
>> > Connection) externally. As soon as I forwarded 3389, RDC started
>> > working
>> > to
>> > that server from my office laptop.
>> >
>> > From an internal (LAN) workstation, when trying to go to
>> > https://sbs2003/remote, I also get the same results; and on that
>> > workstation,
>> > while http://companyweb will appear, clicking "Remote Server Management
>> > also
>> > results in "Page cannot be found". Pinging "sbs2003" from the
>> > workstation
>> > provides responses from 192.168.16.2 -- the server's LAN address.
>> > Opening
>> > http://companyweb on the server itself gives the same results.
>> >
>> >
>> > "Merv Porter [SBS-MVP]" wrote:
>> >
>> >> You should not have to play with the IP address restrictions for
>> >> Default
>> >> WebSite. You need to forward the proper ports in the router to your
>> >> external SBS NIC. The access RWW via
>> >> https://<YourServersFullInternetNameAsInputOnYourWebServerCert>/remote
>> >>
>> >> Example:
>> >> https://mail.mycompany.com/remote
>> >>
>> >> --
>> >> Merv Porter [SBS-MVP]
>> >> ============================
>> >>
>> >> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote
>> >> in
>> >> message news:555A1A7E-56E2-48A8-B9B1-38A948D064AC@microsoft.com...
>> >> >I have temporarily changed the IP address restrictions for Default
>> >> >WebSite
>> >> >in
>> >> > IIS Admin, so all are now Granted Access. It is now possible to
>> >> > navigate
>> >> > to
>> >> > http:\\sbs2003.domain.com, and the default website appears.
>> >> >
>> >> > However, companyweb (My internal website) goes to http:\\companyweb,
>> >> > which
>> >> > of course results in "Internet Explorer cannot display the webpage".
>> >> >
>> >> > All other links (Network Configuration Wizard, Remote Web Workplace,
>> >> > and
>> >> > Information and Answers) bring up "The page cannot be found".
>> >> >
>> >> > Directly going to https://sbs2003.domain.com/Remote now results in
>> >> > "The
>> >> > page
>> >> > cannot be found" instead of the previous "You are not authorized to
>> >> > view
>> >> > this
>> >> > page".
>> >> >
>> >> >
>> >> > "Greg Kirkpatrick" wrote:
>> >> >
>> >> >> I changed IP of the WAN Ethernet adapter in the SBS 2003 to
>> >> >> 192.168.1.10,
>> >> >> and
>> >> >> set the Gateway to the Netopia's IP of 192.168.1.254. I reran
>> >> >> CEICW
>> >> >> as
>> >> >> suggested, including Web Server Certificate.
>> >> >>
>> >> >> I changed the Netopia 3347NWG, so IP Passthrough is disabled, and I
>> >> >> rebooted
>> >> >> it. I then defined these new services in the Netopia's Expert Mode
>> >> >> /
>> >> >> Configure / NAT -- SSL (port 443), Terminal Services (port 3389),
>> >> >> and
>> >> >> Remote
>> >> >> Web Workplace (port 4125). I enabled each of these services there,
>> >> >> pointing
>> >> >> them to 192.168.1.10.
>> >> >>
>> >> >> Remote Desktop Connection is now working to sbs2003.domain.com.
>> >> >>
>> >> >> However, when I attempt externally to go to
>> >> >> http://sbs2003.domain.com/Remote, I get "You are not authorized to
>> >> >> view
>> >> >> this
>> >> >> page". Obviously, it is making a connection, but something is
>> >> >> wrong
>> >> >> for
>> >> >> RWW
>> >> >> in the server.
>> >> >>
>> >> >> "Merv Porter [SBS-MVP]" wrote:
>> >> >>
>> >> >> > Hi Greg,
>> >> >> >
>> >> >> > Any help here?
>> >> >> >
>> >> >> > Port Forwarding for the Netopia 3347NWG
>> >> >> > http://portforward.com/english/route.../SuperSync.htm
>> >> >> >
>> >> >> > You will need to forward ports 443, 4125 (both relating to RWW)
>> >> >> > and
>> >> >> > 3389
>> >> >> > (for RDP use) to your SBS external NIC. Then re-run CEICW,
>> >> >> > enable
>> >> >> > the
>> >> >> > firewall, select your services, complete the Web Server
>> >> >> > Certificate
>> >> >> > screen
>> >> >> > and finish the rest of CEICW.
>> >> >> >
>> >> >> > IMO, discarding external ping (not being able to ping the router)
>> >> >> > is
>> >> >> > a
>> >> >> > good
>> >> >> > thing since it makes you a smaller target on the Internet.
>> >> >> >
>> >> >> > --
>> >> >> > Merv Porter [SBS-MVP]
>> >> >> > ============================
>> >> >> >
>> >> >> > "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com>
>> >> >> > wrote
>> >> >> > in
>> >> >> > message
>> >> >> > news:960F5D02-CBEF-4A02-A2A7-386BA3525606@microsoft.com...
>> >> >> > >I currently have a Netopia 3347NWG, using PPOE to connect to
>> >> >> > >Deltacom
>> >> >> > >(a
>> >> >> > > local DSL), which is connected to the WAN Ethernet Adapter of
>> >> >> > > an
>> >> >> > > SBS
>> >> >> > > 2003
>> >> >> > > Premium R1 (ISA not installed). The LAN Ethernet Adapter (of
>> >> >> > > the
>> >> >> > > SBS) is
>> >> >> > > set
>> >> >> > > to 192.168.16.2 and is connected to a switch into which is
>> >> >> > > connected
>> >> >> > > the
>> >> >> > > rest
>> >> >> > > of the office network.
>> >> >> > >
>> >> >> > > IP passthrough is enabled in the Netopia's Expert -
>> >> >> > > Configuration
>> >> >> > > section
>> >> >> > > to
>> >> >> > > User Configured PC, and the WAN Ethernet Adapter has the static
>> >> >> > > IP
>> >> >> > > address
>> >> >> > > (72.xxx.xxx.xxx).
>> >> >> > >
>> >> >> > > Despite that, external ping and RWW and RDP will not work.
>> >> >> > >
>> >> >> > > Internally, I can use Remote Desktop from a workstation to
>> >> >> > > access
>> >> >> > > the
>> >> >> > > server
>> >> >> > > (via Remote Desktop Connection). I can also ping the server,
>> >> >> > > on
>> >> >> > > either
>> >> >> > > the
>> >> >> > > WAN or LAN adapter.
>> >> >> > >
>> >> >> > > If I try to access RWW from the workstation via
>> >> >> > > https://sbs2003/Remote, I
>> >> >> > > get "Internet Explorer cannot display this webpage".
>> >> >> > >
>> >> >> > > If I try to access RWW from a workstation in the LAN via
>> >> >> > > https://192.168.16.2/Remote, I get "There is a problem with
>> >> >> > > this
>> >> >> > > website's
>> >> >> > > security certificate", and if I then click "Continue to this
>> >> >> > > website
>> >> >> > > (not
>> >> >> > > recommended)", I get "The page cannot be found" (HTTP error
>> >> >> > > 404).
>> >> >> > >
>> >> >> > > In IIS Admin, Default Website is running and can be browsed;
>> >> >> > > companyweb
>> >> >> > > also
>> >> >> > > is running and can be browsed.
>> >> >> > >
>> >> >> > > Remote Access directly into the Netopia setup works, via
>> >> >> > > http://72.xxx.xxx.xxx:8080.
>> >> >> > >
>> >> >> > > Obviously, this needs to be changed, but prior message strings
>> >> >> > > refer
>> >> >> > > to
>> >> >> > > configuration settings which do not seem to be present on this
>> >> >> > > Netopia
>> >> >> > > model.
>> >> >> > >
>> >> >> > > There is a telnet access available to this Netopia, from a
>> >> >> > > local
>> >> >> > > workstation, which seems to provide a lot more options -- with
>> >> >> > > little
>> >> >> > > helpful
>> >> >> > > instruction. The userguide for the 3300 series models refers
>> >> >> > > to
>> >> >> > > nice
>> >> >> > > menus
>> >> >> > > appearing in the telnet session, but all I see are line-by-line
>> >> >> > > responses.
>> >> >> >
>> >> >> >
>> >> >> >
>> >>
>> >>
>> >>
>>
>>
>>

I follow these directions from that link:

"If SBS is already installed then you should be able to go to Start/Control
Panel/Add/Remove Programs and select Windows Small Business Server 2003 then
click on the Change/Remove button.. then follow the setup wizard screens
until you get to the Component Selection screen.. then select Reinstall for
the Server Tools option.. You can set the Server Tools subcomponents to None
(Installed) they should not need to be re-installed. RWW should be
re-installed by simply reinstalling the top level of the Server Tools..
it's not listed as a seperated component like Intranet is (which installs
Windows SharePoint Services and does the SBS provisioning) "

....and I got this error before it finished:
---------------------------
..NET Framework 1.1 -- Device Update 2.0
---------------------------
Command line option syntax error. Type Command /? for Help.
---------------------------
OK
---------------------------
However, it finished otherwise, and did not report any problem. It brought
up a box that said the server had to reboot, but before I clicked OK, I
checked in IIS Admin, and the "Remote" web site under Default Web Site was
now listed.

I then clicked OK, which rebooted the server.

When it returned, I could right-click the "Remote" website under Default Web
Site, and "browse", and see the RWW login page.

However, when I attempted to access it from an external computer (after
logging out of RDC), I got "You are not authorized to view this page".


"Merv Porter [SBS-MVP]" wrote:

> Try this...
>
> Reinstall Remote Web
> http://groups.google.com/group/micro...0a07e39aca4540
>
> --
> Merv Porter [SBS-MVP]
> ============================
>
> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
> message news:465CE79D-647C-4E8F-826D-85C5765D89DB@microsoft.com...
> > Yes, that helped somewhat, as I found that the "Remote" Web Site (under
> > Default Web Site) is missing. That might explain the "Page cannot be
> > found"
> > errors. How can I get this created?
> >
> > "Merv Porter [SBS-MVP]" wrote:
> >
> >> Any help here?
> >>
> >> Error message when you try to access the Remote Web Workplace in Windows
> >> Small Business Server 2003: "You are not authorized to view this page"
> >> http://support.microsoft.com/kb/925653
> >>
> >> --
> >> Merv Porter [SBS-MVP]
> >> ============================
> >>
> >> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
> >> message news:79148A29-E272-4BA8-BE8E-EE0C09E9CA11@microsoft.com...
> >> > My server's FQDN (as stated on its Web Server Certificiate and in the A
> >> > record of the hosting company's DNS entries) is
> >> > sbs2003.thenameofthecompanygoeshere.com, so the address that I have
> >> > been
> >> > using to try to get to RWW is
> >> > https://sbs2003.thenameofthecompanygoeshere.com/remote. However, if
> >> > the
> >> > IP
> >> > address restriction for the Default Website is changed back to normal,
> >> > when
> >> > trying to use RWW, I get "You are not authorized to view this page";
> >> > with
> >> > the
> >> > restrictions lifted, I get "Page cannot be found". Pinging
> >> > "sbs2003.thenameofthecompanygoeshere.com" results in the static IP
> >> > assigned
> >> > by the ISP, 72.xxx.xxx.xxx, and (JUST AS A TEMPORARY TEST) with the
> >> > permission restrictions lifted on Default Website,
> >> > http://sbs2003.thenameofthecompanygoeshere.com brings up the Default
> >> > Website
> >> > externally. This proves that the issue is not DNS related.
> >> >
> >> > These ports are properly forwarded to the server's External (WAN)
> >> > Ethernet
> >> > adapter (192.168.1.10): 443, 444, 3389, and 4125. Per Susan Bradley's
> >> > blog,
> >> > 443 and 4125 are needed for RWW, 444 allows Sharepoint (companyweb) to
> >> > be
> >> > reached externally, and 3389 allows Terminal Services (Remote Desktop
> >> > Connection) externally. As soon as I forwarded 3389, RDC started
> >> > working
> >> > to
> >> > that server from my office laptop.
> >> >
> >> > From an internal (LAN) workstation, when trying to go to
> >> > https://sbs2003/remote, I also get the same results; and on that
> >> > workstation,
> >> > while http://companyweb will appear, clicking "Remote Server Management
> >> > also
> >> > results in "Page cannot be found". Pinging "sbs2003" from the
> >> > workstation
> >> > provides responses from 192.168.16.2 -- the server's LAN address.
> >> > Opening
> >> > http://companyweb on the server itself gives the same results.
> >> >
> >> >
> >> > "Merv Porter [SBS-MVP]" wrote:
> >> >
> >> >> You should not have to play with the IP address restrictions for
> >> >> Default
> >> >> WebSite. You need to forward the proper ports in the router to your
> >> >> external SBS NIC. The access RWW via
> >> >> https://<YourServersFullInternetNameAsInputOnYourWebServerCert>/remote
> >> >>
> >> >> Example:
> >> >> https://mail.mycompany.com/remote
> >> >>
> >> >> --
> >> >> Merv Porter [SBS-MVP]
> >> >> ============================
> >> >>
> >> >> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote
> >> >> in
> >> >> message news:555A1A7E-56E2-48A8-B9B1-38A948D064AC@microsoft.com...
> >> >> >I have temporarily changed the IP address restrictions for Default
> >> >> >WebSite
> >> >> >in
> >> >> > IIS Admin, so all are now Granted Access. It is now possible to
> >> >> > navigate
> >> >> > to
> >> >> > http:\\sbs2003.domain.com, and the default website appears.
> >> >> >
> >> >> > However, companyweb (My internal website) goes to http:\\companyweb,
> >> >> > which
> >> >> > of course results in "Internet Explorer cannot display the webpage".
> >> >> >
> >> >> > All other links (Network Configuration Wizard, Remote Web Workplace,
> >> >> > and
> >> >> > Information and Answers) bring up "The page cannot be found".
> >> >> >
> >> >> > Directly going to https://sbs2003.domain.com/Remote now results in
> >> >> > "The
> >> >> > page
> >> >> > cannot be found" instead of the previous "You are not authorized to
> >> >> > view
> >> >> > this
> >> >> > page".
> >> >> >
> >> >> >
> >> >> > "Greg Kirkpatrick" wrote:
> >> >> >
> >> >> >> I changed IP of the WAN Ethernet adapter in the SBS 2003 to
> >> >> >> 192.168.1.10,
> >> >> >> and
> >> >> >> set the Gateway to the Netopia's IP of 192.168.1.254. I reran
> >> >> >> CEICW
> >> >> >> as
> >> >> >> suggested, including Web Server Certificate.
> >> >> >>
> >> >> >> I changed the Netopia 3347NWG, so IP Passthrough is disabled, and I
> >> >> >> rebooted
> >> >> >> it. I then defined these new services in the Netopia's Expert Mode
> >> >> >> /
> >> >> >> Configure / NAT -- SSL (port 443), Terminal Services (port 3389),
> >> >> >> and
> >> >> >> Remote
> >> >> >> Web Workplace (port 4125). I enabled each of these services there,
> >> >> >> pointing
> >> >> >> them to 192.168.1.10.
> >> >> >>
> >> >> >> Remote Desktop Connection is now working to sbs2003.domain.com.
> >> >> >>
> >> >> >> However, when I attempt externally to go to
> >> >> >> http://sbs2003.domain.com/Remote, I get "You are not authorized to
> >> >> >> view
> >> >> >> this
> >> >> >> page". Obviously, it is making a connection, but something is
> >> >> >> wrong
> >> >> >> for
> >> >> >> RWW
> >> >> >> in the server.
> >> >> >>
> >> >> >> "Merv Porter [SBS-MVP]" wrote:
> >> >> >>
> >> >> >> > Hi Greg,
> >> >> >> >
> >> >> >> > Any help here?
> >> >> >> >
> >> >> >> > Port Forwarding for the Netopia 3347NWG
> >> >> >> > http://portforward.com/english/route.../SuperSync.htm
> >> >> >> >
> >> >> >> > You will need to forward ports 443, 4125 (both relating to RWW)
> >> >> >> > and
> >> >> >> > 3389
> >> >> >> > (for RDP use) to your SBS external NIC. Then re-run CEICW,
> >> >> >> > enable
> >> >> >> > the
> >> >> >> > firewall, select your services, complete the Web Server
> >> >> >> > Certificate
> >> >> >> > screen
> >> >> >> > and finish the rest of CEICW.
> >> >> >> >
> >> >> >> > IMO, discarding external ping (not being able to ping the router)
> >> >> >> > is
> >> >> >> > a
> >> >> >> > good
> >> >> >> > thing since it makes you a smaller target on the Internet.
> >> >> >> >
> >> >> >> > --
> >> >> >> > Merv Porter [SBS-MVP]
> >> >> >> > ============================
> >> >> >> >
> >> >> >> > "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com>
> >> >> >> > wrote
> >> >> >> > in
> >> >> >> > message
> >> >> >> > news:960F5D02-CBEF-4A02-A2A7-386BA3525606@microsoft.com...
> >> >> >> > >I currently have a Netopia 3347NWG, using PPOE to connect to
> >> >> >> > >Deltacom
> >> >> >> > >(a
> >> >> >> > > local DSL), which is connected to the WAN Ethernet Adapter of
> >> >> >> > > an
> >> >> >> > > SBS
> >> >> >> > > 2003
> >> >> >> > > Premium R1 (ISA not installed). The LAN Ethernet Adapter (of
> >> >> >> > > the
> >> >> >> > > SBS) is
> >> >> >> > > set
> >> >> >> > > to 192.168.16.2 and is connected to a switch into which is
> >> >> >> > > connected
> >> >> >> > > the
> >> >> >> > > rest
> >> >> >> > > of the office network.
> >> >> >> > >
> >> >> >> > > IP passthrough is enabled in the Netopia's Expert -
> >> >> >> > > Configuration
> >> >> >> > > section
> >> >> >> > > to
> >> >> >> > > User Configured PC, and the WAN Ethernet Adapter has the static
> >> >> >> > > IP
> >> >> >> > > address
> >> >> >> > > (72.xxx.xxx.xxx).
> >> >> >> > >
> >> >> >> > > Despite that, external ping and RWW and RDP will not work.
> >> >> >> > >
> >> >> >> > > Internally, I can use Remote Desktop from a workstation to
> >> >> >> > > access
> >> >> >> > > the
> >> >> >> > > server
> >> >> >> > > (via Remote Desktop Connection). I can also ping the server,
> >> >> >> > > on
> >> >> >> > > either
> >> >> >> > > the
> >> >> >> > > WAN or LAN adapter.
> >> >> >> > >
> >> >> >> > > If I try to access RWW from the workstation via
> >> >> >> > > https://sbs2003/Remote, I
> >> >> >> > > get "Internet Explorer cannot display this webpage".
> >> >> >> > >
> >> >> >> > > If I try to access RWW from a workstation in the LAN via
> >> >> >> > > https://192.168.16.2/Remote, I get "There is a problem with
> >> >> >> > > this
> >> >> >> > > website's
> >> >> >> > > security certificate", and if I then click "Continue to this
> >> >> >> > > website
> >> >> >> > > (not
> >> >> >> > > recommended)", I get "The page cannot be found" (HTTP error
> >> >> >> > > 404).
> >> >> >> > >
> >> >> >> > > In IIS Admin, Default Website is running and can be browsed;
> >> >> >> > > companyweb
> >> >> >> > > also
> >> >> >> > > is running and can be browsed.
> >> >> >> > >
> >> >> >> > > Remote Access directly into the Netopia setup works, via
> >> >> >> > > http://72.xxx.xxx.xxx:8080.
> >> >> >> > >
> >> >> >> > > Obviously, this needs to be changed, but prior message strings
> >> >> >> > > refer
> >> >> >> > > to
> >> >> >> > > configuration settings which do not seem to be present on this
> >> >> >> > > Netopia
> >> >> >> > > model.
> >> >> >> > >
> >> >> >> > > There is a telnet access available to this Netopia, from a
> >> >> >> > > local
> >> >> >> > > workstation, which seems to provide a lot more options -- with
> >> >> >> > > little
> >> >> >> > > helpful
> >> >> >> > > instruction. The userguide for the 3300 series models refers
> >> >> >> > > to
> >> >> >> > > nice
> >> >> >> > > menus
> >> >> >> > > appearing in the telnet session, but all I see are line-by-line
> >> >> >> > > responses.
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

What if you now go back to...

Error message when you try to access the Remote Web Workplace in Windows
Small Business Server 2003: "You are not authorized to view this page"
http://support.microsoft.com/kb/925653

Also. make sure the default web site and its vritual directories are set to
use .Net Framework 1.1 (not 2.0)

OWA and RWW not accessible.
http://groups.google.com/group/micro...e8e7fea60c5efc

--
Merv Porter [SBS-MVP]
============================
"Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
message news:255EB5C7-DEF9-4EA0-B19D-6EB499A9969D@microsoft.com...
>I follow these directions from that link:
>
> "If SBS is already installed then you should be able to go to
> Start/Control
> Panel/Add/Remove Programs and select Windows Small Business Server 2003
> then
> click on the Change/Remove button.. then follow the setup wizard screens
> until you get to the Component Selection screen.. then select Reinstall
> for
> the Server Tools option.. You can set the Server Tools subcomponents to
> None
> (Installed) they should not need to be re-installed. RWW should be
> re-installed by simply reinstalling the top level of the Server Tools..
> it's not listed as a seperated component like Intranet is (which installs
> Windows SharePoint Services and does the SBS provisioning) "
>
> ...and I got this error before it finished:
> ---------------------------
> .NET Framework 1.1 -- Device Update 2.0
> ---------------------------
> Command line option syntax error. Type Command /? for Help.
> ---------------------------
> OK
> ---------------------------
> However, it finished otherwise, and did not report any problem. It
> brought
> up a box that said the server had to reboot, but before I clicked OK, I
> checked in IIS Admin, and the "Remote" web site under Default Web Site was
> now listed.
>
> I then clicked OK, which rebooted the server.
>
> When it returned, I could right-click the "Remote" website under Default
> Web
> Site, and "browse", and see the RWW login page.
>
> However, when I attempted to access it from an external computer (after
> logging out of RDC), I got "You are not authorized to view this page".
>
>
> "Merv Porter [SBS-MVP]" wrote:
>
>> Try this...
>>
>> Reinstall Remote Web
>> http://groups.google.com/group/micro...0a07e39aca4540
>>
>> --
>> Merv Porter [SBS-MVP]
>> ============================
>>
>> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
>> message news:465CE79D-647C-4E8F-826D-85C5765D89DB@microsoft.com...
>> > Yes, that helped somewhat, as I found that the "Remote" Web Site (under
>> > Default Web Site) is missing. That might explain the "Page cannot be
>> > found"
>> > errors. How can I get this created?
>> >
>> > "Merv Porter [SBS-MVP]" wrote:
>> >
>> >> Any help here?
>> >>
>> >> Error message when you try to access the Remote Web Workplace in
>> >> Windows
>> >> Small Business Server 2003: "You are not authorized to view this page"
>> >> http://support.microsoft.com/kb/925653
>> >>
>> >> --
>> >> Merv Porter [SBS-MVP]
>> >> ============================
>> >>
>> >> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote
>> >> in
>> >> message news:79148A29-E272-4BA8-BE8E-EE0C09E9CA11@microsoft.com...
>> >> > My server's FQDN (as stated on its Web Server Certificiate and in
>> >> > the A
>> >> > record of the hosting company's DNS entries) is
>> >> > sbs2003.thenameofthecompanygoeshere.com, so the address that I have
>> >> > been
>> >> > using to try to get to RWW is
>> >> > https://sbs2003.thenameofthecompanygoeshere.com/remote. However, if
>> >> > the
>> >> > IP
>> >> > address restriction for the Default Website is changed back to
>> >> > normal,
>> >> > when
>> >> > trying to use RWW, I get "You are not authorized to view this page";
>> >> > with
>> >> > the
>> >> > restrictions lifted, I get "Page cannot be found". Pinging
>> >> > "sbs2003.thenameofthecompanygoeshere.com" results in the static IP
>> >> > assigned
>> >> > by the ISP, 72.xxx.xxx.xxx, and (JUST AS A TEMPORARY TEST) with the
>> >> > permission restrictions lifted on Default Website,
>> >> > http://sbs2003.thenameofthecompanygoeshere.com brings up the Default
>> >> > Website
>> >> > externally. This proves that the issue is not DNS related.
>> >> >
>> >> > These ports are properly forwarded to the server's External (WAN)
>> >> > Ethernet
>> >> > adapter (192.168.1.10): 443, 444, 3389, and 4125. Per Susan
>> >> > Bradley's
>> >> > blog,
>> >> > 443 and 4125 are needed for RWW, 444 allows Sharepoint (companyweb)
>> >> > to
>> >> > be
>> >> > reached externally, and 3389 allows Terminal Services (Remote
>> >> > Desktop
>> >> > Connection) externally. As soon as I forwarded 3389, RDC started
>> >> > working
>> >> > to
>> >> > that server from my office laptop.
>> >> >
>> >> > From an internal (LAN) workstation, when trying to go to
>> >> > https://sbs2003/remote, I also get the same results; and on that
>> >> > workstation,
>> >> > while http://companyweb will appear, clicking "Remote Server
>> >> > Management
>> >> > also
>> >> > results in "Page cannot be found". Pinging "sbs2003" from the
>> >> > workstation
>> >> > provides responses from 192.168.16.2 -- the server's LAN address.
>> >> > Opening
>> >> > http://companyweb on the server itself gives the same results.
>> >> >
>> >> >
>> >> > "Merv Porter [SBS-MVP]" wrote:
>> >> >
>> >> >> You should not have to play with the IP address restrictions for
>> >> >> Default
>> >> >> WebSite. You need to forward the proper ports in the router to
>> >> >> your
>> >> >> external SBS NIC. The access RWW via
>> >> >> https://<YourServersFullInternetNameAsInputOnYourWebServerCert>/remote
>> >> >>
>> >> >> Example:
>> >> >> https://mail.mycompany.com/remote
>> >> >>
>> >> >> --
>> >> >> Merv Porter [SBS-MVP]
>> >> >> ============================
>> >> >>
>> >> >> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com>
>> >> >> wrote
>> >> >> in
>> >> >> message news:555A1A7E-56E2-48A8-B9B1-38A948D064AC@microsoft.com...
>> >> >> >I have temporarily changed the IP address restrictions for Default
>> >> >> >WebSite
>> >> >> >in
>> >> >> > IIS Admin, so all are now Granted Access. It is now possible to
>> >> >> > navigate
>> >> >> > to
>> >> >> > http:\\sbs2003.domain.com, and the default website appears.
>> >> >> >
>> >> >> > However, companyweb (My internal website) goes to
>> >> >> > http:\\companyweb,
>> >> >> > which
>> >> >> > of course results in "Internet Explorer cannot display the
>> >> >> > webpage".
>> >> >> >
>> >> >> > All other links (Network Configuration Wizard, Remote Web
>> >> >> > Workplace,
>> >> >> > and
>> >> >> > Information and Answers) bring up "The page cannot be found".
>> >> >> >
>> >> >> > Directly going to https://sbs2003.domain.com/Remote now results
>> >> >> > in
>> >> >> > "The
>> >> >> > page
>> >> >> > cannot be found" instead of the previous "You are not authorized
>> >> >> > to
>> >> >> > view
>> >> >> > this
>> >> >> > page".
>> >> >> >
>> >> >> >
>> >> >> > "Greg Kirkpatrick" wrote:
>> >> >> >
>> >> >> >> I changed IP of the WAN Ethernet adapter in the SBS 2003 to
>> >> >> >> 192.168.1.10,
>> >> >> >> and
>> >> >> >> set the Gateway to the Netopia's IP of 192.168.1.254. I reran
>> >> >> >> CEICW
>> >> >> >> as
>> >> >> >> suggested, including Web Server Certificate.
>> >> >> >>
>> >> >> >> I changed the Netopia 3347NWG, so IP Passthrough is disabled,
>> >> >> >> and I
>> >> >> >> rebooted
>> >> >> >> it. I then defined these new services in the Netopia's Expert
>> >> >> >> Mode
>> >> >> >> /
>> >> >> >> Configure / NAT -- SSL (port 443), Terminal Services (port
>> >> >> >> 3389),
>> >> >> >> and
>> >> >> >> Remote
>> >> >> >> Web Workplace (port 4125). I enabled each of these services
>> >> >> >> there,
>> >> >> >> pointing
>> >> >> >> them to 192.168.1.10.
>> >> >> >>
>> >> >> >> Remote Desktop Connection is now working to sbs2003.domain.com.
>> >> >> >>
>> >> >> >> However, when I attempt externally to go to
>> >> >> >> http://sbs2003.domain.com/Remote, I get "You are not authorized
>> >> >> >> to
>> >> >> >> view
>> >> >> >> this
>> >> >> >> page". Obviously, it is making a connection, but something is
>> >> >> >> wrong
>> >> >> >> for
>> >> >> >> RWW
>> >> >> >> in the server.
>> >> >> >>
>> >> >> >> "Merv Porter [SBS-MVP]" wrote:
>> >> >> >>
>> >> >> >> > Hi Greg,
>> >> >> >> >
>> >> >> >> > Any help here?
>> >> >> >> >
>> >> >> >> > Port Forwarding for the Netopia 3347NWG
>> >> >> >> > http://portforward.com/english/route.../SuperSync.htm
>> >> >> >> >
>> >> >> >> > You will need to forward ports 443, 4125 (both relating to
>> >> >> >> > RWW)
>> >> >> >> > and
>> >> >> >> > 3389
>> >> >> >> > (for RDP use) to your SBS external NIC. Then re-run CEICW,
>> >> >> >> > enable
>> >> >> >> > the
>> >> >> >> > firewall, select your services, complete the Web Server
>> >> >> >> > Certificate
>> >> >> >> > screen
>> >> >> >> > and finish the rest of CEICW.
>> >> >> >> >
>> >> >> >> > IMO, discarding external ping (not being able to ping the
>> >> >> >> > router)
>> >> >> >> > is
>> >> >> >> > a
>> >> >> >> > good
>> >> >> >> > thing since it makes you a smaller target on the Internet.
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > Merv Porter [SBS-MVP]
>> >> >> >> > ============================
>> >> >> >> >
>> >> >> >> > "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com>
>> >> >> >> > wrote
>> >> >> >> > in
>> >> >> >> > message
>> >> >> >> > news:960F5D02-CBEF-4A02-A2A7-386BA3525606@microsoft.com...
>> >> >> >> > >I currently have a Netopia 3347NWG, using PPOE to connect to
>> >> >> >> > >Deltacom
>> >> >> >> > >(a
>> >> >> >> > > local DSL), which is connected to the WAN Ethernet Adapter
>> >> >> >> > > of
>> >> >> >> > > an
>> >> >> >> > > SBS
>> >> >> >> > > 2003
>> >> >> >> > > Premium R1 (ISA not installed). The LAN Ethernet Adapter
>> >> >> >> > > (of
>> >> >> >> > > the
>> >> >> >> > > SBS) is
>> >> >> >> > > set
>> >> >> >> > > to 192.168.16.2 and is connected to a switch into which is
>> >> >> >> > > connected
>> >> >> >> > > the
>> >> >> >> > > rest
>> >> >> >> > > of the office network.
>> >> >> >> > >
>> >> >> >> > > IP passthrough is enabled in the Netopia's Expert -
>> >> >> >> > > Configuration
>> >> >> >> > > section
>> >> >> >> > > to
>> >> >> >> > > User Configured PC, and the WAN Ethernet Adapter has the
>> >> >> >> > > static
>> >> >> >> > > IP
>> >> >> >> > > address
>> >> >> >> > > (72.xxx.xxx.xxx).
>> >> >> >> > >
>> >> >> >> > > Despite that, external ping and RWW and RDP will not work.
>> >> >> >> > >
>> >> >> >> > > Internally, I can use Remote Desktop from a workstation to
>> >> >> >> > > access
>> >> >> >> > > the
>> >> >> >> > > server
>> >> >> >> > > (via Remote Desktop Connection). I can also ping the
>> >> >> >> > > server,
>> >> >> >> > > on
>> >> >> >> > > either
>> >> >> >> > > the
>> >> >> >> > > WAN or LAN adapter.
>> >> >> >> > >
>> >> >> >> > > If I try to access RWW from the workstation via
>> >> >> >> > > https://sbs2003/Remote, I
>> >> >> >> > > get "Internet Explorer cannot display this webpage".
>> >> >> >> > >
>> >> >> >> > > If I try to access RWW from a workstation in the LAN via
>> >> >> >> > > https://192.168.16.2/Remote, I get "There is a problem with
>> >> >> >> > > this
>> >> >> >> > > website's
>> >> >> >> > > security certificate", and if I then click "Continue to this
>> >> >> >> > > website
>> >> >> >> > > (not
>> >> >> >> > > recommended)", I get "The page cannot be found" (HTTP error
>> >> >> >> > > 404).
>> >> >> >> > >
>> >> >> >> > > In IIS Admin, Default Website is running and can be browsed;
>> >> >> >> > > companyweb
>> >> >> >> > > also
>> >> >> >> > > is running and can be browsed.
>> >> >> >> > >
>> >> >> >> > > Remote Access directly into the Netopia setup works, via
>> >> >> >> > > http://72.xxx.xxx.xxx:8080.
>> >> >> >> > >
>> >> >> >> > > Obviously, this needs to be changed, but prior message
>> >> >> >> > > strings
>> >> >> >> > > refer
>> >> >> >> > > to
>> >> >> >> > > configuration settings which do not seem to be present on
>> >> >> >> > > this
>> >> >> >> > > Netopia
>> >> >> >> > > model.
>> >> >> >> > >
>> >> >> >> > > There is a telnet access available to this Netopia, from a
>> >> >> >> > > local
>> >> >> >> > > workstation, which seems to provide a lot more options --
>> >> >> >> > > with
>> >> >> >> > > little
>> >> >> >> > > helpful
>> >> >> >> > > instruction. The userguide for the 3300 series models
>> >> >> >> > > refers
>> >> >> >> > > to
>> >> >> >> > > nice
>> >> >> >> > > menus
>> >> >> >> > > appearing in the telnet session, but all I see are
>> >> >> >> > > line-by-line
>> >> >> >> > > responses.
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>

This is the pertintent text from KB925653:
--------------------------------------------------------------------------------
In this situation, the default.aspx page is not added to the list of default
content pages for the remote virtual directory in IIS.

RESOLUTION
To resolve this issue, follow these steps:
1. Click Start, point to Administrative Tools, and then click Internet
Information Services (IIS) Manager.
2. Under ComputerName (local computer), expand Web Sites, expand Default Web
Site, right-click Remote, and then click Properties.
3. In the Remote Properties dialog box, click the Documents tab, and then
click Add.
4. In the Add Content Page dialog box, type default.aspx in the Default
content page box, and then click OK two times.
--------------------------------------------------------------------------------
APPLIES TO
• Microsoft Windows Small Business Server 2003 Premium Edition
• Microsoft Windows Small Business Server 2003 Standard Edition

Keywords: kbtshoot kbprb KB925653
--------------------------------------------------------------------------------

When I checked, there was a Default.aspx created in the Documents of the
Remote properties, but it was listed last. I deleted it, and recreated it as
default.aspx, and moved it to the top of the list. However, when I attempted
to access RWW via an external computer, I got the same "You are not
authorized to view this page".

I then looked at this message:

OWA and RWW not accessible.
http://groups.google.com/group/micro...e8e7fea60c5efc
--------------------------------------------------------------------------------
[quoting Robert Li of MSFT]:

"All Windows Small Business Server Website and Virtual Directories work only
with .Net Framework 1.1 and are no support with 2.0

- Default website
- Exchange (OWA)
- Remote (RWW)
- ActiveSync
- OMA and all
- Companyweb
- SharePoint Central Administration
- Microsoft SharePoint Administration"


1. Open Internet Information Services (IIS) Manager
2. Expand to Server | Web Sites | Default Web Sites
3. Right click the each web site and select Properties.
4. On the ASP.NET tab, make sure the version is 1.1.4322.
--------------------------------------------------------------------------------

I will not install .NET Framework 2.0 or 3.0 or 3.5 -- I don't want
companyweb and Monitoring to break again.

However, when I checked the properties for Default Web Site, .NET Framework
2.0 was installed (the ASP.NET tab was there) -- something must done it.
ARGH! I have uninstalled .NET 2.0 Framework.

Now, the ASP.NET tab is not present in the properties for Default Web Site
or any virtual directories, so they have to be using 1.1.

I found, in the messages you referenced, a mention of the ASP.NET IIS
Registration Tool (Aspnet_regiis.exe):
http://msdn.microsoft.com/en-us/library/k6h9cz8h.aspx

This is a GREAT command-prompt tool, as it confirms exactly what is mapped
to where instantly:
%WINDIR%\Microsoft.NET\Framework\v1.1.4322\Aspnet_regiis.exe -lk

It also gives a way, via command-prompt commands, to change what is needed.

I think it is tragic that, as Robert Li of MSFT says:

"When installing .NET Framework 2.0 on Windows Small Business Server,
all the websites are automatically switched to use .NET Framework 2.0 which
they are not intended to work with."

This is a recipe for disaster!
Especially since so many other programs, including "WSUS 3.0", require .NET
Framework 2.0.

Why is there NO WARNING GIVEN when installing .NET Framework 2.0 (or 3.0 or
3.5) on SBS 2003?
[This is a rhetorical question, as I don't expect you to answer it.]

Some progress is being made, however:

When I navigate to http://sbs2003.domain.com/ and see the Default Web Site
(as permissions are still, temporarily, unrestricted), I can now click on
Information and Answers and see http://sbs2003.domain.com/ClientHelp and its
sub-pages -- which previously gave me "The page cannot be found".

Clicking on Network Configuration Wizard still gets
http://sbs2003.domain.com/ConnectComputer -- "The page cannot be found".

Clicking on Remote Web Workplace still gets http://sbs2003.domain.com/Remote
-- "You are not authorized to view this page". Changing that to
https://sbs2003.domain.com/Remote has the same result.

Since some parts of an uninstall wait for a reboot, I rebooted the server,
just to see whether that would make any difference. It didn't.



"Merv Porter [SBS-MVP]" wrote:

> What if you now go back to...
>
> Error message when you try to access the Remote Web Workplace in Windows
> Small Business Server 2003: "You are not authorized to view this page"
> http://support.microsoft.com/kb/925653
>
> Also. make sure the default web site and its vritual directories are set to
> use .Net Framework 1.1 (not 2.0)
>
> OWA and RWW not accessible.
> http://groups.google.com/group/micro...e8e7fea60c5efc
>
> --
> Merv Porter [SBS-MVP]
> ============================
> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
> message news:255EB5C7-DEF9-4EA0-B19D-6EB499A9969D@microsoft.com...
> >I follow these directions from that link:
> >
> > "If SBS is already installed then you should be able to go to
> > Start/Control
> > Panel/Add/Remove Programs and select Windows Small Business Server 2003
> > then
> > click on the Change/Remove button.. then follow the setup wizard screens
> > until you get to the Component Selection screen.. then select Reinstall
> > for
> > the Server Tools option.. You can set the Server Tools subcomponents to
> > None
> > (Installed) they should not need to be re-installed. RWW should be
> > re-installed by simply reinstalling the top level of the Server Tools..
> > it's not listed as a seperated component like Intranet is (which installs
> > Windows SharePoint Services and does the SBS provisioning) "
> >
> > ...and I got this error before it finished:
> > ---------------------------
> > .NET Framework 1.1 -- Device Update 2.0
> > ---------------------------
> > Command line option syntax error. Type Command /? for Help.
> > ---------------------------
> > OK
> > ---------------------------
> > However, it finished otherwise, and did not report any problem. It
> > brought
> > up a box that said the server had to reboot, but before I clicked OK, I
> > checked in IIS Admin, and the "Remote" web site under Default Web Site was
> > now listed.
> >
> > I then clicked OK, which rebooted the server.
> >
> > When it returned, I could right-click the "Remote" website under Default
> > Web
> > Site, and "browse", and see the RWW login page.
> >
> > However, when I attempted to access it from an external computer (after
> > logging out of RDC), I got "You are not authorized to view this page".
> >
> >
> > "Merv Porter [SBS-MVP]" wrote:
> >
> >> Try this...
> >>
> >> Reinstall Remote Web
> >> http://groups.google.com/group/micro...0a07e39aca4540
> >>
> >> --
> >> Merv Porter [SBS-MVP]
> >> ============================
> >>
> >> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
> >> message news:465CE79D-647C-4E8F-826D-85C5765D89DB@microsoft.com...
> >> > Yes, that helped somewhat, as I found that the "Remote" Web Site (under
> >> > Default Web Site) is missing. That might explain the "Page cannot be
> >> > found"
> >> > errors. How can I get this created?
> >> >
> >> > "Merv Porter [SBS-MVP]" wrote:
> >> >
> >> >> Any help here?
> >> >>
> >> >> Error message when you try to access the Remote Web Workplace in
> >> >> Windows
> >> >> Small Business Server 2003: "You are not authorized to view this page"
> >> >> http://support.microsoft.com/kb/925653
> >> >>
> >> >> --
> >> >> Merv Porter [SBS-MVP]
> >> >> ============================
> >> >>
> >> >> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote
> >> >> in
> >> >> message news:79148A29-E272-4BA8-BE8E-EE0C09E9CA11@microsoft.com...
> >> >> > My server's FQDN (as stated on its Web Server Certificiate and in
> >> >> > the A
> >> >> > record of the hosting company's DNS entries) is
> >> >> > sbs2003.thenameofthecompanygoeshere.com, so the address that I have
> >> >> > been
> >> >> > using to try to get to RWW is
> >> >> > https://sbs2003.thenameofthecompanygoeshere.com/remote. However, if
> >> >> > the
> >> >> > IP
> >> >> > address restriction for the Default Website is changed back to
> >> >> > normal,
> >> >> > when
> >> >> > trying to use RWW, I get "You are not authorized to view this page";
> >> >> > with
> >> >> > the
> >> >> > restrictions lifted, I get "Page cannot be found". Pinging
> >> >> > "sbs2003.thenameofthecompanygoeshere.com" results in the static IP
> >> >> > assigned
> >> >> > by the ISP, 72.xxx.xxx.xxx, and (JUST AS A TEMPORARY TEST) with the
> >> >> > permission restrictions lifted on Default Website,
> >> >> > http://sbs2003.thenameofthecompanygoeshere.com brings up the Default
> >> >> > Website
> >> >> > externally. This proves that the issue is not DNS related.
> >> >> >
> >> >> > These ports are properly forwarded to the server's External (WAN)
> >> >> > Ethernet
> >> >> > adapter (192.168.1.10): 443, 444, 3389, and 4125. Per Susan
> >> >> > Bradley's
> >> >> > blog,
> >> >> > 443 and 4125 are needed for RWW, 444 allows Sharepoint (companyweb)
> >> >> > to
> >> >> > be
> >> >> > reached externally, and 3389 allows Terminal Services (Remote
> >> >> > Desktop
> >> >> > Connection) externally. As soon as I forwarded 3389, RDC started
> >> >> > working
> >> >> > to
> >> >> > that server from my office laptop.
> >> >> >
> >> >> > From an internal (LAN) workstation, when trying to go to
> >> >> > https://sbs2003/remote, I also get the same results; and on that
> >> >> > workstation,
> >> >> > while http://companyweb will appear, clicking "Remote Server
> >> >> > Management
> >> >> > also
> >> >> > results in "Page cannot be found". Pinging "sbs2003" from the
> >> >> > workstation
> >> >> > provides responses from 192.168.16.2 -- the server's LAN address.
> >> >> > Opening
> >> >> > http://companyweb on the server itself gives the same results.
> >> >> >
> >> >> >
> >> >> > "Merv Porter [SBS-MVP]" wrote:
> >> >> >
> >> >> >> You should not have to play with the IP address restrictions for
> >> >> >> Default
> >> >> >> WebSite. You need to forward the proper ports in the router to
> >> >> >> your
> >> >> >> external SBS NIC. The access RWW via
> >> >> >> https://<YourServersFullInternetNameAsInputOnYourWebServerCert>/remote
> >> >> >>
> >> >> >> Example:
> >> >> >> https://mail.mycompany.com/remote
> >> >> >>
> >> >> >> --
> >> >> >> Merv Porter [SBS-MVP]
> >> >> >> ============================
> >> >> >>
> >> >> >> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com>
> >> >> >> wrote
> >> >> >> in
> >> >> >> message news:555A1A7E-56E2-48A8-B9B1-38A948D064AC@microsoft.com...
> >> >> >> >I have temporarily changed the IP address restrictions for Default
> >> >> >> >WebSite
> >> >> >> >in
> >> >> >> > IIS Admin, so all are now Granted Access. It is now possible to
> >> >> >> > navigate
> >> >> >> > to
> >> >> >> > http:\\sbs2003.domain.com, and the default website appears.
> >> >> >> >
> >> >> >> > However, companyweb (My internal website) goes to
> >> >> >> > http:\\companyweb,
> >> >> >> > which
> >> >> >> > of course results in "Internet Explorer cannot display the
> >> >> >> > webpage".
> >> >> >> >
> >> >> >> > All other links (Network Configuration Wizard, Remote Web
> >> >> >> > Workplace,
> >> >> >> > and
> >> >> >> > Information and Answers) bring up "The page cannot be found".
> >> >> >> >
> >> >> >> > Directly going to https://sbs2003.domain.com/Remote now results
> >> >> >> > in
> >> >> >> > "The
> >> >> >> > page
> >> >> >> > cannot be found" instead of the previous "You are not authorized
> >> >> >> > to
> >> >> >> > view
> >> >> >> > this
> >> >> >> > page".
> >> >> >> >
> >> >> >> >
> >> >> >> > "Greg Kirkpatrick" wrote:
> >> >> >> >
> >> >> >> >> I changed IP of the WAN Ethernet adapter in the SBS 2003 to
> >> >> >> >> 192.168.1.10,
> >> >> >> >> and
> >> >> >> >> set the Gateway to the Netopia's IP of 192.168.1.254. I reran
> >> >> >> >> CEICW
> >> >> >> >> as
> >> >> >> >> suggested, including Web Server Certificate.
> >> >> >> >>
> >> >> >> >> I changed the Netopia 3347NWG, so IP Passthrough is disabled,
> >> >> >> >> and I
> >> >> >> >> rebooted
> >> >> >> >> it. I then defined these new services in the Netopia's Expert
> >> >> >> >> Mode
> >> >> >> >> /
> >> >> >> >> Configure / NAT -- SSL (port 443), Terminal Services (port
> >> >> >> >> 3389),
> >> >> >> >> and
> >> >> >> >> Remote
> >> >> >> >> Web Workplace (port 4125). I enabled each of these services
> >> >> >> >> there,
> >> >> >> >> pointing
> >> >> >> >> them to 192.168.1.10.
> >> >> >> >>
> >> >> >> >> Remote Desktop Connection is now working to sbs2003.domain.com.
> >> >> >> >>
> >> >> >> >> However, when I attempt externally to go to
> >> >> >> >> http://sbs2003.domain.com/Remote, I get "You are not authorized
> >> >> >> >> to
> >> >> >> >> view
> >> >> >> >> this
> >> >> >> >> page". Obviously, it is making a connection, but something is
> >> >> >> >> wrong
> >> >> >> >> for
> >> >> >> >> RWW
> >> >> >> >> in the server.
> >> >> >> >>
> >> >> >> >> "Merv Porter [SBS-MVP]" wrote:
> >> >> >> >>
> >> >> >> >> > Hi Greg,
> >> >> >> >> >
> >> >> >> >> > Any help here?
> >> >> >> >> >
> >> >> >> >> > Port Forwarding for the Netopia 3347NWG
> >> >> >> >> > http://portforward.com/english/route.../SuperSync.htm
> >> >> >> >> >
> >> >> >> >> > You will need to forward ports 443, 4125 (both relating to
> >> >> >> >> > RWW)
> >> >> >> >> > and
> >> >> >> >> > 3389
> >> >> >> >> > (for RDP use) to your SBS external NIC. Then re-run CEICW,
> >> >> >> >> > enable
> >> >> >> >> > the
> >> >> >> >> > firewall, select your services, complete the Web Server
> >> >> >> >> > Certificate
> >> >> >> >> > screen
> >> >> >> >> > and finish the rest of CEICW.
> >> >> >> >> >
> >> >> >> >> > IMO, discarding external ping (not being able to ping the
> >> >> >> >> > router)
> >> >> >> >> > is
> >> >> >> >> > a
> >> >> >> >> > good
> >> >> >> >> > thing since it makes you a smaller target on the Internet.
> >> >> >> >> >
> >> >> >> >> > --
> >> >> >> >> > Merv Porter [SBS-MVP]
> >> >> >> >> > ============================
> >> >> >> >> >
> >> >> >> >> > "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com>
> >> >> >> >> > wrote
> >> >> >> >> > in
> >> >> >> >> > message
> >> >> >> >> > news:960F5D02-CBEF-4A02-A2A7-386BA3525606@microsoft.com...
> >> >> >> >> > >I currently have a Netopia 3347NWG, using PPOE to connect to
> >> >> >> >> > >Deltacom
> >> >> >> >> > >(a
> >> >> >> >> > > local DSL), which is connected to the WAN Ethernet Adapter
> >> >> >> >> > > of
> >> >> >> >> > > an
> >> >> >> >> > > SBS
> >> >> >> >> > > 2003
> >> >> >> >> > > Premium R1 (ISA not installed). The LAN Ethernet Adapter
> >> >> >> >> > > (of
> >> >> >> >> > > the
> >> >> >> >> > > SBS) is
> >> >> >> >> > > set
> >> >> >> >> > > to 192.168.16.2 and is connected to a switch into which is
> >> >> >> >> > > connected
> >> >> >> >> > > the
> >> >> >> >> > > rest
> >> >> >> >> > > of the office network.
> >> >> >> >> > >
> >> >> >> >> > > IP passthrough is enabled in the Netopia's Expert -
> >> >> >> >> > > Configuration
> >> >> >> >> > > section
> >> >> >> >> > > to
> >> >> >> >> > > User Configured PC, and the WAN Ethernet Adapter has the
> >> >> >> >> > > static
> >> >> >> >> > > IP
> >> >> >> >> > > address
> >> >> >> >> > > (72.xxx.xxx.xxx).
> >> >> >> >> > >
> >> >> >> >> > > Despite that, external ping and RWW and RDP will not work.
> >> >> >> >> > >
> >> >> >> >> > > Internally, I can use Remote Desktop from a workstation to

I beg your pardon.

Further testing reveals that the command example I provided will only work
if nothing higher than .NET Framework 1.1 is installed on your computer. If
2.0 or higher are installed, then aspnet_regiis.exe might be located in
another directory. Here is a better way to find it:

cd /d %WINDIR%\Microsoft.NET\Framework
dir aspnet_regiis.exe /s

then change to the directory in which it's located:
cd v2.0.50727

then run this command:
aspnet_regiis.exe -lk

This will give you a report listing all the programs using .NET Framework,
and which version.

I have compared this SBS 2003 server with another one on which RWW is running
fine.
These are some of the differences:

In the non-working-RWW server (sbs2003), in the properties of the Default
Web Site, under Home Directory, the Execute Permissions were set to "Scripts
only", while on the working-RWW server (win2003), it was set to "Scripts and
Executables". On sbs2003, the Application Pool was set to StsAppPool1; on
win2003, it is set to DefaultAppPool. On win2003, the Documents tab shows
four items: Default.htm, Default.asp, index.htm, and iistart.htm. On
sbs2003, there was a fifth (last) item: Default.aspx. On sbs2003, the ISAPI
Filters tab shows SBSFLT with High Priority, followed by fpexedll.dll with
Low Priority, and Owalogon with "Unknown" priority. On win2003, the same,
except SBSFLT is not listed. On sbs2003, HTTP Headers tab has "Enable
content expiration" checked, and "Expire after 30 days" selected. On
win2003, that is not checked; and under Custom Web Header, win2003 has listed
MicrosoftOfficeWebServer: 5.0_Pub and XP-Powered-By: ASP.NET. On sbs2003,
only XP-Powered-By: ASP.NET is listed. On win2003, on the Server Extensions
2003 tab, it says "Microsoft SharePoint is installed on this site. Version
5.0.2.6790. On sbs2003, it says: This server has not been configured to use
the server extensions.

I configured the server extensions for the Default Web Site under sbs2003,
and made changes to mimic the settings on win2003. However, I am still
getting "you are not authorized to view this page" when I attempt to access
https://sbs2003.domain.com/Remote.



"Greg Kirkpatrick" wrote:

> This is the pertintent text from KB925653:
> --------------------------------------------------------------------------------
> In this situation, the default.aspx page is not added to the list of default
> content pages for the remote virtual directory in IIS.
>
> RESOLUTION
> To resolve this issue, follow these steps:
> 1. Click Start, point to Administrative Tools, and then click Internet
> Information Services (IIS) Manager.
> 2. Under ComputerName (local computer), expand Web Sites, expand Default Web
> Site, right-click Remote, and then click Properties.
> 3. In the Remote Properties dialog box, click the Documents tab, and then
> click Add.
> 4. In the Add Content Page dialog box, type default.aspx in the Default
> content page box, and then click OK two times.
> --------------------------------------------------------------------------------
> APPLIES TO
> • Microsoft Windows Small Business Server 2003 Premium Edition
> • Microsoft Windows Small Business Server 2003 Standard Edition
>
> Keywords: kbtshoot kbprb KB925653
> --------------------------------------------------------------------------------
>
> When I checked, there was a Default.aspx created in the Documents of the
> Remote properties, but it was listed last. I deleted it, and recreated it as
> default.aspx, and moved it to the top of the list. However, when I attempted
> to access RWW via an external computer, I got the same "You are not
> authorized to view this page".
>
> I then looked at this message:
>
> OWA and RWW not accessible.
> http://groups.google.com/group/micro...e8e7fea60c5efc
> --------------------------------------------------------------------------------
> [quoting Robert Li of MSFT]:
>
> "All Windows Small Business Server Website and Virtual Directories work only
> with .Net Framework 1.1 and are no support with 2.0
>
> - Default website
> - Exchange (OWA)
> - Remote (RWW)
> - ActiveSync
> - OMA and all
> - Companyweb
> - SharePoint Central Administration
> - Microsoft SharePoint Administration"
>
>
> 1. Open Internet Information Services (IIS) Manager
> 2. Expand to Server | Web Sites | Default Web Sites
> 3. Right click the each web site and select Properties.
> 4. On the ASP.NET tab, make sure the version is 1.1.4322.
> --------------------------------------------------------------------------------
>
> I will not install .NET Framework 2.0 or 3.0 or 3.5 -- I don't want
> companyweb and Monitoring to break again.
>
> However, when I checked the properties for Default Web Site, .NET Framework
> 2.0 was installed (the ASP.NET tab was there) -- something must done it.
> ARGH! I have uninstalled .NET 2.0 Framework.
>
> Now, the ASP.NET tab is not present in the properties for Default Web Site
> or any virtual directories, so they have to be using 1.1.
>
> I found, in the messages you referenced, a mention of the ASP.NET IIS
> Registration Tool (Aspnet_regiis.exe):
> http://msdn.microsoft.com/en-us/library/k6h9cz8h.aspx
>
> This is a GREAT command-prompt tool, as it confirms exactly what is mapped
> to where instantly:
> %WINDIR%\Microsoft.NET\Framework\v1.1.4322\Aspnet_regiis.exe -lk
>
> It also gives a way, via command-prompt commands, to change what is needed.
>
> I think it is tragic that, as Robert Li of MSFT says:
>
> "When installing .NET Framework 2.0 on Windows Small Business Server,
> all the websites are automatically switched to use .NET Framework 2.0 which
> they are not intended to work with."
>
> This is a recipe for disaster!
> Especially since so many other programs, including "WSUS 3.0", require .NET
> Framework 2.0.
>
> Why is there NO WARNING GIVEN when installing .NET Framework 2.0 (or 3.0 or
> 3.5) on SBS 2003?
> [This is a rhetorical question, as I don't expect you to answer it.]
>
> Some progress is being made, however:
>
> When I navigate to http://sbs2003.domain.com/ and see the Default Web Site
> (as permissions are still, temporarily, unrestricted), I can now click on
> Information and Answers and see http://sbs2003.domain.com/ClientHelp and its
> sub-pages -- which previously gave me "The page cannot be found".
>
> Clicking on Network Configuration Wizard still gets
> http://sbs2003.domain.com/ConnectComputer -- "The page cannot be found".
>
> Clicking on Remote Web Workplace still gets http://sbs2003.domain.com/Remote
> -- "You are not authorized to view this page". Changing that to
> https://sbs2003.domain.com/Remote has the same result.
>
> Since some parts of an uninstall wait for a reboot, I rebooted the server,
> just to see whether that would make any difference. It didn't.
>
>
>
> "Merv Porter [SBS-MVP]" wrote:
>
> > What if you now go back to...
> >
> > Error message when you try to access the Remote Web Workplace in Windows
> > Small Business Server 2003: "You are not authorized to view this page"
> > http://support.microsoft.com/kb/925653
> >
> > Also. make sure the default web site and its vritual directories are set to
> > use .Net Framework 1.1 (not 2.0)
> >
> > OWA and RWW not accessible.
> > http://groups.google.com/group/micro...e8e7fea60c5efc
> >
> > --
> > Merv Porter [SBS-MVP]
> > ============================
> > "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
> > message news:255EB5C7-DEF9-4EA0-B19D-6EB499A9969D@microsoft.com...
> > >I follow these directions from that link:
> > >
> > > "If SBS is already installed then you should be able to go to
> > > Start/Control
> > > Panel/Add/Remove Programs and select Windows Small Business Server 2003
> > > then
> > > click on the Change/Remove button.. then follow the setup wizard screens
> > > until you get to the Component Selection screen.. then select Reinstall
> > > for
> > > the Server Tools option.. You can set the Server Tools subcomponents to
> > > None
> > > (Installed) they should not need to be re-installed. RWW should be
> > > re-installed by simply reinstalling the top level of the Server Tools..
> > > it's not listed as a seperated component like Intranet is (which installs
> > > Windows SharePoint Services and does the SBS provisioning) "
> > >
> > > ...and I got this error before it finished:
> > > ---------------------------
> > > .NET Framework 1.1 -- Device Update 2.0
> > > ---------------------------
> > > Command line option syntax error. Type Command /? for Help.
> > > ---------------------------
> > > OK
> > > ---------------------------
> > > However, it finished otherwise, and did not report any problem. It
> > > brought
> > > up a box that said the server had to reboot, but before I clicked OK, I
> > > checked in IIS Admin, and the "Remote" web site under Default Web Site was
> > > now listed.
> > >
> > > I then clicked OK, which rebooted the server.
> > >
> > > When it returned, I could right-click the "Remote" website under Default
> > > Web
> > > Site, and "browse", and see the RWW login page.
> > >
> > > However, when I attempted to access it from an external computer (after
> > > logging out of RDC), I got "You are not authorized to view this page".
> > >
> > >
> > > "Merv Porter [SBS-MVP]" wrote:
> > >
> > >> Try this...
> > >>
> > >> Reinstall Remote Web
> > >> http://groups.google.com/group/micro...0a07e39aca4540
> > >>
> > >> --
> > >> Merv Porter [SBS-MVP]
> > >> ============================
> > >>
> > >> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
> > >> message news:465CE79D-647C-4E8F-826D-85C5765D89DB@microsoft.com...
> > >> > Yes, that helped somewhat, as I found that the "Remote" Web Site (under
> > >> > Default Web Site) is missing. That might explain the "Page cannot be
> > >> > found"
> > >> > errors. How can I get this created?
> > >> >
> > >> > "Merv Porter [SBS-MVP]" wrote:
> > >> >
> > >> >> Any help here?
> > >> >>
> > >> >> Error message when you try to access the Remote Web Workplace in
> > >> >> Windows
> > >> >> Small Business Server 2003: "You are not authorized to view this page"
> > >> >> http://support.microsoft.com/kb/925653
> > >> >>
> > >> >> --
> > >> >> Merv Porter [SBS-MVP]
> > >> >> ============================
> > >> >>
> > >> >> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote
> > >> >> in
> > >> >> message news:79148A29-E272-4BA8-BE8E-EE0C09E9CA11@microsoft.com...
> > >> >> > My server's FQDN (as stated on its Web Server Certificiate and in
> > >> >> > the A
> > >> >> > record of the hosting company's DNS entries) is
> > >> >> > sbs2003.thenameofthecompanygoeshere.com, so the address that I have
> > >> >> > been
> > >> >> > using to try to get to RWW is
> > >> >> > https://sbs2003.thenameofthecompanygoeshere.com/remote. However, if
> > >> >> > the
> > >> >> > IP
> > >> >> > address restriction for the Default Website is changed back to
> > >> >> > normal,
> > >> >> > when
> > >> >> > trying to use RWW, I get "You are not authorized to view this page";
> > >> >> > with
> > >> >> > the
> > >> >> > restrictions lifted, I get "Page cannot be found". Pinging
> > >> >> > "sbs2003.thenameofthecompanygoeshere.com" results in the static IP
> > >> >> > assigned
> > >> >> > by the ISP, 72.xxx.xxx.xxx, and (JUST AS A TEMPORARY TEST) with the
> > >> >> > permission restrictions lifted on Default Website,
> > >> >> > http://sbs2003.thenameofthecompanygoeshere.com brings up the Default
> > >> >> > Website
> > >> >> > externally. This proves that the issue is not DNS related.
> > >> >> >
> > >> >> > These ports are properly forwarded to the server's External (WAN)
> > >> >> > Ethernet
> > >> >> > adapter (192.168.1.10): 443, 444, 3389, and 4125. Per Susan
> > >> >> > Bradley's
> > >> >> > blog,
> > >> >> > 443 and 4125 are needed for RWW, 444 allows Sharepoint (companyweb)
> > >> >> > to
> > >> >> > be
> > >> >> > reached externally, and 3389 allows Terminal Services (Remote
> > >> >> > Desktop
> > >> >> > Connection) externally. As soon as I forwarded 3389, RDC started
> > >> >> > working
> > >> >> > to
> > >> >> > that server from my office laptop.
> > >> >> >
> > >> >> > From an internal (LAN) workstation, when trying to go to
> > >> >> > https://sbs2003/remote, I also get the same results; and on that
> > >> >> > workstation,
> > >> >> > while http://companyweb will appear, clicking "Remote Server
> > >> >> > Management
> > >> >> > also
> > >> >> > results in "Page cannot be found". Pinging "sbs2003" from the
> > >> >> > workstation
> > >> >> > provides responses from 192.168.16.2 -- the server's LAN address.
> > >> >> > Opening
> > >> >> > http://companyweb on the server itself gives the same results.
> > >> >> >
> > >> >> >
> > >> >> > "Merv Porter [SBS-MVP]" wrote:
> > >> >> >
> > >> >> >> You should not have to play with the IP address restrictions for
> > >> >> >> Default
> > >> >> >> WebSite. You need to forward the proper ports in the router to
> > >> >> >> your
> > >> >> >> external SBS NIC. The access RWW via
> > >> >> >> https://<YourServersFullInternetNameAsInputOnYourWebServerCert>/remote
> > >> >> >>
> > >> >> >> Example:
> > >> >> >> https://mail.mycompany.com/remote
> > >> >> >>
> > >> >> >> --
> > >> >> >> Merv Porter [SBS-MVP]
> > >> >> >> ============================
> > >> >> >>
> > >> >> >> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com>
> > >> >> >> wrote
> > >> >> >> in
> > >> >> >> message news:555A1A7E-56E2-48A8-B9B1-38A948D064AC@microsoft.com...
> > >> >> >> >I have temporarily changed the IP address restrictions for Default
> > >> >> >> >WebSite
> > >> >> >> >in
> > >> >> >> > IIS Admin, so all are now Granted Access. It is now possible to
> > >> >> >> > navigate
> > >> >> >> > to
> > >> >> >> > http:\\sbs2003.domain.com, and the default website appears.
> > >> >> >> >
> > >> >> >> > However, companyweb (My internal website) goes to
> > >> >> >> > http:\\companyweb,
> > >> >> >> > which
> > >> >> >> > of course results in "Internet Explorer cannot display the
> > >> >> >> > webpage".
> > >> >> >> >
> > >> >> >> > All other links (Network Configuration Wizard, Remote Web
> > >> >> >> > Workplace,
> > >> >> >> > and
> > >> >> >> > Information and Answers) bring up "The page cannot be found".
> > >> >> >> >
> > >> >> >> > Directly going to https://sbs2003.domain.com/Remote now results
> > >> >> >> > in
> > >> >> >> > "The
> > >> >> >> > page
> > >> >> >> > cannot be found" instead of the previous "You are not authorized
> > >> >> >> > to
> > >> >> >> > view
> > >> >> >> > this
> > >> >> >> > page".
> > >> >> >> >
> > >> >> >> >
> > >> >> >> > "Greg Kirkpatrick" wrote:
> > >> >> >> >
> > >> >> >> >> I changed IP of the WAN Ethernet adapter in the SBS 2003 to

"while on the working-RWW server (win2003)..."

Wait a minute... RWW only comes with SBS 2003. I trust you really mean
that this is just another SBS 2003 server (that is functioning properly).

At this point I would install adn run a scan with the SBS 2003 BPA:

Microsoft Windows Small Business Server 2003 Best Practices Analyzer
http://207.46.19.190/downloads/detai...displaylang=en

Small Business Server 2003 Best Practices Analyzer Updated
http://207.46.19.190/downloads/detai...displaylang=en

How to Use the Windows SBS 2003 BPA
http://blogs.technet.com/sbs/archive...-2003-bpa.aspx

--
Merv Porter [SBS-MVP]
============================

"Greg Kirkpatrick [SBSC,MCTS-Vista,MCITP]" <greg@no_spam_computermagic.cc>
wrote in message news:FA26C6AF-0C69-44E7-9127-73A09785D38E@microsoft.com...
>I have compared this SBS 2003 server with another one on which RWW is
>running
> fine.
> These are some of the differences:
>
> In the non-working-RWW server (sbs2003), in the properties of the Default
> Web Site, under Home Directory, the Execute Permissions were set to
> "Scripts
> only", while on the working-RWW server (win2003), it was set to "Scripts
> and
> Executables". On sbs2003, the Application Pool was set to StsAppPool1; on
> win2003, it is set to DefaultAppPool. On win2003, the Documents tab shows
> four items: Default.htm, Default.asp, index.htm, and iistart.htm. On
> sbs2003, there was a fifth (last) item: Default.aspx. On sbs2003, the
> ISAPI
> Filters tab shows SBSFLT with High Priority, followed by fpexedll.dll with
> Low Priority, and Owalogon with "Unknown" priority. On win2003, the same,
> except SBSFLT is not listed. On sbs2003, HTTP Headers tab has "Enable
> content expiration" checked, and "Expire after 30 days" selected. On
> win2003, that is not checked; and under Custom Web Header, win2003 has
> listed
> MicrosoftOfficeWebServer: 5.0_Pub and XP-Powered-By: ASP.NET. On sbs2003,
> only XP-Powered-By: ASP.NET is listed. On win2003, on the Server
> Extensions
> 2003 tab, it says "Microsoft SharePoint is installed on this site.
> Version
> 5.0.2.6790. On sbs2003, it says: This server has not been configured to
> use
> the server extensions.
>
> I configured the server extensions for the Default Web Site under sbs2003,
> and made changes to mimic the settings on win2003. However, I am still
> getting "you are not authorized to view this page" when I attempt to
> access
> https://sbs2003.domain.com/Remote.
>
>
>
> "Greg Kirkpatrick" wrote:
>
>> This is the pertintent text from KB925653:
>> --------------------------------------------------------------------------------
>> In this situation, the default.aspx page is not added to the list of
>> default
>> content pages for the remote virtual directory in IIS.
>>
>> RESOLUTION
>> To resolve this issue, follow these steps:
>> 1. Click Start, point to Administrative Tools, and then click Internet
>> Information Services (IIS) Manager.
>> 2. Under ComputerName (local computer), expand Web Sites, expand Default
>> Web
>> Site, right-click Remote, and then click Properties.
>> 3. In the Remote Properties dialog box, click the Documents tab, and then
>> click Add.
>> 4. In the Add Content Page dialog box, type default.aspx in the Default
>> content page box, and then click OK two times.
>> --------------------------------------------------------------------------------
>> APPLIES TO
>> . Microsoft Windows Small Business Server 2003 Premium Edition
>> . Microsoft Windows Small Business Server 2003 Standard Edition
>>
>> Keywords: kbtshoot kbprb KB925653
>> --------------------------------------------------------------------------------
>>
>> When I checked, there was a Default.aspx created in the Documents of the
>> Remote properties, but it was listed last. I deleted it, and recreated
>> it as
>> default.aspx, and moved it to the top of the list. However, when I
>> attempted
>> to access RWW via an external computer, I got the same "You are not
>> authorized to view this page".
>>
>> I then looked at this message:
>>
>> OWA and RWW not accessible.
>> http://groups.google.com/group/micro...e8e7fea60c5efc
>> --------------------------------------------------------------------------------
>> [quoting Robert Li of MSFT]:
>>
>> "All Windows Small Business Server Website and Virtual Directories work
>> only
>> with .Net Framework 1.1 and are no support with 2.0
>>
>> - Default website
>> - Exchange (OWA)
>> - Remote (RWW)
>> - ActiveSync
>> - OMA and all
>> - Companyweb
>> - SharePoint Central Administration
>> - Microsoft SharePoint Administration"
>>
>>
>> 1. Open Internet Information Services (IIS) Manager
>> 2. Expand to Server | Web Sites | Default Web Sites
>> 3. Right click the each web site and select Properties.
>> 4. On the ASP.NET tab, make sure the version is 1.1.4322.
>> --------------------------------------------------------------------------------
>>
>> I will not install .NET Framework 2.0 or 3.0 or 3.5 -- I don't want
>> companyweb and Monitoring to break again.
>>
>> However, when I checked the properties for Default Web Site, .NET
>> Framework
>> 2.0 was installed (the ASP.NET tab was there) -- something must done it.
>> ARGH! I have uninstalled .NET 2.0 Framework.
>>
>> Now, the ASP.NET tab is not present in the properties for Default Web
>> Site
>> or any virtual directories, so they have to be using 1.1.
>>
>> I found, in the messages you referenced, a mention of the ASP.NET IIS
>> Registration Tool (Aspnet_regiis.exe):
>> http://msdn.microsoft.com/en-us/library/k6h9cz8h.aspx
>>
>> This is a GREAT command-prompt tool, as it confirms exactly what is
>> mapped
>> to where instantly:
>> %WINDIR%\Microsoft.NET\Framework\v1.1.4322\Aspnet_regiis.exe -lk
>>
>> It also gives a way, via command-prompt commands, to change what is
>> needed.
>>
>> I think it is tragic that, as Robert Li of MSFT says:
>>
>> "When installing .NET Framework 2.0 on Windows Small Business Server,
>> all the websites are automatically switched to use .NET Framework 2.0
>> which
>> they are not intended to work with."
>>
>> This is a recipe for disaster!
>> Especially since so many other programs, including "WSUS 3.0", require
>> .NET
>> Framework 2.0.
>>
>> Why is there NO WARNING GIVEN when installing .NET Framework 2.0 (or 3.0
>> or
>> 3.5) on SBS 2003?
>> [This is a rhetorical question, as I don't expect you to answer it.]
>>
>> Some progress is being made, however:
>>
>> When I navigate to http://sbs2003.domain.com/ and see the Default Web
>> Site
>> (as permissions are still, temporarily, unrestricted), I can now click on
>> Information and Answers and see http://sbs2003.domain.com/ClientHelp and
>> its
>> sub-pages -- which previously gave me "The page cannot be found".
>>
>> Clicking on Network Configuration Wizard still gets
>> http://sbs2003.domain.com/ConnectComputer -- "The page cannot be found".
>>
>> Clicking on Remote Web Workplace still gets
>> http://sbs2003.domain.com/Remote
>> -- "You are not authorized to view this page". Changing that to
>> https://sbs2003.domain.com/Remote has the same result.
>>
>> Since some parts of an uninstall wait for a reboot, I rebooted the
>> server,
>> just to see whether that would make any difference. It didn't.
>>
>>
>>
>> "Merv Porter [SBS-MVP]" wrote:
>>
>> > What if you now go back to...
>> >
>> > Error message when you try to access the Remote Web Workplace in
>> > Windows
>> > Small Business Server 2003: "You are not authorized to view this page"
>> > http://support.microsoft.com/kb/925653
>> >
>> > Also. make sure the default web site and its vritual directories are
>> > set to
>> > use .Net Framework 1.1 (not 2.0)
>> >
>> > OWA and RWW not accessible.
>> > http://groups.google.com/group/micro...e8e7fea60c5efc
>> >
>> > --
>> > Merv Porter [SBS-MVP]
>> > ============================
>> > "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote in
>> > message news:255EB5C7-DEF9-4EA0-B19D-6EB499A9969D@microsoft.com...
>> > >I follow these directions from that link:
>> > >
>> > > "If SBS is already installed then you should be able to go to
>> > > Start/Control
>> > > Panel/Add/Remove Programs and select Windows Small Business Server
>> > > 2003
>> > > then
>> > > click on the Change/Remove button.. then follow the setup wizard
>> > > screens
>> > > until you get to the Component Selection screen.. then select
>> > > Reinstall
>> > > for
>> > > the Server Tools option.. You can set the Server Tools subcomponents
>> > > to
>> > > None
>> > > (Installed) they should not need to be re-installed. RWW should be
>> > > re-installed by simply reinstalling the top level of the Server
>> > > Tools..
>> > > it's not listed as a seperated component like Intranet is (which
>> > > installs
>> > > Windows SharePoint Services and does the SBS provisioning) "
>> > >
>> > > ...and I got this error before it finished:
>> > > ---------------------------
>> > > .NET Framework 1.1 -- Device Update 2.0
>> > > ---------------------------
>> > > Command line option syntax error. Type Command /? for Help.
>> > > ---------------------------
>> > > OK
>> > > ---------------------------
>> > > However, it finished otherwise, and did not report any problem. It
>> > > brought
>> > > up a box that said the server had to reboot, but before I clicked OK,
>> > > I
>> > > checked in IIS Admin, and the "Remote" web site under Default Web
>> > > Site was
>> > > now listed.
>> > >
>> > > I then clicked OK, which rebooted the server.
>> > >
>> > > When it returned, I could right-click the "Remote" website under
>> > > Default
>> > > Web
>> > > Site, and "browse", and see the RWW login page.
>> > >
>> > > However, when I attempted to access it from an external computer
>> > > (after
>> > > logging out of RDC), I got "You are not authorized to view this
>> > > page".
>> > >
>> > >
>> > > "Merv Porter [SBS-MVP]" wrote:
>> > >
>> > >> Try this...
>> > >>
>> > >> Reinstall Remote Web
>> > >> http://groups.google.com/group/micro...0a07e39aca4540
>> > >>
>> > >> --
>> > >> Merv Porter [SBS-MVP]
>> > >> ============================
>> > >>
>> > >> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com> wrote
>> > >> in
>> > >> message news:465CE79D-647C-4E8F-826D-85C5765D89DB@microsoft.com...
>> > >> > Yes, that helped somewhat, as I found that the "Remote" Web Site
>> > >> > (under
>> > >> > Default Web Site) is missing. That might explain the "Page cannot
>> > >> > be
>> > >> > found"
>> > >> > errors. How can I get this created?
>> > >> >
>> > >> > "Merv Porter [SBS-MVP]" wrote:
>> > >> >
>> > >> >> Any help here?
>> > >> >>
>> > >> >> Error message when you try to access the Remote Web Workplace in
>> > >> >> Windows
>> > >> >> Small Business Server 2003: "You are not authorized to view this
>> > >> >> page"
>> > >> >> http://support.microsoft.com/kb/925653
>> > >> >>
>> > >> >> --
>> > >> >> Merv Porter [SBS-MVP]
>> > >> >> ============================
>> > >> >>
>> > >> >> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com>
>> > >> >> wrote
>> > >> >> in
>> > >> >> message
>> > >> >> news:79148A29-E272-4BA8-BE8E-EE0C09E9CA11@microsoft.com...
>> > >> >> > My server's FQDN (as stated on its Web Server Certificiate and
>> > >> >> > in
>> > >> >> > the A
>> > >> >> > record of the hosting company's DNS entries) is
>> > >> >> > sbs2003.thenameofthecompanygoeshere.com, so the address that I
>> > >> >> > have
>> > >> >> > been
>> > >> >> > using to try to get to RWW is
>> > >> >> > https://sbs2003.thenameofthecompanygoeshere.com/remote.
>> > >> >> > However, if
>> > >> >> > the
>> > >> >> > IP
>> > >> >> > address restriction for the Default Website is changed back to
>> > >> >> > normal,
>> > >> >> > when
>> > >> >> > trying to use RWW, I get "You are not authorized to view this
>> > >> >> > page";
>> > >> >> > with
>> > >> >> > the
>> > >> >> > restrictions lifted, I get "Page cannot be found". Pinging
>> > >> >> > "sbs2003.thenameofthecompanygoeshere.com" results in the static
>> > >> >> > IP
>> > >> >> > assigned
>> > >> >> > by the ISP, 72.xxx.xxx.xxx, and (JUST AS A TEMPORARY TEST) with
>> > >> >> > the
>> > >> >> > permission restrictions lifted on Default Website,
>> > >> >> > http://sbs2003.thenameofthecompanygoeshere.com brings up the
>> > >> >> > Default
>> > >> >> > Website
>> > >> >> > externally. This proves that the issue is not DNS related.
>> > >> >> >
>> > >> >> > These ports are properly forwarded to the server's External
>> > >> >> > (WAN)
>> > >> >> > Ethernet
>> > >> >> > adapter (192.168.1.10): 443, 444, 3389, and 4125. Per Susan
>> > >> >> > Bradley's
>> > >> >> > blog,
>> > >> >> > 443 and 4125 are needed for RWW, 444 allows Sharepoint
>> > >> >> > (companyweb)
>> > >> >> > to
>> > >> >> > be
>> > >> >> > reached externally, and 3389 allows Terminal Services (Remote
>> > >> >> > Desktop
>> > >> >> > Connection) externally. As soon as I forwarded 3389, RDC
>> > >> >> > started
>> > >> >> > working
>> > >> >> > to
>> > >> >> > that server from my office laptop.
>> > >> >> >
>> > >> >> > From an internal (LAN) workstation, when trying to go to
>> > >> >> > https://sbs2003/remote, I also get the same results; and on
>> > >> >> > that
>> > >> >> > workstation,
>> > >> >> > while http://companyweb will appear, clicking "Remote Server
>> > >> >> > Management
>> > >> >> > also
>> > >> >> > results in "Page cannot be found". Pinging "sbs2003" from the
>> > >> >> > workstation
>> > >> >> > provides responses from 192.168.16.2 -- the server's LAN
>> > >> >> > address.
>> > >> >> > Opening
>> > >> >> > http://companyweb on the server itself gives the same results.
>> > >> >> >
>> > >> >> >
>> > >> >> > "Merv Porter [SBS-MVP]" wrote:
>> > >> >> >
>> > >> >> >> You should not have to play with the IP address restrictions
>> > >> >> >> for
>> > >> >> >> Default
>> > >> >> >> WebSite. You need to forward the proper ports in the router
>> > >> >> >> to
>> > >> >> >> your
>> > >> >> >> external SBS NIC. The access RWW via
>> > >> >> >> https://<YourServersFullInternetNameAsInputOnYourWebServerCert>/remote
>> > >> >> >>
>> > >> >> >> Example:
>> > >> >> >> https://mail.mycompany.com/remote
>> > >> >> >>
>> > >> >> >> --
>> > >> >> >> Merv Porter [SBS-MVP]
>> > >> >> >> ============================
>> > >> >> >>
>> > >> >> >> "Greg Kirkpatrick" <GregKirkpatrick@discussions.microsoft.com>
>> > >> >> >> wrote
>> > >> >> >> in
>> > >> >> >> message
>> > >> >> >> news:555A1A7E-56E2-48A8-B9B1-38A948D064AC@microsoft.com...
>> > >> >> >> >I have temporarily changed the IP address restrictions for
>> > >> >> >> >Default
>> > >> >> >> >WebSite
>> > >> >> >> >in
>> > >> >> >> > IIS Admin, so all are now Granted Access. It is now
>> > >> >> >> > possible to
>> > >> >> >> > navigate
>> > >> >> >> > to
>> > >> >> >> > http:\\sbs2003.domain.com, and the default website appears.
>> > >> >> >> >
>> > >> >> >> > However, companyweb (My internal website) goes to
>> > >> >> >> > http:\\companyweb,
>> > >> >> >> > which
>> > >> >> >> > of course results in "Internet Explorer cannot display the
>> > >> >> >> > webpage".
>> > >> >> >> >
>> > >> >> >> > All other links (Network Configuration Wizard, Remote Web
>> > >> >> >> > Workplace,
>> > >> >> >> > and
>> > >> >> >> > Information and Answers) bring up "The page cannot be
>> > >> >> >> > found".
>> > >> >> >> >
>> > >> >> >> > Directly going to https://sbs2003.domain.com/Remote now
>> > >> >> >> > results
>> > >> >> >> > in
>> > >> >> >> > "The
>> > >> >> >> > page
>> > >> >> >> > cannot be found" instead of the previous "You are not
>> > >> >> >> > authorized
>> > >> >> >> > to
>> > >> >> >> > view
>> > >> >> >> > this
>> > >> >> >> > page".
>> > >> >> >> >
>> > >> >> >> >
>> > >> >> >> > "Greg Kirkpatrick" wrote:
>> > >> >> >> >
>> > >> >> >> >> I changed IP of the WAN Ethernet adapter in the SBS 2003 to