Solved

OWA works externally but not internally

Posted on 2013-01-14
4
716 Views
Last Modified: 2013-03-26
Server :- Windows SBS 2008
Exchange :- Exchange 2007
External url for email :- remote.helpme.com      ( for eg )
Internal FQDN server.expert.local           ( for eg )
IP range of domain :- 192.168.16.X
Server has 3 ip's. 192.168.16.2, 192.168.16.25, 192.168.16.26

OWA works externally but internally when you try to use it, its trying to use a customized website we have in IIS and not sbs web applications.

also when users are opening outlook they are getting SSL mismatch errors as its trying to use the SSL for the customized website and not the SSL bound to exchange.

Given the above Im guessing the bindings are stuffed but on the face of it. It looks good.

I have customized website bound for HTTP and SSL to .26 and sbs web applications bound to .25
 
When i ping url of remote.helpme.com it return .26 but if i try to web browse there it opens the customized website.

What predated the above was

1 - Resetting of IIs virtual directories for exchange ( to try to address an iphone sync issue which still exists )

2 - changing external and internal uri's to match remote.helpme.com

Anyhelp is very much appeciated.
0
Comment
Question by:Marshes
[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
  • 2
4 Comments
 

Accepted Solution

by:
Marshes earned 0 total points
ID: 38773927
Seems we have gotten past this issue onto another one.

The customized website was using the SSL for remote.company.com for some reason. Changed this, reset iis and we got past that one.

Please delete this thread.
0
 
LVL 35

Expert Comment

by:Cris Hanna
ID: 38776079
Just as an FYI...your configuration (having your domain controller multi-homed) is not supported by Microsoft
0
 
LVL 6

Expert Comment

by:crash2000
ID: 38777305
internally, it is better to use https://servername/owa

Mark
0
 

Author Closing Comment

by:Marshes
ID: 39020761
Fixed it.
0

Featured Post

Revamp Your Training Process

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action.

Question has a verified solution.

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

Read this checklist to learn more about the 15 things you should never include in an email signature.
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta‚Ķ
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates‚Ķ

734 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