E-mails are not going out.  all emails stuck in queue exchange 2013

Hi

I have installed new Exchange server for my company.. but e-mails are not going out from my domain.. I am getting below error.

MX, RDS, Exchange connectivity analyzer all going good.  but e-mail are not going out.

getting below error. if some body can help...

gmail.com    DnsConnectorDelivery    Retry    2    "Saturday, July 05, 2014 1:31:10 PM"    "[{LRT=7/4/2014 12:09:04 PM};{LED=441 4.4.1 Error encountered while communicating with primary target IP address: ""Failed to connect. Winsock error code: 10049, Win32 error code: 10049."" Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 173.194.75.26:25};{FQDN=gmail.com};{IP=173.194.75.26}]"


hotmail.com    DnsConnectorDelivery    Retry    2    "Saturday, July 05, 2014 1:30:53 PM"    "[{LRT=7/5/2014 1:09:40 PM};{LED=441 4.4.1 Error encountered while communicating with primary target IP address: ""Failed to connect. Winsock error code: 10049, Win32 error code: 10049."" Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 65.54.188.72:25};{FQDN=hotmail.com};{IP=65.54.188.72}]"

 

July 6th, 2014 8:48am

Is it just Hotmail and Gmail that are giving the error? They typically have "different" spam filtering than a company running there own email server. If you are only being blocked by these services then look at getting delisted from these filters or sending your outbound email via a filtering service so you don't need to deal with this issue.

If its all domains regardless that generates the error then its firewalling issues and so make sure you have TCP 25 outbound to all IP addresses. To test this install the telnet client on your exchange server and see what happens when you enter telnet ip 25 where ip is the IP listed in the error below

Brian Reid

Exchange MVP and Exchange and Office 365 Certified Master
www.c7solutions.com

Free Windows Admin Tool Kit Click here and download it now
July 6th, 2014 12:01pm

From Exchange Management Shell run "Get-Queue | FL *error*" to get the last error on any queue and post one example back here please.

Also run "Get-Message | FL *error*" to get the last error on messages and post one example back here please.

Then also enable protocol logging on the send connector you have configured - "Get-SendConnector | Set-SendConnector -ProtocolLoggingLevel Verbose" (or see http://technet.microsoft.com/en-us/library/bb124531(v=exchg.150).aspx) and then after five or ten minutes open the log at C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\Hub\ProtocolLog\SmtpSend (Exchange 2010 is V14 and not V15 and no Hub folder).

Here you will see the entire conversation between your server and the one you are connecting to. Post a section here that contains an error, or if no error (it just sends 221 QUIT) then post the entire conversation (remove IP's and domains from posting first please).

July 6th, 2014 1:52pm


Hi Brian

Thanks for your support.

please find the below details..


1)


[PS] C:\Windows\system32>Get-Queue | FL *error*


LastError : [{LRT=7/7/2014 12:17:20 AM};{LED=441 4.4.1 Error encountered while communicating with primary target IP
            address: "Failed to connect. Winsock error code: 10049, Win32 error code: 10049." Attempted failover to
            alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all
            alternate hosts. The last endpoint attempted was 66.196.118.35:25};{FQDN=yahoo.com};{IP=66.196.118.35}]

LastError : [{LRT=7/7/2014 12:10:25 AM};{LED=441 4.4.1 Error encountered while communicating with primary target IP
            address: "Failed to connect. Winsock error code: 10051, Win32 error code: 10051." Attempted failover to
            alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all
            alternate hosts. The last endpoint attempted was
            2607:f8b0:400c:c01::1b:25};{FQDN=gmail.com};{IP=2607:f8b0:400c:c01::1b}]

LastError :


2)


[PS] C:\Windows\system32>Get-Message | FL *error*


LastError :

LastError :

LastError :


3)


[PS] C:\Windows\system32>Get-SendConnector | Set-SendConnector -

ProtocolLoggingLevel Verbose
[PS] C:\Windows\system32>




after 30 Min .. last few lines from ( C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\Hub\ProtocolLog\SmtpSend )

