how-to block ads
|
| | | | FAQ Revisions | Editors: Pinan  , redxii
Last modified on 2009-10-24 02:33:12
| |
|
|
3. Becoming Pingable·How do I become pingable with Zone Alarm?
·How do I become pingable with WinXP firewall?
·How do I become pingable with McAfee Firewall?
·How do I become pingable with Sygate Personal Firewall?
·How do I become pingable with Kerio/Tiny Personal Firewall?
·How do I become pingable with Norton Personal Firewall?
·How do I become pingable with the Vista firewall?
·How do I become pingable with a router or hardware firewall?
| | | 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
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 form
 feedback form
by SunDog$ edited by Pinan
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 form
feedback form
by Pinan edited by redxii
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 form
feedback form
by tferony edited by redxii
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 form
feedback form
by Lanik edited by JMGullett
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.
feedback form
feedback form
by redxii edited by JMGullett
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 form
feedback form
by Pinan edited by JMGullett
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 form
feedback form
by redxii | | | 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.
feedback form
feedback form
by redxii
last modified: 2008-04-19 11:55:41 |
|
