GregKirkpatrick
Thu May 15 07:06:02 PDT 2008
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/routers/port_forwarding/Netopia/3347NWG/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.
> >> >> >
> >> >> >
> >> >> >
> >>
> >>
> >>
>
>
>