Exchange Server - OWA front-end back-end authentication problem
Asked By federico
18-Mar-08 02:41 PM
Hello, I cannot authenticate to our new Exchange 2003 server via our
front-end web access server. I have no problem logging on to accounts
located in the other two back-end servers thru the front-end server. The
other servers are also Exchange 2003 sp2 on Windows 2003 R2 Enterprise, but
they have a couple fewer security updates installed. Further, I have no
problem authenticating to accounts located in the new server if I access its
web interface directly instead of thru the front-end server.
I have compared the settings for the web interface of the new server with
the settings of the older ones (one of which I set up with no problems) and
I cannot see any differences.
Do you have any ideas were the problem could be? Please, any help will be
greatly appreciated.
federico
Windows
(1)
Weeks
(1)
Rubs
(1)
Sp2
(1)
Bluehade replied...
I posted a similar question here about 2 weeks ago. Search for the following
and read the responses given to me. They were very helpful. Hope you find a
solution in one of them.
Search for the following In Exchange Administration.
Added a Second Back-End Server OWA not working
federico replied...
I reboot of the front-end server solved the problem.
It rubs me the wrong way whenever you solve a problem in a server with a
reboot. Probably I could of restarted some service also.
federico replied...
Thanks for your reply Bluehades. In my case a reboot of the front-server
solved the problem.

ideas why this is not working? Any input is appreciated. Thanks, Clay Exchange Admin Discussions Windows Server 2003 (1) Outlook (1) IIS (1) ReplaceCurrent (1) Ater (1) Exch (1) Can you 50 GET / owa - 443 - 99.88.77.66 Mozilla / 4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR 50 GET / owa / - 443 - 99.88.77.66 Mozilla / 4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR owa / &reason = 0 443 - 99.88.77.66 Mozilla / 4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR https%3a%2f%2fwebmail.mydomain.com%2fowa%2f 443 - 99.88.77.66 Mozilla / 4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR premium / contactvw.js - 443 - 99.88.77.66 Mozilla / 4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR premium / daddrbk.js - 443 - 99.88.77.66 Mozilla / 4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR premium / directoryvw.js - 443 - 99.88.77.66 Mozilla / 4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR
Our organization is a simple single-forest, single-domain network environment. We currently have one Windows 2000 Server and two Windows Server 2003 Sp2 Std Edition machines. We have just built a new server with Windows Server 2003 R2 x64 edition, and we plan to migrate Exchange to this machine. All four of these machines are domain controllers. I thought I understood Windows domain and forest functional levels, but now I am finding myself confused. The book I said in different places that: Exchange 2007 requires a domain functional level of at least Windows 2000 native. Exchange 2007 requires a forest functional level of at least Windows 2003. Specifically, it says: = 93To install Exchange Server 2007, the Windows Server 2003 Active Directory domain functional level must be Windows 2000 Server Native or higher
0.875: = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 0.875: 2008 / 08 / 01 06:15:28.927 (local) 0.875: C: \ WINDOWS \ SoftwareDistribution \ Download \ 3fec1449a6a0e537c1d07c6c6890c080 \ update \ update.exe (version 6.1.22.4) 0.922: DoInstallation: GetProcAddress norestart / quiet / ParentInfo:f0202d85ef34624abb0148ee780289e7 2.797: - -- - Old Information In The Registry - -- -- - 2.797: Source:C: \ WINDOWS \ system32 \ spool \ drivers \ W32X86 \ 3 \ temp \ mdiAA7F.tmp (0.3.2175.0) 2.797: Destination: 2.797: Source:C: \ WINDOWS \ system32 \ spool \ DRIVERS \ W32X86 \ 3 \ New \ mdiui.dll 2.797: Destination:C WINDOWS \ system32 \ spool \ DRIVERS \ W32X86 \ 3 \ mdiui.dll (0.3.8166.2) 2.797: Source:g: \ 3e7bac276215caa786a6d1bd985624 2.797: Destination: 2.812: Source:C: \ WINDOWS \ system32 \ SET26.tmp (5.2.3790.4318) 2.812: Destination:C: \ WINDOWS \ system32 \ mswsock.dll (5.2.3790.3959) 2.812: Source:C WINDOWS \ system32 \ SET1A.tmp (5.2.3790.4318) 2.812: Destination:C: \ WINDOWS \ system32 \ dnsapi.dll (5.2.3790.4238) 2.812: Source:C: \ WINDOWS \ system32 \ DllCache \ SET2B
formatted the old one. So at the moment i only have the new exchange 2003 SP2 server. Like i said, i did uninstall the old exchange from the old box - i so at the moment i only have the 1 box. Most recent file in C: \ Windows \ System32 \ LogFiles \ W3SVC1 . Or \ WINNT \ instead of \ Windows \ on Win 2000 server. HI here are some of the entries which i feel is 105 GET / exchange - 80 - 192.168.150.160 Mozilla / 4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident / 4.0;+GTB5;+InfoPath.1;+.NET+CLR+2.0.50727;+.NET 105 GET / exchange - 80 - 192.168.150.160 Mozilla / 4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident / 4.0;+GTB5;+InfoPath.1;+.NET+CLR+2.0.50727;+.NET exchange - 80 CTTOURISM \ craigm 192.168.150.160 Mozilla / 4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident / 4.0;+GTB5;+InfoPath.1;+.NET+CLR+2.0.50727;+.NET exchange / - 80 CTTOURISM \ craigm 192.168.150.160 Mozilla / 4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident / 4.0;+GTB5;+InfoPath.1;+.NET+CLR+2.0.50727;+.NET navbar 80 CTTOURISM \ craigm 192.168.150.160 Mozilla / 4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident / 4.0;+GTB5;+InfoPath.1;+.NET+CLR+2.0.50727;+.NET
issue with one specific user having access problems to OWA. Using an Exchange 2003 (on Windows 2003) configuration in a frontend / backend configuration. Said user has been able to use the auth / owaauth.dll - 443 - 192.168.0.2 Mozilla / 4.0+(compatible;+MSIE+7.0;+Windows+NT +5.1;+Mozilla / 4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1)+;+.NET +CLR+2.0.50727;+.NET+CLR+3.0.04506.30 GET / exchange / - 443 user1 192.168.0.2 Mozilla / 4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Mozilla / 4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1)+;+.NET+CLR +2.0.50727;+.NET+CLR+3.0.04506.30 exchange / &reason = 3D2 443 - 192.168.0.2 Mozilla / 4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+Mozilla / 4.0+ (compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1)+;+.NET+CLR+2.0.50727;+.NET +CLR+3.0.04506.30 auth / owaauth.dll - 443 - 192.168.0.2 Mozilla / 4.0+(compatible;+MSIE+7.0;+Windows+NT +5.1;+Mozilla / 4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1