I'm using Pulse Secure Desktop Client, v9.1.12. I would like to share the vpn routing of my windows 10 pro host with an hyper-v VM running windows server 2012. After researching on the web, I've found lots of suggestions and guides about creating a NATted virtual switch.. and so I configured one. It comes down to three powershell commands:
New-VMSwitch -SwitchName “NATSwitch” -SwitchType Internal
New-NetIPAddress -IPAddress 192.168.0.1 -PrefixLength 24 -InterfaceAlias “vEthernet (NATSwitch)”
New-NetNAT -Name “NATNetwork” -InternalIPInterfaceAddressPrefix 192.168.0.0/24
After that, I configured my VM to use the NATNetwork switch, started the VM and set its network adapter with a static IP, subnet mask, gateway and DNS.
I can browse the internet just fine, but none of the sites that I should reach via VPN. Looks like it's being completely bypassed.. to be honest I'm far from a networking expert, my job is software developer, so I know very litte of this stuff and would greatly appreciate any help.
Thanks a lot,
that should be a configuration limitation of the server. it is possible for the vpn admin to disable the ability of vm clients to go over the vpn tunnel. i would recommend checking with them and opening a case with our support team.
that should be a configuration limitation of the server.
I'm sorry, I failed to mention the very important detail that VirtualBox works just fine.. really sorry about that, but then again I would exclude a server configuration as the reason.