Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Mon, 9 Aug 2021 21:12:43 -0700 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 17A43eh5024535; Tue, 10 Aug 2021 00:03:49 -0400 Received: from outgoing-exchange-7.mit.edu (OUTGOING-EXCHANGE-7.MIT.EDU [18.9.28.58]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 17A43cfC024532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Tue, 10 Aug 2021 00:03:39 -0400 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 17A43bVj000644 for ; Tue, 10 Aug 2021 00:03:38 -0400 Received: from oc11expo8.exchange.mit.edu (18.9.4.13) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Tue, 10 Aug 2021 00:03:06 -0400 Received: from w92exhyb3.exchange.mit.edu (18.7.71.73) by oc11expo8.exchange.mit.edu (18.9.4.13) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Tue, 10 Aug 2021 00:03:37 -0400 Received: from NAM04-MW2-obe.outbound.protection.outlook.com (104.47.73.176) by w92exhyb3.exchange.mit.edu (18.7.71.73) with Microsoft SMTP Server (TLS) id 15.0.1497.23 via Frontend Transport; Tue, 10 Aug 2021 00:03:37 -0400 Received: from CO1PR15CA0048.namprd15.prod.outlook.com (2603:10b6:101:1f::16) by BYAPR01MB4344.prod.exchangelabs.com (2603:10b6:a03:a0::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4394.21; Tue, 10 Aug 2021 04:03:35 +0000 Received: from CO1NAM11FT033.eop-nam11.prod.protection.outlook.com (2603:10b6:101:1f:cafe::c2) by CO1PR15CA0048.outlook.office365.com (2603:10b6:101:1f::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4394.15 via Frontend Transport; Tue, 10 Aug 2021 04:03:34 +0000 Received: from mulvey.us (24.169.71.174) by CO1NAM11FT033.mail.protection.outlook.com (10.13.174.247) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.4394.16 via Frontend Transport; Tue, 10 Aug 2021 04:03:34 +0000 Received: from [192.168.100.55] ([192.168.100.55]) by mulvey.us with MailEnable ESMTPSA (version=TLS1_2 cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256); Tue, 10 Aug 2021 00:03:31 -0400 From: Allen Mulvey To: "piclist@mit.edu" Sender: "piclist-bounces@mit.edu" Date: Mon, 9 Aug 2021 21:03:31 -0700 Subject: Re: [OT] Windows 10 Networking Change Thread-Topic: [OT] Windows 10 Networking Change Thread-Index: AdeNnffzX2l4AV2+SZ6UJdD/h4UBIQ== Message-ID: References: <95c60a46-382b-89d9-7462-dbcffb93c376@amulvey.com> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US Content-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-Exchange-Organization-SenderIdResult: TempError X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of amulvey.com designates 24.169.71.174 as permitted sender) receiver=protection.outlook.com; client-ip=24.169.71.174; helo=mulvey.us; dkim-signature: v=1; c=relaxed/relaxed; h=subject:to:references:from:message-id:date:mime-version:in-reply-to:content-type; d=amulvey.com; s=amulvey; a=rsa-sha256; bh=8KzHLH+2d5IT7b9DfZZHnUByMsa/cqP4/UW0ZMtpQw8=; b=qiVdv7OO7xdyzvq3m9+eA16kPr4PN460Fm/NAI/Xgnpsy5lVHnUwBLSiYIn+cYHMg BvfNS5wH7qGoPOPDAXMTu6PrXnty095AQdI6S4gdoJxCkRYCs1zyMl0fDPk9Zwx1WKN dJTDibEhPdJL2wUjM2H6rdQ4mQCc29nFIzvhe00=; authentication-results: spf=pass (sender IP is 24.169.71.174) smtp.mailfrom=amulvey.com; mit.edu; dkim=pass (signature was verified) header.d=amulvey.com;mit.edu; dmarc=bestguesspass action=none header.from=amulvey.com; user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-topics: [OT] x-content-filtered-by: Mailman/MimeDel 2.1.6 x-me-bayesian: 0.000000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 I'll look into this. Several years ago I was using Mellanox ConnectX-2=20 cards and an update broke them. Right after I bought Mellanox ConnectX-3=20 cards they fixed the problem. Maybe I'll see if it works over copper. Thanks, Allen On 8/9/2021 10:59 PM, RussellMc wrote: > On Tue, 10 Aug 2021 at 13:41, Allen Mulvey wrote: > >> I have an access control system for my home which uses a central >> controller with Wiegand RFID scanner/keyboards at the access points. It >> has worked well for many years. The software was made pre-Windows 10 >> but, until last April, it worked fine on Windows 10 Pro. It worked fine >> on Windows 10 pro in April 2020. >> > There was a change in Win10 earlier this year which "broke" many WIN > systems running on old network hardware. > As usual in such case uSoft did not issue a statement about this or any > form of 'apology'. > What they did do was to make a change in the update rollout that said ~~ > "This update is not suitable for your system - you will be notified when > the update can be installed." > > After a while an updated update was supplied. > Systems that had had the update attempted remained broken. The internet > networking did not work (at all in the systems that I saw as far as I > knew). > I tried to fix one without success and then found that installing a newer > network card worked - in this case I added a USB interfaced card which > "just worked". > > I'd suggest that there is a reasonable likelihood that you are in this > position. > If so either a trial with new hardware (external USB easy) or manually > adding a more recent update may help. Or not. > > It's even p[ossible that a system updated via a temporary new network car= d > will then work on the old card. > > I'd be interested to hear if this works. > > > Russell --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .