> On Thu, 17 Jul 2008 14:27:00 -0700, Lynne
> <(email address - cut out)> wrote:
>
>>I'm new to the VPC world and I don't have much networking experience. My
>>host machine is Windows XP Pro/SP2 and my guest is Windows Server 2003.
>>Initially I was unable to connect to the internet on the guest, but
>>resolved
>>the problem by changing the networking Adapter 1 to Shared networking
>>(NAT)
>>and hardcoding the DNS on the guest to 192.168.131.254. This resolved the
>>internet connectivity problem, but I still cannot connect to the Cisco
>>VPN.
>>The authentication window displays and I can enter my user/password, but
>>the
>>connection never completes. The error is "the virtual adapter failed to
>>enable". I've tried changing my Adapter 1 to my host's network adapter,
>>but
>>then I cannot access the internet and the Cisco VPN authentication window
>>never pops up.
>>
>>Any help would be appreciated. Thanks.
>
> Can't be done...
> First you cannot use Shared Networking for tis.
> Second Cisco VPN is very picky on the networks when it connects and
> basically shuts down all networks other than its own VPN one.
>
> I don't hink it can even be done if you have a properly configured
> network for the guest (using the host NIC instead of Shared
> networking).
>
> What I know works is to connect a Microsoft VPN tunnel from a guest
> using PPTP protocol, but ten PPTP does not sut down other
> networking....
>

>I'm new to the VPC world and I don't have much networking experience. My
>host machine is Windows XP Pro/SP2 and my guest is Windows Server 2003.
>Initially I was unable to connect to the internet on the guest, but resolved
>the problem by changing the networking Adapter 1 to Shared networking (NAT)
>and hardcoding the DNS on the guest to 192.168.131.254. This resolved the
>internet connectivity problem, but I still cannot connect to the Cisco VPN.
>The authentication window displays and I can enter my user/password, but the
>connection never completes. The error is "the virtual adapter failed to
>enable". I've tried changing my Adapter 1 to my host's network adapter, but
>then I cannot access the internet and the Cisco VPN authentication window
>never pops up.
>
>Any help would be appreciated. Thanks.

> I don't hink it can even be done if you have a properly configured
> network for the guest (using the host NIC instead of Shared
> networking).

>
> "Bo Berglund" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > On Thu, 17 Jul 2008 14:27:00 -0700, Lynne
> > <(email address - cut out)> wrote:
> >
> >>I'm new to the VPC world and I don't have much networking experience. My
> >>host machine is Windows XP Pro/SP2 and my guest is Windows Server 2003.
> >>Initially I was unable to connect to the internet on the guest, but
> >>resolved
> >>the problem by changing the networking Adapter 1 to Shared networking
> >>(NAT)
> >>and hardcoding the DNS on the guest to 192.168.131.254. This resolved the
> >>internet connectivity problem, but I still cannot connect to the Cisco
> >>VPN.
> >>The authentication window displays and I can enter my user/password, but
> >>the
> >>connection never completes. The error is "the virtual adapter failed to
> >>enable". I've tried changing my Adapter 1 to my host's network adapter,
> >>but
> >>then I cannot access the internet and the Cisco VPN authentication window
> >>never pops up.
> >>
> >>Any help would be appreciated. Thanks.
> >
> > Can't be done...
> > First you cannot use Shared Networking for tis.
> > Second Cisco VPN is very picky on the networks when it connects and
> > basically shuts down all networks other than its own VPN one.
> >
> > I don't hink it can even be done if you have a properly configured
> > network for the guest (using the host NIC instead of Shared
> > networking).
> >
> > What I know works is to connect a Microsoft VPN tunnel from a guest
> > using PPTP protocol, but ten PPTP does not sut down other
> > networking....
> >
>
> Post directed at the OP:
>
> I'm using Cisco VPN running on a WinServer2003 VPC running over Vista
> Ultimate. Connects fine. The VPC is set to use the host's NIC, it pulls a
> DHCP address of it's own from my router. All is well, internet access is
> still there with the VPN active. In the VPN client, on the Transport tab I
> do have "Allow local LAN Access" checked. I have not tried to see what
> happens if it's un-checked, I've always used it this way with no problems.
>
> I'd troubleshoot the problem with the VPC's internet access first, without
> trying to use the VPN Client. After that is resolved then troublehsoot any
> leftover VPN problem, possibly ignoring the fact that it is on a VPC, at
> least to begin with.
>
> Reinstalling the VPN client or using a newer version might resolve the
> problem. I'm using 4.0.5.
>
> John
>
>
>

