Can't open shares

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

On 7/21/2020 3:50 PM, 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
Done right, you do not need a password on the shared computers, nor a
password to access the shared computer.

I have a desktop and a laptop that I share data, and sync the data
between them, The shared folders are as easy to access as the Local folder.

If when you try to access a shared drive, I have found it is a matter of
who owns the resource and who is trying to share it. You can go in and
share a folder, but unless the account from which you are working owns
the folder, will appear on the other computer but ask the user of the
other computer for a password or something similar.

It an involved process, so do a search on folder ownership and change
all shared folders to be owned by the same account

On 7/21/2020 5:42 PM, knuttle wrote:
On 7/21/2020 3:50 PM, 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
Done right, you do not need a password on the shared computers, nor a
password to access the shared computer.

I have a desktop and a laptop that I share data, and sync the data
between them,Â* The shared folders are as easy to access as the Local
folder.

If when you try to access a shared drive, I have found it is a matter of
who owns the resource and who is trying to share it.Â* You can go in and
share a folder, but unless the account from which you are working owns
the folder, will appear on the other computer but ask the user of the
other computer for a password or something similar.

It an involved process, so do a search on folder ownership and change
all shared folders to be owned by the same account

Found by using search string "MS WINDOWS folder ownership and sharing
folders"


https://answers.microsoft.com/en-us/...6-f17de534bb30

knuttle wrote:
On 7/21/2020 3:50 PM, 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
Done right, you do not need a password on the shared computers, nor a
password to access the shared computer.

I have a desktop and a laptop that I share data, and sync the data
between them, The shared folders are as easy to access as the Local
folder.

If when you try to access a shared drive, I have found it is a matter of
who owns the resource and who is trying to share it. You can go in and
share a folder, but unless the account from which you are working owns
the folder, will appear on the other computer but ask the user of the
other computer for a password or something similar.

It an involved process, so do a search on folder ownership and change
all shared folders to be owned by the same account

I'd be a little careful with this advice.

I can find examples where "password protect shares" and using
an account with no password set, leads to "no burrito for you".
Microsoft has this listed on a web page as an expected result.
They specifically "deny" when you do that.

On older OSes, a combination of various things, the security was
quite lax and you would get away with it.

Now, you're in the Windows 10 group, and anarchy reins...
There are no free lunches in Windows 10. Everything goes on
your tab.

*******

what I do on my humble setup here, is log in as a local
account on the foreign machine.


Typing machine Test machine
username=Bolt username=Bullwinkle

share=rumdisk

Login to
\\Test\rumdisk

as bullwinkle:bullwinkle_password

And that seems to work for me. I cannot log into
the Test machine as "Bolt", as that won't work.

At one time, I could log into Test with Bullwinkle:1234 ,
in other words, a totally bogus password. And that doesn't
work all the time, either.

I have a Win98 VM. Guess what ? No authentication whatsoever.
Just works. And partially enabled by Windows 10 having
SMBV1 turned on.

Bottom line is, you have to log with a usernameassword that
exists on the remote machine, to overcome whatever obstacles
it's throwing up.

On a home LAN, the SIDs of the accounts are different.
Let's say that Bullwinkle exists on two machines, then
the SID on one machine for Bullwinkle could be 123 and
on the other it could be 456.

If I bring a Bullwinkle disk over to a second machine,
the green "takeown" bar appears, and restamps the files.
That happens, because I happen to belong to the administrator
group at the time, and there's sufficient elevation for it
to do that. If I look at the foreign disk now, I see

Owner: 123 \___ Two accounts at owner level
456 /

The files have two owners, and voila, I have access to
the "foreign" disk.

When file sharing happens, notice what a mess that would be.
File sharing must be doing *something* to smooth over the
fact that no two things on a home LAN use the same
identifiers. And that suggests that the logging in step
is important - it might just be applying a transformation
to make the files accessible. Even though, strictly speaking,
the ownership is out of reach. It's because you selected
some setting where "Everyone" "Can make changes" and that
provided a means for the differences to be smoothed over
or smashed. You *did* give permission at some point.

"Advanced Sharing"

https://www.tenforums.com/attachment..._sharing-1.png

Now "Everyone", "Full Control", "OK"

https://www.tenforums.com/attachment..._sharing-3.png

And a ton more, here.

https://www.tenforums.com/tutorials/...dows-10-a.html

Paul

On 22/07/2020 01:21, Paul wrote:
knuttle wrote:
On 7/21/2020 3:50 PM, 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
Done right, you do not need a password on the shared computers, nor a
password to access the shared computer.

