WSL binds all ports, lose network access: Unable to connect
I'm using WSL for some node development on a Windows 10 machine (build 1803). Inevitably, within a few hours of starting WSL, all ports on the system become bound. At this point, no new network connections open, and I effectively lose network access until I restart.
netstat -qn |findstr BOUND
This shows all TCP ports bound up to the max, such as:
TCP 0.0.0.0:60755 0.0.0.0:0 BOUND
I've tried using ipconfig to reset the windows side adapter, killing all WSL processes, and a bunch of other things, but nothing unbinds the ports. I'd like to be able to use my computer without having to restart every few hours.
I was able to find an open issue with limited info: https://github.com/Microsoft/WSL/issues/2523
but no solutions or workarounds.
Any way to reset WSL or open the ports would be much appreciated!
windows networking windows-10 wireless-networking windows-subsystem-for-linux
asked Jan 27 at 23:12
adeebmadeebm
1
add a comment |
I'm using WSL for some node development on a Windows 10 machine (build 1803). Inevitably, within a few hours of starting WSL, all ports on the system become bound. At this point, no new network connections open, and I effectively lose network access until I restart.
netstat -qn |findstr BOUND
This shows all TCP ports bound up to the max, such as:
TCP 0.0.0.0:60755 0.0.0.0:0 BOUND
I've tried using ipconfig to reset the windows side adapter, killing all WSL processes, and a bunch of other things, but nothing unbinds the ports. I'd like to be able to use my computer without having to restart every few hours.
I was able to find an open issue with limited info: https://github.com/Microsoft/WSL/issues/2523
but no solutions or workarounds.
Any way to reset WSL or open the ports would be much appreciated!
windows networking windows-10 wireless-networking windows-subsystem-for-linux
asked Jan 27 at 23:12
adeebmadeebm
1
1
What process/processes is/are responsible? if you run:netstat -qno | find "BOUND", what is the PID (last column) and what does this map to in TaskManager/Tasklist.exe?
– HelpingHand
Jan 27 at 23:31
It seems to be adb, part of a cli for the Expo project I have. I expect it to open connections, as it's for remote debugging. But killing it or even WSL as a whole doesn't release the ports.
– adeebm
Jan 28 at 3:03
It is surprising that killing the process doesn't clean up. Can you run the following PowerShell command and link the results:get-nettcpconnection -state BOUND -OwningProcess ((Get-Process adb).ID)[0] | select LocalAddress, LocalPort, stateNote: I've put the process in asadbis that correct?
– HelpingHand
Jan 28 at 14:11
By randomly killing processes, I found that 'init' in 'LocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalStaterootfs' seems to actually terminate WSL and release the ports. Thanks for pointing me in the right direction!
– adeebm
Jan 30 at 0:38
add a comment |
I'm using WSL for some node development on a Windows 10 machine (build 1803). Inevitably, within a few hours of starting WSL, all ports on the system become bound. At this point, no new network connections open, and I effectively lose network access until I restart.
netstat -qn |findstr BOUND
This shows all TCP ports bound up to the max, such as:
TCP 0.0.0.0:60755 0.0.0.0:0 BOUND
I've tried using ipconfig to reset the windows side adapter, killing all WSL processes, and a bunch of other things, but nothing unbinds the ports. I'd like to be able to use my computer without having to restart every few hours.
I was able to find an open issue with limited info: https://github.com/Microsoft/WSL/issues/2523
but no solutions or workarounds.
Any way to reset WSL or open the ports would be much appreciated!
windows networking windows-10 wireless-networking windows-subsystem-for-linux
asked Jan 27 at 23:12
adeebmadeebm
1
I'm using WSL for some node development on a Windows 10 machine (build 1803). Inevitably, within a few hours of starting WSL, all ports on the system become bound. At this point, no new network connections open, and I effectively lose network access until I restart.
netstat -qn |findstr BOUND
This shows all TCP ports bound up to the max, such as:
TCP 0.0.0.0:60755 0.0.0.0:0 BOUND
I've tried using ipconfig to reset the windows side adapter, killing all WSL processes, and a bunch of other things, but nothing unbinds the ports. I'd like to be able to use my computer without having to restart every few hours.
I was able to find an open issue with limited info: https://github.com/Microsoft/WSL/issues/2523
but no solutions or workarounds.
Any way to reset WSL or open the ports would be much appreciated!
windows networking windows-10 wireless-networking windows-subsystem-for-linux
windows networking windows-10 wireless-networking windows-subsystem-for-linux
asked Jan 27 at 23:12
adeebmadeebm
1
asked Jan 27 at 23:12
adeebmadeebm
1
asked Jan 27 at 23:12
adeebmadeebm
1
asked Jan 27 at 23:12
adeebmadeebm
1
asked Jan 27 at 23:12
adeebmadeebm
1
1
1
What process/processes is/are responsible? if you run:netstat -qno | find "BOUND", what is the PID (last column) and what does this map to in TaskManager/Tasklist.exe?
– HelpingHand
Jan 27 at 23:31
It seems to be adb, part of a cli for the Expo project I have. I expect it to open connections, as it's for remote debugging. But killing it or even WSL as a whole doesn't release the ports.
– adeebm
Jan 28 at 3:03
It is surprising that killing the process doesn't clean up. Can you run the following PowerShell command and link the results:get-nettcpconnection -state BOUND -OwningProcess ((Get-Process adb).ID)[0] | select LocalAddress, LocalPort, stateNote: I've put the process in asadbis that correct?
– HelpingHand
Jan 28 at 14:11
By randomly killing processes, I found that 'init' in 'LocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalStaterootfs' seems to actually terminate WSL and release the ports. Thanks for pointing me in the right direction!
– adeebm
Jan 30 at 0:38
add a comment |
1
What process/processes is/are responsible? if you run:netstat -qno | find "BOUND", what is the PID (last column) and what does this map to in TaskManager/Tasklist.exe?
– HelpingHand
Jan 27 at 23:31
It seems to be adb, part of a cli for the Expo project I have. I expect it to open connections, as it's for remote debugging. But killing it or even WSL as a whole doesn't release the ports.
– adeebm
Jan 28 at 3:03
It is surprising that killing the process doesn't clean up. Can you run the following PowerShell command and link the results:get-nettcpconnection -state BOUND -OwningProcess ((Get-Process adb).ID)[0] | select LocalAddress, LocalPort, stateNote: I've put the process in asadbis that correct?
– HelpingHand
Jan 28 at 14:11
By randomly killing processes, I found that 'init' in 'LocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalStaterootfs' seems to actually terminate WSL and release the ports. Thanks for pointing me in the right direction!
– adeebm
Jan 30 at 0:38
1
1
What process/processes is/are responsible? if you run:
netstat -qno | find "BOUND", what is the PID (last column) and what does this map to in TaskManager/Tasklist.exe?– HelpingHand
Jan 27 at 23:31
What process/processes is/are responsible? if you run:
netstat -qno | find "BOUND", what is the PID (last column) and what does this map to in TaskManager/Tasklist.exe?– HelpingHand
Jan 27 at 23:31
It seems to be adb, part of a cli for the Expo project I have. I expect it to open connections, as it's for remote debugging. But killing it or even WSL as a whole doesn't release the ports.
– adeebm
Jan 28 at 3:03
It seems to be adb, part of a cli for the Expo project I have. I expect it to open connections, as it's for remote debugging. But killing it or even WSL as a whole doesn't release the ports.
– adeebm
Jan 28 at 3:03
It is surprising that killing the process doesn't clean up. Can you run the following PowerShell command and link the results:
get-nettcpconnection -state BOUND -OwningProcess ((Get-Process adb).ID)[0] | select LocalAddress, LocalPort, state Note: I've put the process in as adb is that correct?– HelpingHand
Jan 28 at 14:11
It is surprising that killing the process doesn't clean up. Can you run the following PowerShell command and link the results:
get-nettcpconnection -state BOUND -OwningProcess ((Get-Process adb).ID)[0] | select LocalAddress, LocalPort, state Note: I've put the process in as adb is that correct?– HelpingHand
Jan 28 at 14:11
By randomly killing processes, I found that 'init' in 'LocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalStaterootfs' seems to actually terminate WSL and release the ports. Thanks for pointing me in the right direction!
– adeebm
Jan 30 at 0:38
By randomly killing processes, I found that 'init' in 'LocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalStaterootfs' seems to actually terminate WSL and release the ports. Thanks for pointing me in the right direction!
– adeebm
Jan 30 at 0:38
add a comment |
0
active
oldest
votes
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%2f1399063%2fwsl-binds-all-ports-lose-network-access-unable-to-connect%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f1399063%2fwsl-binds-all-ports-lose-network-access-unable-to-connect%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
1
What process/processes is/are responsible? if you run:
netstat -qno | find "BOUND", what is the PID (last column) and what does this map to in TaskManager/Tasklist.exe?– HelpingHand
Jan 27 at 23:31
It seems to be adb, part of a cli for the Expo project I have. I expect it to open connections, as it's for remote debugging. But killing it or even WSL as a whole doesn't release the ports.
– adeebm
Jan 28 at 3:03
It is surprising that killing the process doesn't clean up. Can you run the following PowerShell command and link the results:
get-nettcpconnection -state BOUND -OwningProcess ((Get-Process adb).ID)[0] | select LocalAddress, LocalPort, stateNote: I've put the process in asadbis that correct?– HelpingHand
Jan 28 at 14:11
By randomly killing processes, I found that 'init' in 'LocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalStaterootfs' seems to actually terminate WSL and release the ports. Thanks for pointing me in the right direction!
– adeebm
Jan 30 at 0:38