From: lyj_e1 on
Hi,

Setup a new SBS 2008 with remote.mydomain.com. Installed a 3rd party SSL
cert. Previously the client was using POP3 emails. Problem is we can't
receive emails.

We've changed the DNS A record for 'remote' to the external server IP
address as normal. We've deleted the old MX record for Mail and replaced it
with Remote.

A Records
Mail > Server IP address
Remote > Server IP address

MX Record
Remote > Server IP address > Priority 0

I have made sure port forwarding is setup on the router, I can telnet port
25 to the server and I can send emails out. When I run a check on a MX
checker website for the domain it is showing no MX records whereas before the
changes it was pointing correctly to mail.mydomain.com?

Thanks in advance,

Lyj
From: Cris Hanna [SBS - MVP] on
www.testexchangeconnectivity.com is your friend

--
Cris Hanna [SBS - MVP] (since 1997)
Co-Contributor, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-Business-Server-Unleashed/dp/0672329573/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"lyj_e1" <lyje1(a)discussions.microsoft.com> wrote in message news:9AB2406B-21F2-4F0F-8F5B-6DE792388D39(a)microsoft.com...
Hi,

Setup a new SBS 2008 with remote.mydomain.com. Installed a 3rd party SSL
cert. Previously the client was using POP3 emails. Problem is we can't
receive emails.

We've changed the DNS A record for 'remote' to the external server IP
address as normal. We've deleted the old MX record for Mail and replaced it
with Remote.

A Records
Mail > Server IP address
Remote > Server IP address

MX Record
Remote > Server IP address > Priority 0

I have made sure port forwarding is setup on the router, I can telnet port
25 to the server and I can send emails out. When I run a check on a MX
checker website for the domain it is showing no MX records whereas before the
changes it was pointing correctly to mail.mydomain.com?

Thanks in advance,

Lyj
From: Ace Fekay [MVP-DS, MCT] on
"lyj_e1" <lyje1(a)discussions.microsoft.com> wrote in message news:9AB2406B-21F2-4F0F-8F5B-6DE792388D39(a)microsoft.com...
> Hi,
>
> Setup a new SBS 2008 with remote.mydomain.com. Installed a 3rd party SSL
> cert. Previously the client was using POP3 emails. Problem is we can't
> receive emails.
>
> We've changed the DNS A record for 'remote' to the external server IP
> address as normal. We've deleted the old MX record for Mail and replaced it
> with Remote.
>
> A Records
> Mail > Server IP address
> Remote > Server IP address
>
> MX Record
> Remote > Server IP address > Priority 0
>
> I have made sure port forwarding is setup on the router, I can telnet port
> 25 to the server and I can send emails out. When I run a check on a MX
> checker website for the domain it is showing no MX records whereas before the
> changes it was pointing correctly to mail.mydomain.com?
>
> Thanks in advance,
>
> Lyj


Where is the MX record created? On your SBS DNS server, or at your public nameserver that's authorative for your public domain name?

Keep in mind, the MX records tells the world who the mail server is for a domain name. Creating it internally is useless to the outside world, unless you are hosting your public zone on your SBS, which first I highly doubt, and second, I highly suggest not to.

If you can post the actual domain name, we can test it for you to see if it is setup correctly.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.
From: Brian Cryer on
"lyj_e1" <lyje1(a)discussions.microsoft.com> wrote in message
news:9AB2406B-21F2-4F0F-8F5B-6DE792388D39(a)microsoft.com...
> Hi,
>
> Setup a new SBS 2008 with remote.mydomain.com. Installed a 3rd party SSL
> cert. Previously the client was using POP3 emails. Problem is we can't
> receive emails.
>
> We've changed the DNS A record for 'remote' to the external server IP
> address as normal. We've deleted the old MX record for Mail and replaced
> it
> with Remote.
>
> A Records
> Mail > Server IP address
> Remote > Server IP address
>
> MX Record
> Remote > Server IP address > Priority 0
>
> I have made sure port forwarding is setup on the router, I can telnet port
> 25 to the server and I can send emails out. When I run a check on a MX
> checker website for the domain it is showing no MX records whereas before
> the
> changes it was pointing correctly to mail.mydomain.com?
>
> Thanks in advance,

If you can tell us your domain name then we can test that your MX/DNS
records are set up correctly.

Things I would check:

1. On a PC external to your network, open a command prompt window and type:
nslookup -type=mx cryer.co.uk
changing "cryer.co.uk" to your domain (without any www bit). That will tell
you the ip address(s) that others will be using when they try to send you
emails.

If the IP address is wrong then go back and correct it. Be aware that any
changes you make can take several hours to filter out and take effect.

2. Still on that external pc:
telnet ip-address 25
where for "ip-address" you should substitute the ip address of your server
(as returned by the previous step). You should then get one or more lines
starting with the number 220.

If you get that far then it shows that Exchange is listening on the correct
port for email. There are a few steps that can be tried beyond this, but I
suspect that this is probably far enough to reveal the problem.

If you can't telnet then its a firewall issue.

HTH.
--
Brian Cryer
www.cryer.co.uk/brian



From: lyj_e1 on
Hi All,

Thanks for the replies. If I type in: nslookup -type=mx mydomain.com, it
doesn't bring up a mx record? The DNS is controlled by the web design agency
people. They have deleted mail.mydomain.com and replaced it with
remote.mydomain.com. Should they have removed the mx record for
remote.mydomain.com, recreate the mx record for mail.mydomain.com, repointed
the IP address to the server and create a new A record for 'remote' to the
same IP address?

Thanks,

Lyj

"Brian Cryer" wrote:

> "lyj_e1" <lyje1(a)discussions.microsoft.com> wrote in message
> news:9AB2406B-21F2-4F0F-8F5B-6DE792388D39(a)microsoft.com...
> > Hi,
> >
> > Setup a new SBS 2008 with remote.mydomain.com. Installed a 3rd party SSL
> > cert. Previously the client was using POP3 emails. Problem is we can't
> > receive emails.
> >
> > We've changed the DNS A record for 'remote' to the external server IP
> > address as normal. We've deleted the old MX record for Mail and replaced
> > it
> > with Remote.
> >
> > A Records
> > Mail > Server IP address
> > Remote > Server IP address
> >
> > MX Record
> > Remote > Server IP address > Priority 0
> >
> > I have made sure port forwarding is setup on the router, I can telnet port
> > 25 to the server and I can send emails out. When I run a check on a MX
> > checker website for the domain it is showing no MX records whereas before
> > the
> > changes it was pointing correctly to mail.mydomain.com?
> >
> > Thanks in advance,
>
> If you can tell us your domain name then we can test that your MX/DNS
> records are set up correctly.
>
> Things I would check:
>
> 1. On a PC external to your network, open a command prompt window and type:
> nslookup -type=mx cryer.co.uk
> changing "cryer.co.uk" to your domain (without any www bit). That will tell
> you the ip address(s) that others will be using when they try to send you
> emails.
>
> If the IP address is wrong then go back and correct it. Be aware that any
> changes you make can take several hours to filter out and take effect.
>
> 2. Still on that external pc:
> telnet ip-address 25
> where for "ip-address" you should substitute the ip address of your server
> (as returned by the previous step). You should then get one or more lines
> starting with the number 220.
>
> If you get that far then it shows that Exchange is listening on the correct
> port for email. There are a few steps that can be tried beyond this, but I
> suspect that this is probably far enough to reveal the problem.
>
> If you can't telnet then its a firewall issue.
>
> HTH.
> --
> Brian Cryer
> www.cryer.co.uk/brian
>
>
>
> .
>