After upgrade to Windows 10 Creators Update 1703 on the host, guests can no longer access host's network shares using SMB network protocol through host-only or NAT IPs.
[TLDR - steps to try to reproduce this -> Access local host network shares using IP address of the VMNet interfaces from either host or guest OS]
This was working ok on previous Win10 version 1607.
VMware Workstation version is 12.5.7 build-5813279 (upgraded from 12.5.6 after Win10 went from 1607 to 1703 few days ago)
After some troubleshooting, it appears that host server is not listening for incoming connections on ports 137,138 UDP and TCP 139 using IP addresses of the VMNet1 (host only) and VMNet8 (NAT) networks.
It's only listening on IP address of Ethernet/LAN/Physical interface.
Assuming 192.168.1.10 is host's Ethernet connection and 192.168.5.1 and 192.168.123.1 are host's VMNet1 and VMNet8 IP addresses respectively, trying to show network shares (either from host cmd prompt, or from guest gives the same result):
> net view \\192.168.1.10
shows host shares, while:
> net view \\192.168.5.1
gives error:
System error 53 has occurred.
The network path was not found.
Listing open (LISTEN) ports on the host is only showing binding to Ethernet IP address, and not VMNet* addresses
> netstat -an |findstr ":139"
TCP 192.168.1.10:139 0.0.0.0:0 LISTENING
Testing on another computer that still has not been upgraded to Creators Update and all is well there, host is listening for and accepting network traffic on Ethernet and on VMNet* IP addresses, and guests can access host's shares.
Things I have tried already:
- windows firewall on host appears to be configured correctly and ping host from guest is working
- checked that all 4 vmware autostart services are running
- restored defaults in Virtual Network Editor
- restarted win10 several times after installing latest workstation version
- disabled and enabled VMware Virtual Ethernet adapters several times
None of this has helped so far.
Has anyone else experienced something similar?
After upgrade to Windows 10 Creators Update 1703 on the host, guests can no longer access host's network shares using SMB network protocol through host-only or NAT IPs.
[TLDR - steps to try to reproduce this -> Access local host network shares using IP address of the VMNet interfaces from either host or guest OS]
This was working ok on previous Win10 version 1607.
VMware Workstation version is 12.5.7 build-5813279 (upgraded from 12.5.6 after Win10 went from 1607 to 1703 few days ago)
After some troubleshooting, it appears that host server is not listening for incoming connections on ports 137,138 UDP and TCP 139 using IP addresses of the VMNet1 (host only) and VMNet8 (NAT) networks.
It's only listening on IP address of Ethernet/LAN/Physical interface.
Assuming 192.168.1.10 is host's Ethernet connection and 192.168.5.1 and 192.168.123.1 are host's VMNet1 and VMNet8 IP addresses respectively, trying to show network shares (either from host cmd prompt, or from guest give same results):
> net view \\192.168.1.10
shows host shares, while:
> net view \\192.168.5.1
gives error:
System error 53 has occurred.
The network path was not found.
Listing open (LISTEN) ports on the host is only showing binding to Ethernet IP address
> netstat -an |findstr ":139"
TCP 192.168.1.10:139 0.0.0.0:0 LISTENING
Testing on another computer that still has not been upgraded to Creators Update and all is well there, host is listening for and accepting network traffic on Ethernet and on VMNet* IP addresses, and guests can access host's shares.
Things I have tried already:
- checked that all 4 vmware services are running
- restored defaults in Virtual Network Editor
- restarted win10 several times after installing latest workstation version
- disabled and enabled VMware Virtual Ethernet adapters several times
None of this has helped so far.
Has anyone else experienced something similar?