You can take NAT device as "one-way router" (it is somewhat more complicated NAT device changes/translates ip addresses in datagrams while transferring them from/to NAT segment) it allows to create tcp connections (or transfer udp requests/responses) from NAT segment to Bridged, but not vice versa (ip adresses at NAT segment are inaccessible from outside). So you need Bridged networking so the VM's act like physical machines with genuine IP addresses in your network.Īll what I said in post #3 is tested/used many times by me.īridged and NAT "networks" are in fact two network segments connected by NAT device - in this case by Vmware Host. If you use (at least in VMWare) NAT networking the VM's can access the external internet but won't be able to access other things on your network by virtue of the fact that the VM's will have a "virtual" IP address. Note Users on VM's don't need to have an account on the main HOST machine. Note also you'll need to enable SMB1 on the Windows 10 machines and of course on the sharing give permissions to users who has access. While it is easy to set host folders to be shared with the VM, how to share folders between VMs?ġ) use BRIDGED Networking on all the VM's.Ģ) then just make folders on the VM's shareableģ) then just use file explorer->net to browse the VM'sĤ) on the relevant VM's just from file explorer from within a VM just "connect network drive" which can then be any drives on visible machines on your LAN - ensure network discovery is also enabled on the VM's as well.
I need to run a CMD command in a VM that would need the access of Windows folder from another VM.
0 kommentar(er)
