In searching online I've seen several posts on various sites that recommend adding a second network adapter to the VM, using bridged mode, or paravirtualized mode, or host-only mode. I'm thinking it's a DNS issue, but I'm honestly not much of a networking guy and am not quite sure how to approach the problem. The internet connection tunnels through, but there are certain domains that are inaccessible from within the guest OS. Running the VPN on the host (with the VirtualBox network set to NAT mode) works. Then when I go to connect, it contacts the server just fine, accepts my AD login info and RSA token, but then ultimately fails to create the VPN connection. The GP installer throws an unsigned driver error on installation, and even if I say to install the driver anyway, it looks like it's failing to create the PANGP network interface in the guest OS. However, if I try to install it inside the VM on Win7, it never works. When I go to install GlobalProtect, it installs fine on the Windows 10 Host. Our PCs run Windows 10 natively, and then we use VirtualBox to run Windows 7 VMs to support some legacy software. One of my clients has recently switched their VPN setup from Checkpoint over to GlobalProtect, and it's completely broken our Virtualbox setup.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |