Setting up Exchange 2003

[leeym]

Hey There,

I've got Windows Server 2003 with an AD namespace of "mycompany.local." However, now that I've installed Exchange 2003 on the same box, how can I ensure that the DNS namesapce is really "mycompany.com?"

Assuming that I cannot remove AD and Exchange and start over, what DNS, MX record, CNAME, etc. changes must I make?

FYI, I can send and receive emails fine between users with the @mycompany.local domain. Just not with @mycompany.com. Also, I can't seem to make right changes so that NSLOOKUP sees the right host.

Any constructive feedback would be appreciated. Thanks

 

[Thor86]

Are you using an outside DNS server for your primary mail server MX records?

 

[leeym]

Yes I am

 

[zodder]

You need to purchase that domain and make sure that the MX record for your domain name is pointing to your WAN IP address. If you have a dynamic IP address from your ISP, there are little progs that can inform you that your WAN IP has changed and what the new address is. Open port 23 on your router/firewall, and route port 23 traffic to your Exchange server IP. You should be good to go after that.

 

[leeym]

Apparently the NSLOOKUP issue was just a temporary one. It's working fine now.

Anyways, I spoke to my ISP late last night, and specifically asked them if they block port 25. Well apparently they do, and to resolve the problem, I asked them if they have an alternate SMTP address I could use as an SMTP Connector smart host. The only issue was that they give me an address that did not require authentication since I don't think Exchange has can do that.

Anyways, they gave me a legacy SMTP address that worked. WHoo Hoo. Everything works great now. Thanks

 

[zodder]

Oops! I meant port 25. 🙂