Ethernet connection takes 90 seconds to become available (Solution: Set Npcap to autostart)How do I determine...
What exploit are these user agents trying to use?
Can I use a neutral wire from another outlet to repair a broken neutral?
When a company launches a new product do they "come out" with a new product or do they "come up" with a new product?
Twin primes whose sum is a cube
Why is the 'in' operator throwing an error with a string literal instead of logging false?
Forgetting the musical notes while performing in concert
Why does Kotter return in Welcome Back Kotter
AES: Why is it a good practice to use only the first 16bytes of a hash for encryption?
Do I have a twin with permutated remainders?
Does a druid starting with a bow start with no arrows?
Why can't we play rap on piano?
In Romance of the Three Kingdoms why do people still use bamboo sticks when papers are already invented?
Why is consensus so controversial in Britain?
Today is the Center
Doing something right before you need it - expression for this?
Fully-Firstable Anagram Sets
If human space travel is limited by the G force vulnerability, is there a way to counter G forces?
90's TV series where a boy goes to another dimension through portal near power lines
How could indestructible materials be used in power generation?
What is the intuition behind short exact sequences of groups; in particular, what is the intuition behind group extensions?
Watching something be written to a file live with tail
Will google still index a page if I use a $_SESSION variable?
Why doesn't H₄O²⁺ exist?
Intersection of two sorted vectors in C++
Ethernet connection takes 90 seconds to become available (Solution: Set Npcap to autostart)
How do I determine why my connection goes down intermittently for 2-3 seconds?Loopback packet from FTTH modem for every 2 secondsSwitching to WiFi connection when Ethernet is slow (Windows 7)Everytime I restart router, i have to plug in ethernet cable again in wan port. Why?Ethernet Connection has Stopped WorkingWired ethernet connection broken after Windows 10 Updates *only over network switch*Role of the DNSEthernet connection - device does not existwhat kind of network activity the blinking ethernet LED really indicates?WiFi router not working properly
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
When I boot my Windows 7 PC, or when I disable and enable my Ethernet connection, it takes exactly 90 seconds for internet to become available. During that time the status is shown as normal (not "identifying").
During that time there are zero packets received or sent. Then, after 90 seconds suddenly there's a burst of traffic and the internet comes on. It works reliably from that point on.
I then disabled the Windows Media Player Sharing Service which was suggested somewhere on the web. Now there is still a 90 seconds window where there is no internet. But at least there are packets being sent. Just zero received packets still.
I tested the cable with another cable. It did not make a difference. The router is a normal ISP provided router. It's a very common device and other devices in the network are not affected. Also, there is only Windows Firewall enabled in a default configuration. No other security software.
What could cause this issue?
windows-7 networking ethernet
asked Mar 27 at 12:42
boot4lifeboot4life
328410
|
show 2 more comments
When I boot my Windows 7 PC, or when I disable and enable my Ethernet connection, it takes exactly 90 seconds for internet to become available. During that time the status is shown as normal (not "identifying").
During that time there are zero packets received or sent. Then, after 90 seconds suddenly there's a burst of traffic and the internet comes on. It works reliably from that point on.
I then disabled the Windows Media Player Sharing Service which was suggested somewhere on the web. Now there is still a 90 seconds window where there is no internet. But at least there are packets being sent. Just zero received packets still.
I tested the cable with another cable. It did not make a difference. The router is a normal ISP provided router. It's a very common device and other devices in the network are not affected. Also, there is only Windows Firewall enabled in a default configuration. No other security software.
What could cause this issue?
windows-7 networking ethernet
asked Mar 27 at 12:42
boot4lifeboot4life
328410
try a new ethernet cable, try a different port for that cable in the router, let me know if that makes any difference
– JohnnyVegas
Mar 27 at 13:04
@JohnnyVegas can it really be the cable if the connection works totally fine otherwise? Also, the software change I described made a difference that cannot be due to hardware. I'd be open to try a different cable but this cable is routed through parts of the room that are very hard to reach...
– boot4life
Mar 27 at 13:24
@boot4life - It is worth a try and it eliminates one of the many factors. Please edit your question, instead of submitting a comment, once you have tested another cable. You don't have to route the cable normally in order to test it.
– Ramhound
Mar 27 at 13:32
Maybe some kind of network loop detection logic on the switch side?
– mtak
Mar 27 at 13:38
I have made further edits. The cable is fine and other devices are not affected.
– boot4life
Mar 27 at 14:07
|
show 2 more comments
When I boot my Windows 7 PC, or when I disable and enable my Ethernet connection, it takes exactly 90 seconds for internet to become available. During that time the status is shown as normal (not "identifying").
During that time there are zero packets received or sent. Then, after 90 seconds suddenly there's a burst of traffic and the internet comes on. It works reliably from that point on.
I then disabled the Windows Media Player Sharing Service which was suggested somewhere on the web. Now there is still a 90 seconds window where there is no internet. But at least there are packets being sent. Just zero received packets still.
I tested the cable with another cable. It did not make a difference. The router is a normal ISP provided router. It's a very common device and other devices in the network are not affected. Also, there is only Windows Firewall enabled in a default configuration. No other security software.
What could cause this issue?
windows-7 networking ethernet
asked Mar 27 at 12:42
boot4lifeboot4life
328410
When I boot my Windows 7 PC, or when I disable and enable my Ethernet connection, it takes exactly 90 seconds for internet to become available. During that time the status is shown as normal (not "identifying").
During that time there are zero packets received or sent. Then, after 90 seconds suddenly there's a burst of traffic and the internet comes on. It works reliably from that point on.
I then disabled the Windows Media Player Sharing Service which was suggested somewhere on the web. Now there is still a 90 seconds window where there is no internet. But at least there are packets being sent. Just zero received packets still.
I tested the cable with another cable. It did not make a difference. The router is a normal ISP provided router. It's a very common device and other devices in the network are not affected. Also, there is only Windows Firewall enabled in a default configuration. No other security software.
What could cause this issue?
windows-7 networking ethernet
windows-7 networking ethernet
asked Mar 27 at 12:42
boot4lifeboot4life
328410
asked Mar 27 at 12:42
boot4lifeboot4life
328410
edited 10 hours ago
boot4life
asked Mar 27 at 12:42
boot4lifeboot4life
328410
asked Mar 27 at 12:42
boot4lifeboot4life
328410
asked Mar 27 at 12:42
boot4lifeboot4life
328410
328410
try a new ethernet cable, try a different port for that cable in the router, let me know if that makes any difference
– JohnnyVegas
Mar 27 at 13:04
@JohnnyVegas can it really be the cable if the connection works totally fine otherwise? Also, the software change I described made a difference that cannot be due to hardware. I'd be open to try a different cable but this cable is routed through parts of the room that are very hard to reach...
– boot4life
Mar 27 at 13:24
@boot4life - It is worth a try and it eliminates one of the many factors. Please edit your question, instead of submitting a comment, once you have tested another cable. You don't have to route the cable normally in order to test it.
– Ramhound
Mar 27 at 13:32
Maybe some kind of network loop detection logic on the switch side?
– mtak
Mar 27 at 13:38
I have made further edits. The cable is fine and other devices are not affected.
– boot4life
Mar 27 at 14:07
|
show 2 more comments
try a new ethernet cable, try a different port for that cable in the router, let me know if that makes any difference
– JohnnyVegas
Mar 27 at 13:04
@JohnnyVegas can it really be the cable if the connection works totally fine otherwise? Also, the software change I described made a difference that cannot be due to hardware. I'd be open to try a different cable but this cable is routed through parts of the room that are very hard to reach...
– boot4life
Mar 27 at 13:24
@boot4life - It is worth a try and it eliminates one of the many factors. Please edit your question, instead of submitting a comment, once you have tested another cable. You don't have to route the cable normally in order to test it.
– Ramhound
Mar 27 at 13:32
Maybe some kind of network loop detection logic on the switch side?
– mtak
Mar 27 at 13:38
I have made further edits. The cable is fine and other devices are not affected.
– boot4life
Mar 27 at 14:07
try a new ethernet cable, try a different port for that cable in the router, let me know if that makes any difference
– JohnnyVegas
Mar 27 at 13:04
try a new ethernet cable, try a different port for that cable in the router, let me know if that makes any difference
– JohnnyVegas
Mar 27 at 13:04
@JohnnyVegas can it really be the cable if the connection works totally fine otherwise? Also, the software change I described made a difference that cannot be due to hardware. I'd be open to try a different cable but this cable is routed through parts of the room that are very hard to reach...
– boot4life
Mar 27 at 13:24
@JohnnyVegas can it really be the cable if the connection works totally fine otherwise? Also, the software change I described made a difference that cannot be due to hardware. I'd be open to try a different cable but this cable is routed through parts of the room that are very hard to reach...
– boot4life
Mar 27 at 13:24
@boot4life - It is worth a try and it eliminates one of the many factors. Please edit your question, instead of submitting a comment, once you have tested another cable. You don't have to route the cable normally in order to test it.
– Ramhound
Mar 27 at 13:32
@boot4life - It is worth a try and it eliminates one of the many factors. Please edit your question, instead of submitting a comment, once you have tested another cable. You don't have to route the cable normally in order to test it.
– Ramhound
Mar 27 at 13:32
Maybe some kind of network loop detection logic on the switch side?
– mtak
Mar 27 at 13:38
Maybe some kind of network loop detection logic on the switch side?
– mtak
Mar 27 at 13:38
I have made further edits. The cable is fine and other devices are not affected.
– boot4life
Mar 27 at 14:07
I have made further edits. The cable is fine and other devices are not affected.
– boot4life
Mar 27 at 14:07
|
show 2 more comments
2 Answers
2
active
oldest
votes
There are two possibilities I can think of and which can be causing this issue but they are more relevant to enterprise rather then home/soho deployments:
- The switch is configured with leaf nodes having STP enabled. This usually causes 15-30 seconds of delay before switch enables traffic forwarding on newly linked port. This can be rectified by disabling STP on leaf port altogether or at least enabling "port-fast" mode.
- 802.1x is enabled on a port. Port will not forward traffic (or will forward it only to enclave VLAN) before the port is authorized. Authentication and authorization is handled by radius server and 90 seconds looks excessively long (but I've seen cheap switches where 802.1x is really slow).
SG-200-08 (mentioned in the other answer) may be both STP and 802.1x capable as this seems to be a clone of SLM2008 which is. Please check your switch configuration.
answered yesterday
TomekTomek
31924
Thanks. Indeed authentication was enabled for me which cost be another 1-2 seconds while the adapter was attempting to authenticate (as evidenced by the status text). I got rid of that. For the solution to my problem see my answer if you are interested. Again thanks for your help.
– boot4life
10 hours ago
add a comment |
I tried everything mentioned in this question. Also, I tried resetting the network stack entirely. This did not help.
I then disabled stuff here:
And it started working. By successively enabling items again I found that the Npcap item was causing the issue. (On this screenshot it is not visible because I already uninstalled it.) I did have the latest Npcap version already. I then reinstalled Wireshark and Npcap which did not help directly but:
When I set no autostart in the Npcap installer then the problem occurs. When I enable autostart the problem goes away.
answered 10 hours ago
boot4lifeboot4life
328410
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1418169%2fethernet-connection-takes-90-seconds-to-become-available-solution-set-npcap-to%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
There are two possibilities I can think of and which can be causing this issue but they are more relevant to enterprise rather then home/soho deployments:
- The switch is configured with leaf nodes having STP enabled. This usually causes 15-30 seconds of delay before switch enables traffic forwarding on newly linked port. This can be rectified by disabling STP on leaf port altogether or at least enabling "port-fast" mode.
- 802.1x is enabled on a port. Port will not forward traffic (or will forward it only to enclave VLAN) before the port is authorized. Authentication and authorization is handled by radius server and 90 seconds looks excessively long (but I've seen cheap switches where 802.1x is really slow).
SG-200-08 (mentioned in the other answer) may be both STP and 802.1x capable as this seems to be a clone of SLM2008 which is. Please check your switch configuration.
answered yesterday
TomekTomek
31924
Thanks. Indeed authentication was enabled for me which cost be another 1-2 seconds while the adapter was attempting to authenticate (as evidenced by the status text). I got rid of that. For the solution to my problem see my answer if you are interested. Again thanks for your help.
– boot4life
10 hours ago
add a comment |
There are two possibilities I can think of and which can be causing this issue but they are more relevant to enterprise rather then home/soho deployments:
- The switch is configured with leaf nodes having STP enabled. This usually causes 15-30 seconds of delay before switch enables traffic forwarding on newly linked port. This can be rectified by disabling STP on leaf port altogether or at least enabling "port-fast" mode.
- 802.1x is enabled on a port. Port will not forward traffic (or will forward it only to enclave VLAN) before the port is authorized. Authentication and authorization is handled by radius server and 90 seconds looks excessively long (but I've seen cheap switches where 802.1x is really slow).
SG-200-08 (mentioned in the other answer) may be both STP and 802.1x capable as this seems to be a clone of SLM2008 which is. Please check your switch configuration.
answered yesterday
TomekTomek
31924
Thanks. Indeed authentication was enabled for me which cost be another 1-2 seconds while the adapter was attempting to authenticate (as evidenced by the status text). I got rid of that. For the solution to my problem see my answer if you are interested. Again thanks for your help.
– boot4life
10 hours ago
add a comment |
There are two possibilities I can think of and which can be causing this issue but they are more relevant to enterprise rather then home/soho deployments:
- The switch is configured with leaf nodes having STP enabled. This usually causes 15-30 seconds of delay before switch enables traffic forwarding on newly linked port. This can be rectified by disabling STP on leaf port altogether or at least enabling "port-fast" mode.
- 802.1x is enabled on a port. Port will not forward traffic (or will forward it only to enclave VLAN) before the port is authorized. Authentication and authorization is handled by radius server and 90 seconds looks excessively long (but I've seen cheap switches where 802.1x is really slow).
SG-200-08 (mentioned in the other answer) may be both STP and 802.1x capable as this seems to be a clone of SLM2008 which is. Please check your switch configuration.
answered yesterday
TomekTomek
31924
There are two possibilities I can think of and which can be causing this issue but they are more relevant to enterprise rather then home/soho deployments:
- The switch is configured with leaf nodes having STP enabled. This usually causes 15-30 seconds of delay before switch enables traffic forwarding on newly linked port. This can be rectified by disabling STP on leaf port altogether or at least enabling "port-fast" mode.
- 802.1x is enabled on a port. Port will not forward traffic (or will forward it only to enclave VLAN) before the port is authorized. Authentication and authorization is handled by radius server and 90 seconds looks excessively long (but I've seen cheap switches where 802.1x is really slow).
SG-200-08 (mentioned in the other answer) may be both STP and 802.1x capable as this seems to be a clone of SLM2008 which is. Please check your switch configuration.
answered yesterday
TomekTomek
31924
answered yesterday
TomekTomek
31924
answered yesterday
TomekTomek
31924
answered yesterday
TomekTomek
31924
31924
Thanks. Indeed authentication was enabled for me which cost be another 1-2 seconds while the adapter was attempting to authenticate (as evidenced by the status text). I got rid of that. For the solution to my problem see my answer if you are interested. Again thanks for your help.
– boot4life
10 hours ago
add a comment |
Thanks. Indeed authentication was enabled for me which cost be another 1-2 seconds while the adapter was attempting to authenticate (as evidenced by the status text). I got rid of that. For the solution to my problem see my answer if you are interested. Again thanks for your help.
– boot4life
10 hours ago
Thanks. Indeed authentication was enabled for me which cost be another 1-2 seconds while the adapter was attempting to authenticate (as evidenced by the status text). I got rid of that. For the solution to my problem see my answer if you are interested. Again thanks for your help.
– boot4life
10 hours ago
Thanks. Indeed authentication was enabled for me which cost be another 1-2 seconds while the adapter was attempting to authenticate (as evidenced by the status text). I got rid of that. For the solution to my problem see my answer if you are interested. Again thanks for your help.
– boot4life
10 hours ago
add a comment |
I tried everything mentioned in this question. Also, I tried resetting the network stack entirely. This did not help.
I then disabled stuff here:
And it started working. By successively enabling items again I found that the Npcap item was causing the issue. (On this screenshot it is not visible because I already uninstalled it.) I did have the latest Npcap version already. I then reinstalled Wireshark and Npcap which did not help directly but:
When I set no autostart in the Npcap installer then the problem occurs. When I enable autostart the problem goes away.
answered 10 hours ago
boot4lifeboot4life
328410
add a comment |
I tried everything mentioned in this question. Also, I tried resetting the network stack entirely. This did not help.
I then disabled stuff here:
And it started working. By successively enabling items again I found that the Npcap item was causing the issue. (On this screenshot it is not visible because I already uninstalled it.) I did have the latest Npcap version already. I then reinstalled Wireshark and Npcap which did not help directly but:
When I set no autostart in the Npcap installer then the problem occurs. When I enable autostart the problem goes away.
answered 10 hours ago
boot4lifeboot4life
328410
add a comment |
I tried everything mentioned in this question. Also, I tried resetting the network stack entirely. This did not help.
I then disabled stuff here:
And it started working. By successively enabling items again I found that the Npcap item was causing the issue. (On this screenshot it is not visible because I already uninstalled it.) I did have the latest Npcap version already. I then reinstalled Wireshark and Npcap which did not help directly but:
When I set no autostart in the Npcap installer then the problem occurs. When I enable autostart the problem goes away.
answered 10 hours ago
boot4lifeboot4life
328410
I tried everything mentioned in this question. Also, I tried resetting the network stack entirely. This did not help.
I then disabled stuff here:
And it started working. By successively enabling items again I found that the Npcap item was causing the issue. (On this screenshot it is not visible because I already uninstalled it.) I did have the latest Npcap version already. I then reinstalled Wireshark and Npcap which did not help directly but:
When I set no autostart in the Npcap installer then the problem occurs. When I enable autostart the problem goes away.
answered 10 hours ago
boot4lifeboot4life
328410
answered 10 hours ago
boot4lifeboot4life
328410
answered 10 hours ago
boot4lifeboot4life
328410
answered 10 hours ago
boot4lifeboot4life
328410
328410
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1418169%2fethernet-connection-takes-90-seconds-to-become-available-solution-set-npcap-to%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
try a new ethernet cable, try a different port for that cable in the router, let me know if that makes any difference
– JohnnyVegas
Mar 27 at 13:04
@JohnnyVegas can it really be the cable if the connection works totally fine otherwise? Also, the software change I described made a difference that cannot be due to hardware. I'd be open to try a different cable but this cable is routed through parts of the room that are very hard to reach...
– boot4life
Mar 27 at 13:24
@boot4life - It is worth a try and it eliminates one of the many factors. Please edit your question, instead of submitting a comment, once you have tested another cable. You don't have to route the cable normally in order to test it.
– Ramhound
Mar 27 at 13:32
Maybe some kind of network loop detection logic on the switch side?
– mtak
Mar 27 at 13:38
I have made further edits. The cable is fine and other devices are not affected.
– boot4life
Mar 27 at 14:07