Anyone else having problems with the new Sonicwall VPN client/firmware?
Bill K
I recently obtained a Sonicwall Pro with the 4.1.1 firmware
installed. I downloaded the VPN client version 3.02, which managed to
trash my network setup completely. Within 30 seconds of creating a SA,
my winsock connection through my NIC died. I yanked the NIC and tried
going only through the dialup on an analog modem, same result.
I am running 98 SE, and had the previous VPN software (VPCom
2.5) on the machine. I uninstalled the other VPN software prior to
loading the newer VPN client, and I followed the VPN Client Simple
Configuration directions to the word. I am testing this by connecting
to my company SW Pro prior to upgrading my customers
I noticed that the newer client doesn't install its own VPN
adapter, so apparently it is using the Micrsoft Virtual Private
Networking adapter??? Also, I miss the old clients' ability to control
the IKE negotiation process, you can't tell what the heck this new
client is trying to do(not even so much as a status to view).
Has anyone been able to get the 3.02 client/4.1.1 firmware
with VPN working successfully? If so, please do tell..... please do :)
Regards-
Bill Kersey
Ole Vik
<591D588EE0111C65.244A90A7...@lp.airnews.net>,
Bill K <cbh...@iag.net> wrote:
This new VPN client is a big improvement from the previous VPCOM client.
In all cases we have installed this, it worked at once. The installation
files you can get from the firmware.sonicwall.com site is very good at
explaining how to do the installation.
I think the problems you have are related to the specific PC involved.
Have you tried it on another one?
--
Ole Vik, Connect AS, Blakstadmarka 26, N-1386 Asker, Norway.
Bill K
I ended up dumping the attempt to VPN through dialup, and put
my machine on the public LAN link at the office (it was behind the SW
Pro). After assigning my box a public address, I get this in the log
when I try to browse to the 192 address of the SW:
17:23:15.060 New Connection - Initiating IKE Phase 1 (IP
ADDR=209.26.177.2)
17:23:15.170 New Connection - SENDING>>>> ISAKMP OAK AG (SA, KE, NON,
ID, VID)
17:23:15.780 New Connection - RECEIVED<<< ISAKMP OAK AG (SA, KE, NON,
ID, HASH)
17:23:15.890 Cannot match Policy Entry for received Phase 1 ID:
17:23:16.000 remote host=DOMAIN=0040100C82F3
17:23:16.110 New Connection - SENDING>>>> ISAKMP OAK INFO (HASH,
NOTIFY:INVALID_ID_INFO)
17:23:16.220 New Connection - Discarding IKE SA negotiation
Ok, some progress! Two errors:
17:23:15.890 Cannot match Policy Entry for received Phase 1 ID:
and
17:23:16.110 New Connection - SENDING>>>> ISAKMP OAK INFO (HASH,
NOTIFY:INVALID_ID_INFO)
I believe that they refer to the same problem, only thing is,
I don't see anything wrong with the configuration on either the Pro or
my machine with the VPN client (3.02e) I have followed the
instructions for the advanced vpn client configuration.
Any ideas? Thanks much for your insight/help, I have sent this
off to SW tech support, but as usual, two days and no response.
Bill K.
Bill K
I had a capital O instead of a 0 in the unique ID on the
client, now it gets past that, but still fails. This is the error
message:
09:20:02.260 New Connection - Initiating IKE Phase 1 (IP
ADDR=209.26.177.2)
09:20:02.370 New Connection - SENDING>>>> ISAKMP OAK AG (SA, KE, NON,
ID, VID)
09:20:02.970 New Connection - RECEIVED<<< ISAKMP OAK AG (SA, KE, NON,
ID, HASH)
09:20:03.080 New Connection - Discarding IKE SA negotiation
Arrgh! Anyone that could help, I would be most appreciative.
This is a VPN advanced configuration, firmware 4.1.1, client 3.02e on
a Sonicwall Pro.
Regards-
Bill K