I can Ping but cant browse

Hi,

Strange problem with SBS 2011... I can ping the server and connect via RDC, but the server cant access the internet. if i ping google.com it resolves, and pinging external addresses works fine too so it looks like DNS is resolving correctly.

Who is Participating?

Turns out the issue was with BT having issues on a particular exchange with port 80 traffic... eh?! Oh well, it works now. Actually it isn't the first time i've had problems with them doing silly things like that.

Just some clarification, are you saying you can ping google.com from SBS2011?

Do you have a firewall on the network or running on SBS? It may be blocking port 80 which is web traffic. Try turning off the firewall on SBS first and see if you can surf.

Also, assuming you are using Internet Explorer to browse, if you don't use a proxy, make sure that the proxy server is not specified in Internet Options. That option is under Internet Options > Connections > LAN Settings. Also make sure that Automatically detect settings is unchecked.

You might also have Internet Explorer Enhanced Security activated so you might also try turning that off and try to browse.

Lastly, there is another setting in Internet Options for Protected Mode under the Security tab. If that is on, try turning it off.

There’s a growing demand for qualified analysts who can make sense of Big Data. With an MS in Data Analytics, you can become the data mining, management, mapping, and munging expert that today’s leading corporations desperately need.

If I may ask,, does your SMS have 1 or 2 NIC cards? can you verify the correct interface is routed correctly by doing a ROUTE PRINT from the command prompt? also when you do a TRACERT where does it end before your browser returns page not found?

If your SBS 2011 server has two NIC cards, then disable one of them. The dual-NIC configuration was dropped in SBS 2008 onwards, and you will have no end of problems if you attempt to use two NICs because SBS doesn't work that way any more.

By any chance did you take a look at the ROUTE PRINT and verify the respective NIC CARD has the correct GATEWAY IP ADRRESS?
this can also be verifed in the TRACERT command
try a TRACERT to a well known outside IP ADDRESS see the packets destined for the GATEWAY is actualy routed to the GATEWAY or if there is a VIRTUAL ETHERNET ADPATER in the picture somewhere. you may need to reset your winsock (netsh int ip reset) from the command prompt.

Turns out the issue was with BT having issues on a particular exchange with port 80 traffic... eh?! Oh well, it works now. Actually it isn't the first time i've had problems with them doing silly things like that.