Exchange 2003 IP Address Change, now no external email

Okay, we had to change the internal IP address schemes of one of our clients from 192.168.0.x to 192.168.200.x.  In turn, we changed all of the static IP addresses for the servers manually and verified their GW, etc.  All have Internet access.  We changed the firewall settings to point everything to the appropriate place with the new IP address scheme.  Exchange works fine internally but when we run an external DNS report from dnsreport.com we receive the following error mesage: "mail.domainname.com: (name substituted) The mailserver terminated the connection before the transaction was complete (state 1). This is not RFC compliant, and therefore either due to an error, or it may be the result of a non-RFC-compliant mailserver or non-RFC-compliant anti-spam program.  We can successfully ping all external IP address from the outside.  We can access everything on all of the servers except for email.  Running the Mail Test from dnsreports.com shows success, however, it appears to only be pinging the MX record which would be the external interface of the firewall.  Any ideas?
anotherhickAsked:
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.

haim96Commented:
do you have mail connections configured on the server ?
0
RDAdamsCommented:
Have you checked all your DNS records to ensure they have been changed accordingly?
0
RDAdamsCommented:
Was any port forwarding happening to the exchange server?
0
Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

haim96Commented:
in case you have SMTP connector:
http://support.microsoft.com/kb/265293/en-us

0
anotherhickAuthor Commented:
Figured it out.  Actually it turns out that someone had specified the IP address on the POP3 and SMTP protocols and left the HTTP and IMAP as All Unassigned IP Addresses.  So much for stabdardization and for clients not changing anything.  ;-)
0
RDAdamsCommented:
Will do it everytime eh.  Glad you worked it out.
0
haim96Commented:
happy end ...   :)
0
GranModCommented:
PAQed with points refunded (500)

GranMod
Community Support Moderator
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
Software

From novice to tech pro — start learning today.