I can't find what caused it, so need your help,thanks a lot. A disaster recovery solution for vSphere VMs that auto. ESXI inside network topology is as below, and promiscuous mode of virtual switch is enabled. The universal distributed logical router (UDLR) in NSX-V is optimized for forwarding in. But it is really strange that on PM1 use RDP connect to VM by 10.61.53.2 is OK, but remote print service can't use. Structer of the network is as below, PM1 is a Physical Machine outside the router subnet, PM2 is a. The server connect to a router with some computers,but some competers not directly connect to the router.
#Tor router vm esxi 6.5 windows 10
MAN can be normally accessed by 10.61.53.4 even from PM1. Our lab server make a ESXI server these days, one of VM installed windows 10 and shared a usb printer on it. When ping VM by 10.61.53.2, it always returns time out, even ping from itself. Usable Network and Disk interfaces on various hypervisors: ESX: Network: vmxnet3.
The whole network seems ok,but don't work well.Connection between PM1 PM2 and MAN all ok, but connection with VM not work well. VMWare Fusion 7 and 8 on OS X VMWare ESXi 6.5 Qemu 2.4.0.1 on Linux and OS X Hyper-V on Windows Server 2008r2, 2012 and Windows 10 (Only Generation 1 Hyper-V virtual machine is supported at the moment) Xen Project 4.6.5 Xen Server 7.1 Warning: Hypervisors that provide paravirtualization are not supported.
Structer of the network is as below, PM1 is a Physical Machine outside the router subnet, PM2 is a physical machine inside the router subnet,VM means the virtual machine with windows 10 and the printer, MAN means the ESXI management page.All the NATs are DMZ forwarding. Our lab server make a ESXI server these days, one of VM installed windows 10 and shared a usb printer on it.