I don't know how many of you might be using the product called VMWare, but I have stumbled across a very interesting way to use the GBVPN Client to set up a virtual PC that logs directly into a corporate domain.
If you set up your VPN Client and test it appropriately on your PC, then set up a VMWare VM client that is set to use the VMWare NAT interface (instead of the default Bridged interface) your VPN Client will kick in and route as if you were logging directly into the remote network. I have to do remote server support and from time to time it is nice to have a desktop system that is actually a member of the remote domain and logs in running scripts and everything. This seems to be a great way to do it and have the VM think that it is actually on the network (albeit a lot slower). The only drawback I have encountered is that if you walk away from the PC with the VM/VPN active the VPN Client time out problems still seem to occur. I was able to work around this by starting a "Ping -t remotehost" from inside the VM to keep the connection alive. Alternatively I have had to "Deactivate/Activate" the Security policy to restart the VPN. I have tested this with the latest VPN Client with a Windows XP Pro host environment. I have successfully tested this with Windows 9X and 2K/XP VMs. Not a support issue, but I thought some of you out there might find this interesting. For those of you who don't know about VMWare and are interested you can check it out at www.vmware.com. I don't know if this would work with other VM programs, but I assume if they offer a Virtual NAT interface it probably would. Bob Reasoner Harris County Public Health & Environmental Services --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] To subscribe to the digest version first unsubscribe, then e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archive of the last 1000 messages: http://www.mail-archive.com/[email protected]
