HELP!!!! Exchange 2010 Receive Connector

[Darthfaded]

Ok so here is my situation as I have it now.... I am totally stumped and I could really use a little help.

 

I have deployed a new Exchange 2010 server at my office,

I am not using edge transport since I have it installed bundled with SBS 2011 so AD is running on the same box.

 

Confirmed my smtp connector is working.

Mail sent to exchange users from within the exchange environment work, whether locally or remotely.

 

I have properly forwarded my MX records with our DOMAIN and an NSlookup of the CNAME that I set up for the exchange properly points to our exchange server IP.

 

Sadly I have a crappy router on our network, and are using a Verizon Westell 327w, I have port forwarding setup for Terminal Services, and that works fine, I have configured port 25 to be forwarded to the exchange server behind the firewall. I also have port 443 and 80 forwarded as well, which both of those forwards seems to be working.

 

I have made sure to allow anonymous permissions on the receive connector, as well as all available ip addresses.

 

I can telnet in to the exchange server from inside the firewall, but not externally, which leads me to believe it is a Port forwarding issue from outside the firewall, but as I said, all my other forwards are working fine.

 

EVERYTHING works except receiving mail from outside mail servers, and I have been ripping my hair out for 2 days now trying to figure it out...

 

Maybe there is something specific to port 25 that is causing the issue? I even tried having the exchange server listen on another port, and change the port forwarding to divert port 25, to the alternate port on the exchange and still nothing...

 

We have Verizon Business DSL, and according to the sadly inept supposed tier 2 rep I talked to, Port 25 is NOT blocked for incoming traffic.

 

In the receive connector I have the permissions set to accept anonymous permissions, and the IP range is accept any email from 0.0.0.0-255.255.255.255 are there any other specific settings in the receive connector or anywhere else for that matter, that would deny access to computers outside my lan? Can someone walk me through the exact steps for setting one up just in case I am missing something?

 

ANY help is greatly appreciated... I am already way over the timeframe I anticipated for deploying this exchange....

 

thanks...

[sukh]

Start with this - https://www.testexchangeconnectivity.com/

 

Seems like an issue with port forwarding.

 

Also, up the logging on the receive connector. - Configure Protocol Logging: Exchange 2010 Help

 

Also run Get-ReceiveConnector | fl and post the results (do from EMS).

[Darthfaded]

RunspaceId : ecbe853f-1fc6-4a99-8252-1abeafa7e98f

AuthMechanism : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer

Banner :

BinaryMimeEnabled : True

Bindings : {10.0.0.20:25}

ChunkingEnabled : True

DefaultDomain :

DeliveryStatusNotificationEnabled : True

EightBitMimeEnabled : True

BareLinefeedRejectionEnabled : False

DomainSecureEnabled : False

EnhancedStatusCodesEnabled : True

LongAddressesEnabled : False

OrarEnabled : False

SuppressXAnonymousTls : False

AdvertiseClientSettings : False

Fqdn : SERVER.SERVER.local

Comment :

Enabled : True

ConnectionTimeout : 00:10:00

ConnectionInactivityTimeout : 00:05:00

MessageRateLimit : unlimited

MessageRateSource : IPAddress

MaxInboundConnection : 5000

MaxInboundConnectionPerSource : unlimited

MaxInboundConnectionPercentagePerSource : 100

MaxHeaderSize : 64 KB (65,536 bytes)

MaxHopCount : 60

MaxLocalHopCount : 12

MaxLogonFailures : 3

MaxMessageSize : 10 MB (10,485,760 bytes)

MaxProtocolErrors : 5

MaxRecipientsPerMessage : 5000

PermissionGroups : AnonymousUsers, ExchangeUsers, ExchangeServers, ExchangeLegacyServers

PipeliningEnabled : True

ProtocolLoggingLevel : None

RemoteIPRanges : {0.0.0.0-255.255.255.255, 10.0.0.2-10.0.0.255, 10.0.0.0-10.0.0.0}

RequireEHLODomain : False

RequireTLS : False

EnableAuthGSSAPI : False

ExtendedProtectionPolicy : None

LiveCredentialEnabled : False

TlsDomainCapabilities : {}

Server : SERVER

SizeEnabled : EnabledWithoutValue

TarpitInterval : 00:00:05

MaxAcknowledgementDelay : 00:00:30

AdminDisplayName :

ExchangeVersion : 0.1 (8.0.535.0)

Name : Default SERVER

DistinguishedName : CN=Default SERVER,CN=SMTP Receive Connectors,CN=Protocols,CN=SERVER,C

N=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrativ

e Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configura

tion,DC=SERVER,DC=local

Identity : SERVER\Default SERVER

Guid : 975c4eef-6f56-47d6-ab26-2b6c06eea558

ObjectCategory : Server.local/Configuration/Schema/ms-Exch-Smtp-Receive-Connector

