Re: Configuring OWA on SBS 2003



You may have to stop and re-start the Default website, for the 1.1
changes to be in effect. However, it does use (and needs to be) .NET
1.1.xx

--
Duncan

In article <#znsuLZ2JHA.3476@xxxxxxxxxxxxxxxxxxxx>, "Michael Salamone"
<mikesa_at_entrek_dot_com> says...
FYI I broke my website by setting ASP.NET version to 1.1. So if that's a
hard requirement for OWA to work, do I need to set up some new virtual
directory (for either my website or OWA)?

Thanks,
Mike


"Michael Salamone" <mikesa_at_entrek_dot_com> wrote in message
news:%23nCN9wV2JHA.5772@xxxxxxxxxxxxxxxxxxxxxxx
Ok - did that. Still showing version 2.something in the new error
messages I'm getting from the browser (which I'll post in reply to Robbins
reply).

I went one level deeper to ExchWeb (and a few others) which have
2.something for ASP.NET and it's grayed out - can't change it.

I went as far to reboot the server (sorry to the person who was in the
middle of 2GB transfer!) but still the same (1.1 setting for the Default
Web Site and 2.something grayed out for ExchWeb and a few others.

Mike

"Duncan McC" <hard@xxxxxxx> wrote in message
news:MPG.247eac12d52602bd989a5f@xxxxxxxxxxxxxxxxxxxxx
Start the IIS Admin MMC console and drill into the Default Web Site.

On that, go into it's properties. Click the ASP.NET tab, and change the
.NET version to 1.1xxx (not 2) in the drop down list.

--
Duncan

In article <#qFozzQ2JHA.4412@xxxxxxxxxxxxxxxxxxxx>, "Michael Salamone"
<mikesa_at_entrek_dot_com> says...
"Michael Salamone" <mikesa_at_entrek_dot_com> wrote in message
news:eQo6GlQ2JHA.1372@xxxxxxxxxxxxxxxxxxxxxxx
"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:uIeLinO2JHA.1416@xxxxxxxxxxxxxxxxxxxxxxx
Michael Salamone <mikesa_at_entrek_dot_com> wrote:
When I browse to https://mysbsipaddr/exchange, I get "There is a
problem with this website's security certificate." page.

Then I click "Continue to this website (not recommended)" and get a
"The page cannot be found" error.

This happens from internal workstation, external (outside the
firewall), and from the SBS server itself. It's never worked in the
past from external workstation, but I *think* I've seen it work
(albeit months and months and months ago) from internal workstation
and from the server, but not sure what's changed there.

I did follow the steps from this KB article:
http://support.microsoft.com/default.aspx/kb/259240. For step 8 re:
ephemeral ports, I followed the instructions here:
http://support.microsoft.com/kb/812873. There were already a few
reserved ports in the 1024-65535 range. I left those there, so
after
my change, the registry value looks like this:

1433-1434
3343-3343
1024-65535

That ok?

I also opened up port 443 for https.

Any help?

Thanks,
Mike

You don't need to do any of that other than opening up port 443. Use
the
SBS wizards. Run the CEICW to configure all of this.




Thanks - I saw in some help that I should run the CEICW wizard but I
was
worried it would muck up something that's already configured and
working
(like DNS and Exchange notwithstanding the OWA issue I'm having).

I ran it anyway. I told it to skip configuring the firewall. It
failed
to create / install certificate. And had some failure configuring
Exchange. OWA still not working :(

Please Let me know if you have any more suggestions.

Here is the report from CEICW:

Connection type: Do not change

The firewall on your computer running Small Business Server could not
be
configured. You must configure a firewall to secure your local network
from the Internet. For more information about configuring firewall
settings for your Small Business Server network, see Help and Support.
Web services on your server's default Web site to be available through
the
firewall to users on the Internet:
None of the Web services

The Web server certificate required for https:// will be created for
the
following Web server name: mysbsserver.myaddomain.local

Email: Enable Exchange for Internet e-mail with the following
settings:
E-mail delivery:
Route e-mail to the Internet by using DNS.
E-mail retrieval:
Use Exchange to retrieve SMTP e-mail.
Email retrieval method:
Route e-mail from the Internet directly to Exchange.
Registered Internet e-mail domain name: myemaildomain.com.
E-mail attachments: Remove e-mail attachments from Internet e-mail as
specified in the wizard.

For more detailed information about the configurations performed by
this
wizard, click the link at the bottom of this page to open
Icwdetails.htm
in C:\Program Files\Microsoft Windows Small Business
Server\Networking\Icw.
Note: each time the Configure E-mail and Internet Connection Wizard is
run, a new .htm file is automatically generated to preserve the
previous
settings. For example, Icwdetails1.htm, Icwdetails2.htm, and so on.



Sorry - I should mention that behavior has changed (but still fails).
Now
when I try to go to OWA URL, I get a popup asking for credentials (not
the
normal OWA login screen). I enter my domain\username (which has admin
priv
if that's important) and pwd. Then get this page:

Server Error in '/' Application.
--------------------------------------------------------------------------------

Configuration Error
Description: An error occurred during the processing of a configuration
file
required to service this request. Please review the specific error
details
below and modify your configuration file appropriately.

Parser Error Message: An error occurred loading a configuration file:
Failed
to start monitoring changes to
'\\.\BackOfficeStorage\entrek.com\MBX\myusername' because access is
denied.

Source Error:


[No relevant source lines]


Source File: \\.\BackOfficeStorage\entrek.com\MBX\mikesa\web.config
Line:
0


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.3082;
ASP.NET Version:2.0.50727.3082








.



Relevant Pages

  • Re: Configuring OWA on SBS 2003
    ... and from the server, but not sure what's changed there. ... I told it to skip configuring the firewall. ... firewall to users on the Internet: ... An error occurred during the processing of a configuration file ...
    (microsoft.public.windows.server.sbs)
  • Re: login attempts
    ... > Every day i have on my win2000 iternet server a lots of wrong login ... Windows by default allows ... You also need a firewall. ... the internet, except for those ports you know you're using. ...
    (microsoft.public.win2000.security)
  • Re: Big hole??
    ... > firewall then even they can't get in, ... > supposedly safe SP2 for Windows XP invites any Internet ... > Connection Sharing of the PC has to be disabled. ... > in fact is a common configuration and not a rare sight. ...
    (microsoft.public.windowsxp.general)
  • Re: Firewall on a single NIC SBS2003 Standard edition
    ... Frank McCallister SBS MVP ... > " Well, if you're wanting to run the firewall on a single NIC, you aren't ... Don't ask the server to do *everything*, ... > internet traffic from the workstations don't have to go through the SBS. ...
    (microsoft.public.windows.server.sbs)
  • Re: Internet on nodes
    ... I stopped the Firewall in SBS and could upload ... print' from both the server and a WS. ... Was not able to connect to the internet on the WS. ...
    (microsoft.public.windows.server.sbs)