Computing.Net > Forums > Windows Server 2003 > Exchange - external mail help :)

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Exchange - external mail help :)

Reply to Message Icon

Name: kentrg
Date: May 24, 2007 at 18:37:08 Pacific
OS: Server 2003
CPU/Ram: 2gig
Product: dell
Comment:

Hi
We have a small office and we are attempting to setup Exchange. Our ISP provides us with dynamic IP.

We registered for a domain with dyndns (elorean.homeip.net) and setup the router to auto update the IP and forward port 25 to machine with exchange.

This is where we hit dead end. I've set up local domain on Server 2003(scholes.local) and installed exchange on top of it. We're unable to send or recieve email and would appretiate if anyone can point us in the right direction.

I believe the problem lies in our DNS mess. Do i need to somehow connect elorean.homeip.net to our local domain on which exchange sits.

Here is a screenshot of the DNS screen
http://elorean.com/serv.jpg
The server with exchange is 192.168.1.105

i've also registered for Mailhop Relay from dyndns in hopes it would fix the problem, but no luck.

Thanks alot




Sponsored Link
Ads by Google

Response Number 1
Name: Razor2.3
Date: May 24, 2007 at 18:58:34 Pacific
Reply:

Random question: Did you add a Mail Exchanger record on your DynDns account? Nslookup tells me you haven't. Also, the A record points to 172.16.0.2, which I know is invalid.


0

Response Number 2
Name: heropsycho2177
Date: May 24, 2007 at 19:02:39 Pacific
Reply:

An internal MX record is not necessary for Exchange and has nothing to do external email, neither inbound or outbound.

There must be an MX record for the domain you want mail to be delivered for.

http://www.han.com/dns.html

"Enough, enough bowing down to disillusion!
Hats off & applause to rogues & evolution!
The ripple effect is too good not to mention.
If you’re not affected, you’re not paying attention!"


0

Response Number 3
Name: kentrg
Date: May 24, 2007 at 19:07:39 Pacific
Reply:

My router has dyndns client built in. Why it continues to point to 172.16.0.2 i dont know.

dyndns update client points to another IP 24.90.140.40 .


0

Response Number 4
Name: kentrg
Date: May 24, 2007 at 19:15:56 Pacific
Reply:

Did you add a Mail Exchanger record on your DynDns account?

No razor, what do i have to put in that field?


0

Response Number 5
Name: heropsycho2177
Date: May 24, 2007 at 19:18:51 Pacific
Reply:

http://www.han.com/dns.html

"Enough, enough bowing down to disillusion!
Hats off & applause to rogues & evolution!
The ripple effect is too good not to mention.
If you’re not affected, you’re not paying attention!"


0

Related Posts

See More



Response Number 6
Name: kentrg
Date: May 24, 2007 at 19:27:35 Pacific
Reply:

thanks for link hero

I posted a pic of my DNS http://elorean.com/serv.jpg

I already have MX record setup for mx1.mailhop.org. I signed up for dyndns mailhop relay.


0

Response Number 7
Name: Razor2.3
Date: May 24, 2007 at 19:33:45 Pacific
Reply:

No razor, what do i have to put in that field?

On the DynDNS page, on your Modify Dynamic DNS page, there should be a text box on the bottom labeled, "Mail Exchanger (optional):" For you, it is not optional.

Of course, it's irrelevant if you can't keep your account from pointing to a private IP. Actually, if the router is connected directly to the modem, and it has a private IP, you won't be able to use that computer (or any computer on your network) as a mail server.


0

Response Number 8
Name: kentrg
Date: May 24, 2007 at 19:53:48 Pacific
Reply:

nope i had modem ->linksys voip adapter -> router

IP issue fixed now.

Raz what exactly do i have to put into "Mail Exchanger (optional)field? sorry for silly questions.


0

Response Number 9
Name: Razor2.3
Date: May 24, 2007 at 20:09:17 Pacific
Reply:

elorean.homeip.net is what I'd go with.

Edit: I'm just going to assume you figured it out on your own, seeing as nslookup now shows the MX record. Now all you need to do is test it.


0

Response Number 10
Name: kentrg
Date: May 24, 2007 at 20:18:58 Pacific
Reply:

Sent myself an email. but dns can take a while to resolve?


0

Response Number 11
Name: kentrg
Date: May 24, 2007 at 20:21:27 Pacific
Reply:

I think my ISP also blocks port 25. So in dyndns mail hop relay options i set port 587. forwarded same port on router to exchange machine. Hope it works although Im sure there is something else screwed up :)

I do want to thank you for your help


0

Response Number 12
Name: kentrg
Date: May 25, 2007 at 09:11:00 Pacific
Reply:

Still no luck


0

Response Number 13
Name: Razor2.3
Date: May 25, 2007 at 18:19:15 Pacific
Reply:

You may have to wait awhile. Your MX record expires every 12 hours, so it could take up to half a day to see your changes go though.

That said, your MX record now points to mx1.mailhop.org, so that's good. Silly questions: Did you remember to change the email port on your server? Did you remember to bounce the service after the change?

Mailhop apparently uses SSL, so if your server allows it, and if your mail server doesn't report its name as elorean.homeip.net, then SSL might break the connection. You'll need to change the name anyways; otherwise, Mailhop may reject any emails from this network.


0

Response Number 14
Name: kentrg
Date: May 25, 2007 at 23:11:14 Pacific
Reply:

well finally problem is fixed. Getting email at last
thanks :)

Had to wait for mx record to update


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: Exchange - external mail help :)

Exchange server -Internal Mail www.computing.net/answers/windows-2003/exchange-server-internal-mail/1905.html

microsoft exchange www.computing.net/answers/windows-2003/microsoft-exchange/4660.html

Routing outgoing Exchange e-mails t www.computing.net/answers/windows-2003/routing-outgoing-exchange-emails-t/4206.html