>
> "Bo Berglund" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> On Thu, 17 Jul 2008 14:27:00 -0700, Lynne
>> <(email address - cut out)> wrote:
>>
>>>I'm new to the VPC world and I don't have much networking experience. My
>>>host machine is Windows XP Pro/SP2 and my guest is Windows Server 2003.
>>>Initially I was unable to connect to the internet on the guest, but
>>>resolved
>>>the problem by changing the networking Adapter 1 to Shared networking
>>>(NAT)
>>>and hardcoding the DNS on the guest to 192.168.131.254. This resolved
>>>the
>>>internet connectivity problem, but I still cannot connect to the Cisco
>>>VPN.
>>>The authentication window displays and I can enter my user/password, but
>>>the
>>>connection never completes. The error is "the virtual adapter failed to
>>>enable". I've tried changing my Adapter 1 to my host's network adapter,
>>>but
>>>then I cannot access the internet and the Cisco VPN authentication window
>>>never pops up.
>>>
>>>Any help would be appreciated. Thanks.
>>
>> Can't be done...
>> First you cannot use Shared Networking for tis.
>> Second Cisco VPN is very picky on the networks when it connects and
>> basically shuts down all networks other than its own VPN one.
>>
>> I don't hink it can even be done if you have a properly configured
>> network for the guest (using the host NIC instead of Shared
>> networking).
>>
>> What I know works is to connect a Microsoft VPN tunnel from a guest
>> using PPTP protocol, but ten PPTP does not sut down other
>> networking....
>>
>
> Post directed at the OP:
>
> I'm using Cisco VPN running on a WinServer2003 VPC running over Vista
> Ultimate. Connects fine. The VPC is set to use the host's NIC, it pulls
> a DHCP address of it's own from my router. All is well, internet access
> is still there with the VPN active. In the VPN client, on the Transport
> tab I do have "Allow local LAN Access" checked. I have not tried to see
> what happens if it's un-checked, I've always used it this way with no
> problems.
>
> I'd troubleshoot the problem with the VPC's internet access first, without
> trying to use the VPN Client. After that is resolved then troublehsoot
> any leftover VPN problem, possibly ignoring the fact that it is on a VPC,
> at least to begin with.
>
> Reinstalling the VPN client or using a newer version might resolve the
> problem. I'm using 4.0.5.
>
> John
>
>

>
>"Bo Berglund" <(email address - cut out)> wrote in message
>news:(email address - cut out)...
>> On Thu, 17 Jul 2008 14:27:00 -0700, Lynne
>> <(email address - cut out)> wrote:
>>
>>>I'm new to the VPC world and I don't have much networking experience. My
>>>host machine is Windows XP Pro/SP2 and my guest is Windows Server 2003.
>>>Initially I was unable to connect to the internet on the guest, but
>>>resolved
>>>the problem by changing the networking Adapter 1 to Shared networking
>>>(NAT)
>>>and hardcoding the DNS on the guest to 192.168.131.254. This resolved the
>>>internet connectivity problem, but I still cannot connect to the Cisco
>>>VPN.
>>>The authentication window displays and I can enter my user/password, but
>>>the
>>>connection never completes. The error is "the virtual adapter failed to
>>>enable". I've tried changing my Adapter 1 to my host's network adapter,
>>>but
>>>then I cannot access the internet and the Cisco VPN authentication window
>>>never pops up.
>>>
>>>Any help would be appreciated. Thanks.
>>
>> Can't be done...
>> First you cannot use Shared Networking for tis.
>> Second Cisco VPN is very picky on the networks when it connects and
>> basically shuts down all networks other than its own VPN one.
>>
>> I don't hink it can even be done if you have a properly configured
>> network for the guest (using the host NIC instead of Shared
>> networking).
>>
>> What I know works is to connect a Microsoft VPN tunnel from a guest
>> using PPTP protocol, but ten PPTP does not sut down other
>> networking....
>>
>
>Post directed at the OP:
>
>I'm using Cisco VPN running on a WinServer2003 VPC running over Vista
>Ultimate. Connects fine. The VPC is set to use the host's NIC, it pulls a
>DHCP address of it's own from my router. All is well, internet access is
>still there with the VPN active. In the VPN client, on the Transport tab I
>do have "Allow local LAN Access" checked. I have not tried to see what
>happens if it's un-checked, I've always used it this way with no problems.
>
>I'd troubleshoot the problem with the VPC's internet access first, without
>trying to use the VPN Client. After that is resolved then troublehsoot any
>leftover VPN problem, possibly ignoring the fact that it is on a VPC, at
>least to begin with.
>
>Reinstalling the VPN client or using a newer version might resolve the
>problem. I'm using 4.0.5.
>

