I have recently migrated an Exchange 2007 Server running on Windows 2003 server to Exchange 2007 running on a Windows 2008 R2 Server. I have an Exchange 2007 Edge Server running on Windows 2003 Server. Both Exchange Servers are running SP3. Since the migration I cannot receive mail from the internet. The Edge server shows the following entry in the transport log for a test email. 2011-11-28T16:26:22.000Z,65.54.190.23,,199.80.117.18,mailsrv,08CE7BE655DAC03D;2011-11-28T16:26:21.484Z;0,mailsrv\Default internal receive connector MAILSRV,SMTP,RECEIVE,723776,<BAY145-ds4CDE5AD03B81A0905C448D6B20@phx.gbl>,bill@rpl.org,,3606,1,,,test24,wlhj@hotmail.com,wlhj@hotmail.com,00A: I would assume the email was forwarded to the internal Exchange Server. However, the exchange server shows no entry. I can receive internal emails (non-internet). My edge server has the inbound connector (to our internal server) set up with the following address space SMTP -- 100 and is set to be routed through the smart host 192.168.100.17 which is our internal Exchange Server address. The internal Exchange Server has the same settings except it shows a source server of : mailsrv (which is the Edge Server name). There are no firewall issues. My DNS is set up with an MX record of 192.168.100.17 for the internal server and has A records for the internal server and the Edge Server (192.168.100.18). I can send email to the internet and send and recieve on our local domain but can't receive from the internet.William Huffman

Hi, Did you create an edgesync subscription on your HT and then registered it the ET?

Yes, that had already been created before I changed hardware. However, I removed it and reinstalled it twice to no avail. Finally gave up, and put it a call to Microsoft support. I have a Technet Plus Subscription and figured this would be worth one of my free calls. It was. Turns out that there was an issue with the Schema. The support person, discovered this by looking through the Exchange entries in Active Directory (that is a little above my pay grade as I would not even begin to know what to look for). SP3 was supposed to make changes to the schema during the install without any intervention but obviously missed something. The support person ran setup.com /prepareschema and that fixed it.William Huffman