Can't send or receive from newly installed Exhcnage 2007 server

I recently installed an Exchange 2007 server on my domain. The domain already had one Exchange 2003 server. I have migrated all of the mailboxes over to the new server and they can be accessed ok in Outlook. I am trying to decommission the 2003 server. In the process I think I created a situation where the two servers are not talking to each other, but yet the 2007 server seems to still want to rely on the 2003 server. After re-homing all resources (or so I thought) to the new server, I ran the uninstall for Exchange on the 2003 server, which appeared to go ok, but upon reboot Exchange was still present on the 2003 server. I have considered using the Exchange management tool on the 2003 server to remove that server from the organization, but I'm afraid that might make my situation even worse (though I shudder to think how).

On the 2007 server, I have set up the send connector under Organization Configuration / Hub Transport. It is set to specify the external domain name of the network and to use the 2007 server. My outbound messages are stuck in the queue with the error "421 4.4.0 Remote server response was not RFC conformant".

On the inbound side, I'm not receiving anything. I'm generating NDR's like such: "5.7.1 Unable to relay for es@xxxxx.net (in reply to RCPT TO command)". The inbound mails were originally showing up in the queue with the error "There is currently no route to the mailbox database." and also referencing the name of the 2003 server though I no longer have the exact text of that. Now the inbound ones are not showing in the queue at all.
I have set the default receipt connector to accept anonymous connections.

I'm suspecting that both problems may be coming from some hidden dependency the 2007 server has on the 2003 server.
ShepherdColorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

skca54Senior EngineerCommented:
By default all routing of mail is via the 2003 server. You need to ensure that you have setup a Receive Connector in 'Server Configuration > Hub Transport' also Check Accepted Domains in 'Organization Configuration > Hub Transport'.
0
skca54Senior EngineerCommented:
0
ShepherdColorAuthor Commented:
I have setup a receive connector (all addresses, port 25). All of the appropriate domains are listed under Accepted Domains.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

ShepherdColorAuthor Commented:
I've seen that thread. I did make sure I was set to report the external DNS name for our IP. I also checked to confirm that the name was resolving to our IP.
0
skca54Senior EngineerCommented:
You will also have a routing connector. I believe these can only be managed via the shell:

Applies to: Exchange Server 2007, Exchange Server 2007 SP1
Topic Last Modified: 2006-07-14


Routing group connectors are used to route e-mail messages between Microsoft Exchange Server 2007 Hub Transport servers and Exchange Server 2003 or Exchange 2000 Server routing groups. You must use the Exchange Management Shell cmdlets to manage routing group connectors that include an Exchange 2007 Hub Transport server as a source server or as a target server.

You can use the following Exchange Management Shell cmdlets to manage routing group connectors:

Get-RoutingGroupConnector


New-RoutingGroupConnector


Remove-RoutingGroupConnector


Set-RoutingGroupConnector


To ensure that you are reading the most up-to-date information and to find additional Exchange Server 2007 documentation, visit the Exchange Server TechCenter.
--------------------------------------------------------------------------------

This is what routes incoming mail to your 2003 server. You should be able to use the 'get' command to check what is currently setup.


0
ShepherdColorAuthor Commented:
The get command yields this:
Name                      SourceRoutingGroup         TargetRoutingGroup
----                      ------------------         ------------------
Server2003-Server2007          First Routing Group        Exchange Routing Group ...
Server2003-Server2007          Exchange Routing Group ... First Routing Group

If I am wanting to get rid of the 2003 sever, do I want to have any connectors in place?

BTW, I am running Exchange 2007 with SP1.
0
ShepherdColorAuthor Commented:
I've read that thread too. I don't think it's related to the FQDN. As far as I can tell, I've got that set correctly
0
skca54Senior EngineerCommented:
Both the connectors link the 2003 to 2007 and vice versa. Both would need to be removed to stop the 2003-2007 link.
0
ShepherdColorAuthor Commented:
I have removed both connectors. No change in results.

Should the FQDN be reported as the name I have registered for the IP, or the name that shows up on reverse dns?
0
ShepherdColorAuthor Commented:
I rand a send test from DNSstuff.com and got:

Getting MX record for xxxxx.net (from local DNS server, may be cached)... Got it!
Host      Preference      IP(s) [Country]
mail.xxxxx.net.      10      24.x.x.x [US]

Step 1:  Try connecting to the following mailserver:
         mail.xxxxx.net. - 24.x.x.x
Step 2:  If still unsuccessful, queue the E-mail for later delivery.

Trying to connect to all mailservers:
   mail.xxxxx.net. - 24.x.x.x  [Could not connect: Got an unknown RCPT TO response: 550 5.7.1 Unable to relay for test@xxxxx.net]
