Hi jogeshdba,

That sounds strange! A couple of options spring to mind to try and diagnose and solve this:

1. Might be an obvious thing, but have you checked your Firefox proxy settings? Are you trying to use a proxy at all? Since pinging works, it sounds like it's something specific to Firefox, which suggests it could be something in your network settings.
2. You can ping, but what happens if you were to, for example, use wget or something else to try and download something from the terminal? Are you directly pinging an IP or a domain name?
3. Since this is virtualbox if you're using the default network settings then you'll be using a bridged internet connection. If you were trying to do something like use a VPN from this box then you'd run into trouble and would need to change the network settings in virtualbox.

Let me know how you get on with those ideas.

Thanks, Dave

Hi David,

Thanks for your reply. I am able to ping any site with ipadress as well as with site url. When using wget to download something, its not able to download from that site, its failing. Its hanging there saying "HTTP Request Sent, awaiting for response".

Do you have any idea what to change in Firefox setting.

Thanks Jogesh

Since firefox and wget share a problem, I would assume that this is actually not just a firefox issue but a system thing, or a virtualbox setting.

If this is a system issue you could have something blocking port 80 which is used for http requests. Do you have any firewall rules in place? Try putting iptables -L into a terminal, and seeing what comes up.

I don't think this can be a DNS issue, since ping can resolve url's. Just to be certain what happens if you try to navigate to one of the website IP's in your browser?

I'm not sure what could do this on virtualbox, but don't want to rule it out yet. Are you using a static IP? I've found an old bug report on the vbox forum which seems to describe your problem https://www.virtualbox.org/ticket/8609 If it's not important for you, you could try changing your virtual box network setting to something other than NAT; such as a bridge. You would do that in your system preferences in VBox.

If none of those things lead to a solution, then would you mind telling me if you are trying to use a proxy or a VPN?

Hi David,

  In iptables -L, what should I check from where I can find out the issue? I am using static IP with bridge network. My centos7 machine ip is 192.168.1.37 and in this iptables -L command output, I can see a line saying :

Chain FORWARD (Policy Accept) ACCEPT all -- anywhere 192.168.122.0/24 ctstage related,established ACCEPT all -- 192.168.122.0/24 anywhere ACCEPT all -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-port-

                                                                                               unreachable

Thanks in advance.

Thanks, Jogesh

Even I am not using any proxy or VPN...I have stoped firewall too by saying the below :

systemctl disable firewalld systemctl stop firewalld

Okay then, so your iptables looks okay as far as I can tell. How about a telnet on port 80 just to make sure that your ports aren't blocked. Try something like

telnet mozilla.org 80

if it makes a connection then I think we have to say this is a problem with your virtualbox set-up. In that case I don't know how much I'll be able to help you!

Having a quick look around seems to reveal similar issues, such as the one below. Perhaps have a look for issues on the virtualbox forum and see if there are any solutions for you there.

http://serverfault.com/questions/491457/virtualbox-bridged-adapter-can-ping-but-cant-curl#491731

Hi David,

  Telnet is not working in my Centos 7.

Thanks, Jogesh

Hi Jogesh,

Unfortunately that just means we haven't necessarily proven that it's virtualbox and haven't discounted anything. Despite that I'm still fairly confident that it won't be your guest os at this stage. So sticking with your virtualbox set-up:

Does using a NAT in stead of bridged make a difference? I know in some situations this might not be an option, but changing it to see whether it works might help to isolate the problem.

Are you trying to do this on a corporate network etc, that might require you to use a proxy? Sometimes direct internet access is blocked in these environments.