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 18:50:47 -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 17A1ddpt006257; Mon, 9 Aug 2021 21:40:19 -0400 Received: from outgoing-exchange-5.mit.edu (OUTGOING-EXCHANGE-5.MIT.EDU [18.9.28.59]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 17A1dbt8006254 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Mon, 9 Aug 2021 21:39:38 -0400 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-5.mit.edu (8.14.7/8.12.4) with ESMTP id 17A1dbLS025252 for ; Mon, 9 Aug 2021 21:39:37 -0400 Received: from oc11exhyb1.exchange.mit.edu (18.9.1.60) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Mon, 9 Aug 2021 21:39:06 -0400 Received: from oc11exhyb7.exchange.mit.edu (18.9.1.112) by oc11exhyb1.exchange.mit.edu (18.9.1.60) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Mon, 9 Aug 2021 21:39:36 -0400 Received: from NAM12-BN8-obe.outbound.protection.outlook.com (104.47.55.177) by oc11exhyb7.exchange.mit.edu (18.9.1.112) with Microsoft SMTP Server (TLS) id 15.0.1497.23 via Frontend Transport; Mon, 9 Aug 2021 21:39:36 -0400 Received: from BN8PR07CA0030.namprd07.prod.outlook.com (2603:10b6:408:ac::43) by BN8PR01MB5412.prod.exchangelabs.com (2603:10b6:408:b3::17) 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 01:39:34 +0000 Received: from BN8NAM11FT022.eop-nam11.prod.protection.outlook.com (2603:10b6:408:ac:cafe::76) by BN8PR07CA0030.outlook.office365.com (2603:10b6:408:ac::43) 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 01:39:34 +0000 Received: from mulvey.us (24.169.71.174) by BN8NAM11FT022.mail.protection.outlook.com (10.13.176.112) 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 01:39:33 +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); Mon, 9 Aug 2021 21:39:31 -0400 From: Allen Mulvey To: PIC List Sender: "piclist-bounces@mit.edu" Date: Mon, 9 Aug 2021 18:39:31 -0700 Subject: [OT] Windows 10 Networking Change Thread-Topic: [OT] Windows 10 Networking Change Thread-Index: AdeNiiPo+MHkVVuFQMK2aHa8tWlFbg== Message-ID: <95c60a46-382b-89d9-7462-dbcffb93c376@amulvey.com> List-Help: List-Subscribe: , List-Unsubscribe: , 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: Pass 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=to:from:subject:message-id:date:mime-version:content-type; d=amulvey.com; s=amulvey; a=rsa-sha256; bh=zdKSRnOPDuIc2MKi/SZoF0sVM7shq1UcUW35FuHkdpo=; b=qwEvTD6jT4RpkG2KLP7QvWuNC+YLFbx8Bm6pZX4wFP/y4N/FF/B7asoCfv+JHkvtm XgHp8sCMkpPa/Fymb831fn2tm/5vpgiqwqhdavtLga2ZW+u6DbeFKI7T85dRCoeelEr 4zuqHMSCNEUioFR1nh5yFtlFoXGi3Krc59aMaAw=; 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 have an access control system for my home which uses a central=20 controller with Wiegand RFID scanner/keyboards at the access points. It=20 has worked well for many years. The software was made pre-Windows 10=20 but, until last April, it worked fine on Windows 10 Pro. It worked fine=20 on Windows 10 pro in April 2020. I did not have need to use it again=20 until about a month ago. Now it occasionally works on Windows 10 but=20 usually it does not, giving an error indicating that it cannot find the=20 controller boards. I have one for my house and one for my garage both=20 are connected to my local area network with fixed (reserved) IP=20 addresses. I can ping them but the software cannot connect. The=20 software, iCCard, works perfectly from a Windows 8 Pro virtual machine=20 (Hyper-V). Apparently something changed in the way Windows 10 handles networking or=20 in my network adapter driver. Does anyone have any idea what happened?=20 It is annoying to have to use a virtual machine just to run this=20 software. My network adapter is a Mellanox ConnectX-3 Ethernet (Fiber)=20 adapter. I looked at the advanced adapter settings in the VM and=20 compared them to my desktop. Nothing seems to influence this problem. Any help would be appreciated, Allen --=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 .