0
skca54Senior EngineerCommented:
It looks like the exchange server is not configured for that xxxxx.net domain correctly. Have you tried a restart of the server since removing the routings?
0
ShepherdColorAuthor Commented:
Restarted. No different.
Is there anywhere else the domain needs to be set up besides Organization / Hub Transport / Accepted Domains?
0
skca54Senior EngineerCommented:
Have you set 'Authoritative Domain' in Accepted Domains?
0
ShepherdColorAuthor Commented:
Yes, each accepted domain is set to Authoritative.
0
skca54Senior EngineerCommented:
0
skca54Senior EngineerCommented:
Just a thought . . Silly Question. . how did you enter each domain? xxxx.com?
0
ShepherdColorAuthor Commented:
At this point, there are no silly questions.

Each domain apparently was added automatically based on the settings on the 2003 server. I didn't create the entries in the 2007 server myself. The Name and Accepted Domain columns both read Domain1.net, Domain2.net, Domain3.net, with the FQDN for each domain (two of them are external domain names, one is the name of the AD domain). I don't know if that's what you mean.
0
skca54Senior EngineerCommented:
That's OK. In 2003 domains were often entered as '@xxxx.net'. One thing to try is: telnet <ip of 2007 server> 25. Try connecting using SMTP test: http://www.yuki-onna.co.uk/email/smtp.html
0
ShepherdColorAuthor Commented:
220 xxx.xxx.net Microsoft ESMTP MAIL Service, Version: 7.0.6001.18000 rea
dy at  Tue, 12 Feb 2008 15:12:51 -0500
HELO xxxx.com
250 xxxx.xxxx.net Hello [206.61.105.130]
MAIL FROM: xx@xxxx.com
250 2.1.0 xx@xxxx.com....Sender OK
RCPT TO: es@xxxx.net
550 5.7.1 Unable to relay for es@stanekfamily.net


It may be that the receipt problems and the sending problems are unrelated. It's kind of looking like the receipt problem comes down to it not accepting the domain or the email address. Perhaps I should remove and re-add the Accepted domains. (I'm much more concerned about the receiving issue than the sending issue.)
I still can't help but suspect that both problems are coming down to the 2007 server thinking that it still needs the 2003 server. After the install of 2007 I was initially able to receive, until I started messing with the 2003 server trying to remove it from the group. There was also a point when I was able to send, after I cleared up the DNS settings on the 2003 box, but now I can do neither.
0
skca54Senior EngineerCommented:
Flash of inspiration! Check the users accounts using Exchange Console and look at the email addresses setup for the users.
0
ShepherdColorAuthor Commented:
Perhaps as a consequence of removing the connectors, I now see this error in the queue:

Identity: Server2007\Unreachable\480
Subject: Hierarchy
Internet Message ID: <E92A95D2DEBAEB4A8511C9CDDCB4346606A3227B@Server2007.xxx.net>
From Address: PublicFolderDatabase@xxx.net
Status: Ready
Size (KB): 4
Message Source Name: FromLocal
Source IP: 255.255.255.255
SCL: -1
Date Received: 2/12/2008 2:30:03 PM
Expiration Time: 2/14/2008 2:30:03 PM
Last Error: There is currently no route to the mailbox database
Queue ID: Server2007\Unreachable
Recipients:  ABC-IS@xxxx.net

Where ABC in the last line was the name of the 2003 server.
0
ShepherdColorAuthor Commented:
I had already checked the user email addresses, multiple times in fact because that seemed like surely it would be the issue.
0
skca54Senior EngineerCommented:
Did you move over the public folders?
0
ShepherdColorAuthor Commented:
I thought I had, but I can't see where to view that in 2007. Would that inhibit receiving if that's messed up?
0
skca54Senior EngineerCommented:
Have you had a look in the Exchange Console Toolbox? Run the Mail Flow Troubleshooter. This helped me my first time.
0
skca54Senior EngineerCommented:
No. You will just lose your public folder data. Exchange 2007 was not intended to support public folders although SP1 readded the feature. But the procedure to more the folders from 2003 to 2007 requires the 2003 server functioning.
0
ShepherdColorAuthor Commented:
If I am interpreting the results of the tool correctly, it's saying that everything looks ok.
0
skca54Senior EngineerCommented:
I will do some more digging for you.
0
ShepherdColorAuthor Commented:
It's a small network, so I think tonight I'll save off the mailboxes to pst's, tear down exchange entirely an install 2007 again as a fresh server.
0
ShepherdColorAuthor Commented:
I managed to completely remove Exchange from the domain and then reinstall the 2007 server. I am able to receive fine. I can send, but it takes a very long time for the sent mails to get where they are going. I seem to recall something in older version of Exchange about reverse dns causing something like that, so I'll look into that tomorrow.
0
skca54Senior EngineerCommented:
Glad it is working finally.
0
ShepherdColorAuthor Commented:
I guess I spoke too soon. A few messages got out and now I'm getting a bunch of "421 4.4.0 Remote server response was not RFC conformant" errors in the send queue.
0
ShepherdColorAuthor Commented:
So I finally got it resolved. The content filtering feature of my firewall was truncating the smtp headers.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.