HardwareBanter

HardwareBanter (http://www.hardwarebanter.com/index.php)
-   Asus Motherboards (http://www.hardwarebanter.com/forumdisplay.php?f=15)
-   -   Keep Getting Network 2 (http://www.hardwarebanter.com/showthread.php?t=199624)

Bill Anderson June 16th 19 06:00 PM

Keep Getting Network 2
 
I'm running an Asus X299-A system with its Intel Network Adapter. I'm
running Win10 64-bit and I've updated the LAN driver to the latest I can
find, v22.9.16.0. My device shown in Device Manager is called Intel(R)
Ethernet Connection (2) I219-V. I've checked the Intel forums and
discovered lots of people are seeing that (2) in the name and can't
figure out why it's there. Even the Intel techs on the forum don't have
a good answer.

I can live with the unexplained (2) in the name, but I'm pulling my hair
out over a possibly unrelated intermittent problem with connection on
boot: sometimes -- rarely I admit, maybe once in 20 boots -- I am
momentarily puzzled at logon to find I can connect to only a few
websites and others are unavailable. Something's wrong!

I've learned from experience that at this point I need to look at my
network connection which will now be named "Network 2" instead of the
normal "Network." With that confirmed, I've learned to go into Device
Manager, look under Network Adapters, uninstall the Intel Ethernet
Connection (2), open Action/Scan for Hardware Changes, and with the scan
complete I will have my Intel Ethernet Connection (2) device back in the
Device Manager list, and I'll also have my "Network" connection back and
functioning normally without the "2." This happens once every 20 boots
or so, and I have no idea what to do about it. As I'm grasping at
straws, I'm wondering if the "(2)" in the network adapter's name can be
confusing the LAN driver as it tries to make a connection at boot? It
sees the (2) in the adapter name and creates a special (but barely
functional) Network 2 connection for it? Maybe? Any other ideas? Thanks.


--
Bill Anderson

I am the Mighty Favog

Shadow[_2_] January 24th 20 11:43 PM

Keep Getting Network 2
 
On Sun, 16 Jun 2019 12:00:47 -0500, Bill Anderson
wrote:

I'm running an Asus X299-A system with its Intel Network Adapter. I'm
running Win10 64-bit and I've updated the LAN driver to the latest I can
find, v22.9.16.0. My device shown in Device Manager is called Intel(R)
Ethernet Connection (2) I219-V. I've checked the Intel forums and
discovered lots of people are seeing that (2) in the name and can't
figure out why it's there. Even the Intel techs on the forum don't have
a good answer.

I can live with the unexplained (2) in the name, but I'm pulling my hair
out over a possibly unrelated intermittent problem with connection on
boot: sometimes -- rarely I admit, maybe once in 20 boots -- I am
momentarily puzzled at logon to find I can connect to only a few
websites and others are unavailable. Something's wrong!

I've learned from experience that at this point I need to look at my
network connection which will now be named "Network 2" instead of the
normal "Network." With that confirmed, I've learned to go into Device
Manager, look under Network Adapters, uninstall the Intel Ethernet
Connection (2), open Action/Scan for Hardware Changes, and with the scan
complete I will have my Intel Ethernet Connection (2) device back in the
Device Manager list, and I'll also have my "Network" connection back and
functioning normally without the "2." This happens once every 20 boots
or so, and I have no idea what to do about it. As I'm grasping at
straws, I'm wondering if the "(2)" in the network adapter's name can be
confusing the LAN driver as it tries to make a connection at boot? It
sees the (2) in the adapter name and creates a special (but barely
functional) Network 2 connection for it? Maybe? Any other ideas? Thanks.


Could be faulty hardware or buggy drivers.
Try installing a network card (or a USB wireless), and make it
the default (there's probably one in a box somewhere).
See if that has issues.
[]'s
--
Don't be evil - Google 2004
We have a new policy - Google 2012

Bill Anderson January 24th 20 11:56 PM

Keep Getting Network 2
 
On 1/24/2020 4:43 PM, Shadow wrote:
On Sun, 16 Jun 2019 12:00:47 -0500, Bill Anderson
wrote:

I'm running an Asus X299-A system with its Intel Network Adapter. I'm
running Win10 64-bit and I've updated the LAN driver to the latest I can
find, v22.9.16.0. My device shown in Device Manager is called Intel(R)
Ethernet Connection (2) I219-V. I've checked the Intel forums and
discovered lots of people are seeing that (2) in the name and can't
figure out why it's there. Even the Intel techs on the forum don't have
a good answer.

I can live with the unexplained (2) in the name, but I'm pulling my hair
out over a possibly unrelated intermittent problem with connection on
boot: sometimes -- rarely I admit, maybe once in 20 boots -- I am
momentarily puzzled at logon to find I can connect to only a few
websites and others are unavailable. Something's wrong!

I've learned from experience that at this point I need to look at my
network connection which will now be named "Network 2" instead of the
normal "Network." With that confirmed, I've learned to go into Device
Manager, look under Network Adapters, uninstall the Intel Ethernet
Connection (2), open Action/Scan for Hardware Changes, and with the scan
complete I will have my Intel Ethernet Connection (2) device back in the
Device Manager list, and I'll also have my "Network" connection back and
functioning normally without the "2." This happens once every 20 boots
or so, and I have no idea what to do about it. As I'm grasping at
straws, I'm wondering if the "(2)" in the network adapter's name can be
confusing the LAN driver as it tries to make a connection at boot? It
sees the (2) in the adapter name and creates a special (but barely
functional) Network 2 connection for it? Maybe? Any other ideas? Thanks.


Could be faulty hardware or buggy drivers.
Try installing a network card (or a USB wireless), and make it
the default (there's probably one in a box somewhere).
See if that has issues.
[]'s


Thanks. I had to fix the problem today, coincidentally. I've gotten
used to it now. Takes me 15 seconds to fix. Annoying, though.

--
Bill Anderson

I am the Mighty Favog

Paul[_28_] January 25th 20 08:24 AM

Keep Getting Network 2
 
Bill Anderson wrote:
On 1/24/2020 4:43 PM, Shadow wrote:
On Sun, 16 Jun 2019 12:00:47 -0500, Bill Anderson
wrote:

I'm running an Asus X299-A system with its Intel Network Adapter. I'm
running Win10 64-bit and I've updated the LAN driver to the latest I can
find, v22.9.16.0. My device shown in Device Manager is called Intel(R)
Ethernet Connection (2) I219-V. I've checked the Intel forums and
discovered lots of people are seeing that (2) in the name and can't
figure out why it's there. Even the Intel techs on the forum don't have
a good answer.

I can live with the unexplained (2) in the name, but I'm pulling my hair
out over a possibly unrelated intermittent problem with connection on
boot: sometimes -- rarely I admit, maybe once in 20 boots -- I am
momentarily puzzled at logon to find I can connect to only a few
websites and others are unavailable. Something's wrong!

I've learned from experience that at this point I need to look at my
network connection which will now be named "Network 2" instead of the
normal "Network." With that confirmed, I've learned to go into Device
Manager, look under Network Adapters, uninstall the Intel Ethernet
Connection (2), open Action/Scan for Hardware Changes, and with the scan
complete I will have my Intel Ethernet Connection (2) device back in the
Device Manager list, and I'll also have my "Network" connection back and
functioning normally without the "2." This happens once every 20 boots
or so, and I have no idea what to do about it. As I'm grasping at
straws, I'm wondering if the "(2)" in the network adapter's name can be
confusing the LAN driver as it tries to make a connection at boot? It
sees the (2) in the adapter name and creates a special (but barely
functional) Network 2 connection for it? Maybe? Any other ideas? Thanks.


Could be faulty hardware or buggy drivers.
Try installing a network card (or a USB wireless), and make it
the default (there's probably one in a box somewhere).
See if that has issues.
[]'s


Thanks. I had to fix the problem today, coincidentally. I've gotten
used to it now. Takes me 15 seconds to fix. Annoying, though.


It's a pretty weird chip.

Of course, they couldn't give a block diagram that helps explain *why*
it works like that. See for example, page 28 (block diagram of buses).

https://digitallibrary.intel.com/con...-datasheet.pdf

It could be dual head, with half of it being intended for the Management Engine.
The shocker is, that the second bus interface seems to be SMBUS. And
SMBUS has perfectly awful operational characteristics!

A question would be, what would happen on a boot cycle, if the
PCIe interface didn't train up properly, and only the SMBUS was
present. Then, the SMBUS was not captured by the ME (because a
particular product SKU doesn't use the Management Engine), and
somehow the device is detected on the SMBUS. And that makes
the device "(2)".

Normally, SMBUS is a serial bus running at 400Kbit/sec or so.
You would think shoving packets over a thing like that would
not end well. I would be tempted to use a local LAN benchmark
and see what kind of comm rate it can manage in the busted state.

https://web.archive.org/web/20130606...ATTCP-0114.zip

On the second (perfectly working) machine, set up the receiver first.

ipconfig # This gives the address of this machine (192.168.1.3)

pcattcp -r -4 # The receiver sits and waits for the transmitter

On the broken machine, do

pcattcp -t -4 192.168.1.3 # Substitute IP address from ipconfig result...

You can try that out with two normal machines first, until
you get the hang of it and the results make sense.

The purpose of doing this, is to see if the rate indicates
the data is actually flowing over the SMBUS. I just don't
see that as being possible. But you never know.

The SMBUS is normally used for reading the SPD chip on DIMMs.

Paul


All times are GMT +1. The time now is 06:56 AM.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
HardwareBanter.com