Exchange Server 2013 can't browse

%3CLINGO-SUB%20id%3D%22lingo-sub-2004503%22%20slang%3D%22en-US%22%3EExchange%20Server%202013%20can't%20browse%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2004503%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20office%20is%20changing%20ISP's%2C%20and%20I%20am%20having%20a%20problem%20with%20our%20Exchange%20Server.%20When%20it%20is%20connected%20to%20the%20old%20ISP%20circuit%2C%20everything%20works%20fine.%20But%20when%20I%20change%20the%20ISP%20circuit%20in%20the%20firewall%2C%20the%20Exchange%20Server%20can't%20browse%20the%20Internet.%20It%20can%20ping%20and%20tracert%20any%20site%20on%20the%20Internet%2C%20but%20it%20will%20not%20browse%20(it%20comes%20up%20with%20a%20connection%20timed-out%20error.%20I%20have%20gone%20through%20the%20DNS%20and%20DHCP%20services%20and%20found%20nothing%20wrong.%20I%20have%20reset%20the%20network%20adapters%20and%20even%20deleted%20and%20recreated%20the%20NIC%20team%2C%20but%20I%20still%20can't%20get%20it%20to%20browse%20the%20Internet.%20Every%20other%20system%20on%20the%20network%20has%20no%20problem%20connecting%20to%20the%20Internet%20on%20the%20new%20circuit.%20It%20is%20just%20the%20Exchange%20Server%202013%20that%20is%20having%20the%20trouble.%20I%20even%20called%20the%20new%20ISP%2C%20and%20they%20ran%20diagnostics%20on%20the%20new%20circuit%20and%20said%20everything%20was%20fine%20on%20their%20end.%20Does%20anybody%20have%20any%20ideas%20on%20how%20I%20can%20get%20this%20server%20to%20browse%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2004503%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ENetworking%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2004521%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202013%20can't%20browse%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2004521%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20DNS%20server%20is%20the%20machine%20using%3F%20May%20need%20to%20update%20the%20forwarders.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2004542%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Server%202013%20can't%20browse%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2004542%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20runs%20the%20DNS%20service%2C%20so%20I%20changed%20the%20forwarders%20to%20the%20DNS%20servers%20for%20the%20new%20ISP.%20When%20that%20didn't%20work%2C%20I%20changed%20them%20to%20OpenDNS%20servers.%20Still%20no%20browsing.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F51719%22%20target%3D%22_blank%22%3E%40Dave%20Patrick%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

My office is changing ISP's, and I am having a problem with our Exchange Server. When it is connected to the old ISP circuit, everything works fine. But when I change the ISP circuit in the firewall, the Exchange Server can't browse the Internet. It can ping and tracert any site on the Internet, but it will not browse (it comes up with a connection timed-out error. I have gone through the DNS and DHCP services and found nothing wrong. I have reset the network adapters and even deleted and recreated the NIC team, but I still can't get it to browse the Internet. Every other system on the network has no problem connecting to the Internet on the new circuit. It is just the Exchange Server 2013 that is having the trouble. I even called the new ISP, and they ran diagnostics on the new circuit and said everything was fine on their end. Does anybody have any ideas on how I can get this server to browse?

4 Replies

What DNS server is the machine using? May need to update the forwarders.

 

 

It runs the DNS service, so I changed the forwarders to the DNS servers for the new ISP. When that didn't work, I changed them to OpenDNS servers. Still no browsing. @Dave Patrick 

Sounds like some other things are now broken. Also note it isn't recommended to install exchange on a domain controller.

 

 

 

An old reverse DNS record was the problem. Once I got the old one deleted and had the new ISP create a new one, all works fine. Thanks again to everyone for all of the input. It is always greatly appreciated.@scottstgelais