I have a desktop and a laptop that I share data, and sync the data
between them,Â* The shared folders are as easy to access as the Local
folder.

If when you try to access a shared drive, I have found it is a matter
of who owns the resource and who is trying to share it.Â* You can go in
and share a folder, but unless the account from which you are working
owns the folder, will appear on the other computer but ask the user of
the other computer for a password or something similar.

It an involved process, so do a search on folder ownership and change
all shared folders to be owned by the same account

I'd be a little careful with this advice.

I can find examples where "password protect shares" and using
an account with no password set, leads to "no burrito for you".
Microsoft has this listed on a web page as an expected result.
They specifically "deny" when you do that.

On older OSes, a combination of various things, the security was
quite lax and you would get away with it.

Now, you're in the Windows 10 group, and anarchy reins...
There are no free lunches in Windows 10. Everything goes on
your tab.

*******

what I do on my humble setup here, is log in as a local
account on the foreign machine.


Â*Â*Â*Â* Typing machineÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Test machine
Â*Â*Â*Â* username=BoltÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* username=Bullwinkle

Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* share=rumdisk

Â*Â*Â*Â* Login to
Â*Â*Â*Â* \\Test\rumdisk

Â*Â*Â*Â* as bullwinkle:bullwinkle_password

And that seems to work for me. I cannot log into
the Test machine as "Bolt", as that won't work.

At one time, I could log into Test with Bullwinkle:1234 ,
in other words, a totally bogus password. And that doesn't
work all the time, either.

I have a Win98 VM. Guess what ? No authentication whatsoever.
Just works. And partially enabled by Windows 10 having
SMBV1 turned on.

Bottom line is, you have to log with a usernameassword that
exists on the remote machine, to overcome whatever obstacles
it's throwing up.

On a home LAN, the SIDs of the accounts are different.
Let's say that Bullwinkle exists on two machines, then
the SID on one machine for Bullwinkle could be 123 and
on the other it could be 456.

If I bring a Bullwinkle disk over to a second machine,
the green "takeown" bar appears, and restamps the files.
That happens, because I happen to belong to the administrator
group at the time, and there's sufficient elevation for it
to do that. If I look at the foreign disk now, I see

Â*Â*Â*Â* Owner:Â* 123Â* \___ Two accounts at owner level
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* 456Â* /

The files have two owners, and voila, I have access to
the "foreign" disk.

When file sharing happens, notice what a mess that would be.
File sharing must be doing *something* to smooth over the
fact that no two things on a home LAN use the same
identifiers. And that suggests that the logging in step
is important - it might just be applying a transformation
to make the files accessible. Even though, strictly speaking,
the ownership is out of reach. It's because you selected
some setting where "Everyone" "Can make changes" and that
provided a means for the differences to be smoothed over
or smashed. You *did* give permission at some point.

"Advanced Sharing"

https://www.tenforums.com/attachment..._sharing-1.png


Now "Everyone", "Full Control", "OK"

https://www.tenforums.com/attachment..._sharing-3.png


And a ton more, here.

https://www.tenforums.com/tutorials/...dows-10-a.html


Â*Â* Paul

Thanks, Paul.

I know how to share folders, done that many times.
As there was no password on the pc, I enabled sharing for Everyone with
full control. That did not work.
Then I added a password to the account of the pc, and enabled a share
for the user, with full control as well. This is the common way.
From the laptop I can see the shares of the pc but I can't open them.
When I try to open a share, the system asks for a password, but after
entering that nothing happens.
Another weird thing is that I cannot see the pc in the network.

This never happened to me before.

Fokke

On 22/07/2020 00:59, knuttle wrote:
On 7/21/2020 5:42 PM, knuttle wrote:
On 7/21/2020 3:50 PM, 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
Done right, you do not need a password on the shared computers, nor a
password to access the shared computer.

I have a desktop and a laptop that I share data, and sync the data
between them,Â* The shared folders are as easy to access as the Local
folder.

If when you try to access a shared drive, I have found it is a matter
of who owns the resource and who is trying to share it.Â* You can go in
and share a folder, but unless the account from which you are working
owns the folder, will appear on the other computer but ask the user of
the other computer for a password or something similar.

It an involved process, so do a search on folder ownership and change
all shared folders to be owned by the same account

Found by using search string "MS WINDOWS folder ownership and sharing
folders"


https://answers.microsoft.com/en-us/...6-f17de534bb30



