SMB share not working with NAT on Windows 10 Enterprise

[rtripathi95051]

The Workstation Pro 16 is running Ubunti 20.04 in VM. Host OS is Windows 10 Enterprise.

I can access the SMB share from Ubuntu if VM's networking is bridged type. However I can't access when it's NAT type.

WorkStation 16 PRO 16.2.0 build-18760230

Edition Windows 10 Enterprise
Version 21H1
Installed on ‎2/‎27/‎2021
OS build 19043.1766
Experience Windows Feature Experience Pack 120.2212.4180.0

[rtripathi95051]

Reinstalled VmWare Workstation 16 Pro and selected repair. Rebooted PC but no improvement

[Technogeezer]

What system is providing the share?

What is the error you are getting - “not working” or “unable to access” doesn’t provide us enough information. 

Are you trying to access the share from the Ubuntu VM by host name or IP address?

[rtripathi95051]

The Ubuntu 20.04 running in VM has smbd installed and is providing the share. User ID and and PW is configured

Trying to access a Ubuntu shared folder via IP address from Windows

\\192.168.233.128

A windows pops up and authentication fails if VM networking is NAT.

If Networking is changed to bridged then everything works fine.

I can ping from Windows console to 192.168.233.128 with NAT 

[rtripathi95051]

[Technogeezer]

Have you examined the Samba logs for smbd to see what information it might contain? 

[bluefirestorm]

It is likely an issue with the Windows 10 firewall not allowing SMB traffic. As the NAT adapter of the Windows 10 host is VMnet8, its default network profile is "Public". SMB traffic is not enabled for Public network profile by default.

Try enabling the following predefined rules with Public profile in the Windows Firewall advanced settings.

File and Printer Sharing (NB-Datagram-In)
File and Printer Sharing (NB-Name-In)
File and Printer Sharing (NB-Session-In)
File and Printer Sharing (SMB-In)
File and Printer Sharing (NB-Datagram-Out)
File and Printer Sharing (NB-Name-Out)
File and Printer Sharing (NB-Session-Out)
File and Printer Sharing (SMB-Out)

The predefined rules has the appropriate ports already set for SMB traffic. To be extra cautious, you can limit the IP addresses to the VMnet8 subnet in the Scope tab for the remote IP address (in your case 192.168.233.0/24).

[rtripathi95051]

Thanks for your reply but I'm not sure where to enter the settings you suggested. I see this on Firewall advanced settings. 

Another window that allows some settings change is

[Technogeezer]

According to what you posted, you are running a SentinelOne Firewall, not Windows Defender. You will need to check that firewall’s settings. 

[rtripathi95051]

Yes, It's company managed Laptop. Looks like I'll have to deal with IT about it.
Thanks a Lot! for your help.