%TCPIP-E-INVINTER, error defining interface: WE0

All of the sudden, I started having a problem this morning. My virtual alpha lost the network connection. When I reboot I started seeing this error when TCPIP is starting:
%TCPIP-E-INVINTER, error defining interface: WE0

I moved the system disk to another machine and it works fine. So I know that the VMS side is OK. it must be something on the windows 10 side.

I noticed that when I boot up this is not appearing on the problem machine:
%EWA0, Twisted-Pair mode set by console
%EWA0, Link state: UP

I looked and I don't see any new updates that were done either by me or the system


I've disabled firewall/AV and there is no difference

At the console, I can see ewa0* and all the parameters match what is on my other system that is working.

I have both FreeAXP and Avanti - both have the same issue.

I have tried changing the network card, and all three do the same thins

If I do $ SHOW DEV EWA0 I do have this device and it shows offline.

I am stuck - any ideas?


Dave

other details:
Windows 10 Pro on both good and failing machine

version 2.6.4.598 for both FreeAXP and Avanti

Have you installed anything that uses WinPCAP 4.1.3? If so, try dropping back to WinPCAP 4.1.2.

Nope - no installs at all that I could see. I even looked on the C:\ to see if it was there.

It sounds like Avanti/FreeAXP is not seeing the Windows NIC. All I can suggest at this point is re-install Avanti/FreeAXP and see if there is a change in the NIC list or program behavior.

Do you have a UBS NIC you could temporarily add to the system to see if it shows up on the Avanti/FreeAXP NIC list?

Any luck determining why the two Windows 10 systems behave differently?