From owner-freebsd-questions@freebsd.org Mon Dec 18 16:13:21 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81964E96F43 for ; Mon, 18 Dec 2017 16:13:21 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-oln040092004080.outbound.protection.outlook.com [40.92.4.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 22CC419E7 for ; Mon, 18 Dec 2017 16:13:20 +0000 (UTC) (envelope-from carmel_ny@outlook.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=BmI6bVeIy+EdHDOqI4KUNr8foDQ03+T1+e2qlEElxuc=; b=anxJ6gkwNBV32bn4zMjYBG+vYmZcYR3YRZnIrKCgIRXElOvs4mgMEK/xCfa0KOxNZYNsVH/xkgxyE/l7tbfqXc3/CVX9Iqwn644RzcDuwbA/iKkuEZY/uSOMbWBKYytvqKsyX9gNlGGceRZXvMJt8iDPsd+G20rDE90QgQkzOLJkJaYKiDd6yUeid8AQUPwL/WgB/tJHgr6oKrBqk56cHzcUu7M+cykCzlwFWo4vJahvkiET4pF3KVQbdkgLTNzuwIvXbiAG5ueKgP16VvHZ28xv5hrhfUP0rt7VrtHK5KNxbJg9dQTiGlkn/JLyjoUU9UaV8QMHdDmfCbaXJrewAw== Received: from BL2NAM02FT059.eop-nam02.prod.protection.outlook.com (10.152.76.52) by BL2NAM02HT193.eop-nam02.prod.protection.outlook.com (10.152.77.133) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.302.6; Mon, 18 Dec 2017 16:13:18 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com (10.152.76.52) by BL2NAM02FT059.mail.protection.outlook.com (10.152.76.247) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.302.6 via Frontend Transport; Mon, 18 Dec 2017 16:13:18 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) by BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) with mapi id 15.20.0323.018; Mon, 18 Dec 2017 16:13:18 +0000 From: Carmel NY To: FreeBSD Subject: "mount_smbfs" fails after update to Windows 10 Fall Creators Update and Windows Server, version 1709 Thread-Topic: "mount_smbfs" fails after update to Windows 10 Fall Creators Update and Windows Server, version 1709 Thread-Index: AQHTeBsdPRuHfTcA40OQIwHluYjuRg== Date: Mon, 18 Dec 2017 16:13:18 +0000 Message-ID: Reply-To: FreeBSD Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:C95E6C00F1ADE339647A08D5FF9654DD51FBF142316579CD50334DA2E5773AE0; UpperCasedChecksum:705C9115A88CA99D05905E0F3582C630542BA5F3C02AEBDF4EC3ACC0458ECBE5; SizeAsReceived:7027; Count:45 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [7yK/DRNl6M9PIKHH9I2KE2mh0R+3DjDg] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; BL2NAM02HT193; 6:eyR7OQgcNn/pkj6wUaQQINzhGArSP1oODc4SmTOyupz6fPeqP1FMjwzCi8FHS+Ok8CDoUIrj4UxsTrEaF2JGThMuEL0xGs/naIj9jFcRnCqdQeRnQTA+rw3epGvY8cLLL9/6Y9YkSossW9pwQ9t9M4q2GecrasSDa8RfVsoLhOznmxn/2vQLvEkBB5Mm9R9DYyvPm3JUBWURSjDsdtvLuyCQc1urepw5JKJp47SLZ9PlNbub+CNxkrUY3SLMNVuFCeSFCNBTek/hX+LCnObO8PCWb7pUqh/3v71RPE5YXTPcEZNAAMm7K9Xtwv9JTkFu+gX33vriANSuOj1W12J0l+ErKWhVS0wLOqGfSjxOKvo=; 5:3fvXWMdEoFzJlKjRZDQSVjxphGUl6A9wR4u+e7dG5/L7FpOx5nNM83RxB50BflZId8zroZ4Yhiw82zbQicyNPpa7WTCs187l3yLmNS8Hp1ZFYxOOTVX347Ps+Q3U2j1yxhNbiBkfjP8a2YNIeSS4djfEf4z6l+W5yyrQ3U/LM+E=; 24:o/ViOvYNAqJllbkKqJQJy+v0KcDB4vITxgcQADDI1XjtRqaahyZm7iGYFF/3LihrF1qmyzsubR9GI9Y5FC5pZIrIRRzDaq4qi5FH6jU6uvs=; 7:EjBOTZ5KsH4h3M9uHVFuaH00q6tZ4uU+kFPt6ZC6SB/9PuO/wiBWd0EHsNZxe8cAli/uDNMUlo6cfQnMB3K+dZpV1PeL1zwslP3j1l4+B9X0aKipWX9nIww335hb/Z1lgRMmvRGA+Hn5GHR6aGYQLv6abLM7Gxdsq9pkvQYEVhomrrUHGlqKQHS2hChChIIwwwBUug5WwFTXHOCCeCbM/cHyeXhhRI+aKD4o7t0M3luvDXboKUyuIMS8g4cntuRA x-incomingheadercount: 45 x-eopattributedmessage: 0 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125374)(1603101448)(1701031045); SRVR:BL2NAM02HT193; x-ms-traffictypediagnostic: BL2NAM02HT193: x-ms-office365-filtering-correlation-id: 85cffc9a-446a-4487-e7d6-08d54632400d x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:BL2NAM02HT193; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:BL2NAM02HT193; x-forefront-prvs: 0525BB0ADF x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:BL2NAM02HT193; H:BN6PR2001MB1730.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/TEg6aqL4WUwXs1/FJOwzMX7"; protocol="application/pgp-signature" MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 85cffc9a-446a-4487-e7d6-08d54632400d X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Dec 2017 16:13:18.5380 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL2NAM02HT193 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 16:13:21 -0000 --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--