Date: Mon, 18 Dec 2017 16:13:18 +0000 From: Carmel NY <carmel_ny@outlook.com> To: FreeBSD <freebsd-questions@freebsd.org> Subject: "mount_smbfs" fails after update to Windows 10 Fall Creators Update and Windows Server, version 1709 Message-ID: <BN6PR2001MB1730B278E44CEB123FD0D651800E0@BN6PR2001MB1730.namprd20.prod.outlook.com>
next in thread | raw e-mail | index | archive | help
--Sig_/TEg6aqL4WUwXs1/FJOwzMX7 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Microsoft removed SMB1 support from their Windows 10 Fall Creators Update a= nd Windows Server, version 1709. https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-win= dows-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 ass= ume 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. --=20 Carmel --=20 Carmel --Sig_/TEg6aqL4WUwXs1/FJOwzMX7 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEh3rFs7ZCOM581rwKjsagALPkYOsFAlo36RoACgkQjsagALPk YOtvngf+NExSKYzQCXQdNQh1VQuI2UOySStZQiffmDuTPFJtZiLANN2SNy6fZrlz 07EqeapRMk3jcIrcae/Zo49XW5DkTKNM5ZkZcePI1pVMnYGI/jZd/gs2arZ++ev3 cZ5h3Fgp8hrozYUBwyGpCUaxpM7d0ySsgbkq/Iykqqz6/VMP1rYzaF4H4wVSHsUk oOTkfAVwoIObdX6iUnxTnYta3gmhkURoruvUXWEbvT3CO93BtC3ncjY4hicUOZYH /DyyENj8zhHKQA51IWwpBjJBVQijd4A5O/vqCHK6L3tFlKdhupKRjtdapFjWayuH gRBq1InmAJ22qVE9/QNeca+2t920pQ== =CL0/ -----END PGP SIGNATURE----- --Sig_/TEg6aqL4WUwXs1/FJOwzMX7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BN6PR2001MB1730B278E44CEB123FD0D651800E0>