Title: Message
 
Kok-Yong,
 
The rule is actually called "Ping".
To enable this rule, click on the Access button, then on the Add Service tab.
From the Custom Service drop-down, choose Ping.
Once you have updated this, click on the Services tab.
Find Ping (which should now be added) and in the Public LAN Server filed, fill in the LAN IP Address of your SonicWALL.
When you ping the WAN IP now from the outside, there should be a reply.
Not the most secure, but it does the job.
 
Scott Milewski
Systems Engineer
ValCom, "A Technology Management Services Company"
South Portland, ME  04106
"Knowledge is of two kinds. We know a subject ourselves, or we know where we can find information upon it." (Samuel Johnson)
PGP Key available upon request

Date: Tue, 26 Mar 2002 16:41:53 -0500

From: Kok-Yong Tan <[EMAIL PROTECTED]>

Subject: RE: [SonicWALL]- SonicWALL

Reply-To: [EMAIL PROTECTED] --============_-1194942722==_ma============

Content-Type: text/plain; charset="us-ascii" ; format="flowed"

I'm curious about this: According to SonicWall tech support, the

TELE2's WAN interface is ALWAYS unpingable from anywhere (WAN or LAN)

and there's nothing I can do to change this. The Stealth option

isn't it because I've tried switching it off and rebooting and my

TELE2's WAN interface is still unpingable. This is the entry from

the onboard help file:

Stealth Mode

By default, the SonicWALL Internet Security Appliance responds to

incoming connection requests as either "blocked" or "open". If you

enable Stealth Mode, no response will be made to inbound requests,

thereby making your network "invisible" to potential attackers.

I can always ping the LAN interface from the LAN but I can never ping

the WAN interface from either the LAN or from the WAN. What access

rule did you change to allow it to be pinged?

Reply via email to