Okay so i have this set up

Two dedicated Exchange 2007 servers. One is in the private network 192.168.1.x/24, the other is my edge transport server in the 10.10.10.x/24 DMZ subnet in a workgroup called 'DMZ'. The edge transport server also has a seconf NIC configured with a 192.168.1.x/24 IP with no Default gateway on that NIC.

I know how you guys like to know configurations!!
All server OS are Windows Server 2003 R2
Firewall is TZ210 SonicWall
All servers are dell Poweredge 2850
Email domain currently registered to GoDaddy. with MX records pointing to my edge transport server's public IP.

I have send and receive connectors configured, I have PTR records in my ISP's public DNS. I have opened and forwarded port 25 to my edge transport server to it's 10.10.10.x/24 interface. Also, the exchange and edge transport server are both listening on port 25.

I can send email anywhere (originating from inside the exchange environment), but I cannot reply to those emails. My public FQDN to smtp.mydomain.com, and I have put that anywhere I can find "What FQDN should this server reply with to a Helo Ehlo inquiry." (that is not the exact verbiage Exchange uses, but I mostly find the spot in the send/receive connector property box.


Basically I can send to and from internal mail boxes just fine, and i can send outside of the environment. I just cannot reply to the emails sent to the outside (I have tested with 2 Gmail accounts, and one Hotmail account).

I have never set up an exchange server and I am having hella trouble. please somebody help!!

The PTR records I have set up with my ISP are to resolve smtp.mydomain.com not just mydomain.com. Is that wrong??

however when I run a port scan on mxtoolbox.com to my fqdn and ip I get the same results. The weird thing is I have telnet and remote connect opened (23, 3389) and I can open and close those in the firewall and see the change reflect back to the portscan. but no matter how many ways I try to configure the smtp it never is able to connect.

Hi,

Do I read things correctly that if you try to telnet from the Internet to the external IP of your Edge server you don't get a connection?

From outside the network, I can telnet on port 23, not on port 25, to the public IP of my edge transport server.

I found a route in my firewall that was causing some confusion with my port 25 traffic. I alleviated that mess, now I can:
> port scan my FQDN and public IP via mxtoolbox.com and port 25 shows open.
> I CAN telnet successfully to my public IP via port 25 from outside the network.
> I pass the Inbound and outboud SMTP test at www.testexchangeconnectivity.com.
> I can send and receive mail to and from exchange users. (for example I have two users John and Carl set up with mailboxes. they can send and receive to each other, but cannot receive a reply from a Gmail account they send out to.)

I still cannot receive email into my exchange user mailboxes. I can send out of my network but I can not recieve replies from outside domains.
(internal mail flows between exchange mailboxes okay)

I have message pilling into the queue now on my edge transport server.

when I run get-queue on edge transport i get two queues "Submission" and "agtw.com"

when I run get-queue on exchange server i only get the queue "Submission"

It's like my edge and exchange servers aren't talking to each other

Can some one please tell me the send/receive connectors i should check

Did you create an edge subscription? That's required, and it should automatically create the necessary connectors.

Do you have your Tek-Tips.com Swag? I've got mine!

Stop by the new Tek-Tips group at LinkedIn.

I had created a subscription, yes. I got everything figured out. There was a static route in my Firewall for anything on port 25 that hit my router to go out a backup WAN connection. That route was configured incorrectly. Being that that was there and my inexperience with MS Exchange I continually thought I had something in exchange configured incorrectly, So I had tweaked so many things the default connectors created when the subscription is added were all messed up. I basically fixed the route and resubscribed the Edge server. Now all is well and mail is flowing in and out as is expected!!

Glad to see you got it worked out.

Do you have your Tek-Tips.com Swag? I've got mine!

Stop by the new Tek-Tips group at LinkedIn.