Hello, I'm implementingExchange 2007 in two servers (Windows Server 2003 R2). I've installed one of them with the following roles:Hub Transport role, Client Access role, Mailbox role, (server 1) and the second serverwithEdge server role(server 2). When I try to send a e-mail it stays atthe Submission queue in Server 1, instead or being send to Server 2 (Edge Server). I don't see any errors on Logs, only once I saw an error on Exchange Queue Viewer in Server 1: "451 4.4.0Primary target IP address responded with: "421 4.4.2 Connection dropped".Send and receive connectors were createdwhen theEdge transport serverwas subscribed tothe ActiveDirectory site.I post the logs: ProtocolLog:#Software: Microsoft Exchange Server #Version: 8.0.0.0 #Log-type: SMTP Send Protocol Log #Date: 2008-12-19T00:02:53.219Z #Fields: date-time,connector-id,session-id,sequence-number,local- endpoint,remote-endpoint,event,data,context 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA,0,,192.168.80.40:25,*,,attempting to connect 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 1,192.168.70.55:35626,192.168.80.40:25,+,, 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 2,192.168.70.55:35626,192.168.80.40:25,<,"220 server2.domain.COM Microsoft ESMTP MAIL Service ready at Fri, 19 Dec 2008 01:01:08 +0100", 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 3,192.168.70.55:35626,192.168.80.40:25,>,EHLO server1.domain.COM, 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA,4,192.168.70.55:35626,192.168.80.40:25,<, 250-server2.domain.COM Hello [192.168.70.55], 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA,5,192.168.70.55:35626,192.168.80.40:25,<, 250-SIZE 10485760, 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA,6,192.168.70.55:35626,192.168.80.40:25,<, 250-DSN, 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA,7,192.168.70.55:35626,192.168.80.40:25,<, 250-ENHANCEDSTATUSCODES, 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA,8,192.168.70.55:35626,192.168.80.40:25,<, 250-STARTTLS, 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA,9,192.168.70.55:35626,192.168.80.40:25,<, 250-X-ANONYMOUSTLS, 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 10,192.168.70.55:35626,192.168.80.40:25,<,250-AUTH GSSAPI NTLM LOGIN, 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 11,192.168.70.55:35626,192.168.80.40:25,<,250-X-EXPS NTLM, 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 12,192.168.70.55:35626,192.168.80.40:25,<,250-8BITMIME, 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 13,192.168.70.55:35626,192.168.80.40:25,<,250-BINARYMIME, 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 14,192.168.70.55:35626,192.168.80.40:25,<,250 OK, 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 15,192.168.70.55:35626,192.168.80.40:25,>,X-ANONYMOUSTLS, 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 16,192.168.70.55:35626,192.168.80.40:25,<,220 2.0.0 SMTP server ready, 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 17,192.168.70.55:35626,192.168.80.40:25,*,,Sending certificate 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 18,192.168.70.55:35626,192.168.80.40:25,*,CN=server1,Certificate subject 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 19,192.168.70.55:35626,192.168.80.40:25,*,CN=server1,Certificate issuer name 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 20,192.168.70.55:35626,192.168.80.40:25,*, 07F9508D7E4AE08B4202FD2A3362D7FA,Certificate serial number 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 21,192.168.70.55:35626,192.168.80.40:25,*, 03EFBF935D46011464E2986F34FE87544FC139ED,Certificate thumbprint 2008-12-19T00:02:53.219Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 22,192.168.70.55:35626,192.168.80.40:25,*,server1;server1.domain.COM,Certificate alternate names 2008-12-19T00:07:54.203Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CA, 23,192.168.70.55:35626,192.168.80.40:25,-,,Remote 2008-12-19T00:17:54.249Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CB,0,,192.168.80.40:25,*,,attempting to connect 2008-12-19T00:17:54.249Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CB, 1,192.168.70.55:35662,192.168.80.40:25,+,, 2008-12-19T00:17:54.249Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CB, 2,192.168.70.55:35662,192.168.80.40:25,<,"220 server2.domain.COM Microsoft ESMTP MAIL Service ready at Fri, 19 Dec 2008 01:16:09 +0100", 2008-12-19T00:17:54.249Z,Conector de envo SMTP interno de la organizacin,08CB2F51409ED2CB, 3,192.168.70.55:35662,192.168.80.40:25,>,EHLO server1.domain.COM, Connection Log: #Software: Microsoft Exchange Server #Version: 8.0.0.0 #Log-type: Transport Connectivity Log #Date: 2008-12-18T10:17:04.068Z #Fields: date-time,session,source,Destination,direction,description 2008-12-18T10:17:04.068Z,08CB2F0D15687BDC,SMTP,edgesync - default- first-site to internet,+,92844c56-1196-43c0-9911-72627e05c6e2 2008-12-18T10:17:04.068Z,08CB2F0D15687BDC,SMTP,edgesync - default- first-site to internet,>,server2.domain.COM[192.168.80.40] 2008-12-18T10:17:04.068Z,08CB2F0D15687BDC,SMTP,edgesync - default- first-site to internet,>,Established connection to 192.168.80.40 2008-12-18T10:18:05.055Z,08CB2F0D15687BDC,SMTP,edgesync - default- first-site to internet,-,Retry 2008-12-18T10:23:05.086Z,08CB2F0D15687BDD,SMTP,edgesync - default- first-site to internet,+,92844c56-1196-43c0-9911-72627e05c6e2 2008-12-18T10:23:05.086Z,08CB2F0D15687BDD,SMTP,edgesync - default- first-site to internet,>,server2.domain.COM[192.168.80.40] 2008-12-18T10:23:05.086Z,08CB2F0D15687BDD,SMTP,edgesync - default- first-site to internet,>,Established connection to 192.168.80.40 2008-12-18T10:24:06.058Z,08CB2F0D15687BDD,SMTP,edgesync - default- first-site to internet,-,Retry MessageTracking: #Software: Microsoft Exchange Server #Version: 8.0.0.0 #Log-type: Message Tracking Log #Date: 2008-12-19T08:23:23.143Z #Fields: date-time,client-ip,client-hostname,server-ip,server- hostname,source-context,connector-id,source,event-id,internal-message- id,message-id,recipient-address,recipient-status,total-bytes,recipient- count,related-recipient-address,reference,message-subject,sender- address,return-path,message-info 2008-12-19T08:23:23.143Z, 192.168.70.55,server1,,server1,"MDB:c3bde501-f133-4fa2- a66c-11c0854e61c2, Mailbox:28255f5f-6297-44b8-85ab-c0140af9c149, Event: 2898, MessageClass:IPM.Note, CreationTime:2008-12-19T08:23:21.518Z, ClientType:User",,STOREDRIVER,SUBMIT,,<3D2247D02D850249BE286B7835C4EE0A2C49613...@server1.domain.COM>,,,,,,,,pru...@domain.com,, 2008-12-19T09:19:24.918Z, 192.168.70.55,server1,,server1,"MDB:c3bde501-f133-4fa2- a66c-11c0854e61c2, Mailbox:28255f5f-6297-44b8-85ab-c0140af9c149, Event: 2913, MessageClass:IPM.Note, CreationTime:2008-12-19T09:19:09.043Z, ClientType:User",,STOREDRIVER,SUBMIT,,<3D2247D02D850249BE286B7835C4EE0A2C49613...@server1.domain.COM>,,,,,,,,pru...@domain.com,, Anybody can help me??? I don't know what is wrong, why server 1 doesn't send emails.Thanks in advance.

