Hi @X3nO , You can add the sharing via Shared Folder by the following steps: 1.Install VMware Tools(It may require GOS restart after the installation). 2.Open VM settings via Virtual Machine menu ...
See more...
Hi @X3nO , You can add the sharing via Shared Folder by the following steps: 1.Install VMware Tools(It may require GOS restart after the installation). 2.Open VM settings via Virtual Machine menu 3.Click Sharing and then '+' button 4.Find the Disk(Files) you want to share and select it. 5.Access the files in VM via 'Open in Guest' button on sharing window or 'VMware Shared Folders' shortcut on the VM Desktop.
Hi @MBnl Could you check SMB is enabled in your Windows 10 VM? https://docs.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3
Hi @snobis The dhcpd.config is not used on Big Sur, the IP address range is declared in nat.conf. VMs will get new IP address assigned by DHCP server. Could your try to disconnect and reconnect the ...
See more...
Hi @snobis The dhcpd.config is not used on Big Sur, the IP address range is declared in nat.conf. VMs will get new IP address assigned by DHCP server. Could your try to disconnect and reconnect the network adapter of your VM?
Hi @dmpm , The IP range for VMs has been changed on Big Sur. You may need to reset the IP range. Here's a link for your references:https://kb.vmware.com/s/article/80793. Hope it could help.
Hi @bauern , The IP range for VMs has been changed on Big Sur, this could be get in /Library/Preferences/VMware Fusion/vmnet8/nat.conf, Could you try to reassign the IP in your AD server and check...
See more...
Hi @bauern , The IP range for VMs has been changed on Big Sur, this could be get in /Library/Preferences/VMware Fusion/vmnet8/nat.conf, Could you try to reassign the IP in your AD server and check if that could resolve your issue? Here's a link for your reference: https://kb.vmware.com/s/article/80793 Hope that could help.
Hi @bricbaker , On Big Sur host, a built-in dhcp sever will be used instead of vmware dhcp server. So 'vmnet-cli' is telling 'DHCP service on vmnetX is not running'.
Hi @a_calo , On Big Sur host, the virtual network adapter will be created when you powered on VM which is set to use NAT network, and it will be named as bridge10X instead of vmnet8.
Hi @XuanXin1 , Did you access the on the Bid Sur host? There's some limitation on Big Sur. On Big Sur hosts, if user configures NAT port forwarding in Fusion, the service running in the virtual mac...
See more...
Hi @XuanXin1 , Did you access the on the Bid Sur host? There's some limitation on Big Sur. On Big Sur hosts, if user configures NAT port forwarding in Fusion, the service running in the virtual machine is unavailable on the macOS host using localhost:exposedPort, hostIP:exposedPort, or 127.0.0.1:exposedPort; Port forwarding is also not accessible inside a NAT virtual machine using hostIP:exposedPort. Workaround: Access the NAT port forwarding through another physical machine with Windows or macOS; or access the NAT port forwarding from a bridged virtual machine running on the same Mac machine as the NAT virtual machine. Here's a link for your reference: https://docs.vmware.com/en/VMware-Fusion/12/rn/VMware-Fusion-12-Release-Notes.html#knownissues
Hi @msikscurloc Do you mean your Catalina host gets an IP from Fusion virtual network? What's the output of command 'cat /Library/Preferences/VMware Fusion/networking'?
Hi, Yes, there are a few differences on Big Sur host. 'X.X.X.1' will be used as the default gateway and dns for NAT VMs. But the default NAT network should work after upgrading if they were set to u...
See more...
Hi, Yes, there are a few differences on Big Sur host. 'X.X.X.1' will be used as the default gateway and dns for NAT VMs. But the default NAT network should work after upgrading if they were set to use DHCP(by using .1 as default gateway and dns).