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.
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?
At 11:25 -0600 03/26/2002, Marcus D. Gand wrote:
I had a similar problem. The ISP would drop the DHCP lease because the ISP could not ping the host. This was due to enabling "Stealth" mode. After changing the access rules and allowing "ping" to my local machine from the WAN, all was fine. Of course, I dropped the ISP in a heartbeat and went to cable. The ISP was Southwestern Bell ADSL. What's the point in trying to secure your system when your ISP won't let you!!! Hope this might be of some help to someone.
--Marcus
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Scott Milewski
Sent: Tuesday, March 26, 2002 11:02 AM
To: '[EMAIL PROTECTED]'
Subject: [SonicWALL]- SonicWALL
Kok-Yong,Not sure if you've gotten any replies back from this.I used to work at a company where our SonicWALL would mysterious disconnect at a specific time every day (or after a specific time interval) and would then need to be manually rebooted in order to reconnect to the ISP. After troubleshooting with SonicWALL, having them send us a new device (to no avail), and then having SonicWALL, myself and our ISP on the same conference call, we discovered it was a problem with the DHCP servers at the ISP. For some reason, a setting they changed a couple weeks before was causing our problem. Whenever the SonicWALL went back to the ISP's DHCP server, it caused the SonicWALL to freeze. Damn annoying. Of course, the ISP said it wasn't their problem, and then a week later, the problem disappeared altogether. Again, nothing got changed on our end.Another customer recently had their SonicWALL go up and down sporadically for about 4 weeks (after changing nothing). After fighting with the ISP for weeks and never getting any higher than a level 2 tech, the ISP finally told them that their SonicWALL was the problem. That afternoon, the ISP called them and told them that the SonicWALL device had taken over a Gateway address on their network for a period of time that day. After getting on the phone (finally) with a senior level tech, they discovered it was another SonicWALL elsewhere in the system causing the customer's problem (that other SonicWALL was configured incorrectly), and that's what had been causing their problems for a month.Not sure if that is what's causing your problem, but it's worth looking into. Almost always blame your ISP's if you have changed nothing on your end. I've since installed about 30 SonicWALL's (and maintained much more) and have never run into the problem being with the SonicWALL. It's almost always the fault of the ISP. However, getting them to admit that is the hard part.Regards,Scott Milewski[This E-mail scanned for viruses by Declude/F-Prot Virus]=====================================================Date: Thu, 7 Mar 2002 16:00:39 -0500
From: Kok-Yong Tan <[EMAIL PROTECTED]>
Subject: RE: [SonicWALL]- Weird Pro-VX
Reply-To: [EMAIL PROTECTED]
At 20:54 +0100 03/07/2002, Jesper Bach wrote:
>Good idea. If you run firmware 6.0.1.0 or earlier i have seen>mysteriuos = reboots and unprovoked clearing of config. 6.0.1.1 has
>made it somewhat more stable, but i would prefer 6.2.x.x
>
>Jesper
Are you sure about this? I've left a tech support request with SonicWall with no replies on it. I am running firmware 6.2.0.0 and over the past month and a half, I've been noticing mysterious reboots every six days at 10:22pm local time. The next "scheduled" mysterious reboot is 10:22pm tonight. If it occurs, I've got a verified pattern. But no obvious reasons (I have a syslog server which also logs most everything when my SonicWall TELE2 resets itself). I've had the TELE2 for about six months and uploaded 6.2.0.0 almost as soon as it came out. But my problems only started recently (in the last month and a half). Any clues?
--
*****************************
Reality Artisans, Inc.
P.O. Box 565, Gracie Station
New York, NY 10028-0019
http://www.realityartisans.com
"We craft ideas into reality"
*****************************
---
--
*****************************
Reality Artisans,
Inc.
P.O. Box 565,
Gracie Station
New York, NY
10028-0019
http://www.realityartisans.com
"We craft
ideas into reality"
*****************************
