OWA and .NET v2.0.50727 strange issues

Tech-Archive recommends: Fix windows errors by optimizing your registry



anyone else experienced problems with .NET v2.0.50727 affecting OWA?

I had a similar issue a few months back when I first installed
v2.0.50727 as a test, no matter what I did I could not get OMA working
with it, I was continually getting "Server Application Error in /"
messages - so I removed v2.0.50727 and reverted to v1.1.4322 and
everything was ok again.

So I left it at v1.1.4322.

Recently though we had a web server crash and had a need to rebuild
the website on the Exchange Server, now this website needed v2.0.50727
(plus a couple other things) to function and I kept an eye on OWA as I
was concecrned about it and at first it seemed fine, then a couple
days again I continually experience "You are not authorized to view
this page" errors, despite the fact nothing had change in the
configuration.

Checking and rechecking authentication settings in IIS showed nothing
had changed or appeared wrong - I experimented with several
authentication changes.

Today, I decided to check and experiment with authentication settings
on the /Exchange directory from with ESM - and by removing the
authentication needs, putting it to anonymous access I was able to get
it working again, so putting the authentication methods back into
place one at a time and testing - basic authentication (+ https),
integrated windows authoentication and the digest authentication -
everything seems to be working again.

So I'm a bit lost to what could have caused the issue in the first
place and not really quite sure why what I did fixed it?

Anyone have any thoughts?


oh and by the way, I still can't fix OMA with v2.0.50727 but that's
less important at this stage

.



Relevant Pages

  • Re: Kerberos machine authentication - apparent authentication fail
    ... > until logon), the wireless connection can kick off when it is ready. ... > was confirmed in the server event logs with IAS (i set that up as the radius ... > as an ordinary user kicks in and takes over from the machine authentication. ... > while the network sorts itself out and a double click on a network link of ...
    (microsoft.public.windows.server.security)
  • Re: Basic Authentication + IIS 5 + Windows 2000 + Frontpage 2002 = failure?
    ... SYSTEM account. ... In IIS I took the virtual server that I was testing, ... Authentication premise. ... From a website perspective, I ...
    (microsoft.public.inetserver.iis.security)
  • Need help configuring Wireless Connection profile
    ... I have an SBS 2003 server and a Server 2003 member server set up using RADIUS ... Windows authentication for all users,4129,LRG\ryanv,4149,Wireless WPA2 PEAP ... Certificate Services ...
    (microsoft.public.windowsxp.general)
  • Re: Remote Web Workplace Issues-Please help!
    ... Open the Server Management Console, ... client after Authentication" right. ... permissions, and Microsoft Windows user rights according to the KB 812614. ... Download the IIS Resource Kit tools from the following page: ...
    (microsoft.public.windows.server.sbs)
  • [REVS] NTLM HTTP Authentication is Insecure By Design
    ... in front of a web server, and that proxy server shares a single TCP ... These are attacks that make use of non-RFC HTTP requests (HTTP Request ... the authentication is associated with the ...
    (Securiteam)