• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 284
  • Last Modified:

MS Exchange 2007 seems to stop receiving mail after a number of hours

Dear Experts,

We have an Exchange 2007 server that works brilliantly for a few hours, but then after 4 or 5 hours seems to stop receiving mail from external sources. I've tried stoppping and starting all the exchange services to remedy this but it does not seem to work. Messages are still received internally. The only cure that I can find is to to a full re boot of the server. If it helps, when this error occurs, users at home can no longer access the OWA element (web outlook).

If anybody can provide any solutions/help/advice or could just point me in the right direction I would be very grateful.

andymellor
0
andymellor
Asked:
andymellor
  • 5
  • 2
1 Solution
 
florin_sCommented:
0
 
andymellorAuthor Commented:
Hi there,

The info contained in these kb pages don't really relate. To be honest there are no entries in any section of event viewer that suggest a possible cause.

Does anybody know of anyway I can debug this. A log file or event log I can look at?

Cheers
0
 
andymellorAuthor Commented:
I have installed rollup 6 for Exchange 2007 but the error still exists.

Just to reiterate - my exchange 2007 server works perfectly for a number of hours before it seems to stop receiving any external originating email. It also does not allow any remote users to connect via OWA. I've tried reatrting every Exchange service but no joy. Is exchange stopping this traffic for a reason?

The only fix is to reboot.

Help!
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
andymellorAuthor Commented:
I'm getting this error in my Application Event log.

Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1936). Exchange Active Directory Provider failed to obtain DNS records for forest DC=counthill,DC=org,DC=uk. DNS Priority and Weight for the Global Catalog servers in this forest will be set to the default values 0 (priority) and 100 (weight).  

Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1936). Exchange Active Directory Provider failed to obtain DNS records for domain counthill.org.uk. DNS Priority and Weight for the Domain Controllers in this domain will be set to the default values 0 (priority) and 100 (weight).

Could this be the problem?
0
 
andymellorAuthor Commented:
Does anybody have any advice on this?

Cheers
0
 
andymellorAuthor Commented:
Helpful - but not a solution. Thanks.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now