"mount_smbfs" fails after update to Windows 10 Fall Creators Update and Windows Server, version 1709

[Carmel NY]

Microsoft removed SMB1 support from their Windows 10 Fall Creators Update and
Windows Server, version 1709.

https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-windows-10-and-windows-server-version-1709

"Samba" shares no longer show up in the MS Network, although they can be
reached by typing in the address, "\\Bios-Name" in the address bar. I have
found a workaround for that however.

My problem now is that the "mount_smbfs" command no longer functions. I assume
it is trying to use the "SMB1" protocol, although I am not positive. I don't
see anyway to force it to use either "SMB2" or "SMB3" instead, if that is in
fact the problem.

-- 
Carmel

-- 
Carmel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20171218/8abb43a1/attachment.sig>