From: Allen Mulvey <allen@amulvey.com>
To: "piclist@mit.edu" <piclist@mit.edu>
Sender: "piclist-bounces@mit.edu" <piclist-bounces@mit.edu>
Date: Wed, 11 Aug 2021 05:33:06 -0700
Subject: Re: [OT] Windows 10 Networking Change
Thread-Topic: [OT] Windows 10 Networking Change
Thread-Index: AdeOrlw8ITxgsx7LSHu/7hIJhPHD/A==
Message-ID: <ced95046-2812-a47d-d644-ef4c03ac9f78@amulvey.com>
References: <95c60a46-382b-89d9-7462-dbcffb93c376@amulvey.com>
	<38a46305-bfcc-4807-3c87-983fa72aaf19@asamicros.com>
In-Reply-To: <38a46305-bfcc-4807-3c87-983fa72aaf19@asamicros.com>
Reply-To: Microcontroller discussion list - Public. <piclist@mit.edu>
Accept-Language: en-US
Content-Language: en-US
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=subject:to:references:from:message-id:date:mime-version:in-reply-to:content-type;
	d=amulvey.com; s=amulvey; a=rsa-sha256;
	bh=yxy8qNyvm2mGgCuAcagYWRyWRMAlc7uSY2F1atFVXnI=;
	b=VmLmXmHrosNpscR0CxfcZw81/jKK9HVi8HXs2F1FoH4yZMhes2j5SNJWOB/yRTp9+
	NxxJIW2lc3vBtFaIMpjJM/iumDES0sKjsb7jyBiOi5GSTzs5purKqI4oJPE5YttNjGq
	+JZ1KAIhytLRVjwzXHx8Lje9pUJkWamkCabLlUE=;
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." <piclist.mit.edu>
list-post: <mailto:piclist@mit.edu>
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

Andy,

I got this earlier and responded with another reply as it did not have a=20
"reply list" option. Apparently it came to me offline. I tried disabling=20
IPV6. It did not work.

My success yesterday seems to have been premature. Shortly after it=20
stopped working again.

Allen

On 8/11/2021 4:28 AM, Info2004 wrote:
> 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
> Windows updates. I could ping the NAS, just not connect to it. After a
> quick sniff on the net, I disabled the IPv6 interface on the network
> adapter, so forcing IPv4 for that interface. Happy as Larry now. My NAS
> is old and does not support IPv6, and Windows was appearing to use it
> 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).
>>
>> 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
>>

--=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
.