File Name -- SEND20140706-1

2014-07-06T18:58:02.911Z,Internet Connector,08D1672E934C96C7,1,,98.138.112.35:25,*,,"Failed to connect. Winsock error code: 10049, Win32 error code: 10049, Error Message: The requested address is not valid in its context 98.138.112.35:25"
2014-07-06T18:58:02.911Z,Internet Connector,08D1672E934C96C8,0,,63.250.192.46:25,*,,attempting to connect
2014-07-06T18:58:02.911Z,Internet Connector,08D1672E934C96C8,1,,63.250.192.46:25,*,,"Failed to connect. Winsock error code: 10049, Win32 error code: 10049, Error Message: The requested address is not valid in its context 63.250.192.46:25"
2014-07-06T18:58:02.911Z,Internet Connector,08D1672E934C96C9,0,,98.136.217.203:25,*,,attempting to connect
2014-07-06T18:58:02.911Z,Internet Connector,08D1672E934C96C9,1,,98.136.217.203:25,*,,"Failed to connect. Winsock error code: 10049, Win32 error code: 10049, Error Message: The requested address is not valid in its context 98.136.217.203:25"
2014-07-06T18:58:02.911Z,Internet Connector,08D1672E934C96CA,0,,98.138.112.37:25,*,,attempting to connect
2014-07-06T18:58:02.911Z,Internet Connector,08D1672E934C96CA,1,,98.138.112.37:25,*,,"Failed to connect. Winsock error code: 10049, Win32 error code: 10049, Error Message: The requested address is not valid in its context 98.138.112.37:25"
2014-07-06T18:58:02.911Z,Internet Connector,08D1672E934C96CB,0,,66.196.118.37:25,*,,attempting to connect
2014-07-06T18:58:02.911Z,Internet Connector,08D1672E934C96CB,1,,66.196.118.37:25,*,,"Failed to connect. Winsock error code: 10049, Win32 error code: 10049, Error Message: The requested address is not valid in its context 66.196.118.37:25"
2014-07-06T18:58:02.911Z,Internet Connector,08D1672E934C96CC,0,,98.138.112.32:25,*,,attempting to connect
2014-07-06T18:58:02.911Z,Internet Connector,08D1672E934C96CC,1,,98.138.112.32:25,*,,"Failed to connect. Winsock error code: 10049, Win32 error code: 10049, Error Message: The requested address is not valid in its context 98.138.112.32:25"
2014-07-06T18:58:02.911Z,Internet Connector,08D1672E934C96CD,0,,66.196.118.33:25,*,,attempting to connect
2014-07-06T18:58:02.911Z,Internet Connector,08D1672E934C96CD,1,,66.196.118.33:25,*,,"Failed to connect. Winsock error code: 10049, Win32 error code: 10049, Error Message: The requested address is not valid in its context 66.196.118.33:25"
2014-07-06T18:58:02.911Z,Internet Connector,08D1672E934C96CE,0,,98.138.112.38:25,*,,attempting to connect
2014-07-06T18:58:02.911Z,Internet Connector,08D1672E934C96CE,1,,98.138.112.38:25,*,,"Failed to connect. Winsock error code: 10049, Win32 error code: 10049, Error Message: The requested address is not valid in its context 98.138.112.38:25"


Free Windows Admin Tool Kit Click here and download it now
July 6th, 2014 3:13pm

Exchange server is on my local subnet ... I have done 1-1 Nat in my firewall for outside connectivity.

Internet is working fine .. I can ping any destination .

I can also telnet to other mail servers on Port 25.

Ping result ..

Pinging 98.138.112.35 with 32 bytes of data:
Reply from 98.138.112.35: bytes=32 time=312ms TTL=47
Reply from 98.138.112.35: bytes=32 time=311ms TTL=47

Pinging 98.136.217.203 with 32 bytes of data:
Reply from 98.136.217.203: bytes=32 time=261ms TTL=44
Reply from 98.136.217.203: bytes=32 time=261ms TTL=44