ObjectClass : {top, msExchSmtpReceiveConnector}

WhenChanged : 3/13/2012 7:41:10 PM

WhenCreated : 3/8/2012 12:13:17 PM

WhenChangedUTC : 3/14/2012 2:41:10 AM

WhenCreatedUTC : 3/8/2012 8:13:17 PM

OrganizationId :

OriginatingServer : SERVER.SERVER.local

IsValid : True

 

RunspaceId : ecbe853f-1fc6-4a99-8252-1abeafa7e98f

AuthMechanism : BasicAuth

Banner :

BinaryMimeEnabled : True

Bindings : {127.0.0.1:25}

ChunkingEnabled : True

DefaultDomain :

DeliveryStatusNotificationEnabled : True

EightBitMimeEnabled : True

BareLinefeedRejectionEnabled : False

DomainSecureEnabled : False

EnhancedStatusCodesEnabled : True

LongAddressesEnabled : False

OrarEnabled : False

SuppressXAnonymousTls : False

AdvertiseClientSettings : False

Fqdn : SERVER.SERVER.local

Comment :

Enabled : True

ConnectionTimeout : 06:00:00

ConnectionInactivityTimeout : 00:05:00

MessageRateLimit : unlimited

MessageRateSource : IPAddress

MaxInboundConnection : 5000

MaxInboundConnectionPerSource : 20

MaxInboundConnectionPercentagePerSource : 2

MaxHeaderSize : 64 KB (65,536 bytes)

MaxHopCount : 60

MaxLocalHopCount : 12

MaxLogonFailures : 3

MaxMessageSize : 10 MB (10,485,760 bytes)

MaxProtocolErrors : 5

MaxRecipientsPerMessage : 200

PermissionGroups : AnonymousUsers, ExchangeUsers

PipeliningEnabled : True

ProtocolLoggingLevel : None

RemoteIPRanges : {127.0.0.1-127.0.0.1}

RequireEHLODomain : False

RequireTLS : False

EnableAuthGSSAPI : False

ExtendedProtectionPolicy : None

LiveCredentialEnabled : False

TlsDomainCapabilities : {}

Server : SERVER

SizeEnabled : Enabled

TarpitInterval : 00:00:05

MaxAcknowledgementDelay : 00:00:30

AdminDisplayName :

ExchangeVersion : 0.1 (8.0.535.0)

Name : Windows SBS Fax Sharepoint Receive SERVER

DistinguishedName : CN=Windows SBS Fax Sharepoint Receive SERVER,CN=SMTP Receive Connectors,C

N=Protocols,CN=SERVER,CN=Servers,CN=Exchange Administrative Group (FYDIBO

HF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchan

ge,CN=Services,CN=Configuration,DC=SERVER,DC=local

Identity : SERVER\Windows SBS Fax Sharepoint Receive SERVER

Guid : c458b9da-a14f-468e-910b-9cef3eafb5c8

ObjectCategory : SERVER.local/Configuration/Schema/ms-Exch-Smtp-Receive-Connector

ObjectClass : {top, msExchSmtpReceiveConnector}

WhenChanged : 3/8/2012 12:51:58 PM

WhenCreated : 3/8/2012 12:51:57 PM

WhenChangedUTC : 3/8/2012 8:51:58 PM

WhenCreatedUTC : 3/8/2012 8:51:57 PM

OrganizationId :

OriginatingServer : SERVER.SERVER.local

IsValid : True

[sukh]

Results from the test?

[Darthfaded]

I didn't run it yet as I got stumped on what it was asking for on the Exchange Web services URL it was asking for... I pointed it at my server IP, but the rest of the URL it is asking for I am unsure about.

 

I havent fully implemented OWA yet. So I am not sure if it would actually workin....

[Darthfaded]

Ok here is another one...

 

I received 3 emails on the exchange.

2 from the USPS and another from a random email marketing company...

 

But I still can't send from yahoo or any other widely know email providers... to my exchange addresses without it being bounced to the secondary in my MX setting.

[sukh]

Bounced? Do you get an NDR? Can you post?

[Darthfaded]

Nope no NDR because I have a secondary MX delivery at lower priority incase delivery to the exchange server fails so the message still delivers to my other mailserver which is hosted IMAP.

 

Did the Get-ReceiveConnectors look setup properly to you?

[sukh]

That looks OK.

What test did you do? From the RCA did you do the internet inbound?

Connector logging?

[Darthfaded]

Yep DId receive connector wizard as Internet Inbound.

 

Are there any specific settings I should be looking at in the receive connector?

 

As far as logging... it looks like the instructions you posted are for edge transport setups, which I do not have since I am running exchange 2010 that is installed with SBS 2011.

 

Any ideas?

 

I have to assume that the port is set properly to forward through my router, since every other port forward I have set up is working.

[sukh]

Not the SBS wizrad, this - https://www.testexchangeconnectivity.com/

 

Connector logging is is as per post above, that still applies to SBS.

[Darthfaded]

I am not sure what my Exchange Web Services URL is....

 

It says "Enter the full URL for Exchange Web Services in your environment. Typically, this will be something like https://mail.contoso.com/EWS/Exchange.asmx."

 

Where would I find that? or is there more that I have to configure.

[sukh]

You are selecting the Internet Inbound Test?

[Darthfaded]

ok it was received via the internet inbound test from microsoft, on my exchange, but no other emails passthrough???

[sukh]

Can you post the results?

[Darthfaded]

Testing Mail Exchanger *****.******.com.

This Mail Exchanger was tested successfully.

 

Test Steps

 

Attempting to resolve the host name *****.******.com in DNS.

The host name resolved successfully.

 

Additional Details

Testing TCP port 25 on host *****.******.com to ensure it's listening and open.

The port was opened successfully.

 

Additional Details

Banner received: 220 *****.******.com Microsoft ESMTP MAIL Service ready at Wed, 14 Mar 2012 14:55:40 -0700

Attempting to send a test e-mail message to *****@*****.com using MX *****.******.com.

The test message was delivered successfully.

Testing the MX *****.******.com for open relay by trying to relay to user [email protected].

The Open Relay test passed. This mx isn't an open relay.

 

Additional Details

The open relay test message delivery failed, which is a good thing.

The exception detail:

Exception details:

Message: Mailbox unavailable. The server response was: 5.7.1 Unable to relay

Type: System.Net.Mail.SmtpFailedRecipientException

Stack trace:

at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender, MailAddressCollection recipients, String deliveryNotify, SmtpFailedRecipientException& exception)

