Network login problem

[Guest]

As per advice here in the ng, I have switched off simple file sharing under
my WinXP Pro in an attempt to make it behave like Win2K, and prompt all
outside access requests for a login that resides on that machine.

I had originally made 2 shares before making the change, and 2 shares since.
I can access the 2 original shares, but not the 2 new ones (access denied -
contact the Administrator etc...). I know why this is, but I cannot figure
out how to resolve it.

When the original shares were made with SFS 'on', under the security tab an
entry was made for 'everybody', full permissions. When making the second 2
shares after turning SFS 'off', this entry under the security tab is not
there. That this entry is in the 2 original shares is the reason I'm allowed
to still access them, and their absence the reason I am denied access to the
2 new shares.

The 'remote' computer I used to access the shares was never requested to
'login' under SFS. Now that SFS is disabled on the computer with the shares,
I am -still- not being prompted to login, and therefore I am not receiving
the proper permissions. How on -EARTH- do I get this thing to ask me to
login? Is there a cache to clear, cookie to kill... what??

When I access the shared computer with a different computer that had never
accessed before when SFS was 'on', it is prompted for a login, grants the
login, and allows me access to all 4 shares! This is driving me insane... = /

This has gotten technically way out of hand... under Win2K, you just create
the share. When someone tried to connect under My Network Places, you were
asked to login (even if all you wanted to do was to send a print job to the
DeskJet). It would accept only valid logins from users setup on the host
machine. That is all I want back, and by gosh it cannot be this hard... Chuck
originally got me going in the right direction with shutting off SFS and
setting Local Policies (which were what he suggested by default - no changes
necessary). I don't want anything more complicated than I had under Win2K,
but the solution so far is not prompting me to login from one computer, but
is on the other. Thanks for any advice anyone has...

-GitterDone

 

[Chuck]

As per advice here in the ng, I have switched off simple file sharing under
my WinXP Pro in an attempt to make it behave like Win2K, and prompt all
outside access requests for a login that resides on that machine.

I had originally made 2 shares before making the change, and 2 shares since.
I can access the 2 original shares, but not the 2 new ones (access denied -
contact the Administrator etc...). I know why this is, but I cannot figure
out how to resolve it.

When the original shares were made with SFS 'on', under the security tab an
entry was made for 'everybody', full permissions. When making the second 2
shares after turning SFS 'off', this entry under the security tab is not
there. That this entry is in the 2 original shares is the reason I'm allowed
to still access them, and their absence the reason I am denied access to the
2 new shares.

The 'remote' computer I used to access the shares was never requested to
'login' under SFS. Now that SFS is disabled on the computer with the shares,
I am -still- not being prompted to login, and therefore I am not receiving
the proper permissions. How on -EARTH- do I get this thing to ask me to
login? Is there a cache to clear, cookie to kill... what??

When I access the shared computer with a different computer that had never
accessed before when SFS was 'on', it is prompted for a login, grants the
login, and allows me access to all 4 shares! This is driving me insane... = /

This has gotten technically way out of hand... under Win2K, you just create
the share. When someone tried to connect under My Network Places, you were
asked to login (even if all you wanted to do was to send a print job to the
DeskJet). It would accept only valid logins from users setup on the host
machine. That is all I want back, and by gosh it cannot be this hard... Chuck
originally got me going in the right direction with shutting off SFS and
setting Local Policies (which were what he suggested by default - no changes
necessary). I don't want anything more complicated than I had under Win2K,
but the solution so far is not prompting me to login from one computer, but
is on the other. Thanks for any advice anyone has...

-GitterDone

With SFS disabled, and Classic authentication, you authenticate automatically,
if the account / password that you're logged on with locally is duplicated on
the server.

As an administrator, you're entitled to add entries to the Access Control List
for any share that you control. Did you try adding the special group Everyone
to the shares, on the server, that you can't access from the client?

Are you using the same account to login locally to the second computer (the one
that "had never accessed before when SFS was 'on'"), as you are to login locally
to the first?

Remember "Everyone" in an Access Control List means all authenticated users. If
you want to be presented with a login screen, have an account on the server
that's not used for logging in locally to the clients, and give appropriate
permissions to that account.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.