access to shares in a workgroup

[Roberto Carraro]

Hello,
I would like to better understand the process below.

In a workgroup network, when I try to connect to a share on pcA, and
there isn't the equivalent username-password that I used to logon to
pcB, it asks me for username and password.
After having input userid and psw, I won't have to input them anymore,
in future connections.

How does it work?
How long does it store information about the userid and psw that I
typed before?
Is there a possiblity to change this default behaviour and force users
to always retype them?

Thanks!
Roberto

 

[Herb Martin]

I would like to better understand the process below.

In a workgroup network, when I try to connect to a share on pcA, and
there isn't the equivalent username-password that I used to logon to
pcB, it asks me for username and password.

In a workgroup, every machine has a separate "user accounts
database" -- so users must have an account on each machine.

The account Machine1\usernameA and OtherMachine\usernameA
are TWO DIFFERENT accounts.

There is however a "workgroup feature" where if the two accounts
are named the same and use the same password an automatic
authentication is performed so that it ACTS LIKE the account is
shared (somewhat.)

After having input userid and psw, I won't have to input them anymore,
in future connections.

For that session. Once you authenticate to a particular machine,
that authentication is used to connect to any or all resources there.
Multiple connections use the already acquired credentials and
access.

How does it work?

See above.

How long does it store information about the userid and psw that I
typed before?

Probably until logoff but there might be a shorter time.

Is there a possiblity to change this default behaviour and force users
to always retype them?

Not for second and third etc. resources. The user is already authenticated.

Most people confuse the following issues: Authentication, Logon, and
Resource mapping or usage.

They are RELATED but not the same thing.

E.G., Logon (normally) requires authentication but authentication
doesn't always lead to a logon etc.

And, a single authentication can be used for access to many resources
(where that authentication is also valid.)