Solved

Can't send or receive on new exchange 2010 server

Posted on 2013-06-11
9
580 Views
Last Modified: 2013-06-21
Hi,
I have a 2003 exchange server, a 2007 server and a 2010 server.
The 2003 server sends and receives all mail out of the organisation
It goes to Symantec cloud filter first.

There are no mailboxes on the 2003 server. It is legacy. I am not sure why (I am still new to the organisation)

The 2007 server currently holds the site’s mailboxes.  It sends outbound mail through the 2003 server using inbound and outbound hub transport connectors.
They are easy to find and I can see their configuration.

We have a plan to upgrade to 2010.  Our plan has been to create a new 2010 server. (all three servers are physical)
The 2003 server I have built as per Microsoft instructions and all tests have been successful till now.

I have migrated an old user’s mailbox across to the new server. I have also created a new user on the new server.

I have used the same settings in the 2010 server as were configured for the 2007 server.

I can open the mailbox via owa and see mail that was already there.
I can’t send and receive from it.  When I go to send from it I get: #550 4.4.7 QUEUE.Expired; message expired ##
Outbound email sits in the queue indefinitely.
When I say send or receive, I mean I can’t send to users inside the organisation on the 2007 mail server, and they can’t send to the 2010 one.
Also externally I can’t send to the 2010 and the 2010 users can’t send externally either.

I can logon via OWA to the mailboxes on the server, I can move mailboxes to the server, the other exchange servers have this server in their heirachy in ESM.

I have removed the connectors and recreated them.
I have restarted the server.

Any ideas ?

Thanks for your help in advance.
0
Comment
Question by:shaunwoy
  • 5
  • 4
9 Comments
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 39237279
To receive emails the Receive connector should have Anonymous users checked on the permissions group ?
for you to be able to send emails out you should have a RGC with Exchange 2003 as 2 way do you have that as thats the Primary server that can send emails externally and is receiving emails

- Rancy
0
 

Author Comment

by:shaunwoy
ID: 39240264
Thanks for the reply Rancy,
The receive connector does have Anonymous users checked on the permissions group, and I removed the connector and recreated it again just to be sure.
I created a two way connector from 2010 server to the 2003 server from the shell and it worked using:
New-RoutingGroupConnector -Name "Interop RGC" -SourceTransportServers "Ex2010Hub1.contoso.com" -TargetTransportServers "Ex2003BH1.contoso.com" -Cost 10 -Bidirectional $true -PublicFolderReferralsEnabled $true.

The 2003 server is the gateway to the rest of the internet for our mail.

I also checked telnet between 2003-2007, 2003-2010, 2007-2010 and vice versa and all is working.
Meanwhile main in and out of 2003 and 2007 works fine but does allow mail in or out of 2010

I tried to create a routing group connector between 2007 and 2010 and it fails with: "Target servers can't be in the same routing group as the source servers.  the source servers belong to the routing group: "Exchange routing group (DWBGZMFD01QNBJR)"

Any more thoughts?
Thanks,
Shaun
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 39241534
No RGC needed between Exchange 2007 and 2010 as they are in the same RoutingGroup :)

Are you able to drop email using telnet ?
Is the Transport and MailSubmission running on the server ?

- Rancy
0
 

Author Comment

by:shaunwoy
ID: 39243341
Hi Rancy,
By Telnet I can send mail between two mailboxes that both live on the 2010 server.

Using Telnet again for a user on the 2010 server to a user on the 2007 server:
mail from: gives 250 2.1.0 sender okay
rcpt to: gives 250 2.1.5 Recipient OK
I go data  and . to send and it gives: 250 2.6.0 2010servername Queued for delivery
It appears in the 2010 server queue and goes no further.

Using Telnet from a 2010 user to an external user:
mail from: gives 250.2.1.0 sender okay
rcpt to: gives 550 5.7.1 Unable to relay

However when I test telnet mail on the 2007 server to an external user it gives the unable to relay message as well, even though I can send to external users in reality on this one.
If I do telnet on the 2007 server to another 2007 user the mail reaches the other user.

What do you think?
Should it be this hard? Would it be quicker to rebuild the 2010 server in case there is something inherently wrong in the build?

Thanks for your help,
Shaun
0
The problems with reply email signatures

Do you wish that you could place an email signature under a reply? Well, unfortunately, you can't. That great Exchange/Office 365 signature you've created will just appear at the bottom of an email chain. What a pain! Is there really no way to solve this? Well, there might be...

 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 39250993
I would say lets try to once run Setup /PrepareAD ... what is the SP and RU for Exchange 2010 ?

- Rancy
0
 

Author Comment

by:shaunwoy
ID: 39252045
Hi Rancy,
Exchange 2010 is Version: 14.01.0438.000 and I have just installed it and checked for updates.
in the exchange upgrade how to from Microsoft I didn't come across Setup /PrepareAD.  Is this part of an exchange installation?
Thanks,
Shaun
0
 

Accepted Solution

by:
shaunwoy earned 0 total points
ID: 39252385
Hi there, I ended up using up one of my TechNet phone calls on this.  The reason Exchange 2010 couldn't connect to the other mail servers was time.  For some reason the time was wrong by 7 minutes on the 2007 server, and the 2010 server was accurate, so it didn't allow communication with it.  I changed the time on the 2007 mail server and mail flowed on the 2010 server.  Microsoft said it can be up to 3 minutes out.  Thanks for your help though Rancy.  Shaun
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 39253492
The time can be max left to differ to 5 mins as i know and .... check if they both are looking to the same Source machine for time

- Rancy
0
 

Author Closing Comment

by:shaunwoy
ID: 39265346
Found the answer by ringing Microsoft through my TechNet subscription
0

Featured Post

Do email signature updates give you a headache?

Do you feel like all of your time is spent managing email signatures? Too busy to visit every user’s desk to make updates? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today!

Join & Write a Comment

"Migrate" an SMTP relay receive connector to a new server using info from an old server.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now