Solved

Unable to connect to OWA from Mailbox server

Posted on 2008-10-22
7
2,099 Views
Last Modified: 2012-05-05
Hi all,

My problem is that, from the console of a Mailbox Server role Exchange 2007 server, I cannot access the OWA log-in authentication screen.
It says "IE cannot display the webpage....."

Now I can successfully connect to OWA from all other machines in my domain except for the mailbox server roles.

My set up is:
2 Hub Transport/CAS servers configured with NLB
2 Mailbox Servers configured with CCR

I think the answer is something simple but could anyone point me in the right direction?

OWA is working fine both internally and externally but it is an inconvenience that it won´t work on the 2 mailbox servers.
I also had this problem on another computer but, after running a dnsflush, it connected fine.
This didn´t work however on the mailbox servers.

Any ideas anyone?

Cheers
0
Comment
Question by:IntoFOS
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 2
7 Comments
 
LVL 33

Assisted Solution

by:Exchange_Geek
Exchange_Geek earned 400 total points
ID: 22781219
IE version are same on mailbox roles as other machines ??
On Exchange box - do you have SSL checked / unchecked for Exchange V.Dir ?
Disable Windows Firewall on Mailbox cluster.

Check if this makes any difference.
0
 

Author Comment

by:IntoFOS
ID: 22781719
Hi,
 
Thanks for the response.
I double-checked and the following is the answer to your queries
IE is at v7.0 on all machines
Firewall is disabled on both nodes
SSL is checked on both the Exchange and OWA virt dirs on the CAS servers but it was not enabled on the Exchange virt dir on the mailbox nodes. I enabled this on both nodes, reset IIS and tried again but to no avail.
Any other ideas?
Thanks
 
0
 
LVL 33

Accepted Solution

by:
Exchange_Geek earned 400 total points
ID: 22781849
IE 7 has always had issues with Public folder access (if it is working else where and not this machine - i would not look at IE7 - however i think its better remove it for further complications).

Are you using any proxy on this box using IE ?

Are we using the same account to access OWA on all other boxes and it works ?? Correct me if i am wrong.

Please run Test-OutlookWebServices | FL and Test-WebServicesConnectivity | FL.

Please run the tool Authdiag on your server (www.microsoft.com/downloads/details.aspx?FamilyID=e90fe777-4a21-4066-bd22-b931f7572e9a) to check for any particular error.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:IntoFOS
ID: 22781911

Ok, I have a bit more information now...
I cannot connect using      https://owa.domain.com/owa
but I can connect using https://frontexchserv.domain.com/owa
where frontexchserv is either of the 2 CAS servers hostnames.
In DNS there is a host record for owa (which points to the IP add of the NLB cluster) and also for both frontexchserv´s
Any ideas?
0
 

Author Comment

by:IntoFOS
ID: 22791492
Hi, sorry for the late reply.
These are the results for the AuthDiag utility run against the owa.domain.com (owa.domain.com is the domain name I am using for OWA externally and internally)
Server's response: HTTP/1.1 403 Forbidden
Learn about IIS status codesPath:W3SVC/1/ROOT
AuthType:Anonymous
Server's response: HTTP/1.1 403 Forbidden
Learn about IIS status codesPath:W3SVC/1/ROOT/aspnet_client
AuthType:Anonymous
Test Authentication
Path:W3SVC/1/ROOT/Autodiscover
AuthType:Basic
Test Authentication
Path:W3SVC/1/ROOT/Autodiscover
AuthType:NTLM
No authentication types are currently configured for IIS. Ensure that your Web site is configured correctly. Path:W3SVC/1/ROOT/Autodiscover/bin
No authentication types are currently configured for IIS. Ensure that your Web site is configured correctly. Path:W3SVC/1/ROOT/Autodiscover/help
Test Authentication
Path:W3SVC/1/ROOT/EWS
AuthType:Basic
Test Authentication
Path:W3SVC/1/ROOT/EWS
AuthType:NTLM
No authentication types are currently configured for IIS. Ensure that your Web site is configured correctly. Path:W3SVC/1/ROOT/EWS/bin
Test Authentication
Path:W3SVC/1/ROOT/Exchange
AuthType:Basic
UNCPassword
An invalid value for UNCUserName or UNCPassword is causing login to fail.Path:W3SVC/1/ROOT/Exchange
AuthType:Anonymous
Test Authentication
Path:W3SVC/1/ROOT/Exchweb
AuthType:Basic
UNCPassword
An invalid value for UNCUserName or UNCPassword is causing login to fail.Path:W3SVC/1/ROOT/Exchweb
AuthType:Anonymous
Test Authentication
Path:W3SVC/1/ROOT/Microsoft-Server-ActiveSync
AuthType:Basic
Test Authentication
Path:W3SVC/1/ROOT/OAB
AuthType:NTLM
Test Authentication
Path:W3SVC/1/ROOT/owa
AuthType:Basic
Server's response: HTTP/1.1 403 Forbidden
Learn about IIS status codesPath:W3SVC/1/ROOT/owa/8.0.813.0
AuthType:Anonymous
Server's response: HTTP/1.1 403 Forbidden
Learn about IIS status codesPath:W3SVC/1/ROOT/owa/8.1.240.5
AuthType:Anonymous
Server's response: HTTP/1.1 403 Forbidden
Learn about IIS status codesPath:W3SVC/1/ROOT/owa/8.1.291.1
AuthType:Anonymous
Server's response: HTTP/1.1 403 Forbidden
Learn about IIS status codesPath:W3SVC/1/ROOT/owa/auth
AuthType:Anonymous
Server's response: HTTP/1.1 403 Forbidden
Learn about IIS status codesPath:W3SVC/1/ROOT/owa/bin
AuthType:Anonymous
Test Authentication
Path:W3SVC/1/ROOT/Public
AuthType:Basic
UNCPassword
An invalid value for UNCUserName or UNCPassword is causing login to fail.Path:W3SVC/1/ROOT/Public
AuthType:Anonymous
Test Authentication
Path:W3SVC/1/ROOT/Rpc
AuthType:Basic
No authentication types are currently configured for IIS. Ensure that your Web site is configured correctly. Path:W3SVC/1/ROOT/RpcWithCert
Test Authentication
Path:W3SVC/1/ROOT/UnifiedMessaging
AuthType:Basic
Test Authentication
Path:W3SVC/1/ROOT/UnifiedMessaging
AuthType:NTLM
No authentication types are currently configured for IIS. Ensure that your Web site is configured correctly. Path:W3SVC/1/ROOT/UnifiedMessaging/bin
Diagnostics complete
 
