Network issue with Windows 11
jlechat34
Posted messages
154
Registration date
Status
Member
Last intervention
-
brupala Posted messages 111108 Registration date Status Member Last intervention -
brupala Posted messages 111108 Registration date Status Member Last intervention -
Hello,
My shared computer running Windows 11 is not visible on another computer running Windows 10. However, with the one running Windows 11, I can access the shared folders of the one running Windows 10.
How can I resolve this issue? I have reset the network but it hasn't helped.
Thank you in advance for your help, have a nice day.
My shared computer running Windows 11 is not visible on another computer running Windows 10. However, with the one running Windows 11, I can access the shared folders of the one running Windows 10.
How can I resolve this issue? I have reset the network but it hasn't helped.
Thank you in advance for your help, have a nice day.
4 answers
Hi,
it's never really useful to have shares in both directions; it's better that all shared folders are on the same PC, it's easier to manage, it avoids duplicates, and it simplifies backups.
Windows 10 and 11 seem to make sharing folders and files in the public folder easier by default, as it is shared by default.
For other folders, it can be more complex regarding access rights; you generally need to configure the same user accounts and the proper NTFS permissions (security tab in folder properties).
--
and ... There you go!
it's never really useful to have shares in both directions; it's better that all shared folders are on the same PC, it's easier to manage, it avoids duplicates, and it simplifies backups.
Windows 10 and 11 seem to make sharing folders and files in the public folder easier by default, as it is shared by default.
For other folders, it can be more complex regarding access rights; you generally need to configure the same user accounts and the proper NTFS permissions (security tab in folder properties).
--
and ... There you go!
Hello,
Thank you for your reply, we need to communicate in both directions because the machines are on different floors and we have a lot of exchanges for the work.
I will continue to look for a solution.
Thanks again and have a great rest of your day.
Thank you for your reply, we need to communicate in both directions because the machines are on different floors and we have a lot of exchanges for the work.
I will continue to look for a solution.
Thanks again and have a great rest of your day.
Sharing resources on M$ is always a hassle.
I also needed this function and the only solution I found was the network connection.
Start both PCs. Wait about ten minutes for W10 to launch the discovery protocol (I think it’s Netbios). Open File Explorer. Click on "This PC", right-click then "Map network drive". Assign a letter (preferably towards the end of the alphabet), make sure the option "Reconnect at sign-in" is checked, then click on Browse. If you see your other PC there, confirm and you're good to go.
If that doesn’t work, I’ll explain the process on one of the two PCs, and you can duplicate it on the second.
Right-click on the folder you are sharing, properties then the "Sharing" tab. Under the "Network Path" heading, you will see a string with <\\PC name\folder> of the directory. Copy this name without error. Go to the other PC. Follow the steps from the beginning of the message up to Browse (where you normally won’t see anything). In the input field, enter the string <\\PC name\directory> from the other PC and confirm.
I also needed this function and the only solution I found was the network connection.
Start both PCs. Wait about ten minutes for W10 to launch the discovery protocol (I think it’s Netbios). Open File Explorer. Click on "This PC", right-click then "Map network drive". Assign a letter (preferably towards the end of the alphabet), make sure the option "Reconnect at sign-in" is checked, then click on Browse. If you see your other PC there, confirm and you're good to go.
If that doesn’t work, I’ll explain the process on one of the two PCs, and you can duplicate it on the second.
Right-click on the folder you are sharing, properties then the "Sharing" tab. Under the "Network Path" heading, you will see a string with <\\PC name\folder> of the directory. Copy this name without error. Go to the other PC. Follow the steps from the beginning of the message up to Browse (where you normally won’t see anything). In the input field, enter the string <\\PC name\directory> from the other PC and confirm.
Hello,
Thank you all for your responses and advice, and especially to SATS_fr; their solution of creating network drives is excellent, easy to implement, and above all, very effective!
Our network issues are finally resolved thanks to them.
Thanks again to everyone and have a great day.
Thank you all for your responses and advice, and especially to SATS_fr; their solution of creating network drives is excellent, easy to implement, and above all, very effective!
Our network issues are finally resolved thanks to them.
Thanks again to everyone and have a great day.
Hello,
It's not really HIS solution,
it's just how things have been done in businesses for about thirty years, basically since Windows started networking, even before Windows NT, I believe.
But indeed, it's a pity that Microsoft doesn't promote this more for individuals; I would even say that the feature is harder to find in the File Explorer since Windows 11, you have to be in local disk view to find it.
But there's always the old-fashioned method of the command line, with NET USE, which is also scriptable and thus executable automatically.
It's not really HIS solution,
it's just how things have been done in businesses for about thirty years, basically since Windows started networking, even before Windows NT, I believe.
But indeed, it's a pity that Microsoft doesn't promote this more for individuals; I would even say that the feature is harder to find in the File Explorer since Windows 11, you have to be in local disk view to find it.
But there's always the old-fashioned method of the command line, with NET USE, which is also scriptable and thus executable automatically.