Vista Windows Update breaks Cisco Client!

  • Thread starter Thread starter shauny
  • Start date Start date
S

shauny

Hi

I was running the Cisco VPN version 5.0.00.0090 happily (as
administrator) until I did a windows update yesterday. Now the VPN
connection gives me a 442 error (Failed to enable virtual adapter). I
have added the UseLegacyIKEPort=0 line to my profile, but it still
errors.

Any ideas?

Shaun
 
If rolling back solves the problem then please turn on the RAS logs and let
us know. Below are the steps for to turn on the RAs logs

1) netsh ras set trac * ena
Repeat the case
2) netsh ras set trac * dis

Get all the files in directory %windows%/tracing

Abhishek
 
If rolling back solves the problem then please turn on the RAS logs and let
us know. Below are the steps for to turn on the RAs logs

1) netsh ras set trac * ena
Repeat the case
2) netsh ras set trac * dis

Get all the files in directory %windows%/tracing

Abhishek
Click to expand...


Hi

Rollback not an option unfortunately, but the logs in tracing are all
pretty dull apart from one line:

[3372] 14:45:17: IsatapUpdateRouterAddress: Failed to resolve router
isatap in site

Nothing network related has changed. Went into Device Manager (at the
advice of a cisco engineer) and enabled the Cisco VPN device, but as
soon as the VPN client fails, it sets the device back to disabled....

:-(

Shaun
 
If rolling back solves the problem then please turn on the RAS logs and let
us know. Below are the steps for to turn on the RAs logs
Click to expand...
1) netsh ras set trac * ena
Repeat the case
2) netsh ras set trac * dis
Click to expand...
Get all the files in directory %windows%/tracing
Click to expand...

Hi

Rollback not an option unfortunately, but the logs in tracing are all
pretty dull apart from one line:

[3372] 14:45:17: IsatapUpdateRouterAddress: Failed to resolve router
isatap in site

Nothing network related has changed. Went into Device Manager (at the
advice of aciscoengineer) and enabled theCiscoVPNdevice, but as
soon as theVPNclient fails, it sets the device back to disabled....

:-(

Shaun
Click to expand...

I get this reasonably often on Vista as well. I am using the same VPN
client version as you mentioned in your original post. I get the
same symptoms, and sometimes fixing it will involve either a) a reboot
of my laptop, or b) enabling the VPN Adapter in "NETWORK
CONNECTIONS"... and then sometimes even that doesn't work, and I have
to rely on simple perservance.

I'm trying to reproduce the issue now, but each time so far, with
logging turned on, I haven't had the issue !

Thanks
Rob
 
Rollback not an option unfortunately, but the logs in tracing are all
pretty dull apart from one line:
Click to expand...
[3372] 14:45:17: IsatapUpdateRouterAddress: Failed to resolve router
isatapin site
Click to expand...
Nothing network related has changed. Went into Device Manager (at the
advice of aciscoengineer) and enabled theCiscoVPNdevice, but as
soon as theVPNclient fails, it sets the device back to disabled....

Shaun
Click to expand...

I get this reasonably often onVistaas well. I am using the sameVPN
client version as you mentioned in your original post. I get the
same symptoms, and sometimes fixing it will involve either a) a reboot
of my laptop, or b) enabling theVPNAdapter in "NETWORK
CONNECTIONS"... and then sometimes even that doesn't work, and I have
to rely on simple perservance.

I'm trying to reproduce the issue now, but each time so far, with
logging turned on, I haven't had the issue !

Thanks
Rob- Hide quoted text -

- Show quoted text -
Click to expand...

Okay so I now this, with the logging turned on. How much of the trace
file do you need to see? Some of it contains server names, which I'm
not sure i'd want to post here, but I can clear those if
necessary.....
 
Rob said:
On Feb 26, 11:53 am, (e-mail address removed)
Click to expand...
If rolling back solves the problem then please turn on the RAS logs and let
us know. Below are the steps for to turn on the RAs logs
Click to expand...
1) netsh ras set trac * ena
Repeat the case
2) netsh ras set trac * dis
Click to expand...
Get all the files in directory %windows%/tracing

:
Hi
Click to expand...
I was running theCiscoVPNversion 5.0.00.0090 happily (as
administrator) until I did a windows update yesterday. Now theVPN
connection gives me a 442 error (Failed to enable virtualadapter). I
have added the UseLegacyIKEPort=0 line to my profile, but it still
errors.
Click to expand...
Any ideas?


