Exchange Server Forums

RE: Edge Transport Configuration

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Installation >> RE: Edge Transport Configuration

Page: << < prev 1 [2]

Message

<< Older Topic Newer Topic >>

RE: Edge Transport Configuration - 28.Sep.2008 9:43:14 PM

jamaliah

Posts: 21
Joined: 28.Aug.2008
Status: offline

hi jveldh,

I already test my exchange with my edge transport server using actual production LAN, actual DNS and firewall. My edge transport is as standalone server and the preferred DNS is point to exchange server. My situation is looks like this:

1. server (A) : exchange 2007, domain controller, DNS
2. server (B) : edge transport, standalone, preferred DNS point to server (A)

Is my edge transport setting correct? I'm not sure of this...

What I get is I can send email to and from exchange to exchange and to-from exchange to Internet. But I can't reply from Internet to exchange. It seems like it can't response to my edge transport setting.

The error message displayed on Edge transport is : could not response to DNS server or DNS server is not exist.

What I understand is, if mail route from internet to exchange, it will first send to Edge transport server then only transfer to exchange server. Am I correct??
This is what did not happened now.

Btw, my Edge transport server got 2 send connectors and 1 receive connector by default after subscribe to hub transport. Send connector:

1) edgesync-default-first-time-name to internet
2) edgesync-inbound to default-first-site name

Receive connector: Default internal receive connector <server name>

At which send connector to setup and is that the correct send and receive connector that should have on Edge server?

What else should I do now? Please someone help me

Thank you
regards / jamaliah

< Message edited by jamaliah -- 29.Sep.2008 2:36:11 AM >

(in reply to jamaliah)

Post #: 21

Featured Links*

RE: Edge Transport Configuration - 29.Sep.2008 3:22:29 PM

jveldh

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

Hi,

Have you tried to do a manual nslookup to check if the DNS can be reached ?
Also check the queues on the Edge server if the mail gets stuck there.

_____________________________

Best regards,

Johan Veldhuis

Visit my Exchange blog

(in reply to jamaliah)

Post #: 22

RE: Edge Transport Configuration - 29.Sep.2008 10:04:52 PM

jamaliah

Posts: 21
Joined: 28.Aug.2008
Status: offline

Hi jveldh,

Yes, I already checked using nslookup on Edge Transport server and noticed that server name cannot be found. And definitely there's a mail stucks on queues.

I'm point the DNS to another server which is only DNS installed. That's mean I'm using one (1) server for Edge transport, one (1) exchange server and one (1) DNS server.

On my Edge transport, DNS Server Address is point to my DNS Server.

So, hope now you can imagine it

Any ideas?

Regards / Jamaliah

(in reply to jveldh)

Post #: 23

RE: Edge Transport Configuration - 30.Sep.2008 1:19:02 PM

jveldh

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

Jamaliah,

Is there a firewall between the Edge server and the DNS ? If so ensure that all correct ports are opened.

_____________________________

Best regards,

Johan Veldhuis

Visit my Exchange blog

(in reply to jamaliah)

Post #: 24

RE: Edge Transport Configuration - 3.Nov.2008 1:19:24 PM

mtawashi

Posts: 10
Joined: 10.May2007
Status: offline

Hi jamaliah,

i will try to answer all your questions

1) the HUB transport server by default is having 1 default recieve connector which is used when recieving emails from edge sever or another HUB server for example,in order to send emails to edge there is should be a send connector on the hub server as well in this case it is an intra-org (implicit) send connector between the HUB and edge (similar to HUB-HUB in different AD sites), while on the edge server you have a default recieve connector for two purposes:
a-Reciving emails from the HUB server
b-reciving emails from the internet

both functionalities are identified by the entity which connects and authenticate to the recieve connectors so for internet emails it is anonymous which has its own permissions while the HUB server lies in another group which has a different permissions on the recieve connector.

in order for the edge server to submit emails to the HUB it uses this send connector(edgesync-inbound to default-name ) and for internet emails it uses edgesync-default-first-time-name to internet

2-DNS:depending on your edge server topology (single or dual NIC) i will assume that your using a single NIC in this case you do the following:

1-in ur NIC DNS config. you enter the IP address of the your ISP DNS
2-use the hosts file on both HUB and edge server so that they can resolve each other which is a requirment for edge sync, u can also edit the edge sever setting using set-trasnportserver or using the EMC for the DNS settings, if you have single NIC you can just edit the external DNS settings

if you need to make sure that your edge server is accepting emails you can try to use basic SMTP verbs and telnet to check

(in reply to jamaliah)

Post #: 25

RE: Edge Transport Configuration - 10.Nov.2008 1:55:45 PM

arumuruga

Posts: 6
Joined: 13.Mar.2008
Status: offline

is it possible to install edge NLB. if possible, how to configure that..

how to NAT mx in edge server NLB...

pls reply urgent.....

quote:

(in reply to mtawashi)

Post #: 26

RE: Edge Transport Configuration - 10.Nov.2008 9:21:06 PM

mtawashi

Posts: 10
Joined: 10.May2007
Status: offline

I am not sure about NLB with edge server but i guess for internal routing between HUB-Edge and Edge-HUB that's load balanced by default in a Round Robin fashion, if you need to load balance the external inbound emails you can think about having additional MX record with the same perference as your existing one

(in reply to arumuruga)

Post #: 27