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 19:57:20 -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 17A2lKsX014992; Mon, 9 Aug 2021 22:47:59 -0400 Received: from outgoing-exchange-1.mit.edu (OUTGOING-EXCHANGE-1.MIT.EDU [18.9.28.15]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 17A2lJkF014987 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Mon, 9 Aug 2021 22:47:19 -0400 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 17A2lJZ5009422 for ; Mon, 9 Aug 2021 22:47:19 -0400 Received: from w92exhyb3.exchange.mit.edu (18.7.71.73) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Mon, 9 Aug 2021 22:46:47 -0400 Received: from oc11exhyb3.exchange.mit.edu (18.9.1.99) by w92exhyb3.exchange.mit.edu (18.7.71.73) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Mon, 9 Aug 2021 22:47:18 -0400 Received: from NAM12-DM6-obe.outbound.protection.outlook.com (104.47.59.175) by oc11exhyb3.exchange.mit.edu (18.9.1.99) with Microsoft SMTP Server (TLS) id 15.0.1497.23 via Frontend Transport; Mon, 9 Aug 2021 22:47:18 -0400 Received: from DM6PR07CA0056.namprd07.prod.outlook.com (2603:10b6:5:74::33) by CH2PR01MB6104.prod.exchangelabs.com (2603:10b6:610:16::32) 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 02:47:17 +0000 Received: from DM6NAM11FT046.eop-nam11.prod.protection.outlook.com (2603:10b6:5:74:cafe::fd) by DM6PR07CA0056.outlook.office365.com (2603:10b6:5:74::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4394.17 via Frontend Transport; Tue, 10 Aug 2021 02:47:17 +0000 Received: from mail-pl1-f172.google.com (209.85.214.172) by DM6NAM11FT046.mail.protection.outlook.com (10.13.172.121) 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 02:47:17 +0000 Received: by mail-pl1-f172.google.com with SMTP id e19so5452663pla.10 for ; Mon, 09 Aug 2021 19:47:16 -0700 (PDT) From: Richard Prosser To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Mon, 9 Aug 2021 19:47:05 -0700 Subject: Re: [OT] Windows 10 Networking Change Thread-Topic: [OT] Windows 10 Networking Change Thread-Index: AdeNk3A6EluCBEZCQWqv/k4hgQMMFQ== Message-ID: 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 gmail.com designates 209.85.214.172 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.214.172; helo=mail-pl1-f172.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=JAufyZuzV6RoJWBMp+iIMChiDPYouR2BxYhMMnzcCHo=; b=L1sZmbr75SPkOxSY5MVNRB6bwL+qg4fGFIeG4tANZs9r8nU6EfL4kwT9mz8vwTaAYu 6rm5/+HT9qP4YPMagGEGSDZbOAcGjPX7XFXG6Z5axVydsP0NnXZL9aGsK7Gm9rVgxSP1 atS2vQ/VNa6cx6dGV91aVoR2eGwn2smU0ln60HsaHE6YzSzFCwRubGb81WFoVa//qf0n e71DUTU/hw/nMNzWnz46A/XR6ntxcfTDvqyoXbxqwnrr6Xh1ruaRNY982Q9oo00VSPz0 8XB3BfelCrdHqZKdsCD0z3lP6tmNeEXnJRDskS6gPcimt/fYG4e4gU2UogR/tAYjQdeR dsaQ== authentication-results: spf=pass (sender IP is 209.85.214.172) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=gmail.com; mit.edu; dmarc=pass action=none header.from=gmail.com; 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:7789:: with SMTP id v9mr30007974pjk.159.1628563636145; Mon, 09 Aug 2021 19:47:16 -0700 (PDT) x-topics: [OT] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Can you just assign the software to "Compatibily Mode" for windows 7 or 8? Is there an updated driver from Wiegand or whoever? RP 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. 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 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .