Exchange Server Forums

Problem with Exchange 2007 and Edge Server!!

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Installation >> Problem with Exchange 2007 and Edge Server!!

Page: [1] 2 next > >>

Message

<< Older Topic Newer Topic >>

Problem with Exchange 2007 and Edge Server!! - 9.Jan.2009 4:10:24 AM

nel0001

Posts: 12
Joined: 9.Jan.2009
Status: offline

Hello,

I'm implementing Exchange 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 server with Edge server role (server 2).
When I try to send a e-mail it stays at the Submission queue in Server 1, instead or being send to internet. I don't see any errors on Logs, and both servers are synchronized. Send connectors were created when the Edge transport server was subscribed to the Active Directory site. And I've configured receive connector and created a new one.
These are the configuration of send and receive connectors:

get-sendconnector en servidor1:

AddressSpaces : {smtp:*;100}
AuthenticationCredential :
Comment :
ConnectedDomains : {}
ConnectionInactivityTimeOut : 00:10:00
DNSRoutingEnabled : True
DomainSecureEnabled : True
Enabled : True
ForceHELO : False
Fqdn :
HomeMTA : Microsoft MTA
HomeMtaServerId : servidor2
Identity : EdgeSync - Default-First-Site to
Internet
IgnoreSTARTTLS : False
IsScopedConnector : False
IsSmtpConnector : True
LinkedReceiveConnector :
MaxMessageSize : 10MB
Name : EdgeSync - Default-First-Site to
Internet
Port : 25
ProtocolLoggingLevel : None
RequireTLS : False
SmartHostAuthMechanism : None
SmartHosts : {}
SmartHostsString :
SourceIPAddress : 0.0.0.0
SourceRoutingGroup : Exchange Routing Group
(DWBGZMFD01QNBJR)
SourceTransportServers : {servidor2}
UseExternalDNSServersEnabled : False

AddressSpaces : {smtp:--;100}
AuthenticationCredential :
Comment :
ConnectedDomains : {}
ConnectionInactivityTimeOut : 00:10:00
DNSRoutingEnabled : False
DomainSecureEnabled : False
Enabled : True
ForceHELO : False
Fqdn :
HomeMTA : Microsoft MTA
HomeMtaServerId : servidor2
Identity : EdgeSync - Inbound to Default-First-
Site
IgnoreSTARTTLS : False
IsScopedConnector : False
IsSmtpConnector : True
LinkedReceiveConnector :
MaxMessageSize : 10MB
Name : EdgeSync - Inbound to Default-First-
Site
Port : 25
ProtocolLoggingLevel : None
RequireTLS : False
SmartHostAuthMechanism : ExchangeServer
SmartHosts : {--}
SmartHostsString : --
SourceIPAddress : 0.0.0.0
SourceRoutingGroup : Exchange Routing Group
(DWBGZMFD01QNBJR)
SourceTransportServers : {servidor2}
UseExternalDNSServersEnabled : False

Get-receiveconnector en Servidor2:

AuthMechanism : Tls, ExchangeServer
Banner :
BinaryMimeEnabled : True
Bindings : {192.168.80.40:25}
ChunkingEnabled : True
DefaultDomain :
DeliveryStatusNotificationEnabled : True
EightBitMimeEnabled : True
DomainSecureEnabled : True
EnhancedStatusCodesEnabled : True
Fqdn : servidor2.domain.COM
Comment :
Enabled : True
ConnectionTimeout : 00:05:00
ConnectionInactivityTimeout : 00:01:00
MessageRateLimit : 600
MaxInboundConnection : 5000
MaxInboundConnectionPerSource : 100
MaxInboundConnectionPercentagePerSource : 2
MaxHeaderSize : 64KB
MaxHopCount : 30
MaxLocalHopCount : 3
MaxLogonFailures : 3
MaxMessageSize : 10MB
MaxProtocolErrors : 5
MaxRecipientsPerMessage : 200
PermissionGroups : AnonymousUsers,
ExchangeServers
PipeliningEnabled : True
ProtocolLoggingLevel : Verbose
RemoteIPRanges : {0.0.0.0-255.255.255.255}
RequireEHLODomain : False
RequireTLS : False
Server : servidor2
SizeEnabled : Enabled
TarpitInterval : 00:00:05
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Receptor Externo
DistinguishedName : CN=Receptor Externo,CN=SMTP
Receive C

