Solved

Error when moving Exchange server to new subnet

Posted on 2006-07-08
2
266 Views
Last Modified: 2010-03-06
Hello--

I'm having an odd problem with my Exchange server.  Here's the setup:

Windows 2003 native domain, two internal DCs running AD DNS, DHCP, etc.
Exchange 2003 front-end server
Exchange 2003 back-end server
Firewall DMZ between them, but opened wide for testing purposes
Multiple sites configured, with all subnets in their correct sites.

Front end server is on the DMZ subnet with a 192.168.100.x IP address  Back end server is on a corporate subnet with a 192.168.1.x IP address.  This is the subnet I'm trying to get rid of, so I'm moving all of my servers and users to a new one 10.1.0.x   I moved the back end exchange server to 10.1.0.x, rebooted, made sure it was correct in DNS, restarted SMTP on the front-end server, made sure that both servers could ping each other by name, and removed all firewall rules on the DMZ temporarily to make sure nothing there was blocking anything.  With the back-end server on the new network, outgoing mail fails with the "cannot relay for <user>.domain.org" error.  Incoming mail works fine, Outlook client connects fine, internal mail works fine, and exchange services are all running.  I rebooted both servers a couple of times, but still no outgoing mail.  I have one domain controller on the new network and one on the old network--both are global catalog servers, and both are also the internal DNS servers.  When I move the back-end server back to the old network everything works fine.  Both DCs can ping the Exchanger server by name.

This seems like some kind of authentication issue, but I have no idea what it might be.  I have Outlook Web Access running on the front-end server, and it has the same problem--it can see the internal mailbox but if you try to send from OWA the mail bounces with the same error.  The mail is bouncing from the back-end server in all cases.

Any idea what's going on here?

Thanks.
0
Comment
Question by:bsternfield
2 Comments
 
LVL 26

Assisted Solution

by:Vahik
Vahik earned 250 total points
ID: 17066778
first ipconfig /flushdns     ipconfig /registerdns....also flush DNS catche on dns server..
make sure on the smtp virtual server and iis all ip addresses are UNASSIGNED....and on the relay section make sure old subnet does not show up(add the new subnet ...wont hurt)....and in the IIS  on the ip restriction section make sure all ips are allowed....
0
 
LVL 9

Accepted Solution

by:
Exchgen earned 250 total points
ID: 17067520
hmmm...

You know what try this...

keep the original configuration, send an email to an external domain... confirm that its coming from the frontend server.

If the email is coming from backend, then just add 10.1.0.x IP of the backend to the firewall after your frontend server.

If email is indeed originating from frontend then try telnet from backend to frontend and try dropping an email to yourself.

If all fails remove the DMZ firewall between backend and frontend and test mailflow, i have seen cases where removing rules does not work all the way...

You may want to try a network trace to get some idea..

Raghu
0

Featured Post

Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

Question has a verified solution.

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

Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
Read this checklist to learn more about the 15 things you should never include in an email signature.
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
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

813 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

11 Experts available now in Live!

Get 1:1 Help Now