We're a small business and we switched our dsl provider to Verizon on Friday. Now, we have several problems: We're not getting incoming email. Outgoing seems fine. We can't connect to our OWA website. We can't remote connect to our server. Funny thing - users can use goto mypc. I presume all this has to do with port forwarding on the dsl set up. It's something I don't know much about and for some reason wasn't an issue with our last broadband provider. On the Verizon set up I have several defaults on a drop-down menu to selectively enable port forwarding. I have two IMAP selections and an https selection. I presume selecting these will fix the incoming email and OWA problems. Is that right? Which one should I look for to fix the remote connection problem? Just in case Verizon's defaults don't work, what are the ports I need to enable to fix these problems? And, last question, how do I determine these ports, myself? Maybe they're not set to defaults... Thank you very much for any help. Ron

Have you chnged your DNS to point to the new IP addresses? For inbound email you need port 25 open inbound - SMTP. IMAP is not for inbound email. For OWA you need 443 if you are using SSL. Go To My PC works because that connects out. It doesn't require a port to be open inbound. The application connects to a central server, as do clients. Gets round firewall issues. Log Me In works in the same way. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

No, I haven't changed the dns, either. I need to change my DNS, too? Wow, what a pain. Sorry for being dense, where would I change the dns? and when you say the new IP addresses, do you mean the new dsl IP addresses? This set up has a static IP. I set all those in the DSL set up, but do I need to make a DNS change at the server? Thanks much. Clearly this is something I don't know a lot about.

You may as well know right now that you are loosing email. If the change occurred on Friday, most servers will start timing out the email in 48 hours. Even if you change the DNS now, it isn't going to be seen by everyone. Being blunt, changing ISPs is not something that is done lightly. I presume you didn't setup the Exchange environment originally? You should have spoken to whoever did, as this could have been easily avoided with advanced planning. The DNS changes are made wherever your DNS is hosted on the internet. This could be a web host, domain name registrar etc. It has nothing to do with your internal DNS. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

I guess I really don't know this. All we did is change our DSL provider, our connection in the office to the outside world. This still affects our DNS record? No, i didn't set up the Exchange environment, originally, and those people are long gone, unfortunately.

I think I understand. After looking through our DNS record, all I need to change is the IP associated with our DSL service. I'm guessing that will fix this. So it might have nothing to do with port forwarding.