Exchange 2013 only sends mail during restart

Here is an odd problem, We are upgrading our Exchange 2007 server to a 2013 server, we have most of the problems sorted out and most things are working.

basically the 2007 server is fully functional and can send emails to users whom reside on the 2013 server, but the 2013 server can only send mail during a reboot, if you send an email it sits in the queue until the server is restarted then it sends them all out at once and proceeds to stop sending them.

The 2013 sends through the 2007 server as a smart host for now (until we fully move to the 2013 server), this happens to both internal and external destinations.

The error that the queue shows while the messages are stuck in the queue on the 2013 is 441 4.4.1 (Socket Error)

My next steps in debugging this issue are to see which service specifically (if any) need to be restarted for this to happen, or if it only happens on a full server reboot. I'm thinking its another service on the server blocking the connections, Wanted to see what you guys thought.
RyanTimmons91Asked:
Who is Participating?
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hi,

What AV measures are installed on this new box? It sounds like exchange boots, sends mail and than some AV product (or malware) is starting later preventing to send mail.
0
 
dsnegi_25decCommented:
Transport service is responsible

http://blogs.technet.com/b/rischwen/archive/2013/03/13/exchange-2013-mail-flow-demystified-hopefully.aspx

my first recommendation is go for latest SP.
Can  you disable the antivirus  & check the status .
Hope Disk is available .
0
 
RyanTimmons91Author Commented:
We are running GFI Viper Business agents on our network for AV, its a fresh installation and malware is unlikely.

Ill take a look at that link, thanks.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
RyanTimmons91Author Commented:
we installed CU3  on the exchange 2013, SP1 is not out yet on that, we have Update Rollup 11 on the exchange 2007 machine.

that link explains how everything works nicely, but doesn't really offer any insight on how to fix the issue, ill look through the AV and possibly remove it to check it
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hi Ryan,

In
some AV product (or malware) is starting later preventing to send mail
i ment malware tools like malwarebytes, i did not mean you had malware on the system.
0
 
RyanTimmons91Author Commented:
Alright, i went ahead and uninstalled Viper from the system to test and mail immediately started flowing to the 2007 server. I suppose I should have tested that before I posted here but it was late and I was a little off my game. Thank you guys!
0
 
RyanTimmons91Author Commented:
Thanks for the insight.
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Youre welcome
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.