dslreports logo
site
spacer

spacer
 
    All FAQs Site FAQ DSL FAQ Cable Tech About DSL Distance DSL Hurdles »»
spc

spacer




how-to block ads




3. Becoming Pingable

Bring up ZAP Control Panel. Click on "Security." Click on "Customize" on the Internet side. Put a tick mark in "Allow incoming ping(ICMP Echo)." Click on "Apply," "OK," and then close the program. This will allow you to be pingable without coming out of Stealth Mode entirely and can be used in Line Quality and Tweaks. Make sure you return to your previous settings when you do not need to be pingable.

Zone Alarm Pro, version 4:

Bring up ZAP Control Panel. Select "Firewall" on the left, then "Main" at the top. Click on the upper "Custom" button (Internet Zone Security). Put a tick mark in "Allow incoming ping (ICMP Echo)." Click on "Apply," "OK," and then close the program. This will allow you to be pingable without coming out of Stealth Mode entirely and can be used in Line Quality and Tweaks. Make sure you return to your previous settings when you do not need to be pingable.

Version 4 tips courtesy of Basil2 See Profile

Version 7 (Paid):

1) Bring up the control panel.
2) Select the custom button Internet Zone Security.
3) Click Allow incoming ping (ICMP Echo).

~~~~~~~~~
Also try this:

Zone Alarm has two zones. Local Zone and Internet Zone. It is normal to set Local Zone security to medium or lower. You must then place our monitoring stations into the list of "local hosts". Please check this screenshot to see an example of the properties screen of Local Zone setup correctly to except our monitoring systems. Please note that the IP's in that screenshot are not the current IP's.

The machines that (currently) do the monitoring are

ny-monitor.dslreports.com
sjc-monitor.dslreports.com
dslreports-west2.speakeasy.net (64.81.79.40 AND 64.81.79.41)

These hosts should be be added to your firewall if ICMP ping is being blocked. The IP addresses do change from time to time, so if you must enter IP address and not DNS name, then please do an NSLOOKUP or PING to make sure of the current IP address.

Important: if you PADLOCK your zonealarm, no matter what, you are disconnected from the net. This will break monitoring. If you wish fulltime line monitoring, the PADLOCK function should not be used.

Feedback received on this FAQ entry:
  • ZoneAlarm Security Suite version:9.1.603.000 cant become pingable

    2010-07-27 20:10:21 (aceman1 See Profile)

  • Do you have any advice for the firewall component in AVG version 8.5 (paid)? Can only see a way of adding IP addresses, not DNS names. Adding the IP addresses for the monitoring machines above to my "safe networks" still does not allow pinging. Must be another setting somewhere to allow specified pinging?

    2009-08-27 08:32:02

  • I use ZoneAlarm (free, version 7) too and to become pingable I found I needed to set the Internet Zone Security slider to 'Med' on the Firewall tab. Mine was previously set to 'High' and the linetests failed due to my PC being un-pingable.

    2009-01-05 09:03:03 (davies63 See Profile)

  • The free edition of ZoneAlarm 7 does not have the "Allow incoming ping" option.

    2008-05-01 01:25:10 (mrglowbug See Profile)

  • My Zone Alarm 7 has NO "allow incoming ping" (or custom button for that matter). It does have an "advanced" button, but still no option for allowing incoming ping.

    2008-04-17 10:42:11 (gludwick See Profile)



by SunDog$ See Profile edited by Pinan See Profile
last modified: 2008-05-01 01:33:32

1. Click Start and open Control Panel. If using the classic start menu, Control Panel is located in Settings.

2. If Control Panel is in Category View, open Network and Internet Connections and then Windows Firewall. If using Classic View, open Windows Firewall.

-OR-

Click Start, Run and run the following command: firewall.cpl

3. Go to the Advanced tab, under ICMP, click Settings....

4. Place a check in Allow incoming echo request, then click OK twice. You will then be pingable.



