Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am unable to access internet from the Windows Command Processor. Below is the output on doing a simple ping:


Pinging [] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

I checked my firewall settings and found that Windows Command Processor was missing from the list of programs that are allowed to communicate through the Windows Firewall. So, I added it. Also, restarted the firewall service. However, I still get the same issue.

The firewall rules corresponding to cmd.exe now are:

Rule Name:                            Windows Command Processor
Enabled:                              Yes
Direction:                            In
Profiles:                             Domain,Private,Public
LocalIP:                              Any
RemoteIP:                             Any
Protocol:                             TCP
LocalPort:                            Any
RemotePort:                           Any
Edge traversal:                       Yes
Action:                               Allow

There is another similar rule for UDP. Also, I am able to ping computers on my local network and my internet is working fine.

What can I do to resolve this issue.

share|improve this question
If you totally disable your firewall, does the issue resolve itself? Are you behind a proxy or anything similar? – Dave Sep 26 '13 at 11:54
Tried disabling the firewall, it didn't work. As per , yes a Proxy server was detected. – Vivek Sep 26 '13 at 12:09
I found that I was indeed behind a proxy and then I found this - . So, turns out I can't really use ping. – Vivek Sep 26 '13 at 13:24
up vote 2 down vote accepted

Totally disable your firewall (if safe to do so) is normally a good way to test.

If you are behind a proxy, you can't really get the return.


As per the link in your comments, more details are here: How to ping when behind a proxy?

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .