Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


Exchange Back-end server dropping the IIS connection to the Front-end server

Posted on 2006-06-17
Medium Priority
Last Modified: 2008-01-09
We currently 2 exchange servers one running win 2000 O.S. with exchange 2003 (front-end) and  the other win 2003 ENT running the exchange 2003 (back-end).

The problem is that it is dropping the Webmail (OWA) connection; this means that Webmail (OWA) can not be accessed at all, internally or externally .
but all the services are running non have failed it just does not allow to access to the Webmail (OWA). to currently fix this problem that keeps reoccurring about the same time everyday. I run the IISRESET on the Back-end server and it fixes the problem for a bit and then it goes down again.

The other things that it is doing are:
Can not get to the OMA page and or any page that is set up on the front-end server to test if IIS failed or not.
When trying to access the exchange system manager on the both servers we receive an error that reads:

[“Access is Denied”
Facility: Win32
ID no: c00700005
Exchange system manager.]

The only way we have found to fix this is to reboot the server.
This problem also make adding users or modifying exchange in any way impossible.
Any feedback would be appreciated

Thank you, and God bless
Question by:cfricke1
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
  • 3
  • 3
LVL 104

Expert Comment

ID: 16975957
Anything between the servers?
Anything else in the event logs on the server?

Are all the servers fully up to date on patches, services packs and the like - for both Windows and Exchange.


Author Comment

ID: 16976517

yes the systems are both up 2 date.
well the front-end server is in our DMZ.
all the ports for the connection between the servers have been open on the firewall.

Thank you Very much for your Responce.

LVL 104

Expert Comment

ID: 16978297
The frontend server being in the DMZ is probably the source of the problem.
I don't deploy frontend servers in a DMZ for any reason as I don't see the point.

Once you have opened all the ports and made the changes to the Exchange config to support the DMZ then you have effectively made the firewall swiss cheese and the security "benefits" have gone.

A better option would be to bring the server inside and have the ports required (443 and 25) open directly. Otherwise deploy an ISA server in to the DMZ on a workgroup machine. Domain members do not belong in the DMZ.

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!


Author Comment

ID: 17004978
I can see the sense in doing like that it would be better.
Thank you

Now of course there are other problems that have come up.
I’m having problems with OWA it only allows a handful of users to log on to it.
All of the users have the permissions needed to access the OWA.
I have looked a few post that I found on this site it has helped a bit but once I fix one problem another pops up.

For example:
My account via the OWA can’t be accessed it gives me an error reading:

The page cannot be displayed
There is a problem with the page you are trying to reach and it cannot be displayed.
Please try the following:
•      Open the webmail.mydomain.org home page, and then look for links to the information you want.
•      Click the Refresh button, or try again later.
•      Click Search to look for information on the Internet.
•      You can also see a list of related sites.

HTTP 500 - Internal server error
Internet Explorer

Sorry to push this other problem onto you also but as far as I can see on this site you’re the Man to talk to.
I tried one of the fixes for the redirect and that is where, all of my problems began.
Because I was not able to just type in the URL “webmail.mydomain.org” it requested me to use the https:// prefix. It still does not work correctly yet.

Thank you again
LVL 104

Accepted Solution

Sembee earned 1000 total points
ID: 17005019
You may have better luck closing this question and opening the question in a new one - I am not always around to answer questions.

Does OWA work inside? Direct to the backend server?
Turn off the require SSL option on the /exchange virtual directory.


Author Comment

ID: 17005109
thank you
for all of you help

Featured Post

Independent Software Vendors: 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!

Question has a verified solution.

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

This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
Know the reasons and solutions to move/import EDB to New Exchange Server. Also, find out how to recover an Exchange .edb file and to restore the file back.
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…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
Suggested Courses

610 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