Windows 7 network share is not accessible, handle invalid, 4672 4634
I have two Windows 7 PCs, no domain, same workgroup.
PC A used to be able to connect to PC B's network shares.
Now it can't. Winf firewall on PC B is off for troubleshooting.
From PC A, double-clicking on PC B name in Explorer's network view prompts a login dialog box.
Login uses PC Busername on PC B, with correct password.
Error message is:
PC B is not accessible. handle is invalid.
Event viewer on PC B eventvwr winlogssecurity shows the event ids:
4672 special logon
and immediately after it
4634 logoff logon type 3 (network)
So it appears PC A is using a valid user account and password to login to PC B, the login is accepted, but then the login is immediately logged off.
Using elevated cmd prompt on PC A, net view \PC B returns
System Error 5 has occurred. Access is denied
The only thing I can think of that may have triggered this is that PC A was renamed using "Computer Properties" and restarted. The access problem began after this procedure.
Any tips on how to further troubleshoot this issue?
windows-7 windows networking authentication
edited Jan 21 at 18:29
Scott
15.9k113990
asked Jan 21 at 16:34
Steve WasiuraSteve Wasiura
147210
add a comment |
I have two Windows 7 PCs, no domain, same workgroup.
PC A used to be able to connect to PC B's network shares.
Now it can't. Winf firewall on PC B is off for troubleshooting.
From PC A, double-clicking on PC B name in Explorer's network view prompts a login dialog box.
Login uses PC Busername on PC B, with correct password.
Error message is:
PC B is not accessible. handle is invalid.
Event viewer on PC B eventvwr winlogssecurity shows the event ids:
4672 special logon
and immediately after it
4634 logoff logon type 3 (network)
So it appears PC A is using a valid user account and password to login to PC B, the login is accepted, but then the login is immediately logged off.
Using elevated cmd prompt on PC A, net view \PC B returns
System Error 5 has occurred. Access is denied
The only thing I can think of that may have triggered this is that PC A was renamed using "Computer Properties" and restarted. The access problem began after this procedure.
Any tips on how to further troubleshoot this issue?
windows-7 windows networking authentication
edited Jan 21 at 18:29
Scott
15.9k113990
asked Jan 21 at 16:34
Steve WasiuraSteve Wasiura
147210
Two recent Windows Updates (KB 4480970 and KB 4480960) broke the ability for administrators to access SMB2 shares on several OS versions, including Windows 7. Did you recently install those updates on either A or B? Is the user in question an administrator?
– Doug Deden
Jan 21 at 17:04
1
I've heard an update is causing WIN7 to stop seeing SMB Shares. Please check if any update have been recently installed (manually or though automatic update) in the time this issue start to occur. ThisKB4480970in particular is known for this. More info here.
– Manuel Florian
Jan 21 at 17:06
thanks for the links, i will investigate the proposed solution at bleepingcomputer.com/news/microsoft/…
– Steve Wasiura
Jan 21 at 19:26
add a comment |
I have two Windows 7 PCs, no domain, same workgroup.
PC A used to be able to connect to PC B's network shares.
Now it can't. Winf firewall on PC B is off for troubleshooting.
From PC A, double-clicking on PC B name in Explorer's network view prompts a login dialog box.
Login uses PC Busername on PC B, with correct password.
Error message is:
PC B is not accessible. handle is invalid.
Event viewer on PC B eventvwr winlogssecurity shows the event ids:
4672 special logon
and immediately after it
4634 logoff logon type 3 (network)
So it appears PC A is using a valid user account and password to login to PC B, the login is accepted, but then the login is immediately logged off.
Using elevated cmd prompt on PC A, net view \PC B returns
System Error 5 has occurred. Access is denied
The only thing I can think of that may have triggered this is that PC A was renamed using "Computer Properties" and restarted. The access problem began after this procedure.
Any tips on how to further troubleshoot this issue?
windows-7 windows networking authentication
edited Jan 21 at 18:29
Scott
15.9k113990
asked Jan 21 at 16:34
Steve WasiuraSteve Wasiura
147210
I have two Windows 7 PCs, no domain, same workgroup.
PC A used to be able to connect to PC B's network shares.
Now it can't. Winf firewall on PC B is off for troubleshooting.
From PC A, double-clicking on PC B name in Explorer's network view prompts a login dialog box.
Login uses PC Busername on PC B, with correct password.
Error message is:
PC B is not accessible. handle is invalid.
Event viewer on PC B eventvwr winlogssecurity shows the event ids:
4672 special logon
and immediately after it
4634 logoff logon type 3 (network)
So it appears PC A is using a valid user account and password to login to PC B, the login is accepted, but then the login is immediately logged off.
Using elevated cmd prompt on PC A, net view \PC B returns
System Error 5 has occurred. Access is denied
The only thing I can think of that may have triggered this is that PC A was renamed using "Computer Properties" and restarted. The access problem began after this procedure.
Any tips on how to further troubleshoot this issue?
windows-7 windows networking authentication
windows-7 windows networking authentication
edited Jan 21 at 18:29
Scott
15.9k113990
asked Jan 21 at 16:34
Steve WasiuraSteve Wasiura
147210
edited Jan 21 at 18:29
Scott
15.9k113990
asked Jan 21 at 16:34
Steve WasiuraSteve Wasiura
147210
edited Jan 21 at 18:29
Scott
15.9k113990
edited Jan 21 at 18:29
Scott
15.9k113990
edited Jan 21 at 18:29
Scott
15.9k113990
15.9k113990
asked Jan 21 at 16:34
Steve WasiuraSteve Wasiura
147210
asked Jan 21 at 16:34
Steve WasiuraSteve Wasiura
147210
asked Jan 21 at 16:34
Steve WasiuraSteve Wasiura
147210
147210
Two recent Windows Updates (KB 4480970 and KB 4480960) broke the ability for administrators to access SMB2 shares on several OS versions, including Windows 7. Did you recently install those updates on either A or B? Is the user in question an administrator?
– Doug Deden
Jan 21 at 17:04
1
I've heard an update is causing WIN7 to stop seeing SMB Shares. Please check if any update have been recently installed (manually or though automatic update) in the time this issue start to occur. ThisKB4480970in particular is known for this. More info here.
– Manuel Florian
Jan 21 at 17:06
thanks for the links, i will investigate the proposed solution at bleepingcomputer.com/news/microsoft/…
– Steve Wasiura
Jan 21 at 19:26
add a comment |
Two recent Windows Updates (KB 4480970 and KB 4480960) broke the ability for administrators to access SMB2 shares on several OS versions, including Windows 7. Did you recently install those updates on either A or B? Is the user in question an administrator?
– Doug Deden
Jan 21 at 17:04
1
I've heard an update is causing WIN7 to stop seeing SMB Shares. Please check if any update have been recently installed (manually or though automatic update) in the time this issue start to occur. ThisKB4480970in particular is known for this. More info here.
– Manuel Florian
Jan 21 at 17:06
thanks for the links, i will investigate the proposed solution at bleepingcomputer.com/news/microsoft/…
– Steve Wasiura
Jan 21 at 19:26
Two recent Windows Updates (KB 4480970 and KB 4480960) broke the ability for administrators to access SMB2 shares on several OS versions, including Windows 7. Did you recently install those updates on either A or B? Is the user in question an administrator?
– Doug Deden
Jan 21 at 17:04
Two recent Windows Updates (KB 4480970 and KB 4480960) broke the ability for administrators to access SMB2 shares on several OS versions, including Windows 7. Did you recently install those updates on either A or B? Is the user in question an administrator?
– Doug Deden
Jan 21 at 17:04
1
1
I've heard an update is causing WIN7 to stop seeing SMB Shares. Please check if any update have been recently installed (manually or though automatic update) in the time this issue start to occur. This
KB4480970 in particular is known for this. More info here.– Manuel Florian
Jan 21 at 17:06
I've heard an update is causing WIN7 to stop seeing SMB Shares. Please check if any update have been recently installed (manually or though automatic update) in the time this issue start to occur. This
KB4480970 in particular is known for this. More info here.– Manuel Florian
Jan 21 at 17:06
thanks for the links, i will investigate the proposed solution at bleepingcomputer.com/news/microsoft/…
– Steve Wasiura
Jan 21 at 19:26
thanks for the links, i will investigate the proposed solution at bleepingcomputer.com/news/microsoft/…
– Steve Wasiura
Jan 21 at 19:26
add a comment |
3 Answers
3
active
oldest
votes
Doug and Manuel are right on! I was having the same issue, plus remote desktop wasn't working. The fix was https://support.microsoft.com/en-us/help/4487345/update-for-windows-7-sp1-and-windows-server-2008-r2. And yes, my account was administrator on the machines that were failing.
answered Jan 22 at 6:46
Dave StrandbergDave Strandberg
1
Please provide your steps in answer how you solved it.
– Biswapriyo
Jan 22 at 8:43
add a comment |
I had the exact same problem as the OP. This problem was new and out of the blue, after having installed recent Windows update updates.
If you follow https://support.microsoft.com/en-us/help/4487345/update-for-windows-7-sp1-and-windows-server-2008-r2 as mentioned in @Dave Strandberg's answer, you'll get to a page that describes the problem. It says:
This update resolves the issue where local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows 7 SP1 and Windows Server 2008 R2 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.
To get the stand-alone package for this update, go to the Microsoft Update Catalog website.
It offers a link to http://www.catalog.update.microsoft.com/Search.aspx?q=KB4487345.
I wasn't keen to uninstall updates, so I applied this update and it fixed the problem. The update requires a reboot (at least it did on my machines). Note that you want to apply it to the machine that hosts the share, not the machine trying to access it.
answered Jan 27 at 21:40
trwtrw
10613
add a comment |
had a same issue with win 7. After uninstalling KB 4480970 problem disappeared.
If you can't uninstall KB 4480970 you can get remote desktop running by changing My Computer-->properties-->remote settings--> Remote desktop--> Allow connections from computers running any version of remote desktop.
I have not managed to resolve shares issue without KB uninstall.
Two days later KB 4480970 got installed again. You have to disable it permanently.
answered Jan 26 at 13:33
Wojciech SulekWojciech Sulek
11
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%2f1396686%2fwindows-7-network-share-is-not-accessible-handle-invalid-4672-4634%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Doug and Manuel are right on! I was having the same issue, plus remote desktop wasn't working. The fix was https://support.microsoft.com/en-us/help/4487345/update-for-windows-7-sp1-and-windows-server-2008-r2. And yes, my account was administrator on the machines that were failing.
answered Jan 22 at 6:46
Dave StrandbergDave Strandberg
1
Please provide your steps in answer how you solved it.
– Biswapriyo
Jan 22 at 8:43
add a comment |
Doug and Manuel are right on! I was having the same issue, plus remote desktop wasn't working. The fix was https://support.microsoft.com/en-us/help/4487345/update-for-windows-7-sp1-and-windows-server-2008-r2. And yes, my account was administrator on the machines that were failing.
answered Jan 22 at 6:46
Dave StrandbergDave Strandberg
1
Please provide your steps in answer how you solved it.
– Biswapriyo
Jan 22 at 8:43
add a comment |
Doug and Manuel are right on! I was having the same issue, plus remote desktop wasn't working. The fix was https://support.microsoft.com/en-us/help/4487345/update-for-windows-7-sp1-and-windows-server-2008-r2. And yes, my account was administrator on the machines that were failing.
answered Jan 22 at 6:46
Dave StrandbergDave Strandberg
1
Doug and Manuel are right on! I was having the same issue, plus remote desktop wasn't working. The fix was https://support.microsoft.com/en-us/help/4487345/update-for-windows-7-sp1-and-windows-server-2008-r2. And yes, my account was administrator on the machines that were failing.
answered Jan 22 at 6:46
Dave StrandbergDave Strandberg
1
answered Jan 22 at 6:46
Dave StrandbergDave Strandberg
1
answered Jan 22 at 6:46
Dave StrandbergDave Strandberg
1
answered Jan 22 at 6:46
Dave StrandbergDave Strandberg
1
1
Please provide your steps in answer how you solved it.
– Biswapriyo
Jan 22 at 8:43
add a comment |
Please provide your steps in answer how you solved it.
– Biswapriyo
Jan 22 at 8:43
Please provide your steps in answer how you solved it.
– Biswapriyo
Jan 22 at 8:43
Please provide your steps in answer how you solved it.
– Biswapriyo
Jan 22 at 8:43
add a comment |
I had the exact same problem as the OP. This problem was new and out of the blue, after having installed recent Windows update updates.
If you follow https://support.microsoft.com/en-us/help/4487345/update-for-windows-7-sp1-and-windows-server-2008-r2 as mentioned in @Dave Strandberg's answer, you'll get to a page that describes the problem. It says:
This update resolves the issue where local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows 7 SP1 and Windows Server 2008 R2 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.
To get the stand-alone package for this update, go to the Microsoft Update Catalog website.
It offers a link to http://www.catalog.update.microsoft.com/Search.aspx?q=KB4487345.
I wasn't keen to uninstall updates, so I applied this update and it fixed the problem. The update requires a reboot (at least it did on my machines). Note that you want to apply it to the machine that hosts the share, not the machine trying to access it.
answered Jan 27 at 21:40
trwtrw
10613
add a comment |
I had the exact same problem as the OP. This problem was new and out of the blue, after having installed recent Windows update updates.
If you follow https://support.microsoft.com/en-us/help/4487345/update-for-windows-7-sp1-and-windows-server-2008-r2 as mentioned in @Dave Strandberg's answer, you'll get to a page that describes the problem. It says:
This update resolves the issue where local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows 7 SP1 and Windows Server 2008 R2 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.
To get the stand-alone package for this update, go to the Microsoft Update Catalog website.
It offers a link to http://www.catalog.update.microsoft.com/Search.aspx?q=KB4487345.
I wasn't keen to uninstall updates, so I applied this update and it fixed the problem. The update requires a reboot (at least it did on my machines). Note that you want to apply it to the machine that hosts the share, not the machine trying to access it.
answered Jan 27 at 21:40
trwtrw
10613
add a comment |
I had the exact same problem as the OP. This problem was new and out of the blue, after having installed recent Windows update updates.
If you follow https://support.microsoft.com/en-us/help/4487345/update-for-windows-7-sp1-and-windows-server-2008-r2 as mentioned in @Dave Strandberg's answer, you'll get to a page that describes the problem. It says:
This update resolves the issue where local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows 7 SP1 and Windows Server 2008 R2 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.
To get the stand-alone package for this update, go to the Microsoft Update Catalog website.
It offers a link to http://www.catalog.update.microsoft.com/Search.aspx?q=KB4487345.
I wasn't keen to uninstall updates, so I applied this update and it fixed the problem. The update requires a reboot (at least it did on my machines). Note that you want to apply it to the machine that hosts the share, not the machine trying to access it.
answered Jan 27 at 21:40
trwtrw
10613
I had the exact same problem as the OP. This problem was new and out of the blue, after having installed recent Windows update updates.
If you follow https://support.microsoft.com/en-us/help/4487345/update-for-windows-7-sp1-and-windows-server-2008-r2 as mentioned in @Dave Strandberg's answer, you'll get to a page that describes the problem. It says:
This update resolves the issue where local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows 7 SP1 and Windows Server 2008 R2 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.
To get the stand-alone package for this update, go to the Microsoft Update Catalog website.
It offers a link to http://www.catalog.update.microsoft.com/Search.aspx?q=KB4487345.
I wasn't keen to uninstall updates, so I applied this update and it fixed the problem. The update requires a reboot (at least it did on my machines). Note that you want to apply it to the machine that hosts the share, not the machine trying to access it.
answered Jan 27 at 21:40
trwtrw
10613
edited Jan 27 at 21:58
answered Jan 27 at 21:40
trwtrw
10613
answered Jan 27 at 21:40
trwtrw
10613
answered Jan 27 at 21:40
trwtrw
10613
10613
add a comment |
add a comment |
had a same issue with win 7. After uninstalling KB 4480970 problem disappeared.
If you can't uninstall KB 4480970 you can get remote desktop running by changing My Computer-->properties-->remote settings--> Remote desktop--> Allow connections from computers running any version of remote desktop.
I have not managed to resolve shares issue without KB uninstall.
Two days later KB 4480970 got installed again. You have to disable it permanently.
answered Jan 26 at 13:33
Wojciech SulekWojciech Sulek
11
add a comment |
had a same issue with win 7. After uninstalling KB 4480970 problem disappeared.
If you can't uninstall KB 4480970 you can get remote desktop running by changing My Computer-->properties-->remote settings--> Remote desktop--> Allow connections from computers running any version of remote desktop.
I have not managed to resolve shares issue without KB uninstall.
Two days later KB 4480970 got installed again. You have to disable it permanently.
answered Jan 26 at 13:33
Wojciech SulekWojciech Sulek
11
add a comment |
had a same issue with win 7. After uninstalling KB 4480970 problem disappeared.
If you can't uninstall KB 4480970 you can get remote desktop running by changing My Computer-->properties-->remote settings--> Remote desktop--> Allow connections from computers running any version of remote desktop.
I have not managed to resolve shares issue without KB uninstall.
Two days later KB 4480970 got installed again. You have to disable it permanently.
answered Jan 26 at 13:33
Wojciech SulekWojciech Sulek
11
had a same issue with win 7. After uninstalling KB 4480970 problem disappeared.
If you can't uninstall KB 4480970 you can get remote desktop running by changing My Computer-->properties-->remote settings--> Remote desktop--> Allow connections from computers running any version of remote desktop.
I have not managed to resolve shares issue without KB uninstall.
Two days later KB 4480970 got installed again. You have to disable it permanently.
answered Jan 26 at 13:33
Wojciech SulekWojciech Sulek
11
edited Jan 31 at 15:04
answered Jan 26 at 13:33
Wojciech SulekWojciech Sulek
11
answered Jan 26 at 13:33
Wojciech SulekWojciech Sulek
11
answered Jan 26 at 13:33
Wojciech SulekWojciech Sulek
11
11
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%2f1396686%2fwindows-7-network-share-is-not-accessible-handle-invalid-4672-4634%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
Two recent Windows Updates (KB 4480970 and KB 4480960) broke the ability for administrators to access SMB2 shares on several OS versions, including Windows 7. Did you recently install those updates on either A or B? Is the user in question an administrator?
– Doug Deden
Jan 21 at 17:04
1
I've heard an update is causing WIN7 to stop seeing SMB Shares. Please check if any update have been recently installed (manually or though automatic update) in the time this issue start to occur. This
KB4480970in particular is known for this. More info here.– Manuel Florian
Jan 21 at 17:06
thanks for the links, i will investigate the proposed solution at bleepingcomputer.com/news/microsoft/…
– Steve Wasiura
Jan 21 at 19:26