onnectors,CN=Protocols,CN=servidor2,
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 : servidor2\Receptor Externo
Guid : 78d808e5-352f-4a26-8c3c-
e9eb3033ae4a
ObjectCategory : 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:22
WhenCreated : 19/12/2008 16:22:01
OriginatingServer : localhost
IsValid : True

AuthMechanism : ExchangeServer
Banner :
BinaryMimeEnabled : True
Bindings : {192.168.80.40:25}
ChunkingEnabled : True
DefaultDomain :
DeliveryStatusNotificationEnabled : True
EightBitMimeEnabled : True
DomainSecureEnabled : False
EnhancedStatusCodesEnabled : True
Fqdn : servidor2.domain.COM
Comment :
Enabled : True
ConnectionTimeout : 00:05:00
ConnectionInactivityTimeout : 00:01:00
MessageRateLimit : 600
MaxInboundConnection : 5000
MaxInboundConnectionPerSource : 100
MaxInboundConnectionPercentagePerSource : 2
MaxHeaderSize : 64KB
MaxHopCount : 30
MaxLocalHopCount : 3
MaxLogonFailures : 3
MaxMessageSize : 10MB
MaxProtocolErrors : 5
MaxRecipientsPerMessage : 200
PermissionGroups : AnonymousUsers,
ExchangeServers
PipeliningEnabled : True
ProtocolLoggingLevel : None
RemoteIPRanges :
{192.168.70.55-192.168.70.58}
RequireEHLODomain : False
RequireTLS : False
Server : servidor2
SizeEnabled : Enabled
TarpitInterval : 00:00:05
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Conector Interno
DistinguishedName : CN=Conector Interno,CN=SMTP
Receive C

onnectors,CN=Protocols,CN=servidor2,
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 : servidor2\Conector Interno
Guid :
6937f2eb-7b8f-4f24-933d-32c8fc58c70a
ObjectCategory : CN=ms-Exch-Smtp-Receive-
Connector,CN=
Schema,CN=Configuration,CN=
{AD7E0FF1-
4298-4327-98D7-8A475D5B5B13}
ObjectClass : {top,
msExchSmtpReceiveConnector}
WhenChanged : 08/01/2009 18:23:47
WhenCreated : 07/01/2009 19:28:04
OriginatingServer : localhost
IsValid : True

Please, anybody can help me ?? what can I configure to make it work. I don't know what else can I do.

Thanks a lot!!

Post #: 1

Featured Links*

RE: Problem with Exchange 2007 and Edge Server!! - 9.Jan.2009 8:19:05 AM

jveldh

Posts: 2335
Joined: 12.Apr.2008
From: The Netherlands
Status: offline

Hi,

You can try to remove the edge synchronisation and create a new one.

The only thing I see below is that your are using a .com domain for servers internally. You may try to change this to the IP-addressand then check if it works.

_____________________________

Best regards,

Johan Veldhuis

Visit my Exchange blog

(in reply to nel0001)

Post #: 2

RE: Problem with Exchange 2007 and Edge Server!! - 9.Jan.2009 8:29:23 AM

ravisha_22

Posts: 445
Joined: 16.Sep.2008
Status: offline

At first look everything looks fine. But if there are any problems with the EDGE subscription, i would expect the mail to be stuck in the edge connector not in submission. For submission, the problem could be related to mailbox server or HUB server. Check for events in the HUB server.

_____________________________

Ravishankar

(in reply to nel0001)

Post #: 3

RE: Problem with Exchange 2007 and Edge Server!! - 9.Jan.2009 8:46:12 AM

remjak

Posts: 31
Joined: 16.Dec.2008
From: Norway
Status: offline

Mailsubmission service could be hanging.

Try to restart it:

From powershell:

restart-service MsExchangeMailSubmission

Remi

(in reply to nel0001)

Post #: 4

RE: Problem with Exchange 2007 and Edge Server!! - 9.Jan.2009 10:13:26 AM

nel0001

Posts: 12
Joined: 9.Jan.2009
Status: offline

I restarted Mailsubmission Service and an error appeared: "451 4.4.0 Primary target IP address responded with: "421 4.4.2 Connection dropped".

Sorry, I writed that mails were stucked in the submission queue but I don't really know were they are . I see them in the Queue Viewer in Hub Transport Server.

I also removed the edge synchronisation and create a new one, but it doesn't work.

I don't know how to change to the IP-addressand, could you explain me how to do it?

Any other idea?

Thanks a lot.

(in reply to remjak)

Post #: 5

RE: Problem with Exchange 2007 and Edge Server!! - 9.Jan.2009 10:33:40 AM

ravisha_22