Pinging 66.196.118.35 with 32 bytes of data:
Reply from 66.196.118.35: bytes=32 time=238ms TTL=43
Reply from 66.196.118.35: bytes=32 time=238ms TTL=43

Telnet 98.138.112.35 on port 25

220 mta1371.mail.ne1.yahoo.com ESMTP ready

Telnet 98.136.217.203 on port 25

220 mta1406.mail.gq1.yahoo.com ESMTP ready

For Send connector I am using -- Mx Record associated with Recipient Domain

I am using same setting as in below given web page..

http://careexchange.in/how-to-create-a-send-connector-in-exchange-2013/

Thanks & Regards,

Raman

July 6th, 2014 3:49pm

Please provide the output from ipconfig /all on each Exchange Server and Get-SendConnector | FL.

Thanks

Brian

Free Windows Admin Tool Kit Click here and download it now
July 6th, 2014 4:06pm

OK. As it is a domain joined machine its DNS should be the domain controller(s) and nothing else - suspect your second DNS entry is wrong.

The second connector is bound to 0.0.0.0 as the source IP address. Do you have something else that is attempting to bind to that address as well please (netstat -ano | find ":25" should show that (from admin cmd prompt and not PowerShell)

July 6th, 2014 4:22pm

1)

The Second DNS Server is from my ISP

2)

The output of netstat -ano | find ":25"

 TCP    0.0.0.0:25             0.0.0.0:0              LISTENING       6780
 TCP    0.0.0.0:2525           0.0.0.0:0              LISTENING       8220
 TCP    192.168.2.11:2525      192.168.2.11:53237     ESTABLISHED     8220
 TCP    192.168.2.11:53237     192.168.2.11:2525      ESTABLISHED     6780
 TCP    [::]:25                [::]:0                 LISTENING       6780
 TCP    [::]:2525              [::]:0                 LISTENING       8220

3)

I have already tried with Disabling my Antivirus but no improvement.

Thanks for All you support Brian..

Thanks & Regards,

Raman

Free Windows Admin Tool Kit Click here and download it now
July 6th, 2014 4:32pm

Good - can you mark the above response as the answer please
July 7th, 2014 6:02am

Thanks Brian.

Its working after removing the Antivirus & Second DNS entry ..

Thanks very much for all your support.

Thanks & Regards,

Raman

  • Marked as answer by Raman10181 Monday, July 07, 2014 9:59 AM
  • Unmarked as answer by Raman10181 Monday, July 07, 2014 9:59 AM
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2014 9:52am

Thanks Brian.

Its working after removing the Antivirus & Second DNS entry ..

Thanks very much for all your support.

Thanks & Regards,

Raman

  • Marked as answer by Raman10181 Monday, July 07, 2014 9:59 AM
  • Unmarked as answer by Raman10181 Monday, July 07, 2014 9:59 AM
July 7th, 2014 12:52pm

The fix for this is to setup a receive connector on the old box (2007/2010) as the name of the server you've just put in

Specify the FQDN as that of the existing exchange 07/10 server

Give the connector the remote ip of the new exchange 2013 server and set for it to receive mail from any IP on port 25

Supply it with TLS and Exchange Server auth and Exchange Servers and Legacy Exchange servers Permissions and all should work fine

Free Windows Admin Tool Kit Click here and download it now
October 24th, 2014 11:47am

The fix for this is to setup a receive connector on the old box (2007/2010) as the name of the server you've just put in

Specify the FQDN as that of the existing exchange 07/10 server

Give the connector the remote ip of the new exchange 2013 server and set for it to receive mail from any IP on port 25

Supply it with TLS and Exchange Server auth and Exchange Servers and Legacy Exchange servers Permissions and all should work fine

  • Proposed as answer by Adz Net Man 21 hours 10 minutes ago
October 24th, 2014 3:39pm

RichKingstongold thank you that worked great
Free Windows Admin Tool Kit Click here and download it now
July 29th, 2015 6:22am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics