Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 256
  • Last Modified:

Problem with Outgoing emails

We have moved Exchange 2003 (was on dc01) to Exchange 2007 (dc02).  Yesterday, the whole process was complete and was working fine.  
One of the procedures on the internet was to remove the connector.  I have deleted the connector.  Now the situation is:

1.  We are able to RECEIVE emails.
2.  NOT able to SEND emails.

Your help is appreciated.

0
JD
Asked:
JD
  • 6
  • 4
1 Solution
 
ctuckeriniCommented:
Hi slokula-
Since you no longer have "connectors" it is imperitive that your DNS be setup correctly.  Can you successfully do external MX lookups via nslookup from the Exchange server?
0
 
JDAuthor Commented:
Dear Ctuckerini:
The DNS on DC02 (Exchange 2007) was pointed to dc01 (192xxxx.10) and Dell (.16)
is this what you are looking for ?
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\slokula>nslookup
Default Server:  rmdc01.ramtechsystems.com
Address:  192.168.1.10

> mxlookup
Server:  rmdc01.ramtechsystems.com
Address:  192.168.1.10

*** rmdc01.ramtechsystems.com can't find mxlookup: Non-existent domain
> google.com
Server:  rmdc01.ramtechsystems.com
Address:  192.168.1.10

Name:    google.com
Addresses:  64.233.187.99
          209.85.171.99
          72.14.207.99

>
0
 
ctuckeriniCommented:
almost.  I believe your syntax is a little off...try this, each line being a new command at the command prompt:
nslookup
set type=MX
google.com

let me know the results

thanks,
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
JDAuthor Commented:
Ctuckerini:

Here are the results:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\slokula>nslookup
Default Server:  rmdc01.ramtechsystems.com
Address:  192.168.1.10

> set type=mx
> google.com
Server:  rmdc01.ramtechsystems.com
Address:  192.168.1.10

google.com      MX preference = 10, mail exchanger = smtp3.google.com
google.com      MX preference = 10, mail exchanger = smtp4.google.com
google.com      MX preference = 10, mail exchanger = smtp1.google.com
google.com      MX preference = 10, mail exchanger = smtp2.google.com
google.com      nameserver = ns4.google.com
google.com      nameserver = ns1.google.com
google.com      nameserver = ns2.google.com
google.com      nameserver = ns3.google.com
smtp1.google.com        internet address = 209.85.237.25
smtp2.google.com        internet address = 64.233.165.25
smtp3.google.com        internet address = 64.233.183.25
smtp4.google.com        internet address = 72.14.221.25
ns1.google.com  internet address = 216.239.32.10
ns2.google.com  internet address = 216.239.34.10
ns3.google.com  internet address = 216.239.36.10
ns4.google.com  internet address = 216.239.38.10
>


0
 
JDAuthor Commented:
Dear CTuckerini:

I read this article at
http://www.petri.co.il/configuring-exchange-2007-send-external-email.htm

Snapshot:
In Exchange 2007 the story is entirely different. Exchange 2007 does not send outgoing e-mail to the external world just like that. Meaning, after the installation of an Exchange server 2007 machine, you must manually configure it to be able to "talk" to the external world. You do so by creating a send connector by either using PowerShell or EMC (Exchange Management Console).

Send connectors are configured on computers that are running Exchange 2007 and that have Hub Transport and Edge Transport server roles installed (see more about Exchange 2007 roles on the Related Articles section below). The Send Connector represents a logical gateway through which outbound messages are sent. A Send connector controls outbound connections from the internal sending server to the external receiving server or destination e-mail system. As stated above, by default, no explicit Send connectors are created when the Hub Transport server role or the Edge Transport server role is installed.

Like most Exchange configuration settings, Send connectors that are created on Hub Transport servers are stored in Active Directory in the Configuration Partition. This makes them available to all Hub Transport servers in the organization. If a Send connector is configured to send e-mail to an external domain, when any Hub Transport server in the organization routes a e-mail to that domain, the e-mail is delivered to a source server for that connector for relay to the destination domain.

Creating the Send connector

0
 
ctuckeriniCommented:
Good Job!! Hope it resolves your issue.
0
 
JDAuthor Commented:
Dear CTuckerini:

The OUTGOING MAILS  are PERFECT.  IT GOES THROUGH.
Thank you for taking up my problem and woking on it.
0
 
ctuckeriniCommented:
Nice.  I wish I could have helped more but I know it feels better to find the resolution yourself!!  Take care.
0
 
JDAuthor Commented:
Thank you for the attention and help
0
 
JDAuthor Commented:
Thank you for your prompt help.  
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now