I am having a bear of a time setting up a new exchange organization. I have 2 servers one hub/cleint/mailbox and one exchange transport server. I am seemingly able to send mail, but I can not recieve mail. The e-mail domains are hosted on godaddy. The local domain is unregistered. I am afraid that I have scrwed up my send and recieve connectors trying to tweek this thing into working. We have several domains we are recieving mail from, all have been added into accepted domains as authoritative. we have a sonicwall firewall that I opened imap, pop, and smtp to the edge transport and in an attempt to trouble shoot I opened them up to the hub transport. I added MX records on godaddy for one domain while I am testing and if I can get that domain to work I will add the others. any suggestions

The only change that you need to make from the default configuration to receive email is to ensure that Anonymous is enabled on the Default Receive Connector. Nothing else. However as you are using an Edge server, do ensure that you have the connector configured correctly for that communication: http://technet.microsoft.com/en-us/library/aa996395.aspx The domain that you want to receive email for must be listed on the Accepted Domains list. You will also need to either create an email address policy, or add the email addresses to the users as required. If the domains are hosted with GoDaddy then you will need to create an A record in their DNS control panel pointing to your external IP address. Then set that host name as the MX record, clearning out the default GoDaddy records. You will then have to wait for GoDaddy's system to update before those records become live. For testing though, you can use telnet - http://exchange.sembee.info/network/telnet-test.asp Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

When you say clearing out the GoDaddy records, which records? The MX, Cnames, A records? We are still going to have the Web sites hosted there. I had created 2 a records, 1 initially for the edge server, then one for the hub transport.

just tested telnet and that worked.

Removed the Godaddy MX records and I am no longer getting bounce backs on e-mails being sent to my exchange server. I am still not recieving e-mail either.

It was on the MX records that you needed to remove. The MX record should point to an A Record that points to the external IP address of your Edge server. If you are going to use OWA, Outlook Anywhere and ActiveSync then you will either need to use the same host name and then forward port 443 to the CAS role, or a different host name. You will also need an A record for autodiscover.example.com which points at the CAS role. Use one of the many SMTP/MX record verification test sites to see if it makes a connection and then fails. It could be that your DNS is wrong. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Went to MX toolbox.com and it returned that there are no MX records for the domain and it does state that it hit the GoDaddy name server. This looks like a GoDaddy problem, do I need to add a nameserver to the GoDaddy DNS?

If the domain is using GoDaddy's name servers, then you shouldn't need to do anything there. If the MX records are in place correctly, then it is probably going to need a phone call to GoDaddy to get them to look at it. I have heard of errors with the GoDaddy DNS happening before, where only part of a change takes effect. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Personally, I like www.mxtoolbox.com, so he could use this website to check that his MX records are setup correctly. --jp

That is the tool I used and it said that the Godaddy nameserver did not show any MX records for that domain.

GoDaddy is the problem. I have used a few tools to try to find MX records and they are not finding any. I will bang on Godaddy to have them fix the problem. Thank you all for your time and help.

Just FYI, You can also look up MX records via http://www.unlocktheinbox.com/dnslookup/mx/ But...After setting up the records you are also able to validate the records settings via a test email to mailtest@unlocktheinbox.com. You can see a sample of the data returned here: http://www.unlocktheinbox.com/resources/emailauthentication/ I always use this tool after making config changes to verify the records, and it's saved me more time that I care to admit from either fat-fingering, or copy and paste errors. HTH!