Hi,Did you configure a send connector on server 1? This is most likely where you are needing configuration. From my readings and experience, a send connector is what determines where the mail will go. This needs to be configured on the Hub Transport server. This is under the EMC under Organization Configuration under Hub Transport. This may assist you in what you are accomplishing.Scotty

Hi,Please run the command get-sendconnector |fl in EMS on in server 1, run get-receiveconnector |fl in server2, then post the information on the forum.ThanksAllen

Two send connectorare configured on server 1, and this is the configuration: AddressSpaces : {smtp:*;100}AuthenticationCredential :Comment :ConnectedDomains : {}ConnectionInactivityTimeOut : 00:10:00DNSRoutingEnabled : TrueDomainSecureEnabled : TrueEnabled : TrueForceHELO : FalseFqdn :HomeMTA : Microsoft MTAHomeMtaServerId : server2Identity : EdgeSync - Default-First-Site to InternetIgnoreSTARTTLS : FalseIsScopedConnector : FalseIsSmtpConnector : TrueLinkedReceiveConnector :MaxMessageSize : 10MBName : EdgeSync - Default-First-Site to InternetPort : 25ProtocolLoggingLevel : NoneRequireTLS : FalseSmartHostAuthMechanism : NoneSmartHosts : {}SmartHostsString :SourceIPAddress : 0.0.0.0SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)SourceTransportServers : {server2}UseExternalDNSServersEnabled : False AddressSpaces : {smtp:--;100}AuthenticationCredential :Comment :ConnectedDomains : {}ConnectionInactivityTimeOut : 00:10:00DNSRoutingEnabled : FalseDomainSecureEnabled : FalseEnabled : TrueForceHELO : FalseFqdn :HomeMTA : Microsoft MTAHomeMtaServerId : server2Identity : EdgeSync - Inbound to Default-First-SiteIgnoreSTARTTLS : FalseIsScopedConnector : FalseIsSmtpConnector : TrueLinkedReceiveConnector :MaxMessageSize : 10MBName : EdgeSync - Inbound to Default-First-SitePort : 25ProtocolLoggingLevel : NoneRequireTLS : FalseSmartHostAuthMechanism : ExchangeServerSmartHosts : {--}SmartHostsString : --SourceIPAddress : 0.0.0.0SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)SourceTransportServers : {server2}UseExternalDNSServersEnabled : FalseTwo receive connectors are configured on server2 and this is the configuration: AuthMechanism : Tls, Integrated, BasicAuth, ExchangeS erverBanner :BinaryMimeEnabled : TrueBindings : {192.168.80.40:25}ChunkingEnabled : TrueDefaultDomain :DeliveryStatusNotificationEnabled : TrueEightBitMimeEnabled : TrueDomainSecureEnabled : TrueEnhancedStatusCodesEnabled : TrueFqdn : server2.domain.COMComment :Enabled : TrueConnectionTimeout : 00:10:00ConnectionInactivityTimeout : 00:05:00MessageRateLimit : 600MaxInboundConnection : 5000MaxInboundConnectionPerSource : 100MaxInboundConnectionPercentagePerSource : 2MaxHeaderSize : 64KBMaxHopCount : 30MaxLocalHopCount : 3MaxLogonFailures : 3MaxMessageSize : 10MBMaxProtocolErrors : 5MaxRecipientsPerMessage : 200PermissionGroups : AnonymousUsers, ExchangeUsers, Exchan geServers, PartnersPipeliningEnabled : TrueProtocolLoggingLevel : VerboseRemoteIPRanges : {0.0.0.0-255.255.255.255}RequireEHLODomain : FalseRequireTLS : FalseServer : server2SizeEnabled : EnabledTarpitInterval : 00:00:05AdminDisplayName :ExchangeVersion : 0.1 (8.0.535.0)Name : Default internal receive connector server2DistinguishedName : CN=Default internal receive connector server2,CN=SMTP Receive Connect ors,CN=Protocols,CN=server2,CN=S ervers,CN=Exchange Administrative Gro up (FYDIBOHF23SPDLT),CN=Administrativ e Groups,CN=First Organization,CN=Mic rosoft Exchange,CN=Services,CN=Config uration,CN={AD7E0FF1-4298-4327-98D7-8 A475D5B5B13}Identity : server2\Default internal receive connector server2Guid : a96578df-37ac-4153-b26b-ccdce8ca547cObjectCategory : CN=ms-Exch-Smtp-Receive-Connector,CN= Schema,CN=Configuration,CN={AD7E0FF1- 4298-4327-98D7-8A475D5B5B13}ObjectClass : {top, msExchSmtpReceiveConnector}WhenChanged : 19/12/2008 16:19:58WhenCreated : 06/09/2008 17:30:30OriginatingServer : localhostIsValid : True AuthMechanism : Tls, ExchangeServerBanner :BinaryMimeEnabled : TrueBindings : {192.168.70.45:25}ChunkingEnabled : TrueDefaultDomain :DeliveryStatusNotificationEnabled : TrueEightBitMimeEnabled : TrueDomainSecureEnabled : FalseEnhancedStatusCodesEnabled : TrueFqdn : server2.domain.COMComment :Enabled : TrueConnectionTimeout : 00:05:00ConnectionInactivityTimeout : 00:01:00MessageRateLimit : 600MaxInboundConnection : 5000MaxInboundConnectionPerSource : 100MaxInboundConnectionPercentagePerSource : 2MaxHeaderSize : 64KBMaxHopCount : 30MaxLocalHopCount : 3MaxLogonFailures : 3MaxMessageSize : 10MBMaxProtocolErrors : 5MaxRecipientsPerMessage : 200PermissionGroups : ExchangeServersPipeliningEnabled : TrueProtocolLoggingLevel : NoneRemoteIPRanges : {192.168.70.55-192.168.70.58}RequireEHLODomain : FalseRequireTLS : FalseServer : server2SizeEnabled : EnabledTarpitInterval : 00:00:05AdminDisplayName :ExchangeVersion : 0.1 (8.0.535.0)Name : Receptor InternoDistinguishedName : CN=Receptor Interno,CN=SMTP Receive C onnectors,CN=Protocols,CN=server2,CN=Servers,CN=Exchange Administrati ve Group (FYDIBOHF23SPDLT),CN=Adminis trative Groups,CN=First Organization, CN=Microsoft Exchange,CN=Services,CN= Configuration,CN={AD7E0FF1-4298-4327- 98D7-8A475D5B5B13}Identity : server2\Receptor InternoGuid : 78d808e5-352f-4a26-8c3c-e9eb3033ae4aObjectCategory : CN=ms-Exch-Smtp-Receive-Connector,CN= Schema,CN=Configuration,CN={AD7E0FF1- 4298-4327-98D7-8A475D5B5B13}ObjectClass : {top, msExchSmtpReceiveConnector}WhenChanged : 19/12/2008 16:26:43WhenCreated : 19/12/2008 16:22:01OriginatingServer : localhostIsValid : TrueThanks a lot for your help!!