Thanks, but never done this before.
Never needed it with shares before.

Fokke

On 7/22/2020 5:18 AM, Fokke Nauta wrote:
On 22/07/2020 01:21, Paul wrote:
knuttle wrote:
On 7/21/2020 3:50 PM, 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
Done right, you do not need a password on the shared computers, nor a
password to access the shared computer.

I have a desktop and a laptop that I share data, and sync the data
between them,Â* The shared folders are as easy to access as the Local
folder.

If when you try to access a shared drive, I have found it is a matter
of who owns the resource and who is trying to share it.Â* You can go
in and share a folder, but unless the account from which you are
working owns the folder, will appear on the other computer but ask
the user of the other computer for a password or something similar.

It an involved process, so do a search on folder ownership and change
all shared folders to be owned by the same account

I'd be a little careful with this advice.

I can find examples where "password protect shares" and using
an account with no password set, leads to "no burrito for you".
Microsoft has this listed on a web page as an expected result.
They specifically "deny" when you do that.

On older OSes, a combination of various things, the security was
quite lax and you would get away with it.

Now, you're in the Windows 10 group, and anarchy reins...
There are no free lunches in Windows 10. Everything goes on
your tab.

*******

what I do on my humble setup here, is log in as a local
account on the foreign machine.


Â*Â*Â*Â*Â* Typing machineÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Test machine
Â*Â*Â*Â*Â* username=BoltÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* username=Bullwinkle

Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* share=rumdisk

Â*Â*Â*Â*Â* Login to
Â*Â*Â*Â*Â* \\Test\rumdisk

Â*Â*Â*Â*Â* as bullwinkle:bullwinkle_password

And that seems to work for me. I cannot log into
the Test machine as "Bolt", as that won't work.

At one time, I could log into Test with Bullwinkle:1234 ,
in other words, a totally bogus password. And that doesn't
work all the time, either.

I have a Win98 VM. Guess what ? No authentication whatsoever.
Just works. And partially enabled by Windows 10 having
SMBV1 turned on.

Bottom line is, you have to log with a usernameassword that
exists on the remote machine, to overcome whatever obstacles
it's throwing up.

On a home LAN, the SIDs of the accounts are different.
Let's say that Bullwinkle exists on two machines, then
the SID on one machine for Bullwinkle could be 123 and
on the other it could be 456.

If I bring a Bullwinkle disk over to a second machine,
the green "takeown" bar appears, and restamps the files.
That happens, because I happen to belong to the administrator
group at the time, and there's sufficient elevation for it
to do that. If I look at the foreign disk now, I see

Â*Â*Â*Â*Â* Owner:Â* 123Â* \___ Two accounts at owner level
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* 456Â* /

The files have two owners, and voila, I have access to
the "foreign" disk.

When file sharing happens, notice what a mess that would be.
File sharing must be doing *something* to smooth over the
fact that no two things on a home LAN use the same
identifiers. And that suggests that the logging in step
is important - it might just be applying a transformation
to make the files accessible. Even though, strictly speaking,
the ownership is out of reach. It's because you selected
some setting where "Everyone" "Can make changes" and that
provided a means for the differences to be smoothed over
or smashed. You *did* give permission at some point.

"Advanced Sharing"

https://www.tenforums.com/attachment..._sharing-1.png


Now "Everyone", "Full Control", "OK"

https://www.tenforums.com/attachment..._sharing-3.png


And a ton more, here.

https://www.tenforums.com/tutorials/...dows-10-a.html


Â*Â*Â* Paul

Thanks, Paul.

I know how to share folders, done that many times.
As there was no password on the pc, I enabled sharing for Everyone with
full control. That did not work.
Then I added a password to the account of the pc, and enabled a share
for the user, with full control as well. This is the common way.
From the laptop I can see the shares of the pc but I can't open them.
When I try to open a share, the system asks for a password, but after
entering that nothing happens.
Another weird thing is that I cannot see the pc in the network.

This never happened to me before.

FokkeI said this before. Windows really doesn't know how to properly network
and I'll add, just for the fun of it, multitask. Anyway, I've found
that you have to open the Security tab on the folder's properties and
add 'Everyone' to it, with full control. It may not be right, but
that's what I do inside my home network, so that I can get to every PC
from every PC without it nagging for passwords.

On 22/07/2020 13:28, Todesco wrote:
On 7/22/2020 5:18 AM, Fokke Nauta wrote:
On 22/07/2020 01:21, Paul wrote:
knuttle wrote:
On 7/21/2020 3:50 PM, 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
Done right, you do not need a password on the shared computers, nor
a password to access the shared computer.

