Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 350
  • Last Modified:

Exchange 2013 No Mail Flow

All of a sudden today mail flow has stopped both internally and externally on my Exchange 2013 server.  I also have an Exchange 2010 server running on SBS 2011 in the same environment that is not used.  When I try to open the Exchange Toolbox both on the Windows Server 2012 R2 that is running Exchange 2013 and on another 2012 R2 server with the Exchange Toolbox the MMC crashes.  I opened Exchange Management Shell and I get the error:

VERBOSE: Connecting to Server2.domain.local.
New-PSSession : [Server2.domain.local] Connecting to remote server Server2.domain.local failed with the following error
message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
VERBOSE: Connecting to Server2.domain.local.
New-PSSession : [Server2.domain.local] Connecting to remote server Server2.domain.local failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed

After it has failed trying to connect to the Exchange Server 2013 it will try and connect to the Exchange 2010 SBS 2011 and will be successful.  All services are running that should be for Exchange.  I have checked IIS Manager and both the Default Web Site and the Exchange Back End https bindings are bound to the correct certificate.

I have tried shutting down the Exchange 2010 SBS 2011 server and restarting the Exchange 2013 server and I get the same issues in EMS and the Toolbox.  Mail flow also does not return internally or externally.

Any assistance would be of much help.

Thanks.
0
ollybuba
Asked:
ollybuba
  • 2
1 Solution
 
R--RCommented:
Check the time sync between the DC and Exchange server. check if the user on Exchange 2013 can send mail to itself. Also let us know how the emails route in/out of organization. C
0
 
ollybubaAuthor Commented:
I use a McAfee SaaS spam filter and traffic is pointed towards that..  I changed my smart host back to use my local MX records when I first started having issues with mail flow.    I also have a record in my DNS for mail.domain.local and I removed my other two MX records for my smart host.  I was still unable to send internal mail even to myself.  I have two DCs in my environment and I made sure that the information had replicated.  My DNS was also changed and my server was on for hours after that.  I had my Exchange server off for about 10 hours and I just turned it back on.  All of a sudden internal mail flow started working again.  EMS also connects to the exchange server and the Toolbox opens properly.  Does anyone have any ideas as to why this would have started working again after having the sever off for an extended period of time?
0
 
ollybubaAuthor Commented:
This problem was able to correct itself by having the server off for a few hours.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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