Solved

Exchange 2010 unable to recieve external emails when firewall points to it

Posted on 2010-09-06
14
493 Views
Last Modified: 2012-05-10
Have recently installed Exchange 2010 into an existing 2003 Organisation. Currently everything is coexisting fine and we are able to send and receive emails. Users with legacy exchange mailboxes can access OWA using https://oldexchangeserver/exchange internally and https://mail.ourdomainname.com/exchange

I have moved some test mailboxes to the 2010 server and can access using webapp at https://newexchangeserver/owa internaly

(please note i have not setup a legacy namespace as i plan to move all mailboxes soon as there are not many)

Our firewall does basic nat translation to the oldexchange server. If i change the nat rule to the new exchange server I can no longer receive emails externally and I cannot connect to https://mail.ourdomainname/owa

i cant see it as the nat rule itself as all i am doing is changing the server it is pointed to and have confirmed this is OK

I have setup the receive connector to accept anonymous users here is the output of the command get-receiveconnector :fl

RunspaceId                              : 1e98eadc-b558-42c9-ae54-0e0aca28b504
AuthMechanism                        : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
Banner                                     :
BinaryMimeEnabled                  : True
Bindings                                   : {:::25, 0.0.0.0:25}
ChunkingEnabled                         : True
DefaultDomain                           :
DeliveryStatusNotificationEnabled       : True
EightBitMimeEnabled                     : True
DomainSecureEnabled                     : False
EnhancedStatusCodesEnabled              : True
LongAddressesEnabled                    : False
OrarEnabled                             : False
SuppressXAnonymousTls                   : False
AdvertiseClientSettings                 : False
Fqdn                                    : EXCHANGE2010.ourdomain.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                             : 30
MaxLocalHopCount                        : 8
MaxLogonFailures                        : 3
MaxMessageSize                          : 10 MB (10,485,760 bytes)
MaxProtocolErrors                       : 5
MaxRecipientsPerMessage                 : 5000
PermissionGroups                        : AnonymousUsers, ExchangeUsers, ExchangeServers, ExchangeLegacyServers
PipeliningEnabled                       : True
ProtocolLoggingLevel                    : None
RemoteIPRanges                          : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
RequireEHLODomain                       : False
RequireTLS                              : False
EnableAuthGSSAPI                        : False
LiveCredentialEnabled                   : False
Server                                  : BENEXCH
SizeEnabled                             : EnabledWithoutValue
TarpitInterval                          : 00:00:05
MaxAcknowledgementDelay                 : 00:00:30
AdminDisplayName                        :
ExchangeVersion                         : 0.1 (8.0.535.0)
Name                                    : Default EXCHANGE2010
DistinguishedName                       : CN=Default EXCHANGE2010,CN=SMTP Receive Connectors,CN=Protocols,CN=EXCHANGE2010,CN=Serv
                                          ers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Grou
                                          ps,CN=Our Company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC
                                          =domain,DC=local
Identity                                : EXCHANGE2010\Default EXCHANGE2010
Guid                                    : 413ac4f1-dafa-44e9-b1f4-050425e8d1b9
ObjectCategory                          : domain.local/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
ObjectClass                             : {top, msExchSmtpReceiveConnector}
WhenChanged                             : 7/09/2010 9:45:38 AM
WhenCreated                             : 4/09/2010 11:55:29 AM
WhenChangedUTC                          : 6/09/2010 11:45:38 PM
WhenCreatedUTC                          : 4/09/2010 1:55:29 AM
OrganizationId                          :
OriginatingServer                       : OURDC.benrad.local
IsValid                                 : True
0
Comment
Question by:PACSAdmin
  • 8
  • 6
14 Comments
 
LVL 32

Expert Comment

by:endital1097
Comment Utility
update your receive connector to allow anonymous connections on the permissions group tab for the "Default SERVER" receive connector
0
 
LVL 32

Expert Comment

by:endital1097
Comment Utility
sorry, re-reading :)
0
 
LVL 6

Author Comment

by:PACSAdmin
Comment Utility
I knew that would be the first comment so i specificlly wrote

"I have setup the receive connector to accept anonymous"

0
 
LVL 6

Author Comment

by:PACSAdmin
Comment Utility
thats OK  i hid it at the bottom
0
 
LVL 32

Expert Comment

by:endital1097
Comment Utility
that's what happens when you have a kid talking to you while on the phone and reading a post :)
0
 
LVL 32

Accepted Solution

by:
endital1097 earned 500 total points
Comment Utility
have you tried to establish a telnet session from an external source on port 25?
your receive connector looks good, the remote ip ranges are all inclusive, you have anonymous (as stated too)
i would enable the logging on the connector to verbose and check the log

do you have another receive connector configured (other than client)?
0
 
LVL 6

Author Comment

by:PACSAdmin
Comment Utility
I have no other receive connectors other than client.

Can telnet to it internally but not externally.
0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 
LVL 32

Assisted Solution

by:endital1097
endital1097 earned 500 total points
Comment Utility
you changed the nat translation which in some cases will move all traffic to the new server
double check the port forwarding rules to ensure that 80,443,and 25 are going to the correct server

enabling the logging on the receive connector should show the lack of connections
0
 
LVL 6

Author Comment

by:PACSAdmin
Comment Utility
Not quite sure what you are getting at?

I am changing the nat rules that are setup to route  25 and 443 to the new exchange2010 Server. I want 25 and 443 to go directly to the new exchange receive connector to test OWA and email connectivity to the new server before i move all the mailboxes over and decommision the old exchange server.

I was assuming that once 25 and 443 were directed to the New Server that i would be able to access https://mail.ourdomain.com/owa and receive emails through this connector and have them route to the 2010 mailboxes. Is this assumption wrong or does mail flow still need to go though the old server

0
 
LVL 32

Expert Comment

by:endital1097
Comment Utility
No that is correct
Enable logging and see if the connection reaches your server
0
 
LVL 6

Author Comment

by:PACSAdmin
Comment Utility
I checked that under Server configuration -- Hub Transport -- Log settings tab that logging was enabled

also clicked on manage Diagnostic Logging properties and upped the logging properties for smtpReceive  to expert

changed the nat back to the new server and attempted to send an email from outside into our mail server

checked under the "..\logs\protocolLog\SmtpReceive" directory. The location is empty so am i gueesing right in saying the smtp receive connector is not getting hit.

0
 
LVL 6

Author Comment

by:PACSAdmin
Comment Utility
also checked the nat rules logging on the Cisco ASA and that seems ok too seems to be translating the address OK
0
 
LVL 6

Author Comment

by:PACSAdmin
Comment Utility
fixed it.

Installed wireshark on exchange server and verified 25 and 443 was hitting it so it had to be a routing issue. Turned out to be simple misconfiguration of gateway.

0
 
LVL 6

Author Closing Comment

by:PACSAdmin
Comment Utility
even though i fixed the issue myself i am awarding points to endital for pointing me in the right direction which ultimatly led to resolution
0

Featured Post

Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

Join & Write a Comment

Synchronize a new Active Directory domain with an existing Office 365 tenant
This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
how to add IIS SMTP to handle application/Scanner relays into office 365.

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now