Posts: 445
Joined: 16.Sep.2008
Status: offline

Check if you are able to connect in port 25 from HUB server to the EDGE server using telnet. If you are able to, then try to submit a message to your mailbox.

Dont over do the troubleshooting, we really need to know the "Delivery type" and "name" of the queue on which the mails are stuck.

_____________________________

Ravishankar

(in reply to nel0001)

Post #: 6

RE: Problem with Exchange 2007 and Edge Server!! - 12.Jan.2009 3:37:36 AM

nel0001

Posts: 12
Joined: 9.Jan.2009
Status: offline

I can connect from Hub server to Edge server with telnet on port 25, but when I send a mail, it stuck on this server. I get an error:
550 5.7.1 Unable to relay.
I can see this mail on Queue viewer, and also there is an error on this viewer: DNSConnectorDelivery - 451 4.4.0 DNS Query Failed.
I don't know how to find the name of de queues, could you help me?
Thanks

(in reply to ravisha_22)

Post #: 7

RE: Problem with Exchange 2007 and Edge Server!! - 12.Jan.2009 5:40:16 AM

ravisha_22

Posts: 445
Joined: 16.Sep.2008
Status: offline

Unable to relay could be because the "Anonymous" permission is not checked in the default receive connector of HUB server, if so check it and restart the transport service.

Secondly use nslookup to see if the dns server mentioned for HUB server to resolve it's hops is able to resolve internet domains and the edge server.
If it is able to, then change the settings under the HUB server properties under server configuration to use the NIC card settings (from the drop down list) for bother internal and external DNS lookup.

_____________________________

Ravishankar

(in reply to nel0001)

Post #: 8

RE: Problem with Exchange 2007 and Edge Server!! - 13.Jan.2009 4:16:17 AM

nel0001

Posts: 12
Joined: 9.Jan.2009
Status: offline

I've checked permissions of the receive connectors and all of them have "anonymous" checked.

Hub server is in subnet 192.168.70.x in the Active Directory and Edge server is in the DMZ (192.168.80.x) out of the AC. If I run nslookup in Hub server, I get as the result the name of de Domain Server and DNS server (and as MX register the HUB server) because the NIC card settings is configured with internal DNS server but if I run nslookup in the Edge server I get as a result an external server (also as MX register) because if I configure the NIC card settings in the Edge Transport Server with internal DNS I get an error, so it's configured with an external DNS and it's able to resolve internet domains.
I've changed Hub server properties to use the NIC card settings and the mail that were stucked on Edge server has disappeared from Queue viewer, but it's not in my Inbox (maybe because I haven't changed MX register yet and it's a server in the ISP, I can't change it because we are still using its mail services until everything is configured and working).
I don't know if the reason why it doesn't work is this MX register.
I tried to explain it fine, but if you don't understand something tell me and I'll explain it again.

Thanks a lot.

(in reply to ravisha_22)

Post #: 9

RE: Problem with Exchange 2007 and Edge Server!! - 13.Jan.2009 4:54:08 AM

ravisha_22

Posts: 445
Joined: 16.Sep.2008
Status: offline

i suggested to use nslookup in HUB server to check resolution of edge server name, use in edge server to check resolution of internet domains.

Anymore troubleshooting would only mess up the whole setup, so i suggest you remove the current subscription and re-susbcribe the edge server.

_____________________________

Ravishankar

(in reply to nel0001)

Post #: 10

RE: Problem with Exchange 2007 and Edge Server!! - 13.Jan.2009 10:00:16 AM

nel0001

Posts: 12
Joined: 9.Jan.2009
Status: offline

When I run nslookup in HUB server, the resolution of edge server name is ok. And when I run nslookup in Edge server the resolution of internet domains is also ok.
But, the mail I try to send stucks on Hub server, 'Edgesync - default first site to internet' and 'Last Error': "421 4.4.2 Connection dropped. Attempted failover to alternate host, but did nos succeed. Either there are no alternate hosts, or delivery failed to all alternate host.

Some idea of what's wrong?

Thanks

(in reply to ravisha_22)

Post #: 11

RE: Problem with Exchange 2007 and Edge Server!! - 13.Jan.2009 10:10:01 AM

ravisha_22

Posts: 445
Joined: 16.Sep.2008
Status: offline

looks like some problem with the edge subscription. Can you run start-edgesynchronisation and check if all the replication succeeds?

_____________________________

Ravishankar

(in reply to nel0001)

Post #: 12

RE: Problem with Exchange 2007 and Edge Server!! - 14.Jan.2009 4:20:58 AM

nel0001

Posts: 12
Joined: 9.Jan.2009
Status: offline

I've ran start-edgesynchronization and it seems to synchronize but the mail doesn't been send.

Thanks

(in reply to ravisha_22)

Post #: 13

RE: Problem with Exchange 2007 and Edge Server!! - 14.Jan.2009 1:42:09 PM

de.blackman

Posts: 3542
Joined: 4.Apr.2005
From: Toronto, Canada
Status: offline

Have you determined if the problem is with the edge server and not the hub transport? I would remove any edge subscriptions and connectors, create a send connector on the hub transport to send mail directly to the internet and see if that works. If it does then we know the problem is the edge or the edge subscription.

_____________________________

Ibrahim Benna - Microsoft Exchange MVP
Forum Moderator
Navantis
@IbrahimBenna

(in reply to nel0001)

Post #: 14

RE: Problem with Exchange 2007 and Edge Server!! - 15.Jan.2009 3:37:10 AM

nel0001

Posts: 12
Joined: 9.Jan.2009
Status: offline

I've removed the subscription and connectors and created a new one to send mail to internet on the hub transport server and it works perfectly.
So, the problem is in the connection between Hub and Edge servers.
Any idea of what else can I do to make it work?

Thanks

(in reply to de.blackman)

Post #: 15

RE: Problem with Exchange 2007 and Edge Server!! - 15.Jan.2009 10:22:36 AM

de.blackman

Posts: 3542
Joined: 4.Apr.2005
From: Toronto, Canada
Status: offline

Ok now that we have confirmed the issue, lets take it a step further. Recreate the edge subscription and import it onto the hub transport (remove the previous send connector before going through this step). Make sure that the receive connector on the edge transport has anonymous, exchange servers and partners permissions enabled on the "permissions group" tab.

When you created the edge transport server, did you assign the appropriate domain DNS suffix to it? From the hub transport server, you must be able to ping the FQDN of the edge transport, are you?

_____________________________

Ibrahim Benna - Microsoft Exchange MVP
Forum Moderator
Navantis
@IbrahimBenna

(in reply to nel0001)

Post #: 16

RE: Problem with Exchange 2007 and Edge Server!! - 15.Jan.2009 1:03:28 PM

nel0001

Posts: 12
Joined: 9.Jan.2009
Status: offline

I've done what you comment in your first paragraph several times and the servers synchronize, but mails stuck on Hub server, 'edgesync default- first-site to internet'.
The name of the edge transport server is server2.mydomain.com and the name of the domain is mydomain.com but the server doesn't belong to the domain. Also, I can ping from hub server to edge server and vice versa.
Thanks a lot

(in reply to de.blackman)

Post #: 17

RE: Problem with Exchange 2007 and Edge Server!! - 15.Jan.2009 3:50:04 PM

de.blackman

Posts: 3542
Joined: 4.Apr.2005
From: Toronto, Canada
Status: offline

Do you by any chance have McAfee (or other antivirus applications) installed on either the hub or edge transport? If so, disable it.

_____________________________

Ibrahim Benna - Microsoft Exchange MVP
Forum Moderator
Navantis
@IbrahimBenna

(in reply to nel0001)

Post #: 18

RE: Problem with Exchange 2007 and Edge Server!! - 16.Jan.2009 5:06:27 AM

nel0001

Posts: 12
Joined: 9.Jan.2009
Status: offline

There is no antivirus instaled on the servers. There is a perimetral security appliance from Panda Security between both of them that works as a Firewall, router ... but it permmit connections because there are synchronization between the servers, and I can telnet on port 25 in both directions.
Do you think the problem is this device?

(in reply to de.blackman)

Post #: 19

RE: Problem with Exchange 2007 and Edge Server!! - 16.Jan.2009 10:08:16 AM

de.blackman

Posts: 3542
Joined: 4.Apr.2005
From: Toronto, Canada
Status: offline

Are you able to spoof a message from telnet on the hub transport to the edge transport? Steps being:

1. from hub, telnet to edge on port 25
2. type EHLO then enter
3. type MAIL FROM: user@yourdomain.com then enter
4. type RCPT TO: internetuser@internetaddress.com (preferably an email address you can access or get someone to check) then enter
5. type DATA then enter
6. type a test message then enter and then a period and then enter again!

Does the message go to the internet user?

_____________________________

Ibrahim Benna - Microsoft Exchange MVP
Forum Moderator
Navantis
@IbrahimBenna

(in reply to nel0001)

Post #: 20