Hi,After viewing the configuration information, I understand that you created additional receive connector on Server2 to be responsible for receiving the email comes from 192.168.70.55.-192.168.70.58. And two Network Cards were deployed which associated with the Receive Connector in different subnet.Now I would like to confirm whether we could telnet server2 on server1.Pleas try to run the below command to verify the result:telnet server2 25Then let me know the outcome.ThanksAllen

Hi Allen, This is the result when I run 'telnet server2 25' on server1:220 Server2.domain.COM Microsoft ESMTP MAIL Service ready at Tue, 23 Dec 2008 10:41:16 +0100451 4.7.0 Timeout waiting for client input C:\>ThanksMari

Hi,How about the IP address?In order to confirm the cause of the issue, please continue to telnet server2 byusingthe IP addresss (192.168.70.45:25)If the result is the same as the previous one, please verify whether any firewall deployed on server2, it seems that the 25 port was blocked.ThanksAllen

the result now is:'telnet error : could not open connection on port 25, connection failed'This is the good response, when I run it before, I had on 'hosts' file: ' 192.168.80.40 server2.domain.com' that is why the response was different.But there is no firewall between the servers, only a switch that can't block ports, so do you have any idea of whatcan behappening?Thanks Mari

Hi,Apparently, the communication is impossible since the two servers are located in different subnet after creating hosts file on the server1.Please ensure you could telnet192.168.70.45on 25 port since the server1 also included in the same subnet. You can add another record (192.168.70.45 server2.domain.com) in hosts file.ThanksAllen

