Reason 442: Cannot enable virtual adaptor

Hi,
I work in a remote sales office and I installed the Cisco VPN client on my
laptop while connected to my executive suite wireless network and then
connect to the vpn at our HQ with no problem. When I go home and connect to
my home network and launch the client I get the "Reason 442: Cannot enable
the virtual adaptor" error. After trying to connect at home I can no longer
connect at the office either. I can uninstall the client and reinstall and
it will work either at home or work, depending on where I am when I install
it. As soon as I try to connect to the VPN while getting internet access
from a network other than the one I was on when I installed the client, I get
the Reason 442 error. I travel a lot and this is a big problem for me.

I have tried versions 4.8.01.0590 and 4.8.02.0010 and 5.0.00.0090. I
couldn't get the 5.0 version to work even on the first install. I have also
tried adding the UseLegacyIKEPort=0 line to my profile.

The VPN worked fine at work, home and road when I was running WinXP, but
since switching to Vista I just can't get it to work consistantly.

Thanks

[SanDegan]

Have you solved this problem?

Yesterday after much headache, I got Cisco VPN client 4.8.xxxx to connect to a client office. I am using Vista Home.

Today, I cannot create a connection. I keep getting “Reason 442:".

On Mon, 14 Jul 2008 18:40:05 +0100, SanDegan
<SanDegan.3cjv0f@no-mx.forums.vistaheads.com> wrote:

>
>Have you solved this problem?

Wake up.

The person you are talking to posted ON FEBRUARY 26 OF 2007, and is
not registered on the forum you are using: i.e., he/she won't even
know you replied.

[SanDegan]

John,
Thanks for the truly insightful reply.
While the original poster may not be registered, my reply is none the less available to others in this forum, evidenced by the fact that you found it.
As such, someone with actual insight into the problem posted may be able to provide some helpful information.
But alas we are entertained by your truly insightful reply.

These posts may help.

Collections of fixing Cisco VPN Reason 442
http://chicagotech.net/netforums/viewtopic.php?t=4549

Cisco VPN Reason 442
http://chicagotech.net/netforums/vie...hp?p=7303#7303

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"SanDegan" <SanDegan.3cjv0f@no-mx.forums.vistaheads.com> wrote in message
news:SanDegan.3cjv0f@no-mx.forums.vistaheads.com...
>
> Have you solved this problem?
>
> Yesterday after much headache, I got Cisco VPN client 4.8.xxxx to
> connect to a client office. I am using Vista Home.
>
> Today, I cannot create a connection. I keep getting “Reason
> 442:".
>
>
> --
> SanDegan
> Posted via http://www.vistaheads.com
>

[SanDegan]

Thanks Robert,
Unfortunately, I have already been to those posts. They did not help the problem.
I am beginning to suspect that the client site is somehow causing my issues. They are in New York, I am in California.
Yesterday (Sunday) was a non work day, so light on their systems. Early today I was having the problem nonstop. Now that it’s after closing time in New York, I seem to be able to connect each time without the error.
Any opinions?

Do you have other computers to test it? If other computer has the same
problem, I would check the VPN server; if it works, I would try to remove
the Cisco VPN manually and then re-install it.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"SanDegan" <SanDegan.3ck8wf@no-mx.forums.vistaheads.com> wrote in message
news:SanDegan.3ck8wf@no-mx.forums.vistaheads.com...
>
> ::Thanks Robert,::
> ::Unfortunately, I have already been to those posts. They did not help
> the problem. ::
> ::I am beginning to suspect that the client site is somehow causing my
> issues. They are in New York, I am in California.::
> ::Yesterday (Sunday) was a non work day, so light on their systems.
> Early today I was having the problem nonstop. Now that it’s after
> closing time in New York, I seem to be able to connect each time without
> the error. ::
> ::Any opinions?::
>
>
> --
> SanDegan
> Posted via http://www.vistaheads.com
>