asked on 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
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
Exchange
Last Comment
Will Szymkowski
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Mail is been pointed to a smart host - third party spam company's records
From the Exchange 2013 server can you telnet to it and send a test email?
Will.
Will.
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:
http://exchangeserverpro.com/configuring-outbound-mail-flow-in-exchange-server-2013/
http://mxtoolbox.com/public/tools/emailheaders.aspx
https://testconnectivity.microsoft.com/
Rob
http://exchangeserverpro.com/configuring-outbound-mail-flow-in-exchange-server-2013/
http://mxtoolbox.com/public/tools/emailheaders.aspx
https://testconnectivity.microsoft.com/
Rob
ASKER
Server accepts a telenet command, I've not tried sending a mail via telnet
Rob - first thing I checked windows firewall has been disabled
Rob - first thing I checked windows firewall has been disabled
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
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
Accepted answer: 0 points for Deepin's comment #a40837926
for the following reason:
Resolve was resolved by myself
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?
Will.
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?
Will.