0

In my Windows Server hosted in AWS, I tried to access a particular site from Chrome/IE and both browsers returned - the site can't be reached/the server refused to connect. However, when I try to ping the same website from cmd it seems to work just fine. I don't use any proxy in the network setting and Chrome is set to detect network settings automatically.

So this is definitely not an IP based block from the website. My local PC and my server PC are in the same region, but different city. It works great in my local PC but in the server, it simply works via ping.

What are some possible reasons that might have caused this?

Updates Telnet Connection Failed

kent-id
  • 103

2 Answers2

1

Is not an IP based block, but what about procotol type or port block?

ping sends ICMP packages to a host but when you try to open the website via Chrome you need to establish a TCP connection to a host:port. So you should check the firewall in your server, if is hosted in AWS check also the Security Group rules. Then you can test if you are able to connect to HTTP (80) or HTTPS ports (443), for example using:

telnet myserver 80 
telnet myserver 443

instead of

ping myserver
alemarmed
  • 36
0

It is might be that site is stopped in IIS for example. In this case ping will show response but browser won't. Check IIS settings for sites, bindings and AppPools.

warder
  • 148