exchange 2013 mail flow issues

Incoming mail is working must out going mail is getting stuck in the queue

LED=441 4.4.1 Error Encountered while communicating with primary target IP address. Failed to connect. Winsock Error code 10061. Win32
error code 10061 attempted to failover to alternate host.

Exchange 2013 /windows 2012 server -  just done a migration and changed the receive connect to the new exchange 2013 server
DeepinInfrastructure Engineer Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
How are you sending mail? Do you have a send connector pointing to a SMTP smart host? Do you have proper NAT-ing in place from your smart host to your Exchange 2013 server?

DeepinInfrastructure Engineer Author Commented:
Mail is been pointed to a smart host - third party spam company's records
Will SzymkowskiSenior Solution ArchitectCommented:
From the Exchange 2013 server can you telnet to it and send a test email?

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.

I'd check windows server firewall (turn off for testing), exchange services (all started?), smart host authentication (if the smart host requires it), perhaps verify with these sites and tools:

DeepinInfrastructure Engineer Author Commented:
Server accepts a telenet command, I've not tried sending a mail via telnet

Rob - first thing I checked windows firewall has been disabled
DeepinInfrastructure Engineer Author Commented:
there was a firewall rule on the sonicwall to allow smtp traffic  from the old server only, changed to new server and its working now

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DeepinInfrastructure Engineer Author Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for Deepin's comment #a40837926

for the following reason:

Resolve was resolved by myself
Will SzymkowskiSenior Solution ArchitectCommented:
Please accept the below comment as the solution as NAT-ing has been stated already in my first comment.

NAT-ing is the terminology for what you have done for correcting your issue.

Will Szymkowski2015-06-18 at 14:33:59ID: 40837791

How are you sending mail? Do you have a send connector pointing to a SMTP smart host? Do you have proper NAT-ing in place from your smart host to your Exchange 2013 server?

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.