Okay, I work remotely two days a week. Starting about a month ago something changed just for me. I have worked with other people on my team that can still print remotely while on VPN with no problems. Currently, when on the corporate network using a VM Workstation image (Windows Server 2012r2 Standard) I am able to print all day to network printers. However, when I go home and still need to print to a network printer I am unable to print to them.
Current settings:
Preferences \ Default hardware compatibility: Workstation 12.x
Virtual Network Editor:
Name: Type: External Connection: Host Connection: DHCP: Subnet Address:
VMNet0: Bridged Auto-bridging - - -
Automatic Settings: Checked 'Intel(r) Ethernet Connection...', 'Bluetooth Device...', and 'PANGP virtual Ethernet...'
VMNet1 Host-Only - Connected Enabled 192.168.130.0
Connect a host virtual adapter to this network | Host virtual adapter name: VMware Network Adapter VMnet1
Use local DHCP service to distribute IP address to VMs
DHCP Settings | Starting IP Address: 192.168.130.128
DHCP Settings | Ending IP Address: 192.168.130.254
DHCP Settings | Broadcast Address: 192.168.130.255
DHCP Settings | Default lease time : 0.0.30
DHCP Settings | Max lease time: 0.2.0
Subnet IP: 192.168.130.0 Subnet mask: 255.255.255.0
VMNet8 NAT NAT Connected - 192.168.233.0
Connect a host virtual adapter to this network | Host virtual adapter name: VMware Network Adapter VMnet8
NAT Settings | Gateway IP: 192.168.233.2
NAT Settings | Advanced | Allow Active FTP
NAT Settings | Advanced | Allow any Organizational Unique Identifier
NAT Settings | Advanced | UDP timeout (in seconds): 30
NAT Settings | Advanced | Config Port: 0
Subnet IP: 192.168.133.0 Subnet mask: 255.255.255.0
Using Global Protect VPN
The Global Protect VPN is setup on your windows server 2012r2 VM or on your host system? And your VM worked under bridge mode or nat mode, is that fine to ping the ip of your network printer?