Re: Netopia 3347NWG with Remote Desktop and Remote Web Workplace

Correct -- the working-RWW server is named "win2003", but it is an SBS 2003
Premium R2. The non-working-RWW server is named "sbs2003" and it is an SBS
2003 Premium R1. Hopefully, that won't make any difference in RWw's setup.

Your second link was the same as the first, perhaps you meant this one?
Microsoft Exchange Best Practices Analyzer Web Update Pack
http://www.microsoft.com/downloads/details.aspx?familyid=4f2f1339-cbcd-4d26-9174-f30c10d7ec4c&displaylang=en

When I ran SBS 2003 Best Practices Analyzer, I got these 6 warnings:
Network driver is more than a year old [I know this, but there doesn't
appear to be an update, either from OEM, Tyan (most recent 2006/01/09) or
from Vendor, nVidia (most recent 2006/07). ]
EDNS is enabled [never heard of this, but I followed the steps to disable it]
The OWA update is not installed [it is now]
Reverse DNS zone does not allow for secure updates [so why wasn't this set
automatically? it does now.]
Windows Backup Wizard has not yet run [I know -- I was waiting to get this
clean, but now's a good time, I think]
Microsoft Outlook 2003 is missing [from the ClientApps folder--I hadn't
installed Outlook 2003 or IE6, as all the workstations are on Office 2007 &
IE7, but to keep BPA happy, I did so]

The Reverse DNS message was a tad vague:
You should configure Reverse Lookup Zone: 16.168.192.in-addr.arpa to allow
only secure dynamic updates. To configure the Reverse Lookup Zone, click
Start, point to Administrative Tools, and then click DNS. Right-click the
Reverse Lookup Zone: 16.168.192.in-addr.arpa, and then click Properties.
Select Secure only from the Dynamic Updates dropdown list.

When I looked in DNS, the only entry under Reverse Lookup Zones was
"192.168.16.x Subnet". I tried to create "16.168.192.in-addr.arpa" -- but
then I was told that it already exists. So I went to "192.168.16.x Subnet"
and right-clicked, and clicked on Properties, and on the General tab, I
changed the Dynamic Updates drop-down from "non-secure and secure" to "Secure
only". [Rhetorical question: why on earth is this option even necessary?
would there ever be a reason to have this set to anything except "Secure
only"? and if not, why doesn't Windows Update set this automatically?]

None of those warnings would appear to have any effect on the non-working of
RWW, and in fact, following the changes, RWW is still showing "You are not
authorized to view this page" from external and internal workstations.





"Merv Porter [SBS-MVP]" wrote:

"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/details.aspx?familyid=3874527A-DE19-49BB-800F-352F3B6F2922&displaylang=en

Small Business Server 2003 Best Practices Analyzer Updated
http://207.46.19.190/downloads/details.aspx?familyid=3874527A-DE19-49BB-800F-352F3B6F2922&displaylang=en

How to Use the Windows SBS 2003 BPA
http://blogs.technet.com/sbs/archive/2007/10/22/how-to-use-the-windows-sbs-2003-bpa.aspx

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

"Greg Kirkpatrick [SBSC,MCTS-Vista,MCITP]" <greg@xxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message news:FA26C6AF-0C69-44E7-9127-73A09785D38E@xxxxxxxxxxxxxxxx
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/microsoft.public.windows.server.sbs/msg/0fe8e7fea60c5efc
--------------------------------------------------------------------------------
[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/microsoft.public.windows.server.sbs/msg/0fe8e7fea60c5efc

--
Merv Porter [SBS-MVP]
============================
"Greg Kirkpatrick" <GregKirkpatrick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:255EB5C7-DEF9-4EA0-B19D-6EB499A9969D@xxxxxxxxxxxxxxxx
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/microsoft.public.windows.server.sbs/browse_thread/thread/1a3611424795b7a2/ad0a07e39aca4540?hl=en&lnk=st&q=sbs+reinstall+remote+web+site#ad0a07e39aca4540

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

"Greg Kirkpatrick" <GregKirkpatrick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message news:465CE79D-647C-4E8F-826D-85C5765D89DB@xxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote
in
message
news:79148A29-E272-4BA8-BE8E-EE0C09E9CA11@xxxxxxxxxxxxxxxx
My server's FQDN (as stated on its Web Server Certificiate and
in
.

Loading