If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
#16
|
|||
|
|||
Can't open shares
On 7/27/2020 4:11 PM, NY wrote:
"Fokke Nauta" wrote in message ... Thanks to this news group I was able to open the shares on the pc on his laptop. I had to do two things: 1. On the shared disks of the pc I changed the security to Everyone, with full access. 2. I changed the rights of the shares to Everyone, with full rights. Finally It worked, but this is highly uncommon. And unsafe. If you can trust everyone on your LAN, then granting "Everyone: Full" rights is one way of making sure it works, even if you then start to tighten security to the point where it just stops working. I fine security a right PITA. I am more interested in making things work, than stopping them working. You're in a domain, then you can grant domain-users:read or my-subgroup:read/write, but in a home network (with Windows Home rather then Pro), you would have to create a user account on every PC if you wanted user-specific permissions. When you have only two computers on your private LAN and a printer that belongs to you, giving every one full access to your shared folders is not a big problem. |
Ads |
#17
|
|||
|
|||
Can't open shares
knuttle wrote:
On 7/27/2020 4:11 PM, NY wrote: "Fokke Nauta" wrote in message ... Thanks to this news group I was able to open the shares on the pc on his laptop. I had to do two things: 1. On the shared disks of the pc I changed the security to Everyone, with full access. 2. I changed the rights of the shares to Everyone, with full rights. Finally It worked, but this is highly uncommon. And unsafe. If you can trust everyone on your LAN, then granting "Everyone: Full" rights is one way of making sure it works, even if you then start to tighten security to the point where it just stops working. I fine security a right PITA. I am more interested in making things work, than stopping them working. You're in a domain, then you can grant domain-users:read or my-subgroup:read/write, but in a home network (with Windows Home rather then Pro), you would have to create a user account on every PC if you wanted user-specific permissions. When you have only two computers on your private LAN and a printer that belongs to you, giving every one full access to your shared folders is not a big problem. You have to decide for yourself whether: "If they get inside my perimeter, I'm dead meat" is the right policy for you. That's how I'm operating right now. I'm relying on my perimeter for protection, with no Plan B (emphasis on machine level security). And I run that way, because I can boot into too many OSes to do otherwise. Lots of people who visit here, have more static configurations (no multiboot), and for them, a little tightening here and there might be worth it. Paul |
#19
|
|||
|
|||
Can't open shares
On 27/07/2020 22:34, knuttle wrote:
On 7/27/2020 4:11 PM, NY wrote: "Fokke Nauta" wrote in message ... Thanks to this news group I was able to open the shares on the pc on his laptop. I had to do two things: 1. On the shared disks of the pc I changed the security to Everyone, with full access. 2. I changed the rights of the shares to Everyone, with full rights. Finally It worked, but this is highly uncommon. And unsafe. If you can trust everyone on your LAN, then granting "Everyone: Full" rights is one way of making sure it works, even if you then start to tighten security to the point where it just stops working. I fine security a right PITA. I am more interested in making things work, than stopping them working. You're in a domain, then you can grant domain-users:read or my-subgroup:read/write, but in a home network (with Windows Home rather then Pro), you would have to create a user account on every PC if you wanted user-specific permissions. When you have only two computers on your private LAN and a printer that belongs to you, giving every one full access to your shared folders is not a big problem. That's exactly how the situation is. No risks. But I assume that in this case you're more vulnerable for attacks from outside. Fokke |
#20
|
|||
|
|||
Can't open shares
On 7/29/2020 3:26 AM, Fokke Nauta wrote:
On 27/07/2020 22:34, knuttle wrote: On 7/27/2020 4:11 PM, NY wrote: "Fokke Nauta" wrote in message ... Thanks to this news group I was able to open the shares on the pc on his laptop. I had to do two things: 1. On the shared disks of the pc I changed the security to Everyone, with full access. 2. I changed the rights of the shares to Everyone, with full rights. Finally It worked, but this is highly uncommon. And unsafe. If you can trust everyone on your LAN, then granting "Everyone: Full" rights is one way of making sure it works, even if you then start to tighten security to the point where it just stops working. I fine security a right PITA. I am more interested in making things work, than stopping them working. You're in a domain, then you can grant domain-users:read or my-subgroup:read/write, but in a home network (with Windows Home rather then Pro), you would have to create a user account on every PC if you wanted user-specific permissions. When you have only two computers on your private LAN and a printer that belongs to you, giving every one full access to your shared folders is not a big problem. That's exactly how the situation is. No risks. But I assume that in this case you're more vulnerable for attacks from outside. Fokke With both computer protected by security programs, and the firewalls provided by the firewall in the router and in the security program, the risk is there but low. Also the best absolute system is used on both computers. When finished using the computer they are both turned off, not put to sleep or hibernation but turned off. |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|