[Webinar] Streamline your web hosting managementRegister Today

x
?
Solved

Relaying Issue from Front End to Back End Server

Posted on 2006-06-09
9
Medium Priority
?
350 Views
Last Modified: 2010-03-06
I have a basic exchange setup. 1 Front End Server -> 1 Back End Server

We maintain multiple domain name addresses and want to be able to accept email from these addresses. I have added these domain addresses into the Receiptents Policy.

When I point my incoming mail directly to the back end server, the mail goes through just fine for all domains in the receiptent policy. When I point my incoming mail to the front end server, I get an "550 5.7.1 Unable to relay for" error for all but the primary domain.

I did upgrade the back end server several months back, and have been maintaining the old back-end server as a backup system. They are both domain controllers.

On my front end server, under Directory Access it shows as domain controllers the following:
Front End Server, Type = Config
Front End Server, Type = DC
Old Back End Server, Type = GC

It does not list my newer back end server. Don't know if this could cause the issue.

Thanks for your help.

Morgan
0
Comment
Question by:tiggermt
  • 6
  • 3
9 Comments
 
LVL 2

Accepted Solution

by:
homemade earned 2000 total points
ID: 16873351
Is your old backend server the first DC in your forest? And do you keep it online or offline?
If offline have you transferred all the roles to the new server?
Is any other set up as GC/Global Catalog?

0
 

Author Comment

by:tiggermt
ID: 16873612
The old backend server was the first DC in the forest. It is online, but I have been slowly working to transfer the functionality from it to the new backend server. I had not configured the new backend server as a GC. It has been done now.

How long do I need to wait for this to propagate? Could the issue have been the front end server trying to check my old backend server for acceptable domains (as the GC)? It should still have been looking up from the recipient policies that was configured for the Exchange group.
0
 
LVL 2

Expert Comment

by:homemade
ID: 16873835
Sorry have to ask some more questions here:
a) Is the old backend still a backend server?
b) can you check Recipient policies in System Manager on all Exchange-servers and confirm they are the same
c) are you using any connectors?
d) is the FrontEnd in a DMZ? If so is enough ports open for syncing AD etc?

0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 

Author Comment

by:tiggermt
ID: 16873903
No problem.

a) Yes it was still configured as a backend server. I have disabled that (Changed it to "Not part of an Exchange managed RPC-HTTP topology". I will likely uninstall exchange from that machine shortly.

b) Recipient policies are the same on all three Exchange servers

c) There is an SMTP Connector. It is mostly the default, with a few configuration changes. I have specified the front end server as a bridgehead, I have a smart host that I forward email through, send HELO instead of EHLO. I have not modifed the Address Space section. It still have SMTP and * (cost = 1) for the addresses.

d) The frontend is not in a DMZ. It is behind our firewall with appropiate NAT through the firewall.

Thanks again
0
 
LVL 2

Expert Comment

by:homemade
ID: 16874281
Have you transferred the appropiate roles from old-backend to either frontend or new backend?
This is fr 2003: http://support.microsoft.com/default.aspx?scid=kb;en-us;822931
http://www.msexchange.org/tutorials/Remove-Exchange-server-entire-Exchange-organization.html

I have sometimes found the SMTP connectors to misbehave.

If you are in a daring mood, you could delete the connector,
that allows each server to
0
 
LVL 2

Expert Comment

by:homemade
ID: 16874410
Sorry, glitch....
Posted in mid-editing by accident :)

If you delete SMTP-connector, each Exchange-server will send email from users hosted on that server out directly (using DNS)
(unless smarthost is setup on smtp virtual server)
You could change the SMTP virtual servers on the backend to use your smarthost for outgoing.

As for incoming mail without smtp connector, the virtual server on frontend should receive emails for domains in recipientpolicy and forward to correct backend, even without the smtp connector.
Also have you rebooted or stopped and started Exchange services on the servers after adding the new domains? It shouldn't be necessary, but can often help in these cases;O)

Found som links from MS regarding realying and troubleshooting.

Good luck,
I'm turning in for the night ;O)



0
 
LVL 2

Expert Comment

by:homemade
ID: 16874424
0
 

Author Comment

by:tiggermt
ID: 16879575
Looks like I have discovered where the problem lies. My old server was still the GC and was not correctly sync'ing with the new server. When I removed the old server as a GC, my exchange came to a halt as the new server was not correctly configured as a GC.

Thank you very much for your help.
0
 
LVL 2

Expert Comment

by:homemade
ID: 16880153
Ok, great that it is solved.

Thanks for the points!
Brgds Henri
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

There are literally thousands of Exchange recovery applications out there. So how do you end up picking one that’s ideal for your business & purpose? By carefully scouting the product’s features, the benefits it offers you, & reading ample reviews f…
The Exchange database may sometimes fail to mount owing to various technical reasons. A dismounted EDB file can be the source of many Exchange errors including mailbox inaccessibility for users. Resolving the root cause of mounting problems becomes …
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
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses

607 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