Feedback received on this FAQ entry:
  • I also followed these steps in Vista using Windows Firewall and I am still not pingable.

    2013-05-10 16:50:21

  • I also checked allow echo in WindowsXP Firewall and still am unpingable

    2012-02-16 23:41:05 (Hovito See Profile)

  • I have WinXP SP3. Echo reest is 'on' & still 'un-pingable'. My problem, and maybe others, might be that years (!) ago I got a tool from Steve Gibson at gibson labs. If I recall it makes you 'invisible'. I don't remember the name of the tool... google his name and maybe you did the same. Sorry that I don't have time now to give more info than this, but it might explain the issue. BTW, he always wrote stuff in *really* tight* code, & if it didn't fit on a 'floppy' (< 1.44mb) he would not release it. Sorry if I went a bit off topic & ' 73 ! ; )

    2011-03-11 10:45:00 (zenzen See Profile)

  • I checked WindowsXP Firewall and Allow Echo was already checked, but I am still "unpingable" I am using AVG, will that interrupt? Security settings are down to Medium

    2010-12-15 14:30:17

  • I checked WindowsXP Firewall and Allow Echo was already checked, but I am still "unpingable" I am using AVG, will that interrupt? Security settings are down to Medium

    2010-12-15 14:29:27

  • Cannot become pingable, running xp sp3, was on wireless network, am now directly connected (ethernet) to dsl modem. I checked allow ping and disabled firewall still not pingable

    2010-04-12 00:17:46 (acmech See Profile)

  • I am not pingable either. I had the XP firewall off, have the ICMP box checked anyway. I am running XP SP3 and Trend Micro. I am losing packets like crazy and need to document it.

    2010-02-11 00:02:38 (carrolljd0 See Profile)

  • My firewall is off and I enabled echo request but its still saying I am unpingable. What am I doing wrong?

    2009-11-01 18:15:40 (Deganveran See Profile)

  • I can not become pingable either. Do these instructions work with most xp firewalled service pack 2 or 3 users?

    2009-10-11 16:17:08 (aztekwargod See Profile)

  • I am not able to be pingable either, although I have allowed incoming echo request in the windows XP Pro Firewall. I can even disable the firewall and it says that I am not pingable. I am using Shaw secure, maybe that has some type of firewall built in. I have service pack 3 installed.

    2009-03-19 14:34:31 (web_tracker See Profile)

  • It's not working for me too. I have Windows XP SP3, with AVG free Virus scanner. I have Roadrunner for my internet. My download speeds are variable between 10 MB/s to 1400 MB/s and my upload speeds are variable from 300 MB/s to 400 MB/s.

    2009-01-17 10:45:13 (Mechafish See Profile)

  • Ok, I am with Chuck Jones with almost the same problem. I am running XP SP3, with Trend Micro Internet Security Pro 2009 on Road Runner. Tried all suggestions, no dice. Please help! My download speeds vary from 10mbs to 1410mbs, upload is terrible at 410 to 480, should be up around 800 t0 980!

    2009-01-05 19:03:52 (Hardlign See Profile)

  • Many thanks for the instructions re pingable on WinXP...have done and will now try it. doowopdarlin

    2008-08-09 23:48:58 (doowopdarlin See Profile)

  • I am using windows XP sp2. I checked the box "to allow incoming echo request" I am still not pingable. I shutoff "Trend Internet Security" and turned off the windows firewall and I am still not pingable.

    2008-07-29 12:43:00 (chuck jones See Profile)

  • I didn't see where he said "My Network places" but, there are multiple ways to do EVERYTHING in Windows. He stated Click Start, Run and run the following command: firewall.cpl and that should work if you are running Windows XP SP2.

    2008-02-10 18:19:27 (terrypen See Profile)

  • No such thing as My Network places on my copy of XP XP2. Unable to find any of your suggestions.

    2008-01-08 12:42:45

  • @ jdenoyon Im assuming you are using vista due to the fact that it is now in the "windows firewall with Advanced sercurity". To get, go to your control panel then select "Administrative Tools". You must be logged in the admin account. Then select the Windows Firewall with Advanced Security". Once you get the window open go here to finish the process! http://technet2.microsoft.com/WindowsVista/en/library/9428d113-ade8-4dbe-ac05-6ef10a6dd7a51033.mspx?mfr=true

    2007-12-07 00:13:11 (sup2069 See Profile)



by Pinan See Profile edited by redxii See Profile
last modified: 2008-01-14 16:38:26

Version 10.3

  • On the McAfee SecurityCenter pane, click Internet & Network, then click Configure.

  • On the Internet & Network Configuration pane, under Firewall protection is enabled, click Advanced.

  • On the Security Level pane, under Security Settings, select Allow ICMP ping requests to allow detection of your computer on the network using ping requests.

