Can't connect to shared folders on Win 7 computer from Win 10 on local network
Things I've tried:
On Win 7 computer - it's a home network (not public), advanced sharing settings all set as permissively as possible, shared folders have the following groups set to "FULL CONTROL" for both sharing and security: everyone, network, guest, anonymous. Disabled IPv6. IPv4 is set to static IP. Left homegroup (since win 10 doesn't care about this anymore and it wasn't working with it on). Verified it's connected to the same 5G network as my Win10 computer. Both use wireless.
I found advice that seemed sensible to enable the "Function Discovery Resource Publication" so I set both machines to load the service automatically.
On win10, pinging the machine by name returns the right address. NSlookup returns an address on the Internet for some reason instead of the local machine (non-authoritive answer 198.105.244.228). No idea why or how to fix it. If I look in the router settings, it shows the computer with the right name and IP in the list of connected devices.
EDIT: I almost forgot; if I type IPADDRESS into Windows Explorer on Win10 where IPADDRESS is the ipv4 of the Win 7 machine, it gives me a username and password login (which it shouldn't do) and if I type "guest" with no password, it lets me connect.
Also, during all of my testing and changes, using VNC with just the hostname has worked flawlessly. Apparently my VNC client is able to get the right IP somehow.
windows-7 networking file-sharing
asked Jan 19 at 23:16
not_a_generic_usernot_a_generic_user
1013
add a comment |
Things I've tried:
On Win 7 computer - it's a home network (not public), advanced sharing settings all set as permissively as possible, shared folders have the following groups set to "FULL CONTROL" for both sharing and security: everyone, network, guest, anonymous. Disabled IPv6. IPv4 is set to static IP. Left homegroup (since win 10 doesn't care about this anymore and it wasn't working with it on). Verified it's connected to the same 5G network as my Win10 computer. Both use wireless.
I found advice that seemed sensible to enable the "Function Discovery Resource Publication" so I set both machines to load the service automatically.
On win10, pinging the machine by name returns the right address. NSlookup returns an address on the Internet for some reason instead of the local machine (non-authoritive answer 198.105.244.228). No idea why or how to fix it. If I look in the router settings, it shows the computer with the right name and IP in the list of connected devices.
EDIT: I almost forgot; if I type IPADDRESS into Windows Explorer on Win10 where IPADDRESS is the ipv4 of the Win 7 machine, it gives me a username and password login (which it shouldn't do) and if I type "guest" with no password, it lets me connect.
Also, during all of my testing and changes, using VNC with just the hostname has worked flawlessly. Apparently my VNC client is able to get the right IP somehow.
windows-7 networking file-sharing
asked Jan 19 at 23:16
not_a_generic_usernot_a_generic_user
1013
Maybe this?....zdnet.com/article/…
– Moab
Jan 20 at 0:04
You MUST use exactly the same username and password on both systems, or else create an account on the Win7 system and then enter that account name & password when you are prompted. And please turn off the Guest account(!), unless you want to invite exploits.
– Debra
Jan 22 at 21:37
BTW, a quick method that usually is easier for me is to type the command "NET USE T: \remotesysnamec$ /persistent:yes" where "remotesysname" is the name of the Win7 system, and T: is not necessarily the letter you must use for any reason. Again you have to have either the identical account created on that system, or else add the username & password to the "NET USE" command. ("NET USE /?" for help with this.) Then in the future you can always refer to T: instead of trying to browse & re-connect.
– Debra
Jan 22 at 21:39
add a comment |
Things I've tried:
On Win 7 computer - it's a home network (not public), advanced sharing settings all set as permissively as possible, shared folders have the following groups set to "FULL CONTROL" for both sharing and security: everyone, network, guest, anonymous. Disabled IPv6. IPv4 is set to static IP. Left homegroup (since win 10 doesn't care about this anymore and it wasn't working with it on). Verified it's connected to the same 5G network as my Win10 computer. Both use wireless.
I found advice that seemed sensible to enable the "Function Discovery Resource Publication" so I set both machines to load the service automatically.
On win10, pinging the machine by name returns the right address. NSlookup returns an address on the Internet for some reason instead of the local machine (non-authoritive answer 198.105.244.228). No idea why or how to fix it. If I look in the router settings, it shows the computer with the right name and IP in the list of connected devices.
EDIT: I almost forgot; if I type IPADDRESS into Windows Explorer on Win10 where IPADDRESS is the ipv4 of the Win 7 machine, it gives me a username and password login (which it shouldn't do) and if I type "guest" with no password, it lets me connect.
Also, during all of my testing and changes, using VNC with just the hostname has worked flawlessly. Apparently my VNC client is able to get the right IP somehow.
windows-7 networking file-sharing
asked Jan 19 at 23:16
not_a_generic_usernot_a_generic_user
1013
Things I've tried:
On Win 7 computer - it's a home network (not public), advanced sharing settings all set as permissively as possible, shared folders have the following groups set to "FULL CONTROL" for both sharing and security: everyone, network, guest, anonymous. Disabled IPv6. IPv4 is set to static IP. Left homegroup (since win 10 doesn't care about this anymore and it wasn't working with it on). Verified it's connected to the same 5G network as my Win10 computer. Both use wireless.
I found advice that seemed sensible to enable the "Function Discovery Resource Publication" so I set both machines to load the service automatically.
On win10, pinging the machine by name returns the right address. NSlookup returns an address on the Internet for some reason instead of the local machine (non-authoritive answer 198.105.244.228). No idea why or how to fix it. If I look in the router settings, it shows the computer with the right name and IP in the list of connected devices.
EDIT: I almost forgot; if I type IPADDRESS into Windows Explorer on Win10 where IPADDRESS is the ipv4 of the Win 7 machine, it gives me a username and password login (which it shouldn't do) and if I type "guest" with no password, it lets me connect.
Also, during all of my testing and changes, using VNC with just the hostname has worked flawlessly. Apparently my VNC client is able to get the right IP somehow.
windows-7 networking file-sharing
windows-7 networking file-sharing
asked Jan 19 at 23:16
not_a_generic_usernot_a_generic_user
1013
asked Jan 19 at 23:16
not_a_generic_usernot_a_generic_user
1013
edited Jan 19 at 23:49
not_a_generic_user
asked Jan 19 at 23:16
not_a_generic_usernot_a_generic_user
1013
asked Jan 19 at 23:16
not_a_generic_usernot_a_generic_user
1013
asked Jan 19 at 23:16
not_a_generic_usernot_a_generic_user
1013
1013
Maybe this?....zdnet.com/article/…
– Moab
Jan 20 at 0:04
You MUST use exactly the same username and password on both systems, or else create an account on the Win7 system and then enter that account name & password when you are prompted. And please turn off the Guest account(!), unless you want to invite exploits.
– Debra
Jan 22 at 21:37
BTW, a quick method that usually is easier for me is to type the command "NET USE T: \remotesysnamec$ /persistent:yes" where "remotesysname" is the name of the Win7 system, and T: is not necessarily the letter you must use for any reason. Again you have to have either the identical account created on that system, or else add the username & password to the "NET USE" command. ("NET USE /?" for help with this.) Then in the future you can always refer to T: instead of trying to browse & re-connect.
– Debra
Jan 22 at 21:39
add a comment |
Maybe this?....zdnet.com/article/…
– Moab
Jan 20 at 0:04
You MUST use exactly the same username and password on both systems, or else create an account on the Win7 system and then enter that account name & password when you are prompted. And please turn off the Guest account(!), unless you want to invite exploits.
– Debra
Jan 22 at 21:37
BTW, a quick method that usually is easier for me is to type the command "NET USE T: \remotesysnamec$ /persistent:yes" where "remotesysname" is the name of the Win7 system, and T: is not necessarily the letter you must use for any reason. Again you have to have either the identical account created on that system, or else add the username & password to the "NET USE" command. ("NET USE /?" for help with this.) Then in the future you can always refer to T: instead of trying to browse & re-connect.
– Debra
Jan 22 at 21:39
Maybe this?....zdnet.com/article/…
– Moab
Jan 20 at 0:04
Maybe this?....zdnet.com/article/…
– Moab
Jan 20 at 0:04
You MUST use exactly the same username and password on both systems, or else create an account on the Win7 system and then enter that account name & password when you are prompted. And please turn off the Guest account(!), unless you want to invite exploits.
– Debra
Jan 22 at 21:37
You MUST use exactly the same username and password on both systems, or else create an account on the Win7 system and then enter that account name & password when you are prompted. And please turn off the Guest account(!), unless you want to invite exploits.
– Debra
Jan 22 at 21:37
BTW, a quick method that usually is easier for me is to type the command "NET USE T: \remotesysnamec$ /persistent:yes" where "remotesysname" is the name of the Win7 system, and T: is not necessarily the letter you must use for any reason. Again you have to have either the identical account created on that system, or else add the username & password to the "NET USE" command. ("NET USE /?" for help with this.) Then in the future you can always refer to T: instead of trying to browse & re-connect.
– Debra
Jan 22 at 21:39
BTW, a quick method that usually is easier for me is to type the command "NET USE T: \remotesysnamec$ /persistent:yes" where "remotesysname" is the name of the Win7 system, and T: is not necessarily the letter you must use for any reason. Again you have to have either the identical account created on that system, or else add the username & password to the "NET USE" command. ("NET USE /?" for help with this.) Then in the future you can always refer to T: instead of trying to browse & re-connect.
– Debra
Jan 22 at 21:39
add a comment |
1 Answer
1
active
oldest
votes
I'm not sure if you are still struggling with this issue, but:
This is probaly caused by update kb4480970 installed on the Windows 7 machine. You can resolve this issue by installing hotfix (KB4487345) which can be installed from here
This hotfix is not included in the regular Windows 7 updates.
(Thanks to Twisty impersonator who has adressed this solution here)
answered Feb 1 at 9:32
user386956user386956
1
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%2f1396196%2fcant-connect-to-shared-folders-on-win-7-computer-from-win-10-on-local-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I'm not sure if you are still struggling with this issue, but:
This is probaly caused by update kb4480970 installed on the Windows 7 machine. You can resolve this issue by installing hotfix (KB4487345) which can be installed from here
This hotfix is not included in the regular Windows 7 updates.
(Thanks to Twisty impersonator who has adressed this solution here)
answered Feb 1 at 9:32
user386956user386956
1
add a comment |
I'm not sure if you are still struggling with this issue, but:
This is probaly caused by update kb4480970 installed on the Windows 7 machine. You can resolve this issue by installing hotfix (KB4487345) which can be installed from here
This hotfix is not included in the regular Windows 7 updates.
(Thanks to Twisty impersonator who has adressed this solution here)
answered Feb 1 at 9:32
user386956user386956
1
add a comment |
I'm not sure if you are still struggling with this issue, but:
This is probaly caused by update kb4480970 installed on the Windows 7 machine. You can resolve this issue by installing hotfix (KB4487345) which can be installed from here
This hotfix is not included in the regular Windows 7 updates.
(Thanks to Twisty impersonator who has adressed this solution here)
answered Feb 1 at 9:32
user386956user386956
1
I'm not sure if you are still struggling with this issue, but:
This is probaly caused by update kb4480970 installed on the Windows 7 machine. You can resolve this issue by installing hotfix (KB4487345) which can be installed from here
This hotfix is not included in the regular Windows 7 updates.
(Thanks to Twisty impersonator who has adressed this solution here)
answered Feb 1 at 9:32
user386956user386956
1
answered Feb 1 at 9:32
user386956user386956
1
answered Feb 1 at 9:32
user386956user386956
1
answered Feb 1 at 9:32
user386956user386956
1
1
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%2f1396196%2fcant-connect-to-shared-folders-on-win-7-computer-from-win-10-on-local-network%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
Maybe this?....zdnet.com/article/…
– Moab
Jan 20 at 0:04
You MUST use exactly the same username and password on both systems, or else create an account on the Win7 system and then enter that account name & password when you are prompted. And please turn off the Guest account(!), unless you want to invite exploits.
– Debra
Jan 22 at 21:37
BTW, a quick method that usually is easier for me is to type the command "NET USE T: \remotesysnamec$ /persistent:yes" where "remotesysname" is the name of the Win7 system, and T: is not necessarily the letter you must use for any reason. Again you have to have either the identical account created on that system, or else add the username & password to the "NET USE" command. ("NET USE /?" for help with this.) Then in the future you can always refer to T: instead of trying to browse & re-connect.
– Debra
Jan 22 at 21:39