Rollback not an option unfortunately, but the logs in tracing are all
pretty dull apart from one line:
Click to expand...
[3372] 14:45:17: IsatapUpdateRouterAddress: Failed to resolve router
isatapin site
Click to expand...
Nothing network related has changed. Went into Device Manager (at the
advice of aciscoengineer) and enabled theCiscoVPNdevice, but as
soon as theVPNclient fails, it sets the device back to disabled....

Shaun
Click to expand...

I get this reasonably often onVistaas well. I am using the sameVPN
client version as you mentioned in your original post. I get the
same symptoms, and sometimes fixing it will involve either a) a reboot
of my laptop, or b) enabling theVPNAdapter in "NETWORK
CONNECTIONS"... and then sometimes even that doesn't work, and I have
to rely on simple perservance.

I'm trying to reproduce the issue now, but each time so far, with
logging turned on, I haven't had the issue !

Thanks
Rob- Hide quoted text -

- Show quoted text -
Click to expand...

Okay so I now this, with the logging turned on. How much of the trace
file do you need to see? Some of it contains server names, which I'm
not sure i'd want to post here, but I can clear those if
necessary.....
Click to expand...
I just learnt that Cisco client does not use remote access client of MS so
these logs might not help.
 
If you have multiple NICs in your machine (e.g. 1 ethernet, 1 wireless), try disabling 1 of them before using the VPN client.

I have been experiencing the same problem, but disabling either 1 of my NICs then allows the VPN client to connect successfully.

I am on an earlier version of the client, but hope this is of help to some.

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
 
If you have multiple NICs in your machine (e.g. 1 ethernet, 1 wireless), try disabling 1 of them before using the VPN client.

I have been experiencing the same problem, but disabling either 1 of my NICs then allows the VPN client to connect successfully.

I am on an earlier version of the client, but hope this is of help to some.

EggHeadCafe.com - .NET Developer Portal of Choicehttp://www.eggheadcafe.com
Click to expand...

I will try that out tonight.

I do have multiple NICs. I have the onboard ethernet, and wireless,
along with 2 VMWare NICs (which are already disabled). Normally when
I attempt to VPN then I'm on wireless, but the regular NIC isn't
connected (but is still enabled).

A reboot always seems to cure it for me, but then a few VPN sessions
later, and I'm back to "Failed to enable Virtual Adapter".
 
I will try that out tonight.

I do have multiple NICs. I have the onboard ethernet, and wireless,
along with 2 VMWare NICs (which are already disabled). Normally when
I attempt to VPN then I'm on wireless, but the regular NIC isn't
connected (but is still enabled).

A reboot always seems to cure it for me, but then a few VPN sessions
later, and I'm back to "Failed to enable Virtual Adapter".
Click to expand...

Hi

I tried disabling the other NIC's but I get the same error. As I do
if I enable the adapter through control panel. *Sometimes*
uninstalling the Cisco VPN software, rebooting and re-installing
works, but its not exactly convenient.

Oh well, back to XP I guess - Vista is no use to me without a
connection to my office.

:-(

Shaun
 
I tried disabling all the other nics on the machine, and then running
the vpn software... seemed to work for a bit, even when I come in and
out of standby

But just now I tried it, and it's back to the same "Failed to enable
Virtual Adapter".

I've rebooted the machine, and it has just connected fine.!
 
Gents:

I have the same problem, yet I do not see that Citrix client as the
sole cause (if at all) since I do not run it.

MULTIPLE re-boots are not solving the problem. Here is some more
information on the problem for the benefit of other searchers (my
exact configuration may or may not be contributing to the problem vs.
a software bug):

Windows Vista Business 32-bit
Dell Latitude D420
U2500 @ 1.20GHz Processor
2038MB RAM

I run Cisco VPN version 5.0.00.0090 as administrator on this machine.

Despite disabling other connections (e.g. besides one ethernet
connection in use), and enabling "Local Area Connection 2" manually
(which is for Cisco Systems VPN Adapter on my setup), the error
message persists, and occurs COMMONLY:

"VPN Client: Secure VPN Connection terminated locally by the Client.
Reason 442: Failed to enable Virtual Adapter. Connection terminated
on: MM DD YYYY HH:MM:SS Duration: 0 day(s), 00:00.00"

This has amounted to a relatively severe loss of productivity; I'm
disappointed in Cisco's inability to resolve (darn near impossible to
find meaningful, current information on their site)...
 
Back
Top