If the firewall is set to Stealth security level, and you try to ping the computer from another computer in your network, the ping will fail. Both IPv4 and IPv6 block ICMP traffic when the firewall is set to Stealth mode, even if Allow ICMP Pings is enabled. ICMP requests are ignored as a way of protecting your computer on the network by keeping it hidden.

To allow a computer to respond to ICMP pings you must lower the security settings. Raise the security level once testing is complete.

Feedback received on this FAQ entry:
  • go to your system try (lower right corner of screen) Right click mcafee go to change settings select firewall Select smart advice and Adv. settings select allow ICMP ping Click Apply

    2012-07-10 07:13:20

  • McAfee Firewall current version is 11.5.131 (11.5 build 131) This is current as of 6/7/2010. I am also having a hard time configuring for ping.

    2010-06-14 15:54:05 (zbuckone See Profile)

  • If you configure your McAfee firewall to allow ICMP pings and you're still not pingable, make sure your router is pingable as well. I had to reconfigure both McAfee (9.15) and my router to become pingable. Worked just fine.

    2009-09-30 21:40:34 (jakeydsl See Profile)

  • You're suppose to click Configure first and then Internet & Network will show up. The rest of the steps are in order. Although i checked Allow ICMP ping requests and and turned my security level down, I am still not pingable according to dslreports.com

    2009-08-28 02:27:38 (spacecake12 See Profile)

  • McAfee Firewall is now version 10.3. Any possibility someone knows the secret? I have gone through all the applicable settings in McAfee Security Center to include checking the "Allow other computers to ping" to no avail. A little help here.

    2009-05-07 21:05:20 (RWBizSvcs See Profile)

  • Actually, the newest version is 9.1 now - 4/18/2008 - and this does not work with the 9.1 version either.

    2008-04-18 13:51:13 (RWBizSvcs See Profile)

  • Just so you know the latest version of McAfee is 8.2 not 3.02 and this guide doesn't work for that

    2007-10-31 14:38:54



by tferony See Profile edited by redxii See Profile
last modified: 2009-05-07 21:40:58

Here are the directions:

1. Double click the Sygate tray icon
2. Tools > Advanced Rules > Add
3. In rule descriptions, type: BBR
4. Select "Allow Traffic," select your NIC (Network Interface Card) and select your screen saver mode.



7. In the Hosts tab, select "IP Addresses"
8. Type in: 206.65.191.129,209.123.109.175,209.191.132.40,66.80.133.170,216.254.95.40



9. Hit Protocols and Ports tab
10. Check "Echo Reply - 0" and "Echo Request - 8"



11.Under Traffic direction, select Both Directions. Click OK twice and close Sygate.

You're done.

Feedback received on this FAQ entry:
  • i have did this for my winxpsp3 pc and Sygate,windows firewall but still cant be pinged during tweak.Any ideas?

    2008-06-18 00:49:52 (antoinefinch See Profile)

  • that was wonderfull thanks very much for your help!!!!!!!!!

    2008-03-07 11:30:55



by Lanik See Profile edited by JMGullett See Profile
last modified: 2007-02-26 14:36:44

This works even with "Deny Unknown" used. Tested with Tiny and Kerio Personal firewall pre-3.x.

1) Open up the firewalls Administration area, then click Advanced...



2) Click Add...

Set everything to the following:

Description
Anything you want it to be.

Protocol
ICMP. Click Set ICMP and choose [0] Echo Reply and [8] Echo Request.

Direction
Both directions.

Remote Endpoint
Address type: Any address

Action
Permit.

3) Click OK, then Apply. You should now be pingable.

by redxii See Profile edited by JMGullett See Profile
last modified: 2007-02-19 15:22:51

Here are the steps for NIS 2002: See below for 2003

1) Open the NIS/NPF Main Window
2) Click on Personal Firewall


3) Click on Internet Access Control
4) Click on Configure
5) Click on System Wide Settings


6) Click on Add


7) Select Permit


8) Click on Next
9) Select Connections to and from other computers


10) Select Only the computers and sites listed below
11) Click on Add


12) Select individually and type the following IP Addresses in the box spacing once between each

206.65.191.129
209.123.109.175
209.191.132.40
216.200.176.6
40.132.191.209

Note: Because of a bug in NIS/NPF, the IP address of some incoming ICMP requests are inverted. Therefore, NIS/NPF "sees" 209.191.132.40 as 40.132.191.209. This means that although 40.132.191.209 is not an IP address belonging to BBR, it must be included to be pingable. It is important to note that this is not a security risk. It simply means that your computer will respond to a request from 40.132.191.209. It is hoped that Symantec will correct this soon.

13) Click OK


14) Click Next
15) Select ICMP
16) Select Only the types of communication or ports listed below
17) Click Add


18) Select 0 echo Echo Reply and 8 echo-req Echo Request


19) Click OK
20) Type a name such as "BBR Pingable"
21) Click OK
22) Close NIS/NPF Window
23) Reboot

Note: This rule must be moved to the top of the System Rules, otherwise the default rules will override the DSLR rule. If you prefer not to be pingable by DSLR/BBR all of the time, you may de-select the rule that you just created by un-checking the box next to it in the System-wide Settings list. To become pingable for tweak tests, simply activate the rule before initiating the test, then de-active after.

Here are the steps for NIS 2003:

1) Open the NIS/NPF 2003 Main Window
2) Click on Personal Firewall



3) Click on Configure (enter password if requested)
4) Click on the Advanced Tab



5) Click on the General Rules button
6) Continue with the above directions for NIS 2002 starting from number 6.
--
Thanks to jazzman916 for the directions and screen shots.


Feedback received on this FAQ entry:
  • Not working at all with Norton 2012.

    2013-04-29 23:27:23

  • Not working at all with Norton 2011. Followed all directions. Any suggestions?

    2011-04-28 12:24:51

  • update for Norton Internet Security 2009 and simmilar in order to change and add the rules as outlined in the NIS2002 starting from number 6 you must first get to the General rules configuration setting. 1)To get to the General Rules configuration settings start from the main Norton Internet Security screen and 2) click on the Internet Settings link. *It may ask for a password, if it does enter the password for the program. 3)from the settings screen click on the "Smart Firewall" "Advanced Settings" "Configure[+]" link. 4)click on the General Rules Configure[+] link Continue with the above directions from NIS 2002 starting with number 6.

    2010-03-04 05:07:46 (spaceman2002 See Profile)

  • Not working with newest version of Norton or not working because I am in Europe?

    2008-01-05 12:13:35 (Rizava See Profile)



by Pinan See Profile edited by JMGullett See Profile
last modified: 2007-02-26 14:42:05

To edit local Group Policy settings for Windows Firewall with Advanced Security, use the Local Computer Policy snap-in. To open the local Computer Policy snap-in, type secpol at the command prompt. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue. Navigate to Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security to configure the Windows Firewall with Advanced Security policy

To enable ICMP Echo Request for ICMPv4 and ICMPv6.

1. In the Windows Firewall with Advanced Security snap-in, click Inbound Rules in the tree, and click New Rule in the Actions Pane.

2. Click Custom and click Next.

3. Click All programs and click Next.

4. For Protocol type, select ICMPv4.

5. Click Customize for Internet Control Message Protocol (ICMP) settings.

6. Click Echo Request, click OK, and then click Next.

7. Under Which local IP address does this rule match? and for Which remote IP address does this rule match click either Any IP address or These IP Addresses. If you click These IP addresses, specify the IP addresses and click Add, then click Next.

8. Click Allow the connection, and then click Next.

9. Under When does this rule apply?, click the active profile, any or all profiles (Domain, Private, Public) to which you want this rule to apply, and then click Next.

10. For Name type a name for this rule and for Description an optional description. Click Finish.

11. Repeat steps for ICMPv6, selecting ICMPv6 for Protocol Type instead of ICMPv4.

