vito Posted January 9, 2012 Posted January 9, 2012 (edited) Hi guys I just completed the transition from Exchange 2003 to 2010 early last year. Exchange 2003 is still running as the legacy exchange server and the school is still using it as the only exchange server because we can't get the exchange 2010 to receive external mails. 2003 box is working perfectly normal. Only way we can test if the 2010 receiving, we assign the Exchange 2003's external facing IP address to exchange 2010. This IP address is recognised in ISP provider's LAN as the external relay IP address for the Exchange server. 2010 can send and receive internally and can send to external recipients but can't receive from external. Does my ISP Provider need to make further changes in their DNS (i.e. creating a new MX Record)? Do they have the internal name of my exchange server on their DNS records? Because the local name of the new exchange box is obviously different to the 2003 box. Any help would be appreciated. Thanks Edited January 9, 2012 by vito
glennda Posted January 9, 2012 Posted January 9, 2012 I think you need to enable to new exchange box to receive emails anonomously - in exchange management console go to server config hub transport select the server and open properties on default [servername] permission groups and then select Anonymous users.
vito Posted January 9, 2012 Author Posted January 9, 2012 Thanks for the reply Glennda. "Anonymous users" option is allready selected. Thanks
pantscat Posted January 9, 2012 Posted January 9, 2012 Does your ISP know the external address of your 2010 box?
vito Posted January 9, 2012 Author Posted January 9, 2012 Yes they do. It is the address that the old exchange uses. When I do the test on exch 2010, I borrow that IP address from the old exchange. on the mx record I change the priorty to be 0 for exch 2010.
pantscat Posted January 9, 2012 Posted January 9, 2012 Sorry - I misread your original post. A few things to check. 1. "Organisation Configuration - Hub Transport - Remote Domains" - this should be set to "*" 2. "Organisation Configuration - Hub Transport - Accepted domains" - Should be set to your external domain name. 3. "Server Congfiguration - Hub Transport - Receive Connectors" - Check the Default send connector has anonymous authentication ticked and that it is set to use all IP addresses on the Network tab. You can also turn the protocol logging up to verbose (e.g. lots!) to see if it's working. It might also be worth telnetting through to your 2010 box via the external IP and see if you can send a simple email using HELO/EHLO. A
vito Posted January 9, 2012 Author Posted January 9, 2012 (edited) Thanks for all the replies. Pantscat, I just checked, the external domain name wasn't included but *.domain suffix was included in accepted domains. But I still included the full name as you advised me to. I can't test it yet because I need to use the IP address of the Exch 2003 that means people can't use the email. I'll test it tonight and I'll do the telnet test. I'll let you know how I got on. On the "Specify the FQDN this connector will provide in response to HELO or EHLO:" Do we need the enter the local name of the exch box or the external name of it? Thanks again. Edited January 9, 2012 by vito
vito Posted January 9, 2012 Author Posted January 9, 2012 Hi dgardner. SMTP Connectors created one is default, which accepts all IP ranges, the other one particularly accepts ISP's mail server IP ranges.
Gardinho Posted January 9, 2012 Posted January 9, 2012 We use live@edu here, so it's been a while since I used Exchange 2010 and I'll be rusty. I'm fairly sure that you need an incoming smtp connector and route the mail through the smart host (which will be isp issued) the last one I worked on was a dns name. I think it was in the hub transport section.
timzim Posted January 9, 2012 Posted January 9, 2012 On the "Specify the FQDN this connector will provide in response to HELO or EHLO:" Do we need the enter the local name of the exch box or the external name of it? Should be the server local FQDN but make sure server name is in caps, e.g. EXCH1.domain.local Also check you've opened the appropriate ports on the mail server (25 for SMTP, 465/587 for SMTPS).
Gardinho Posted January 9, 2012 Posted January 9, 2012 If you don't use the IP address for the Exchange 2010 box that your ISP is relaying mail to, it will definitely not work. I also seem to remember that Exchange 2010 was very fiddly with certificates. Especially if you have alternative common names for OWA etc. I had no end of trouble with that...
Gardinho Posted January 9, 2012 Posted January 9, 2012 Yes they do. It is the address that the old exchange uses. When I do the test on exch 2010, I borrow that IP address from the old exchange. on the mx record I change the priorty to be 0 for exch 2010. Sorry, just re-read this. Forget my comment about relaying the mail to the old IP.
zag Posted January 9, 2012 Posted January 9, 2012 We had a very similar problem installing exchange 2010 and I never got to the bottom of it. It was something to do with the connector permissions for us. We moved to live@edu in the end. Couldn't be happier with the decision, no more messing with exchange routing
sukh Posted January 9, 2012 Posted January 9, 2012 1. To receive email from the internet you need a receive connector which you already have with the correct permission. This is created by setup.exe by default. 2. To send email to the outside world, you need to create a send connector, which isn't created by setup.exe. 3. To receive emails from the internet, make sure the MX records with lower priority points to Exchange 2010, then make sure if you have a NAT/Firewall that port forwarding is setup correctly. I would change the MX for testing to 5 for Exchange 2010 and 10 for Exchange 2003. 4. When you switch over for testing and send an email say from hotmail, do you get an NDR? 5. Up the logging on the Default receive connector to see if a connection is even attempted. 6. From an external host, try and telnet onto the Exchange 2010 external IP to see if it's listening on port 25
vito Posted May 17, 2012 Author Posted May 17, 2012 Thanks for all the help guys, It looks like, it is something to do with the ISP's LAN. I can't get to the correct people to solve this problem out and I am stuck with the single point of contact. I ended up getting rid off the Exchange 2010 (My ISP will be the next). I am thinking of trying Live@edu. Thanks again.
vito Posted May 17, 2012 Author Posted May 17, 2012 Thanks for all the help guys, It looks like, it is something to do with the ISP's LAN. I can't get to the correct people to solve this problem out and I am stuck with the single point of contact. I ended up getting rid off the Exchange 2010 (My ISP will be the next). I am thinking of trying Live@edu. Thanks again.
zag Posted May 17, 2012 Posted May 17, 2012 Thanks for all the help guys, It looks like, it is something to do with the ISP's LAN. I can't get to the correct people to solve this problem out and I am stuck with the single point of contact. I ended up getting rid off the Exchange 2010 (My ISP will be the next). I am thinking of trying Live@edu. Thanks again. I keep on saying this but no idea why people are still running local exchange servers in this day and age. Google Apps and Live@edu are such a huge improvement.
AndiMarv Posted May 17, 2012 Posted May 17, 2012 I would love to be on live@edu myself but we are running an in house Exchange 2010 system and the tools offered by Microsoft for that type of migration are lacking. One partner quoted us £5000 to do the migration for 150 mailboxes. At that cost we will have to wait! :s
zag Posted May 17, 2012 Posted May 17, 2012 I would love to be on live@edu myself but we are running an in house Exchange 2010 system and the tools offered by Microsoft for that type of migration are lacking. One partner quoted us £5000 to do the migration for 150 mailboxes. At that cost we will have to wait! :s WTF! We migrated 1000 users in 2 days, it was easy. There are also tools like metavis that will do this for you if you really need automation. It really wasn't a big problem for us, we did it manually for staff by simply adding both mailboxes to outlook and dragging the emails over. For students we just ran the old exchange server webmail for 6 months while making the new one default homepage.
pantscat Posted May 17, 2012 Posted May 17, 2012 @zag - did you use two different domains for mail delivery? or did you just switch your MX records straight over to the hosted Exchange?
zag Posted May 17, 2012 Posted May 17, 2012 @zag - did you use two different domains for mail delivery? or did you just switch your MX records straight over to the hosted Exchange? Yes we registered a new email domain and got rid of our old long .sch.uk address. Worked well as we ran them in parallel for a few months so no one really complained and they liked the fact it was a shorted email address. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now