at System.Net.Mail.SmtpClient.Send(MailMessage message)

at Microsoft.Exchange.Tools.ExRca.Tests.SmtpOpenRelayTest.PerformTestReally()

[sukh]

OK, so what happens if you send an email from say hotmail? Do you get an NDR?

 

Connector logging on yet?

[Darthfaded]

I believe I have the smtp receive logger on now...

 

No NDR because the mail still delivers to my alternate mail server.

[sukh]

Was that test above going to your Exch server or the IMAP?

Can you send an email and see if it hits Exchange, have a look at the logs

[Darthfaded]

I am having a hard time enabling receiveconnector logging because the instructions you posted earlier for edge transport which I am not using.

[sukh]

You do have the Exchange Management Console right, go there and on the connector change to verbose.

[Darthfaded]

My brain is fried... ok I got it...

 

Logs that were already there are saying 421 4.3.2 Service not available, but that was from last night...

 

How can I try to send an email and see the log results immediately?

[sukh]

Send via hotmail and you should see if a connection attempt is made.

[Darthfaded]

2012-03-14T23:12:55.585Z,SERVER\Internet,08CECF9E822D0C90,0,10.0.0.20:25,108.170.16.119:44024,+,,

2012-03-14T23:12:55.650Z,SERVER\Internet,08CECF9E822D0C90,1,10.0.0.20:25,108.170.16.119:44024,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions

2012-03-14T23:12:55.650Z,SERVER\Internet,08CECF9E822D0C90,2,10.0.0.20:25,108.170.16.119:44024,>,"220 ******.com Microsoft ESMTP MAIL Service ready at Wed, 14 Mar 2012 16:12:54 -0700",

2012-03-14T23:12:55.722Z,SERVER\Internet,08CECF9E822D0C90,3,10.0.0.20:25,108.170.16.119:44024,<,EHLO headfly.info,

2012-03-14T23:12:55.722Z,SERVER\Internet,08CECF9E822D0C90,4,10.0.0.20:25,108.170.16.119:44024,>,250-******.com Hello [108.170.16.119],

2012-03-14T23:12:55.722Z,SERVER\Internet,08CECF9E822D0C90,5,10.0.0.20:25,108.170.16.119:44024,>,250-SIZE 10485760,

2012-03-14T23:12:55.722Z,SERVER\Internet,08CECF9E822D0C90,6,10.0.0.20:25,108.170.16.119:44024,>,250-PIPELINING,

2012-03-14T23:12:55.722Z,SERVER\Internet,08CECF9E822D0C90,7,10.0.0.20:25,108.170.16.119:44024,>,250-DSN,

2012-03-14T23:12:55.722Z,SERVER\Internet,08CECF9E822D0C90,8,10.0.0.20:25,108.170.16.119:44024,>,250-ENHANCEDSTATUSCODES,

2012-03-14T23:12:55.723Z,SERVER\Internet,08CECF9E822D0C90,9,10.0.0.20:25,108.170.16.119:44024,>,250-AUTH,