I have a desktop and a laptop that I share data, and sync the data
between them,Â* The shared folders are as easy to access as the Local
folder.

If when you try to access a shared drive, I have found it is a
matter of who owns the resource and who is trying to share it.Â* You
can go in and share a folder, but unless the account from which you
are working owns the folder, will appear on the other computer but
ask the user of the other computer for a password or something similar.

It an involved process, so do a search on folder ownership and
change all shared folders to be owned by the same account

I'd be a little careful with this advice.

I can find examples where "password protect shares" and using
an account with no password set, leads to "no burrito for you".
Microsoft has this listed on a web page as an expected result.
They specifically "deny" when you do that.

On older OSes, a combination of various things, the security was
quite lax and you would get away with it.

Now, you're in the Windows 10 group, and anarchy reins...
There are no free lunches in Windows 10. Everything goes on
your tab.

*******

what I do on my humble setup here, is log in as a local
account on the foreign machine.


Â*Â*Â*Â*Â* Typing machineÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Test machine
Â*Â*Â*Â*Â* username=BoltÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* username=Bullwinkle

Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* share=rumdisk

Â*Â*Â*Â*Â* Login to
Â*Â*Â*Â*Â* \\Test\rumdisk

Â*Â*Â*Â*Â* as bullwinkle:bullwinkle_password

And that seems to work for me. I cannot log into
the Test machine as "Bolt", as that won't work.

At one time, I could log into Test with Bullwinkle:1234 ,
in other words, a totally bogus password. And that doesn't
work all the time, either.

I have a Win98 VM. Guess what ? No authentication whatsoever.
Just works. And partially enabled by Windows 10 having
SMBV1 turned on.

Bottom line is, you have to log with a usernameassword that
exists on the remote machine, to overcome whatever obstacles
it's throwing up.

On a home LAN, the SIDs of the accounts are different.
Let's say that Bullwinkle exists on two machines, then
the SID on one machine for Bullwinkle could be 123 and
on the other it could be 456.

If I bring a Bullwinkle disk over to a second machine,
the green "takeown" bar appears, and restamps the files.
That happens, because I happen to belong to the administrator
group at the time, and there's sufficient elevation for it
to do that. If I look at the foreign disk now, I see

Â*Â*Â*Â*Â* Owner:Â* 123Â* \___ Two accounts at owner level
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* 456Â* /

The files have two owners, and voila, I have access to
the "foreign" disk.

When file sharing happens, notice what a mess that would be.
File sharing must be doing *something* to smooth over the
fact that no two things on a home LAN use the same
identifiers. And that suggests that the logging in step
is important - it might just be applying a transformation
to make the files accessible. Even though, strictly speaking,
the ownership is out of reach. It's because you selected
some setting where "Everyone" "Can make changes" and that
provided a means for the differences to be smoothed over
or smashed. You *did* give permission at some point.

"Advanced Sharing"

https://www.tenforums.com/attachment..._sharing-1.png


Now "Everyone", "Full Control", "OK"

https://www.tenforums.com/attachment..._sharing-3.png


And a ton more, here.

https://www.tenforums.com/tutorials/...dows-10-a.html


Â*Â*Â* Paul

Thanks, Paul.

I know how to share folders, done that many times.
As there was no password on the pc, I enabled sharing for Everyone
with full control. That did not work.
Then I added a password to the account of the pc, and enabled a share
for the user, with full control as well. This is the common way.
Â*From the laptop I can see the shares of the pc but I can't open them.
When I try to open a share, the system asks for a password, but after
entering that nothing happens.
Another weird thing is that I cannot see the pc in the network.

This never happened to me before.

FokkeI said this before.Â* Windows really doesn't know how to properly
network
and I'll add, just for the fun of it, multitask.Â* Anyway,Â* I've found
that you have to open the Security tab on the folder's properties and
add 'Everyone' to it, with full control.Â* It may not be right, but
that's what I do inside my home network, so that I can get to every PC
from every PC without it nagging for passwords.

It's surely not the best solution and I never needed to do so. I always
worked with the user name and password and it always worked.
But in this case I will follow your advice and see if it works.
I'm curious.

Fokke