>
>
> "Lynne" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> It definitely can be done because I have co-workers who are successful
>> with
>> it. We've compared configurations and the only difference is our ISP.
>> I've
>> changed from Shared networking (NAT) to using my host's NIC and this
>> makes it
>> worse - I can't connect to the internet or to the VPN. I already tried
>> re-installing the VPN client to no avail and I am running Cisco 5.0.02.
>> Any
>> other thoughts from anyone? Thanks for the help.
>>
> Your situation is quite different from John Sheridan's. His host machine
> is on a local LAN and the vm gets its network config from a local DHCP
> server when he uses the physical NIC option for his vm.
>
> If you are connecting directly to your ISP this will not work. Your host
> has already connected to the ISP and established an Internet connection
> (and received an IP from the ISP's DHCP server). The ISP will not issue an
> additional public IP for your vm automatically. You may be able to
> persuade them to do that for an additional fee!
>
> Using the shared networking (NAT) option allows you to connect to the
> Internet by sharing the host's Internet connection. The vm gets a private
> IP address from the mini-DHCP server (similar to the situation with ICS).
> Obviously the Cisco VPN client isn't happy running over this connection.
>
>

> It definitely can be done because I have co-workers who are successful
> with
> it. We've compared configurations and the only difference is our ISP.
> I've
> changed from Shared networking (NAT) to using my host's NIC and this makes
> it
> worse - I can't connect to the internet or to the VPN. I already tried
> re-installing the VPN client to no avail and I am running Cisco 5.0.02.
> Any
> other thoughts from anyone? Thanks for the help.
>

>
> "Bill Grant" <not.available@online> wrote in message
> news:(email address - cut out)...
> >
> >
> > "Lynne" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> >> It definitely can be done because I have co-workers who are successful
> >> with
> >> it. We've compared configurations and the only difference is our ISP.
> >> I've
> >> changed from Shared networking (NAT) to using my host's NIC and this
> >> makes it
> >> worse - I can't connect to the internet or to the VPN. I already tried
> >> re-installing the VPN client to no avail and I am running Cisco 5.0.02.
> >> Any
> >> other thoughts from anyone? Thanks for the help.
> >>
> > Your situation is quite different from John Sheridan's. His host machine
> > is on a local LAN and the vm gets its network config from a local DHCP
> > server when he uses the physical NIC option for his vm.
> >
> > If you are connecting directly to your ISP this will not work. Your host
> > has already connected to the ISP and established an Internet connection
> > (and received an IP from the ISP's DHCP server). The ISP will not issue an
> > additional public IP for your vm automatically. You may be able to
> > persuade them to do that for an additional fee!
> >
> > Using the shared networking (NAT) option allows you to connect to the
> > Internet by sharing the host's Internet connection. The vm gets a private
> > IP address from the mini-DHCP server (similar to the situation with ICS).
> > Obviously the Cisco VPN client isn't happy running over this connection.
> >
> >
>
> Googling "Cisco VPN" and "ICS" brings up many, many hits with the word
> "incompatible" in the preview. I'd say it's a safe bet Cisco VPN won't work
> with ICS.
>
> The solution would be to get a router, which isn't worth it if you only have
> one physical PC, or a second address from the ISP.
>
> BTW, Lynne, who is your ISP, and is it cable or DSL?
>
> John
>
>
>

> On Sun, 20 Jul 2008 06:38:01 -0700, Lynne
> <(email address - cut out)> wrote:
>
> >My ISP is Qwest and it is DSL. The device they have provided, which I refer
> >to as a router, does allow multiple devices to be connected and I do have
> >multiple PCs connected to it. The VPC connection is picking up a new IP
> >address, so it seems to me it should work without buying additional hardware.
> >
> >Lynne
>
> Which IP address do you get in the host and guest respectively?
>
>

>My ISP is Qwest and it is DSL. The device they have provided, which I refer
>to as a router, does allow multiple devices to be connected and I do have
>multiple PCs connected to it. The VPC connection is picking up a new IP
>address, so it seems to me it should work without buying additional hardware.
>
>Lynne

>> >My ISP is Qwest and it is DSL. The device they have provided, which I refer
>> >to as a router, does allow multiple devices to be connected and I do have
>> >multiple PCs connected to it. The VPC connection is picking up a new IP
>> >address, so it seems to me it should work without buying additional hardware.
>> >
>> >Lynne
>>
>> Which IP address do you get in the host and guest respectively?
>>
>My host ipconfig is as follows:
>
>IP Address: 192.168.0.204
>Subnet Mask: 255.255.255.0
>Default Gateway: 192.168.0.1
>
>My guest ipconfig is as follows:
>
>IP Address: 192.168.0.205
>Subnet Mask: 255.255.255.0
>Default Gateway: 192.168.0.1
>