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.

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

On 27/07/2020 21:38, Paul wrote:
Fokke Nauta wrote:
On 27/07/2020 17:14, pjp wrote:
In article , says...

On 21/07/2020 21:50, Fokke Nauta wrote:
Hi all,

For many times I created shares on a remote pc. I was always able
to see
this pc on the network and was able to open the shared directories.
Therefore I needed a name and a password. And this has worked for many
years.
But now for something completely different.
I help an old friend (80+) with his pc and his laptop. As his
health is
getting worse he wants to work on his laptop instead of his pc. He
wants
to see on the laptop the files of his pc. On his pc his account had no
password. I added a password to enable shared partitions. There are a
few hard disks which I shared to the user with a password.
On his laptop I can't see his pc. This is weird. When I looked in the
network at \\"Name of the pc" I was able to see the shared disks, but
they are not accessible. I can't open them. Never seen this before. It
always worked.
What can be wrong here?

Thanks beforehand.

Both systems running W10

Fokke Nauta

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.

Thanks.

Fokke

I've simply used Everyone almost since day 1 of starting to network two
pcs together in Windows (after Lantastic and the like decades ago now).

It's all internal on local network so I don't really have a problem
giving every pc a Temp folder with full access and other shared folders
usually only Read permission.


I've never done this before. I always worked with a user account name
and password. And that always worked. This time not.

Fokke


You're free to go back and do more experiments.

Getting it to the point of working, using Everyone,
proves that other parts of the authentication worked.

Now you can crank the security back into position,
a bit at a time, and see how much it will tolerate.

You can also check details of the successful connection. Powershell :
get-smbconnection

https://docs.microsoft.com/en-us/pow...?view=win10-ps


Â*Â* Paul

No, Paul.

I stick with how it is now. I have put enough time into this ...

Fokke

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

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.