2012-03-14T23:12:55.723Z,SERVER\Internet,08CECF9E822D0C90,10,10.0.0.20:25,108.170.16.119:44024,>,250-8BITMIME,

2012-03-14T23:12:55.723Z,SERVER\Internet,08CECF9E822D0C90,11,10.0.0.20:25,108.170.16.119:44024,>,250-BINARYMIME,

2012-03-14T23:12:55.723Z,SERVER\Internet,08CECF9E822D0C90,12,10.0.0.20:25,108.170.16.119:44024,>,250 CHUNKING,

2012-03-14T23:12:55.796Z,SERVER\Internet,08CECF9E822D0C90,13,10.0.0.20:25,108.170.16.119:44024,<,MAIL FROM: BODY=8BITMIME,

2012-03-14T23:12:55.797Z,SERVER\Internet,08CECF9E822D0C90,14,10.0.0.20:25,108.170.16.119:44024,*,08CECF9E822D0C90;2012-03-14T23:12:55.549Z;1,receiving message

2012-03-14T23:12:55.797Z,SERVER\Internet,08CECF9E822D0C90,15,10.0.0.20:25,108.170.16.119:44024,<,RCPT TO:,

2012-03-14T23:12:55.806Z,SERVER\Internet,08CECF9E822D0C90,16,10.0.0.20:25,108.170.16.119:44024,>,250 2.1.0 Sender OK,

2012-03-14T23:12:55.806Z,SERVER\Internet,08CECF9E822D0C90,17,10.0.0.20:25,108.170.16.119:44024,>,250 2.1.5 Recipient OK,

2012-03-14T23:12:55.893Z,SERVER\Internet,08CECF9E822D0C90,18,10.0.0.20:25,108.170.16.119:44024,<,BDAT 6775 LAST,

2012-03-14T23:12:56.497Z,SERVER\Internet,08CECF9E822D0C90,19,10.0.0.20:25,108.170.16.119:44024,*,Tarpit for '0.00:00:00.662' due to 'DelayedAck',Delivered

2012-03-14T23:12:56.498Z,WMB-SERVER\WMB Internet,08CECF9E822D0C90,20,10.0.0.20:25,108.170.16.119:44024,>,250 2.6.0 <[email protected]> [internalId=57] Queued mail for delivery,

2012-03-14T23:12:56.570Z,SERVER\Internet,08CECF9E822D0C90,21,10.0.0.20:25,108.170.16.119:44024,<,MAIL FROM: BODY=8BITMIME,

2012-03-14T23:12:56.570Z,SERVER\Internet,08CECF9E822D0C90,22,10.0.0.20:25,108.170.16.119:44024,*,08CECF9E822D0C90;2012-03-14T23:12:55.549Z;2,receiving message

2012-03-14T23:12:56.570Z,SERVER\Internet,08CECF9E822D0C90,23,10.0.0.20:25,108.170.16.119:44024,<,RCPT TO:,

2012-03-14T23:12:56.575Z,SERVER\Internet,08CECF9E822D0C90,24,10.0.0.20:25,108.170.16.119:44024,>,250 2.1.0 Sender OK,

2012-03-14T23:12:56.575Z,SERVER\Internet,08CECF9E822D0C90,25,10.0.0.20:25,108.170.16.119:44024,>,250 2.1.5 Recipient OK,

2012-03-14T23:12:56.655Z,SERVER\Internet,08CECF9E822D0C90,26,10.0.0.20:25,108.170.16.119:44024,<,BDAT 6790 LAST,

2012-03-14T23:12:56.986Z,SERVER\Internet,08CECF9E822D0C90,27,10.0.0.20:25,108.170.16.119:44024,*,Tarpit for '0.00:00:01.151' due to 'DelayedAck',Delivered

2012-03-14T23:12:56.987Z,SERVER\Internet,08CECF9E822D0C90,28,10.0.0.20:25,108.170.16.119:44024,>,250 2.6.0 <[email protected]> [internalId=58] Queued mail for delivery,

2012-03-14T23:12:57.060Z,SERVER\Internet,08CECF9E822D0C90,29,10.0.0.20:25,108.170.16.119:44024,<,QUIT,

2012-03-14T23:12:57.060Z,SERVER\Internet,08CECF9E822D0C90,30,10.0.0.20:25,108.170.16.119:44024,>,221 2.0.0 Service closing transmission channel,

2012-03-14T23:12:57.060Z,SERVER\Internet,08CECF9E822D0C90,31,10.0.0.20:25,108.170.16.119:44024,-,,Local

[sukh]

1. Did you receive that message? It seems like it was accepted from [email protected] (which I assume is the external address)?

2. Try Set-ReceiveConnector "SERVER\Internet" -TarpitInterval 00:00:00 (Do this from the Exchange shell).