On 7/22/2020 7:43 AM, Fokke Nauta wrote:
On 22/07/2020 13:28, Todesco wrote:
On 7/22/2020 5:18 AM, Fokke Nauta wrote:
On 22/07/2020 01:21, Paul wrote:
knuttle wrote:
On 7/21/2020 3:50 PM, 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
Done right, you do not need a password on the shared computers, nor
a password to access the shared computer.

I have a desktop and a laptop that I share data, and sync the data
between them,Â* The shared folders are as easy to access as the
Local folder.

If when you try to access a shared drive, I have found it is a
matter of who owns the resource and who is trying to share it.Â* You
can go in and share a folder, but unless the account from which you
are working owns the folder, will appear on the other computer but
ask the user of the other computer for a password or something
similar.

It an involved process, so do a search on folder ownership and
change all shared folders to be owned by the same account

I'd be a little careful with this advice.

I can find examples where "password protect shares" and using
an account with no password set, leads to "no burrito for you".
Microsoft has this listed on a web page as an expected result.
They specifically "deny" when you do that.

On older OSes, a combination of various things, the security was
quite lax and you would get away with it.

Now, you're in the Windows 10 group, and anarchy reins...
There are no free lunches in Windows 10. Everything goes on
your tab.

*******

what I do on my humble setup here, is log in as a local
account on the foreign machine.


Â*Â*Â*Â*Â* Typing machineÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Test machine
Â*Â*Â*Â*Â* username=BoltÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* username=Bullwinkle

Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* share=rumdisk

Â*Â*Â*Â*Â* Login to
Â*Â*Â*Â*Â* \\Test\rumdisk

Â*Â*Â*Â*Â* as bullwinkle:bullwinkle_password

And that seems to work for me. I cannot log into
the Test machine as "Bolt", as that won't work.

At one time, I could log into Test with Bullwinkle:1234 ,
in other words, a totally bogus password. And that doesn't
work all the time, either.

I have a Win98 VM. Guess what ? No authentication whatsoever.
Just works. And partially enabled by Windows 10 having
SMBV1 turned on.

Bottom line is, you have to log with a usernameassword that
exists on the remote machine, to overcome whatever obstacles
it's throwing up.

On a home LAN, the SIDs of the accounts are different.
Let's say that Bullwinkle exists on two machines, then
the SID on one machine for Bullwinkle could be 123 and
on the other it could be 456.

If I bring a Bullwinkle disk over to a second machine,
the green "takeown" bar appears, and restamps the files.
That happens, because I happen to belong to the administrator
group at the time, and there's sufficient elevation for it
to do that. If I look at the foreign disk now, I see

Â*Â*Â*Â*Â* Owner:Â* 123Â* \___ Two accounts at owner level
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* 456Â* /

The files have two owners, and voila, I have access to
the "foreign" disk.

When file sharing happens, notice what a mess that would be.
File sharing must be doing *something* to smooth over the
fact that no two things on a home LAN use the same
identifiers. And that suggests that the logging in step
is important - it might just be applying a transformation
to make the files accessible. Even though, strictly speaking,
the ownership is out of reach. It's because you selected
some setting where "Everyone" "Can make changes" and that
provided a means for the differences to be smoothed over
or smashed. You *did* give permission at some point.

"Advanced Sharing"

https://www.tenforums.com/attachment..._sharing-1.png


Now "Everyone", "Full Control", "OK"

https://www.tenforums.com/attachment..._sharing-3.png


And a ton more, here.

https://www.tenforums.com/tutorials/...dows-10-a.html


Â*Â*Â* Paul

Thanks, Paul.

I know how to share folders, done that many times.
As there was no password on the pc, I enabled sharing for Everyone
with full control. That did not work.
Then I added a password to the account of the pc, and enabled a share
for the user, with full control as well. This is the common way.
Â*From the laptop I can see the shares of the pc but I can't open
them. When I try to open a share, the system asks for a password, but
after entering that nothing happens.
Another weird thing is that I cannot see the pc in the network.

This never happened to me before.

FokkeI said this before.Â* Windows really doesn't know how to properly
network
and I'll add, just for the fun of it, multitask.Â* Anyway,Â* I've found
that you have to open the Security tab on the folder's properties and
add 'Everyone' to it, with full control.Â* It may not be right, but
that's what I do inside my home network, so that I can get to every PC
from every PC without it nagging for passwords.

It's surely not the best solution and I never needed to do so. I always
worked with the user name and password and it always worked.
But in this case I will follow your advice and see if it works.
I'm curious.

Fokke
You may have to change the ownership of the shared folders to
"Everyone". I have found that only the owner of a folder may share it.