Feedback received on this FAQ entry:
  • I followed the instructions above to make Vista pingable. My firewall now allows this app. thru. After rebooting and running the Tweak Test I still get the make pingable message.

    2011-03-17 01:21:57

  • how do i become pingable with windows 7 firewall

    2010-09-06 04:44:58 (alt1231 See Profile)

  • okay, let me get this straight.. is your internet connection feeding only off the modem or modem/router? im running modem/router because i have multiple network connections. im running vista 64 and i did everything by this tut and how tgwombat posted, and no luck. figuring my router is causing me to be unpingable

    2009-08-17 15:02:46 (vbrsm See Profile)

  • I had a little trouble getting to "Windows Firewall with Advanced Security"; here's how I finally did it: Method 1: RMB on Start button, "Properties", "Start Menu" tab, "Classic Start Menu" radio button, "Customize" button, "Display Administrative Tools" checkbox, "Ok" button. Now go to Start -> Programs -> Administrative Tools -> Windows Firewall with Advanced Security" Method 2: Start -> Settings -> Control Panel -> Windows Firewall -> Change Settings -> ("Continue" if prompted) -> "Advanced" tab -> "Where can I find ICMP and logging settings?" link -> "What happened to the ICMP and logging settings in Windows Firewall?" link -> "Click to open Administrative Tools" link -> "Windows Firewall with Advanced Security"

    2009-08-08 22:03:36 (Lulu58e2 See Profile)

  • jinhuang1980: I had to go Start -> Programs -> Accessories, then RMB (right mouse button) on "Command Prompt" and choose "Run as Administrator"; After that I ran the command and it returned "Ok". The line test still says I'm not ping-able though.

    2009-08-08 21:47:37 (Lulu58e2 See Profile)

  • tgwombat....i tried what you said to do but it gave me this message..."the requested operation requires elevation" not sure what this means.

    2009-05-09 20:03:44 (jinhuang1980 See Profile)

  • Windows VISTA: First, be sure you are using WINDOWS security/firewall, and not Norton or some other one that often gets shipped with your computer. Then, in Windows Vista, open Windows Security Center (should be a "shield" shaped shortcut on the lower right side of your desktop toolbar--right-click to open); then click on "Windows Firewall" on the left side of the menu. Click on the "Change Settings" underlined link in the center-right of the window (next to the multi-colored shield icon). Click on the "Advanced" tab. If you basically have no options to change anything there, it means you are NOT signed on as System Administrator. At the bottom of the window, click on the underlined link that says "Where can I find ICMP and logging settings?". This will open a Windows Help and Support menu, where you can click on the underlined link question "How do I view and edit all firewall properties?". Just follow the instructions there. NOTE, however, that you MUST have System Administrator privlidges!

    2009-03-01 20:37:47 (SgtFury See Profile)

  • i tryed this to make the smoke ping work in windows vista (hmm home i guess) but it still says : sorry, 90.235.161.195 is not pingable from www.dslreports.com. Please disable firewall ping protection. See this FAQ section for more information. could you please mail me @ jecucejecuce@gmail.com for help and/or feddback on this issue /regards chris

    2009-01-31 16:06:02

  • tgwombat gave the correct solution, simpler is better...more work/play less talk. Dont be afraid of the command prompt

    2009-01-13 18:10:30 (spazo See Profile)

  • Works for me under Vista 64bit Ultimate. If you do the test on a different day, you have to delete the previous entries and re do them. Good luck to all.

    2009-01-10 02:14:30 (papi4baby See Profile)

  • If you bring up the command prompt as an administrator and enter "netsh firewall set icmpsetting 8 enable" without the quotation marks it will enable ICMP Echo Request. Much simpler than this whole process.

    2008-12-26 04:17:52 (tgwombat See Profile)

  • These instructions do not apply to move Vista users since secpol.msc is not available in Windows Vista Starter, Windows Vista Home Basic, or Windows Vista Home Premium (see technet article below). So how does one do this with one of these more common versions of Vista? http://technet.microsoft.com/en-us/library/cc709691.aspx

    2008-12-07 14:55:24 (gimpster See Profile)

  • OK, I followed all the instruction for Vista Windows Firewall with advanced security the line quality test still says not pingable.

    2008-06-04 13:54:12 (airedale See Profile)

  • "How do I become pingable with the Vista firewall? (#15764)" says: "Navigate to Computer Configuration\Windows Settings\Security Settings\Windows Firewall with Advanced Security to configure the Windows Firewall with Advanced Security policy" (sic) No need to navigate. Just expand the "Windows Firewall with Advanced Security" in the left pane. Also this: it says: "1. In the Windows Firewall with Advanced Security snap-in, click Inbound Rules in the tree, and click New Rule in the Actions Pane." There is no actions pane. "New Rule" is located in the Action menu, not pane. Must also cancel any highlighting of any rule (if applicable) to see the "New Rule", or else it will not appear but "Disable Rule" appears instead.

    2008-01-17 23:39:57 (Mdoc See Profile)



by redxii See Profile

Due to varying & ever-changing manufacturers, models, and firmware, it is tedious to list instructions for every one of those. Refer to your router or hardware firewall documentation, either included with your router or hardware firewall and is also usually available in PDF format from the manufacturer's website.

by redxii See Profile
last modified: 2008-04-19 11:55:41