| Author |
%TCPIP-E-INVINTER, error defining interface: WE0 |
pampreen_d
Member
Posts: 10
Joined: 16.07.08 |
| Posted on April 10 2017 16:27 |
|
|
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 |
|
|
| Author |
RE: %TCPIP-E-INVINTER, error defining interface: WE0 |
pampreen_d
Member
Posts: 10
Joined: 16.07.08 |
| Posted on April 10 2017 16:47 |
|
|
other details:
Windows 10 Pro on both good and failing machine
version 2.6.4.598 for both FreeAXP and Avanti
|
|
|
| Author |
RE: %TCPIP-E-INVINTER, error defining interface: WE0 |
Bruce Claremont
Moderator
Posts: 623
Joined: 07.01.10 |
| Posted on April 11 2017 05:04 |
|
|
|
Have you installed anything that uses WinPCAP 4.1.3? If so, try dropping back to WinPCAP 4.1.2. |
|
|
| Author |
RE: %TCPIP-E-INVINTER, error defining interface: WE0 |
pampreen_d
Member
Posts: 10
Joined: 16.07.08 |
| Posted on April 11 2017 08:47 |
|
|
|
Nope - no installs at all that I could see. I even looked on the C:\ to see if it was there. |
|
|
| Author |
RE: %TCPIP-E-INVINTER, error defining interface: WE0 |
Bruce Claremont
Moderator
Posts: 623
Joined: 07.01.10 |
| Posted on April 12 2017 02:23 |
|
|
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? |
|
|
| Author |
RE: %TCPIP-E-INVINTER, error defining interface: WE0 |
Bruce Claremont
Moderator
Posts: 623
Joined: 07.01.10 |
| Posted on April 13 2017 04:09 |
|
|
|
Any luck determining why the two Windows 10 systems behave differently? |
|
|
| Author |
RE: %TCPIP-E-INVINTER, error defining interface: WE0 |
pampreen_d
Member
Posts: 10
Joined: 16.07.08 |
| Posted on April 14 2017 16:08 |
|
|
I was able to reinstall and it seems to have fixed it.
I can't figure out why, nothing in the event logs or AV logs that might point to a reason.
After a bit of testing it I moved it back to the original machine just now, so I will see how that goes.
Fingers crossed.
|
|
|