Fokke Nauta wrote:
On 22/07/2020 13:28, Todesco wrote:
On 7/22/2020 5:18 AM, Fokke Nauta wrote:
On 22/07/2020 01:21, Paul wrote:
knuttle wrote:
On 7/21/2020 3:50 PM, 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
Done right, you do not need a password on the shared computers, nor
a password to access the shared computer.

I have a desktop and a laptop that I share data, and sync the data
between them, The shared folders are as easy to access as the
Local folder.

If when you try to access a shared drive, I have found it is a
matter of who owns the resource and who is trying to share it. You
can go in and share a folder, but unless the account from which you
are working owns the folder, will appear on the other computer but
ask the user of the other computer for a password or something
similar.

It an involved process, so do a search on folder ownership and
change all shared folders to be owned by the same account

I'd be a little careful with this advice.

I can find examples where "password protect shares" and using
an account with no password set, leads to "no burrito for you".
Microsoft has this listed on a web page as an expected result.
They specifically "deny" when you do that.

On older OSes, a combination of various things, the security was
quite lax and you would get away with it.

Now, you're in the Windows 10 group, and anarchy reins...
There are no free lunches in Windows 10. Everything goes on
your tab.

*******

what I do on my humble setup here, is log in as a local
account on the foreign machine.


Typing machine Test machine
username=Bolt username=Bullwinkle

share=rumdisk

Login to
\\Test\rumdisk

as bullwinkle:bullwinkle_password

And that seems to work for me. I cannot log into
the Test machine as "Bolt", as that won't work.

At one time, I could log into Test with Bullwinkle:1234 ,
in other words, a totally bogus password. And that doesn't
work all the time, either.

I have a Win98 VM. Guess what ? No authentication whatsoever.
Just works. And partially enabled by Windows 10 having
SMBV1 turned on.

Bottom line is, you have to log with a usernameassword that
exists on the remote machine, to overcome whatever obstacles
it's throwing up.

On a home LAN, the SIDs of the accounts are different.
Let's say that Bullwinkle exists on two machines, then
the SID on one machine for Bullwinkle could be 123 and
on the other it could be 456.

If I bring a Bullwinkle disk over to a second machine,
the green "takeown" bar appears, and restamps the files.
That happens, because I happen to belong to the administrator
group at the time, and there's sufficient elevation for it
to do that. If I look at the foreign disk now, I see

Owner: 123 \___ Two accounts at owner level
456 /

The files have two owners, and voila, I have access to
the "foreign" disk.

When file sharing happens, notice what a mess that would be.
File sharing must be doing *something* to smooth over the
fact that no two things on a home LAN use the same
identifiers. And that suggests that the logging in step
is important - it might just be applying a transformation
to make the files accessible. Even though, strictly speaking,
the ownership is out of reach. It's because you selected
some setting where "Everyone" "Can make changes" and that
provided a means for the differences to be smoothed over
or smashed. You *did* give permission at some point.

"Advanced Sharing"

https://www.tenforums.com/attachment..._sharing-1.png


Now "Everyone", "Full Control", "OK"

https://www.tenforums.com/attachment..._sharing-3.png


And a ton more, here.

https://www.tenforums.com/tutorials/...dows-10-a.html


Paul

Thanks, Paul.

I know how to share folders, done that many times.
As there was no password on the pc, I enabled sharing for Everyone
with full control. That did not work.
Then I added a password to the account of the pc, and enabled a share
for the user, with full control as well. This is the common way.
From the laptop I can see the shares of the pc but I can't open
them. When I try to open a share, the system asks for a password, but
after entering that nothing happens.
Another weird thing is that I cannot see the pc in the network.

This never happened to me before.

FokkeI said this before. Windows really doesn't know how to properly
network
and I'll add, just for the fun of it, multitask. Anyway, I've found
that you have to open the Security tab on the folder's properties and
add 'Everyone' to it, with full control. It may not be right, but
that's what I do inside my home network, so that I can get to every PC
from every PC without it nagging for passwords.

It's surely not the best solution and I never needed to do so. I always
worked with the user name and password and it always worked.
But in this case I will follow your advice and see if it works.
I'm curious.

Fokke

In services.msc , check and make the two services with "Function"
in the name, are running.

One of those is what makes the network name appear (in combination
with SMBV1 being enabled, if this is an SMBV1 case). The Function one
has something to do with nameserving. It shouldn't really affect
access to an individual share, as you're experiencing.

Paul

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

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.

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

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

"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.