From: Allen Mulvey <allen@amulvey.com>
To: "piclist@mit.edu" <piclist@mit.edu>
Sender: "piclist-bounces@mit.edu" <piclist-bounces@mit.edu>
Date: Tue, 10 Aug 2021 06:10:46 -0700
Subject: Re: [OT] Windows 10 Networking Change
Thread-Topic: [OT] Windows 10 Networking Change
Thread-Index: AdeN6tBwhshgO+KgSB6yM6+aDAOoDg==
Message-ID: <87d1410b-8f19-b8c2-29d6-5422d5ad9b08@amulvey.com>
References: <95c60a46-382b-89d9-7462-dbcffb93c376@amulvey.com>
	<CACZQxzNsX1+fwSgRWpSp06i+CbyjUyApGJhat_yKY23_2L9HCQ@mail.gmail.com>
	<ac8f64d3-596d-285d-5765-9069ad322e0e@amulvey.com>
In-Reply-To: <ac8f64d3-596d-285d-5765-9069ad322e0e@amulvey.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=z9OxFeG09pXQVep432tU+mU3wseO5C0C7boj/qApWCs=;
	b=uSGhSjrUZ+v0mc7apd4YPh3J3NZDW72YKZP/eJnTxlFMdyhIbkR5l7KSvyqL3xmia
	DH6cxtxcxi9VLLp+mV1RbqbTy7QnbuZDPudx1fgTayvb6kGtF1TPmE61+3jSj938VNR
	jLF9cTS5LxLpZDuT+4CkvwfXrF6STvZcs6+tfQE=;
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

I tried switching to copper. It did not work. It appears to be something=20
in Windows not the adapter.

Thanks,
Allen

On 8/10/2021 12:03 AM, Allen Mulvey wrote:
> I'll look into this. Several years ago I was using Mellanox ConnectX-2
> cards and an update broke them. Right after I bought Mellanox ConnectX-3
> cards they fixed the problem. Maybe I'll see if it works over copper.
>
> Thanks,
> Allen
>
> On 8/9/2021 10:59 PM, RussellMc wrote:
>> On Tue, 10 Aug 2021 at 13:41, Allen Mulvey <allen@amulvey.com> 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.
>>>
>> There was a change in Win10 earlier this year which "broke" many WIN
>> systems running on old network hardware.
>> As usual in such case uSoft did not issue a statement about this or any
>> form of 'apology'.
>> What they did do was to make a change in the update rollout that said ~~
>> "This update is not suitable for your system - you will be notified when
>> the update can be installed."
>>
>> After a while an updated update was supplied.
>> Systems that had had the update attempted remained broken. The internet
>> networking did not work (at all in the systems that I saw as far as I
>> knew).
>> I tried to fix one without success and then found that installing a newe=
r
>> network card worked - in this case I added a USB interfaced card which
>> "just worked".
>>
>> I'd suggest that there is  a reasonable likelihood that you are in this
>> position.
>> If so either a trial with new hardware (external USB easy) or manually
>> adding a more recent update may help. Or not.
>>
>> It's even p[ossible that a system updated via a temporary new network ca=
rd
>> will then work on the old card.
>>
>> I'd be interested to hear if this works.
>>
>>
>>    Russell

--=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
.