Edge Role Server Emails Stuck in Queue

I have set up a Edge role server in a DMZ. I can see that the edge server is recieving emails but then they stay in the queue with the following error: 451 4.4.0 Primary target IP address responded with: "421 4.2.1 Unable to connect."

I am able to telnet from the edge server to the hub server and vice versa on port 25. I have disable the firewalls on both servers and still the emails are stuck in the queue.

Any help would be greatly appreciated.

Exchange 2007
rbasilidesAsked:
Who is Participating?
 
sunnyc7Connect With a Mentor Commented:
I think there's a DNS error.

How many NIC's do you have there

Open Exchange
Go to Edge Transport server
Go to Properties.

Select Internal DNS Lookup tab.
Default settings is all available.

Please post some screenshots @ internal dns lookups
0
 
sunnyc7Commented:
on the edge server run this

dcdiag /v /e /TEST:DNS > c:\dcdiagdns.txt

upload it here.

I hope you dont have any outbound rules on your firewall
0
 
rbasilidesAuthor Commented:
This is what i get sunny:

Directory Server Diagnosis


Performing initial setup:

   Trying to find home server...

   * Verifying that the local machine req-edge-1, is a Directory Server.
   ***Error: req-edge-1 is not a Directory Server.  Must specify /s:<Directory

   Server> or  /n:<Naming Context> or nothing to use the local machine.
   ERROR: Could not find home server.
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
sunnyc7Commented:
oops.
that was supposed to be run on a server with DNS.

-
lets go back a few steps:
a) did you create an edge subscription and setup edge sync ?

Let me know what guide you followed to setup Edge Transport role.
0
 
rbasilidesAuthor Commented:
I did set up the edge subscription and did the test-edgesubscription command and everything looks correct. the connectors are created and i can see the accepted domains on the edge server.
0
 
rbasilidesAuthor Commented:
Ok, I found the issue. It was a DNS error. The edge server is the only server I have in the DMZ so there is no DC in there. What I did was before was to add the exchange server host name to the local host file on the edge server but that was not working. I finally put the FQDN (hostname.company.local) into the host files and the emails started coming in.

I appreciate the help sunny!
0
 
sunnyc7Commented:
ta da...
Alls well that ends well.
0
All Courses

From novice to tech pro — start learning today.