We're a small non-profitrunning Exchange Server 2000 on a Small Business Server 2000 system (waiting for an equipment upgrade before we can upgrade our software to a newer version). We have a ADSL line... the router connects directly to the server and to one of our network switches so users may all access the connection. All of our e-mail comes in from our ISP and is distributed to our user inboxes by Exchange. On our workstations most users use Outlook 2002, one uses 2003. Our Internet connection was down yesterday, and in the process of troubleshooting SBC/ATT tech support had me reset the DSL router (an actual reset, not just cycling the power on and off). In the meantime, the entirecity experienced an SBC Internet service outage. When the service came back up, we coudl access the Internet and send e-mails from Outlook, but not receive messages. I've sent test messages from my Hotmail account and do not receive a bounce message. The tech was able to walk me through the router setup to at least get us reconnected to the Internet on the phone. He wasn't going to be able to help me any further than that. Myknowlege of Exchange/DSN is shaky at best.Can someone tell me what settings on the server I need to check to find out what needs to be reprogrammed in Exchange? I have a list of our IP addresses, gateway, etc. Looking at the Small Business Server Administrative Console, the DHCP server has stopped. I tried to restart it last night before leaving, but as of this morning it was still stopped. I don't know if this is related or not. Thanks in advance.

Go to www.dnsstuff.com > Add your domain name there and confirm that your domain name is not "blacklisted". Call ISP and tel lthem to add your exchange public IP in there DNS. We had same problem before. If your DNS is not registered in the DNS server of ISP, it cant get replicated to DNS servers across the continant. And thus e-mail bounce back happens results your domain gets blacklisted. These days Exchange 2003 checks reverse look up for every mail. And as your Exchange is old enough it is possible symptom. We had Exchange 5.5 before.