• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

OWA External Access - No URL / URL Invalid

CyberKatPR

New Member
Outlook version
Outlook on the web
Email Account
Exchange Server 2010
#1
Hi everyone!

I am wondering if any of you have experienced this at some point. I am performing a migration from EX2003 to EX2010. Everything is working as expected, however, OWA is only accessible from LAN. When trying to reach OWA from the Internet, everyone gets;

Invalid URL

The requested URL "[no URL]", is invalid.
Reference #...

It happens in IE, chrome, Android...I have tried different computers and devices.

External DNS record (mail2.domain.com) resolves to the right IP, Cisco confirmed 443 traffic is reaching the firewall and being forwarded to the right IP/host. SMTP traffic is reaching the barracuda and mail flow has not been affected. OWA 2003 is accessible externally from mail.domain.com, which leaves EX2010 as the point of failure (firewall is off).

I have checked the event viewer and the only entry related to OWA (2010) refers to;

*********************************************************************************************************************
Event 1310, ASP.net 2.0.50727.0

Exception information:
Exception type: ConfigurationErrorsException
Exception message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. (E:\Program Files\Exchange\V14\ClientAccess\owa\web.config line 37)

Request information:
Request URL: https://hostname.domain.local:443/exchange/default.aspx
Request path: /exchange/default.aspx
User host address: IP
User:
Is authenticated: False
Authentication Type:
Thread account name: IIS APPPOOL\DefaultAppPool.

Exception information:
Exception type: ConfigurationErrorsException
Exception message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond
application level. This error can be caused by a virtual directory not being configured as an application in IIS.
(E:\Program Files\Exchange\V14\ClientAccess\owa\web.config line 37)

Request information:
Request URL: https://hostname.domain.local:443/exchange/default.aspx
Request path: /exchange/default.aspx
User host address: IP
User:
Is authenticated: False
Authentication Type:
Thread account name: IIS APPPOOL\DefaultAppPool

Thread information:
Thread ID: 31
Thread account name: IIS APPPOOL\DefaultAppPool
Is impersonating: False
Stack trace: at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean
checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
at System.Web.Configuration.RuntimeConfig.GetSectionObject(String sectionName)
at System.Web.Configuration.RuntimeConfig.GetSection(String sectionName, Type type, ResultsIndex index)
at System.Web.Configuration.RuntimeConfig.get_Identity()
at System.Web.HttpContext.SetImpersonationEnabled()
at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)

*********************************************************************************************************************

However, the above warning doesn't occur if one uses https://cert_hostname.domain.com:443(internally), which makes believe that it is not related to the main issue. We have deployed a GoDaddy SAN Cert that includes autodiscover, legacy, domain.com, mail, mail2...but the issue (unable to reach OWA externally) presented before the cert installation.

Any pointers?

Your help and knowledge will be greatly appreciated,


George
 

Similar threads