I can't find the reply I had gotten
from someone about setting all the ports for the LAN, WAN, and DMZ to 100MB
half duplex as opposed to autosensing, but I just wanted to pass along that
this advice so far seems to have made a difference. Been over a week now
and I haven't had a single reboot or freeze of the Pro-VX.
Whoever you were, sorry I can't give
you immediate credit, but it seems to have worked! Thanks!
Now if I can just figure out why my VPN
stopped working a couple days ago when there was absolutely NO change anywhere
on the network or sonicwall! J
Gotta love this list... been over 2
weeks since I contacted Sonicwall's support for this problem, and I *still* haven't heard a single word
back... Maybe this list should be getting payments from Sonicwall for
fulfilling the role of customer support. <G>
John
-----Original Message-----
From: Kok-Yong Tan
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 22, 2002 1:07
PM
To: [EMAIL PROTECTED]
Subject: Re: [SonicWALL]-
Intermittant SonicWALL
As an aside to this problem, if John wants to see what
the SonicWall is doing up to the point of freezeup, it might be helpful to set
it to log information at debug priority level and above to an external syslog
server since when the SonicWall freezes and is power-cycled, it blanks its
onboard logfile. This may require a syslog server with a lot of disk
space free since the SonicWall will spit out a lot of information that gets
logged at the debug priority level. Hope this helps.
At 12:36 -0400 05/22/2002, Scott Milewski wrote:
John,
I actually have seen this before.
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
Systems Engineer
ValCom & VTEC - Partners in
Information Technology and Education
Visit our Web Sites at www.valcommaine.com
& www.vtec.org
From: [EMAIL PROTECTED]
Subject: [SonicWALL]- Pro-VX locks
up randomly?
Date: Tue, 21 May 2002 16:13:43
-0500
Reply-To: [EMAIL PROTECTED]
This message is in MIME format.
Since your mail reader does not understand this format, some or all of this
message may not be legible.
------_=_NextPart_001_01C2010C.63603540
Content-Type: text/plain
I'm running a sonicwall pro vx. it's
in NAT mode, and my company LAN is sitting behind it on a 172.16.x.x address
range. I've got about half a dozen servers and devices on the WAN link (not
counting the routers) and just one machine in the DMZ at the moment. The
sonicwall is programmed with the IP's in the WAN switch, and also is programmed
for the one in the DMZ. There are no IP conflicts that I can find. But
randomly, sometimes two or three times in an hour, sometimes a week between, it
simply locks up. No outbound traffic works, can't open the admin web page on
the sonicwall, nothing. And the only way to fix it is to power it off, then
power it back on again.
I'm running firmware 6.3.1.0, but it
also did this with 6.2 as well a couple of times. One of the reasons I upgraded
the firmware was in hopes that this problem would be cleared up.
There's no VPN usage when it
happens, as I'm the only one setup at the moment to VPN through it until I can
figure out a way for the rest of my clients to pull a WINS server address from
their VPN connection using the 8.0 client software, since I don't want to have
a bunch of lmhost files to have to maintain on everyone's notebooks.
When it happens, I can't even see if
there are any errors in the log because the logs are empty. I've turned the
device off momentarily and did a scan of my internal network to see if someone
had hard coded the same IP onto one of their computers or something, but there
are no address conflicts with it.
Has anyone else ever seen this? If
so, did you ever resolve it? I still have support through September on it, and
contacted Sonicwall on the 17th, but have gotten absolutely nothing from them
as of yet.
Thanks for any replies.
John
Scott Milewski
Systems Engineer
ValCom & VTEC - Partners in
Information Technology and Education
P: 207-775-2223 ext. 3072
F: 207-775-0241
[EMAIL PROTECTED]
Visit our Web Sites at www.valcommaine.com
& www.vtec.org
--
P.O. Box 565,
Gracie Station
http://www.realityartisans.com
"We
craft ideas into reality"
