> I have read a lot of the posts using the Keywords Microsoft Loopback
> Adapter
> and they kind of answer my question which is what do I need to do to use a
> VPN connection to attach my virtual network to the corporate forests.
>
> I have resently moved to a remote site and my connection to the corp
> network
> is through a VPN. When I was connected physically to the Corp network I
> had
> access to all the forests that we have on the network.
>
> On the Host machine, a dell server with Windows Server 2003R2 sp2 on it, I
> can still access the resources on all the forests, but the VPC's have all
> lost that functionality. My network admin advised me to add a M. Loopback
> Adapter which I have done. I also have enabled ICS on the VPN Miniport
> for
> the MLA to use internet, which didn't work. I enable ICS on the physical
> network card and now the internet works on the VPC's.
>
> My problem is that I think I am getting too many parts (not enough parts?)
> to make this work. In other words, I'm confused. :(
>
> The functionality that I need is:
> 1.) to have the VPC (with the OS's of XPPro and WS2003/8) be available to
> the host
> via Remote Desktop Connection.
> 2.) To have the VPC's be able to use the internet (host always connected
> via
> a WRT54G router with an internal IP of 192.168.3.1).
> 3.) To have the VPC's be able to see the corporate forests and each other
> and the local host (yes it is part of one of the corporate forests)
>
> Sounds simple and probably is. Can anyone help?
>
> --
> Thanks, Marc

> No, it is not simple, but it might be possible. ICS (I would have used
> RRAS/NAT on a server) and a loopback adapter will let you share the host's
> Internet connection but it doesn't help with the VPN link, which is what you
> need to see the corporate network.
>
> Exactly what sort of VPN connection do you have? Is it configured as a
> site-to-site VPN link? Can all machines in your site see all machines on the
> corporate LAN?
>
> What you need to be able to do is route your virtual network to the
> corporate network through the VPN link. By default this doesn't happen.
>
> You probably can't do anything simply by making changes at your end of
> the connection. For the routing to work, the VPN server at the corporate end
> has to know the IP addresses of your local networks and have a route to send
> them through the VPN link. By default it will only have a route for your LAN
> network 192.168.3.0/24 . Even if you changed the routing at your end to send
> corporate traffic from the virtual network through the VPN, nothing would
> work because the VPN corporate router would not know how to route the
> traffic back through the VPN link.

> One thing though, the Host machine is visible on the Corp Network.
> --
> Thanks, Marc
>
>