and these are the results for the test-outlookwebservices command
 

 
Id      : 1003
Type    : Information
Message : About to test AutoDiscover with the e-mail address postmaster@domain.com.
Id      : 1007
Type    : Information
Message : Testing server exchfe01.domain.com with the published name https://exchfe01.domain.com/EWS/Exchange.ascom & https://owa.domain.com/EWS/Exchange.ascom.
Id      : 1019
Type    : Information
Message : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://exchfe01.domain.com/Autodiscover/Autodiscover.xml.
Id      : 1006
Type    : Information
Message : The Autodiscover service was contacted at https://exchfe01.domain.com/Autodiscover/Autodiscover.xml.
Id      : 1016
Type    : Success
Message : [EXCH]-Successfully contacted the AS service at https://exchfe01.domain.com/EWS/Exchange.ascom. The elapsed time was 15 milliseconds.
Id      : 1015
Type    : Success
Message : [EXCH]-Successfully contacted the OAB service at https://exchfe01.domain.com/EWS/Exchange.ascom. The elapsed time was 0 milliseconds.
Id      : 1014
Type    : Success
Message : [EXCH]-Successfully contacted the UM service at https://exchfe01.domain.com/UnifiedMessaging/Service.ascom. The elapsed time was 15 milliseconds.
Id      : 1013
Type    : Error
Message : When contacting https://owa.domain.com/EWS/Exchange.ascom received the error The request failed with HTTP status 401: Unauthorized.
Id      : 1016
Type    : Error
Message : [EXPR]-Error when contacting the AS service at https://owa.domain.com/EWS/Exchange.ascom. The elapsed time was 0 milliseconds.
Id      : 1015
Type    : Success
Message : [EXPR]-Successfully contacted the OAB service at https://owa.domain.com/EWS/Exchange.ascom. The elapsed time was 0 milliseconds.
Id      : 1014
Type    : Success
Message : [EXPR]-Successfully contacted the UM service at https://owa.domain.com/UnifiedMessaging/Service.ascom. The elapsed time was 0 milliseconds.
Id      : 1017
Type    : Success
Message : [EXPR]-Successfully contacted the RPC/HTTP service at https://owa.domain.com/Rpc. The elapsed time was 0 milliseconds.
Id      : 1006
Type    : Success
Message : The Autodiscover service was tested successfully.
Id      : 1021
Type    : Information
Message : The following web services generated errors.
              As in EXPR
          Please use the prior output to diagnose and correct the errors.
 
 
As it stands:
 
external users:        
can access owa using https://owa.domain.com/owa
all internal users in other sites than the main site:
 can access owa using the above plus both https://exchfe01.domain.com/owa and https://exchfe02.domain.com/owa        
some internal users:         in the main site can access owa using the latter 2 URLs above but not https://owa.domain.com/owa
I am logging on with the same account to each computer to try which is a domain admin account with full exch permissions
 
Does this mean anything to anyone as I am confused?
Thanks in advance
0
 

Author Comment

by:IntoFOS
ID: 22799859
I have fixed the problem.

After a lot of testing I was sure the problem was related to the NLB cluster, so I trashed the existing cluster, reconfigured a new one and now everything is working like a charm.

I will award 250 points to Exchange_Geek for the effort.
Thank you again.

Cheers
0
 

Author Closing Comment

by:IntoFOS
ID: 31508906
Thanks Exchange_Geek.
0

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In-place Upgrading Dirsync to Azure AD Connect
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses
Course of the Month10 days, 13 hours left to enroll

628 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question