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; Wed, 11 Aug 2021 01:39:34 -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 17B8Swgg018818; Wed, 11 Aug 2021 04:29:43 -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 17B8StMl018815 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Wed, 11 Aug 2021 04:28:56 -0400 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 17B8SmI4004779 for ; Wed, 11 Aug 2021 04:28:55 -0400 Received: from oc11expo32.exchange.mit.edu (18.9.4.113) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Wed, 11 Aug 2021 04:28:52 -0400 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by oc11expo32.exchange.mit.edu (18.9.4.113) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Wed, 11 Aug 2021 04:28:53 -0400 Received: from NAM02-SN1-obe.outbound.protection.outlook.com (104.47.57.40) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1497.23 via Frontend Transport; Wed, 11 Aug 2021 04:28:53 -0400 Received: from DM5PR12CA0062.namprd12.prod.outlook.com (2603:10b6:3:103::24) by SN2PR01MB2207.prod.exchangelabs.com (2603:10b6:804:d::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4394.19; Wed, 11 Aug 2021 08:28:52 +0000 Received: from DM6NAM11FT033.eop-nam11.prod.protection.outlook.com (2603:10b6:3:103:cafe::db) by DM5PR12CA0062.outlook.office365.com (2603:10b6:3:103::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4415.13 via Frontend Transport; Wed, 11 Aug 2021 08:28:52 +0000 Received: from mout.kundenserver.de (217.72.192.73) by DM6NAM11FT033.mail.protection.outlook.com (10.13.172.221) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4415.14 via Frontend Transport; Wed, 11 Aug 2021 08:28:51 +0000 Received: from [192.168.1.191] ([212.159.71.94]) by mrelayeu.kundenserver.de (mreue108 [212.227.15.179]) with ESMTPSA (Nemesis) id 1N8ojI-1n9SyK1YMY-015sPI for ; Wed, 11 Aug 2021 10:28:50 +0200 From: Info2004 To: "piclist@mit.edu" Sender: "piclist-bounces@mit.edu" Date: Wed, 11 Aug 2021 01:28:49 -0700 Subject: Re: [OT] Windows 10 Networking Change Thread-Topic: [OT] Windows 10 Networking Change Thread-Index: AdeOjGm2Y6dJma5RQOucKFodRfYE7w== Message-ID: <38a46305-bfcc-4807-3c87-983fa72aaf19@asamicros.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 Content-Language: en-GB 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: None (protection.outlook.com: asamicros.com does not designate permitted sender hosts) dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitprod.onmicrosoft.com; s=selector2-mitprod-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=zkGQz2yWqnXx1iNVRPuDkJ7gUOIVYVN/wFCARIjH3lc=; b=F7xoneZkDiQQ0tJI+kEG52GYzTbsoG1QXuKLjl5Jea+oHlyBV/hdAF7rbVzQbuaQn266SFEGcoIQlIy+24Ue3jQ4eXgc4u4lMow+Ad19HjhP0WLUJvcKKWj2nZfoLGNztlNbo77Mo1VDn99Kevgw08uL6oscMlXSOeiSoYUuk4A= authentication-results: spf=none (sender IP is 217.72.192.73) smtp.mailfrom=asamicros.com; mit.edu; dkim=none (message not signed) header.d=none; mit.edu; dmarc=none action=none header.from=asamicros.com; user-agent: Mozilla/5.0 (X11; Linux x86_64; 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-provags-id: V03:K1:OHSvQRIGI4hw5OtqNSi9rPP4TTSDPPaaRTBFNyI+HWysiFnIm2L v480bWyl6/F4RMYb7gBoEz1jNPLNKrmFJ2INhkowv0GPvDTgme0YB20s+RQ5/H7hczltbDg QzFTengE5y2dkRelycsQME1SKvrcx56E+nf8BgUBC/7wloWKsla4PoPuOvy4pFTiETulGl/ C4l3h8Zb5ccmSPgrk40nw== x-spam-flag: NO x-topics: [OT] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Previous reply did not go to list, so here it is again: Hi, My Win 100 machine stopped connecting to my NAS - after one of the=20 Windows updates. I could ping the NAS, just not connect to it. After a=20 quick sniff on the net, I disabled the IPv6 interface on the network=20 adapter, so forcing IPv4 for that interface. Happy as Larry now. My NAS=20 is old and does not support IPv6, and Windows was appearing to use it=20 instead of IPv4, as it had done previous to the update. Hope it helps. ....Andy On 10/08/2021 02:39, 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). >=20 > 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. >=20 > Any help would be appreciated, > Allen >=20 --=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 .