I recently added an Edge Transport to my configuration.......I am having a problem sending emails out and I don't know what's going on here....here's my situation I can send emails internally without a problem I can receive internet emails without a problem. I can send an email to the internet from the Edge Transport by creating a .eml file and dropping it into the pickup folder But.... I cannot send from Outlook/OWA to the internet....if i go into the queue viewer on the Edge Server, it doesn't show any emails pending.....but when I go into the queue viewer on the Hub Transport server it shows.... edgesync - default-first-site-name to internet - SMTP Relay in Active Directory Site to Edge Transport Server the error code is 451 4.4.0 the target ip responded with 421.4.2.1 I'm really not sure what I am doing wrong.....any help is much appreciated

just to add more info My connectors are configured tosend and receive mail through port 10025 since port 25 is blocked from my ISP On the Edge Server, I ran the Windows 2003 SCW and opened ports 50389 and 50636 on internal nic and port 10025 and even port 25 on both internal and external I have not run the SCW on the HT server Before I introduced the Edge Transport server......I was able to send and receive on the HT server...once I deployed Edge, i deleted the old send connector on the HT server and unchecked annoymous access on the HT's receive connector On the edge transport server.....my internal ip is 192.168.0.90, on my domain controller, I added an A record for SEA-EDGE-01 with the ip 192.168.0.90

Hi, Have you setup Edge Sync between HUB & Edge or configured connectors correctly? Now, please run test-edgesynchronization command in EMS, and paste the information on the forum. Then run get-sendconnector |fl command in EMS, paste the information on the forum. I suspect the 25 port on Edge server could not be connected from Hub Transport server. Please run telnet edge server name 25 in dos command. What's the result? Thanks Allen

I am using Edge Synchronization I tried telnet last night, if I am on the hub transport server and i try to telnet to my edge server on port 25, it does indeed fail....I'm not sure why though On the edge transport, I ran the SCW and opened port 25 and 10025(which I am using to send/receive through my smarthost). I used the Set-Sendconnector -port 10025, and i configured the receive connector to use port 10025 If i look on edge server, there are 2 send connectors, but 1 receive connector.....should there be 2? I am not with machine now....I removed the subscription because I was goingto try toset the connectors up manually just to see if that works, but i'd really like to get Edgesync working. So I will set it up again and post the cmdlet output The only other thing i can think of that could be causing a problem, is since I am using this in a home lab, i only have 1 network, so my internal ip is setup as 192.168.0.20 using my domain's dns server, and the external is 192.168.0.30 using ISP's dns

Hi, First, it's no problem that only one receive connector in Edge server. Please understand that the communication betweet the Hub and the Edge is SMTP, the port 25 from Hub to Edge is natural and couldn't be changed. Now I would like to explain the process of sending email: The email is submitted, then Hub server will send the email to Edge server by using the send connector (this connector is invisible and created in memory), Edge server receives the email via the Receive connector itself. Then send it to ISPvia edgesync - default-first-site-name to internet. Thus, we need to change port as 25 rather than 10025 on receive connector in Edge server. Please understand the restriction of the port on ISP affects the send connector rather than receive connector. Thus, there is no need to change the port of the receive connector in Edge server. After that, please test this issue. Thanks Allen

Here is the result from Test-EdgesynchronizationName : sea-edge1LeaseHolder : sea-CASHUB1LeaseType : OptionConnectionResult : SucceededFailureDetail : LeaseExpiry : 9/11/2008 1:06:13 AMLastSynchronized : 9/11/2008 12:06:13 AMCredentialStatus : SynchronizedTransportServerStatus : SynchronizedTransportConfigStatus : SynchronizedAcceptedDomainStatus : SynchronizedSendConnectorStatus : SynchronizedMessageClassificationStatus : SynchronizedRecipientStatus : SynchronizedCredentialRecords : Number of credentials 3 Here is the result when trying to telnet from the HT to the Edge using port 25>telnet sea-edge1 25Connecting To sea-edge1...Could not open connection to the host, on port 25: Connect failedI am able to telnet using port 25 from the Edge to the HT though Here is the output from the Edgesync to internet send connector AddressSpaces : {smtp:*;100}AuthenticationCredential : System.Management.Automation.PSCredentialComment : ConnectedDomains : {}ConnectionInactivityTimeOut : 00:10:00DNSRoutingEnabled : FalseDomainSecureEnabled : FalseEnabled : TrueForceHELO : FalseFqdn : HomeMTA : Microsoft MTAHomeMtaServerId : sea-edge1Identity : EdgeSync - Site-NJ to InternetIgnoreSTARTTLS : FalseIsScopedConnector : FalseIsSmtpConnector : TrueLinkedReceiveConnector : MaxMessageSize : 10MBName : EdgeSync - Site-NJ to InternetPort : 10025ProtocolLoggingLevel : NoneRequireTLS : FalseSmartHostAuthMechanism : BasicAuthRequireTLSSmartHosts : {outbound.mailhop.org}SmartHostsString : outbound.mailhop.orgSourceIPAddress : 0.0.0.0SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)SourceTransportServers : {sea-edge1}UseExternalDNSServersEnabled : False And here is the send connector output for the inbound to site connnector AddressSpaces : {smtp:--;100}AuthenticationCredential : Comment : ConnectedDomains : {}ConnectionInactivityTimeOut : 00:10:00DNSRoutingEnabled : FalseDomainSecureEnabled : FalseEnabled : TrueForceHELO : FalseFqdn : HomeMTA : Microsoft MTAHomeMtaServerId : sea-edge1Identity : EdgeSync - Inbound to Site-NJIgnoreSTARTTLS : FalseIsScopedConnector : FalseIsSmtpConnector : TrueLinkedReceiveConnector : MaxMessageSize : 10MBName : EdgeSync - Inbound to Site-NJPort : 25ProtocolLoggingLevel : NoneRequireTLS : FalseSmartHostAuthMechanism : ExchangeServerSmartHosts : {--}SmartHostsString : --SourceIPAddress : 0.0.0.0SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)SourceTransportServers : {sea-edge1}UseExternalDNSServersEnabled : False Please help......just a reminder,receiving internet to my exchange server is not a problem and sending to the internet from the Edge's pickup folder is not a problem. It's just when sending from HT to internet. thanks so much

Hello, I followed your advice and switched the port of the Edge's receive connector back to 25 and I can nowsend from the HT to the Internet, TY!! but now I am no longer able to receive emails from the internet. can you tell me how to remedy?

I think I got it.....On the edge transport, i unchecked anonymous users from the default receive connector.....and created a new internet receive connector and set it to use port 10025. Did I do this correct? On the default receive connector on the edge, the only permission groups that are checked are "exchange servers and partners" On the new receive connector that i created, the only permission group checked is anonymous users

Hi, It seems that the restriction of the ISP also apply with inbound email. If so, you did right. Additionally, please also ensure the Exchange Server authentication of the default receive connector is checked. I believe that, after this configuration, the issue can be resolved. Thanks Allen

Allen, Exchange Server authentication is checked...........under permission groups, "exchange users" should NOT be checked right? Thank you so much, you've been a huge help.

Hi, Of course, "exchange users" should be unchecked Thanks Allen