Exchange 2010 Integration

have a new exchange 2010 integration in process.  We decided to create a new domain as the old domain was creating issues, server is old and exchange is having issues with space.  Had SBS 2003 with exchange 2003 server.  New domain has server 2008 r2 and 2010 exchange installed. The old domain server and exchange 2003 still exists and is being used in production until new exchange is ready.  I have one pc logged into the new domain and I have created a test mailbox. would like to get the server sending and receiving test email first, then move mailboxes from exchange 2003 thats in another domain.  After I will join other pc's to new domain and have outlook log to the appropriate mailbox.  How should I proceed from here?  I have created a send connector (smart connector) on the exchange 2010 but it fails to send.  Do I need to first add a UCC cert or can I get by without the cert for now?  Any thoughts on how to proceed further will be greatly appreciated.
ajc2cAsked:
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.

NagarajbCommented:
Hope you have configured Send connector correctly (with a DNS resolution or smart host entry)

To reeive mails you need to have MX record pointing to your new server/domian.
0
mattconroyCommented:
Outbound mail is usually send via SMTP port 25. To test this, run a command prompt from the new Exchange 2010 Server and type:

telnet contribs.org 25

The screen should clear to the top, keep pressing enter and you should exit the telnet session. If this does not work you will get an error stating that you could not connect. Port 25 must be opened outbound from the Exchange Server in order to send mail.
0
ajc2cAuthor Commented:
I have a production exchange 2003 server that I do not want to step on right now.  it uses a smart connector (outgoing.verizon.net) I used the same setup with 2010 smart connector, I have that working.  I have no MX record pointing for inbound as of current.  Can I add another pointer to that exchange /domain server along with existing 2003 exchange/domain? I do not want to switch over yet....want to get everything tested and working before I completely cut over to new exchange as I need to join pc's to domain and when in new domain they will not see old exchange. How do I get the current mail boxes over to the new domain?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

ajc2cAuthor Commented:
again is there anyway I can have both servers recieving and sending email? I do not want to intrude on a production server as of current.  Want to get as much configured as I can first.  I have a sonicwall tz180 that is configured for the old exchange....It has an smtp rule to let traffic come in to that server.  I have mx pointer to that server.....I have created a secound mx pointer to mail2.blabla.com...I suppose I will need another public address for the new server....
0
NagarajbCommented:
So your Sonicwall is receiving mail and then giving it to Exchange 2003.

The next option is allow your sonicwall to receive mails and deliver it to Exchange 2010 server.

Your requriement is possible by having 2 mx record with same preference. That means the mails can land up in any of the server first (instead Only E2010 or E2k3).
0
ajc2cAuthor Commented:
The sonicwall is just a pass thru to the current 2003 exchange server.  The new server 2010 exchange is not recieving mail now. If I enter an additonal mx record what will or should it look like?  the current setup shows MX pointing to the current server ip address......do I need a secondary public address on my 2010 exchange?  How will the email be directed to the correct server?

I tried creating a new MX pointer briefly and had to roll it back to the original settings as no one was getting email on the current 2003 exchange.
0
MarkMichaelCommented:
Hi there,

You are going to need 2 things.

A 2nd Public IP address, this may live on your sonicwall and port 25 opened to the Internet.
You'll need a new rule to catch anything hitting that new public IP address on your sonicwall and pass that through to your exchange 2010 server.

This will allow you to run 2 servers without impacting one another.

You will then need a test domain purchased through any domain provider for testing.

Point the MX records for that domain at your new Public IP on the Sonicwall.

Once this is set up, you'll be looking to test communications in and out of your exchange 2010 server using the new test domain.

Good luck.
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.