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; Tue, 10 Aug 2021 11:05:06 -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 17AHvNMP027238; Tue, 10 Aug 2021 13:57:25 -0400 Received: from outgoing-exchange-3.mit.edu (OUTGOING-EXCHANGE-3.MIT.EDU [18.9.28.13]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 17AHvMVa027233 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Tue, 10 Aug 2021 13:57:22 -0400 Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) by outgoing-exchange-3.mit.edu (8.14.7/8.12.4) with ESMTP id 17AHuOPr022306 for ; Tue, 10 Aug 2021 13:57:22 -0400 Received: from oc11exhyb8.exchange.mit.edu (18.9.1.113) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Tue, 10 Aug 2021 13:57:00 -0400 Received: from w92exhyb6.exchange.mit.edu (18.7.71.111) by oc11exhyb8.exchange.mit.edu (18.9.1.113) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Tue, 10 Aug 2021 13:56:45 -0400 Received: from NAM11-BN8-obe.outbound.protection.outlook.com (104.47.58.173) by w92exhyb6.exchange.mit.edu (18.7.71.111) with Microsoft SMTP Server (TLS) id 15.0.1497.23 via Frontend Transport; Tue, 10 Aug 2021 13:56:45 -0400 Received: from MWHPR14CA0056.namprd14.prod.outlook.com (2603:10b6:300:81::18) by DM5PR0101MB3180.prod.exchangelabs.com (2603:10b6:4:36::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4394.15; Tue, 10 Aug 2021 17:56:39 +0000 Received: from CO1NAM11FT005.eop-nam11.prod.protection.outlook.com (2603:10b6:300:81:cafe::f5) by MWHPR14CA0056.outlook.office365.com (2603:10b6:300:81::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4415.14 via Frontend Transport; Tue, 10 Aug 2021 17:56:39 +0000 Received: from mail-pl1-f180.google.com (209.85.214.180) by CO1NAM11FT005.mail.protection.outlook.com (10.13.174.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4394.16 via Frontend Transport; Tue, 10 Aug 2021 17:56:38 +0000 Received: by mail-pl1-f180.google.com with SMTP id a20so22331672plm.0 for ; Tue, 10 Aug 2021 10:56:38 -0700 (PDT) Received: from DAR5.planet.eon.net (d142-59-123-176.abhsia.telus.net. [142.59.123.176]) by smtp.gmail.com with ESMTPSA id 195sm3069081pfw.120.2021.08.10.10.56.37 for (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 10 Aug 2021 10:56:37 -0700 (PDT) From: Dwayne Reid To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Tue, 10 Aug 2021 10:56:36 -0700 Subject: Re: [OT] Windows 10 Networking Change Thread-Topic: [OT] Windows 10 Networking Change Thread-Index: AdeOEkBp++fIRYENQYua+1jai14B/w== Message-ID: <6112bdd5.1c69fb81.d8247.7028@mx.google.com> References: <95c60a46-382b-89d9-7462-dbcffb93c376@amulvey.com> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <95c60a46-382b-89d9-7462-dbcffb93c376@amulvey.com> Reply-To: Microcontroller discussion list - Public. Accept-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: Pass X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of planet.eon.net designates 209.85.214.180 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.214.180; helo=mail-pl1-f180.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=planet.eon.net; s=google; h=message-id:date:to:from:subject:in-reply-to:references:mime-version; bh=gCMXZbKv18ecjYgLpj78d4UuIyHFP5yVDPAwMaweDxc=; b=Id8IJldnI6msb25BqtZpTinJ9K+oxdsOlM/LV97q7IYgkiW61eDa/QpGS3Yr9Dv/jU mrOo5/6NNf2uWe6MtnIiA4M7VA6eE6Bev9Shejn3snQj7Ye1Sn1FyaOZtWotOvlE+grf uO9/4RhgqvalXoefl0PW66a8pGDb+99QgoKG86j8T/0A8GKBDJxDmXLbjLYGekv0Qo1H Jej+kr+2oi99M1gocN6v4QCt3dBLtERQEcL/BIa+pUAqCVXvcBF7csxi7PHxbVKr4qhg i0S4Aqbit7uq5p9h/igKge648Xp1pWpTFyNrfVjoX41URRK+sV8VEfoDXaWBSYsT3U3U ZVuQ== authentication-results: spf=pass (sender IP is 209.85.214.180) smtp.mailfrom=planet.eon.net; mit.edu; dkim=pass (signature was verified) header.d=planet.eon.net;mit.edu; dmarc=bestguesspass action=none header.from=planet.eon.net; 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-received: by 2002:a17:90a:3d0d:: with SMTP id h13mr33243252pjc.20.1628618198183; Tue, 10 Aug 2021 10:56:38 -0700 (PDT) x-topics: [OT] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Hi there, Allen. The latest edition of the newsletter "Ask Woody"=20 Plus version has something that may help. AskWoody Plus =96 18.30.0 =96 2021-08-09 =96 The sheriff in the inbox This is a copy / paste of part of the article: Freeware Spotlight three tools to make your printer print By Deanna McElveen The last few builds of Windows 10 have not played=20 well with LAN and Wi-Fi printers. It's not as if=20 our printers didn't have enough problems with just a USB connection. I spend a lot of time fixing customers' printing=20 issues and the networking issues caused by=20 Windows updates. It seems like half of what we do at our shop these days. How do we fix our printer woes on a tight budget?=20 Freeware to the rescue! You really can't do better than free. Our first free tool is one we discussed not too=20 long ago. But it has a secret weapon. Have your=20 computers and devices not been seeing each other=20 on your network? Is that one network printer that=20 has been an unwavering workhorse for years now=20 refusing to print? Let's fire that Complete=20 Internet Repair by Rizonesoft back up, and we'll=20 make simple work of a normally time-consuming=20 fix. Need to download it? Grab it from=20 OlderGeeks.com. I can copy more if you need but the above should get you started. I have no idea if this will help but I think that it shouldn't hurt. dwayne At 07:39 PM 8/9/2021, 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. I did not have need to use it again >until about a month ago. Now it occasionally works on Windows 10 but >usually it does not, giving an error indicating that it cannot find the >controller boards. I have one for my house and one for my garage both >are connected to my local area network with fixed (reserved) IP >addresses. I can ping them but the software cannot connect. The >software, iCCard, works perfectly from a Windows 8 Pro virtual machine >(Hyper-V). > >Apparently something changed in the way Windows 10 handles networking or >in my network adapter driver. Does anyone have any idea what happened? >It is annoying to have to use a virtual machine just to run this >software. My network adapter is a Mellanox ConnectX-3 Ethernet (Fiber) >adapter. I looked at the advanced adapter settings in the VM and >compared them to my desktop. Nothing seems to influence this problem. > >Any help would be appreciated, >Allen >-- >http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive >View/change your membership options at >http://mailman.mit.edu/mailman/listinfo/piclist --=20 Dwayne Reid Trinity Electronics Systems Ltd Edmonton, AB, CANADA 780-489-3199 voice 780-487-6397 fax 888-489-3199 Toll Free www.trinity-electronics.com Custom Electronics Design and Manufacturing --=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 .