I can't understand why the comunication is impossible since Server 2 has two network Card and one of them is in subnet 192.168.70.x, the same subnet of Server 1. It is necessary to open port 25 ? I don't think so, but I understand nothing. The result is the same, with or without the record, and is the one I posted.Thanks Mari

Hi,Please understand that 25 port is the SMTP communication between the Hub and Edge server. That is premise ofthe email to be transmitted.From the originallog on the SMTPSend Connector, we can find the email is mail loop in the internal environment (Edge server)but not connecting external server.I am confused why you created two network cards on the Edge server, whethermore thanone AD site in the environment? Did you subscribe the Edge server to other AD site?If it is, please remove all edge subscription and recreate only one with server 1 since one Edge server can only subscribe one AD site.ThanksAllen

I configured the Edge server on the DMZ, that's why I created two network cards, one for the comunication with the internal network and the other with internet. It's not ok?After I subscribed the Edge server, I configured the connectors. If I configure only one network card, is it possible to use this card for both comunication with internal and external networks? Thanks a lot, Mari

Hi,It is possible to have only one network card in an edge server.Leif

Hi, Finally it worked.... Ides-subscribe Edge Server and deleted connectors I'd created before, and I subscribe Edge Server again (with two network cards). At first, I got an error when sending mails (530 5.7.1 Client was not authenticated), but after I changed authentication between internal send connectorand receive connector it worked!!!I don't really understand why it works now if I tried with this configuration before, but it works.Thanks a lot!!!!Meri

Hi,I am glad to hear the issue has been resolved after recreating the Edge Subscription. Thanks for your sharing and devoted time on this issue.It seems that the previous Edge Subscription was created before one of the network cards was deployed in the Edge Server.Please understand the Edge Subscription should be created on the premise that the Edge server is done without any change. If any change is occurred on the Edge server, we need to remove the Edge Subscription and recreate it.ThanksAllen

Hi again, I've been thinking about configuring only one network card because it seems to be secureless and I've tried this configuration, but now I can't send or receive emails again. I configured only one netword card on server 2, and after that I recreated Edge Subscription.I can telnet192.168.80.40 on por 25 from server 1 and 192.168.70.45 on por 25 form server 2.When I run 'get-sendconnector' in server 1, I get: AddressSpaces : {smtp:*;100}AuthenticationCredential :Comment :ConnectedDomains : {}ConnectionInactivityTimeOut : 00:10:00DNSRoutingEnabled : TrueDomainSecureEnabled : TrueEnabled : TrueForceHELO : FalseFqdn :HomeMTA : Microsoft MTAHomeMtaServerId : server2Identity : EdgeSync - Default-First-Site to InternetIgnoreSTARTTLS : FalseIsScopedConnector : FalseIsSmtpConnector : TrueLinkedReceiveConnector :MaxMessageSize : 10MBName : EdgeSync - Default-First-Site to InternetPort : 25ProtocolLoggingLevel : NoneRequireTLS : FalseSmartHostAuthMechanism : NoneSmartHosts : {}SmartHostsString :SourceIPAddress : 0.0.0.0SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)SourceTransportServers : {server2}UseExternalDNSServersEnabled : True AddressSpaces : {smtp:--;100}AuthenticationCredential :Comment :ConnectedDomains : {}ConnectionInactivityTimeOut : 00:10:00DNSRoutingEnabled : FalseDomainSecureEnabled : FalseEnabled : TrueForceHELO : FalseFqdn :HomeMTA : Microsoft MTAHomeMtaServerId : server2Identity : EdgeSync - Inbound to Default-First-SiteIgnoreSTARTTLS : FalseIsScopedConnector : FalseIsSmtpConnector : TrueLinkedReceiveConnector :MaxMessageSize : 10MBName : EdgeSync - Inbound to Default-First-SitePort : 25ProtocolLoggingLevel : NoneRequireTLS : FalseSmartHostAuthMechanism : ExchangeServerSmartHosts : {--}SmartHostsString : --SourceIPAddress : 0.0.0.0SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)SourceTransportServers : {server2}UseExternalDNSServersEnabled : FalseAnd 'Get-receiveconnector' on server2: AuthMechanism : Tls, ExchangeServerBanner :BinaryMimeEnabled : TrueBindings : {192.168.80.40:25}ChunkingEnabled : TrueDefaultDomain :DeliveryStatusNotificationEnabled : TrueEightBitMimeEnabled : TrueDomainSecureEnabled : TrueEnhancedStatusCodesEnabled : TrueFqdn : server2.domain.COMComment :Enabled : TrueConnectionTimeout : 00:05:00ConnectionInactivityTimeout : 00:01:00MessageRateLimit : 600MaxInboundConnection : 5000MaxInboundConnectionPerSource : 100MaxInboundConnectionPercentagePerSource : 2MaxHeaderSize : 64KBMaxHopCount : 30MaxLocalHopCount : 3MaxLogonFailures : 3MaxMessageSize : 10MBMaxProtocolErrors : 5MaxRecipientsPerMessage : 200PermissionGroups : AnonymousUsers, ExchangeServersPipeliningEnabled : TrueProtocolLoggingLevel : VerboseRemoteIPRanges : {0.0.0.0-255.255.255.255}RequireEHLODomain : FalseRequireTLS : FalseServer : server2SizeEnabled : EnabledTarpitInterval : 00:00:05AdminDisplayName :ExchangeVersion : 0.1 (8.0.535.0)Name : Receptor ExternoDistinguishedName : CN=Receptor Externo,CN=SMTP Receive C onnectors,CN=Protocols,CN=domain 4,CN=Servers,CN=Exchange Administrati ve Group (FYDIBOHF23SPDLT),CN=Adminis trative Groups,CN=First Organization, CN=Microsoft Exchange,CN=Services,CN= Configuration,CN={AD7E0FF1-4298-4327- 98D7-8A475D5B5B13}Identity : server2\Receptor ExternoGuid : 78d808e5-352f-4a26-8c3c-e9eb3033ae4aObjectCategory : CN=ms-Exch-Smtp-Receive-Connector,CN= Schema,CN=Configuration,CN={AD7E0FF1- 4298-4327-98D7-8A475D5B5B13}ObjectClass : {top, msExchSmtpReceiveConnector}WhenChanged : 07/01/2009 19:27:22WhenCreated : 19/12/2008 16:22:01OriginatingServer : localhostIsValid : True AuthMechanism : ExchangeServerBanner :BinaryMimeEnabled : TrueBindings : {192.168.80.40:25}ChunkingEnabled : TrueDefaultDomain :DeliveryStatusNotificationEnabled : TrueEightBitMimeEnabled : TrueDomainSecureEnabled : FalseEnhancedStatusCodesEnabled : TrueFqdn : server2.domain.COMComment :Enabled : TrueConnectionTimeout : 00:05:00ConnectionInactivityTimeout : 00:01:00MessageRateLimit : 600MaxInboundConnection : 5000MaxInboundConnectionPerSource : 100MaxInboundConnectionPercentagePerSource : 2MaxHeaderSize : 64KBMaxHopCount : 30MaxLocalHopCount : 3MaxLogonFailures : 3MaxMessageSize : 10MBMaxProtocolErrors : 5MaxRecipientsPerMessage : 200PermissionGroups : AnonymousUsers, ExchangeServersPipeliningEnabled : TrueProtocolLoggingLevel : NoneRemoteIPRanges : {192.168.70.55-192.168.70.58}RequireEHLODomain : FalseRequireTLS : FalseServer : server2SizeEnabled : EnabledTarpitInterval : 00:00:05AdminDisplayName :ExchangeVersion : 0.1 (8.0.535.0)Name : Conector InternoDistinguishedName : CN=Conector Interno,CN=SMTP Receive C onnectors,CN=Protocols,CN=domain 4,CN=Servers,CN=Exchange Administrati ve Group (FYDIBOHF23SPDLT),CN=Adminis trative Groups,CN=First Organization, CN=Microsoft Exchange,CN=Services,CN= Configuration,CN={AD7E0FF1-4298-4327- 98D7-8A475D5B5B13}Identity : server2\Conector InternoGuid : 6937f2eb-7b8f-4f24-933d-32c8fc58c70aObjectCategory : CN=ms-Exch-Smtp-Receive-Connector,CN= Schema,CN=Configuration,CN={AD7E0FF1- 4298-4327-98D7-8A475D5B5B13}ObjectClass : {top, msExchSmtpReceiveConnector}WhenChanged : 08/01/2009 17:01:15WhenCreated : 07/01/2009 19:28:04OriginatingServer : localhostIsValid : True I'm very confused again. Can you help me?ThanksMari