workgroup sharing

Is it possible to use NTFS permissions for file security in an XPpro
workgroup environment?
Lets say I have four machines and I set all the users and passwords
identical on each one.
I set a directory to be only available to me.
Should I be able to manipulate that directory from another machine on the
workgroup using my login password? Similiar to the way a domain works but
without the centralized administration.
I tried, and at best was greeted with a greyed out Guest prompt which
allowed me access but I couldn't change anything.
Turning on simple file sharing resolved that but now the doors are wide
open. Any solution short of a domain model?

Sure, you should be able to do that. If you can't make changes, you may want to take over owner.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<(E-Mail Removed)> wrote in message news:%(E-Mail Removed)...
Is it possible to use NTFS permissions for file security in an XPpro
workgroup environment?
Lets say I have four machines and I set all the users and passwords
identical on each one.
I set a directory to be only available to me.
Should I be able to manipulate that directory from another machine on the
workgroup using my login password? Similiar to the way a domain works but
without the centralized administration.
I tried, and at best was greeted with a greyed out Guest prompt which
allowed me access but I couldn't change anything.
Turning on simple file sharing resolved that but now the doors are wide
open. Any solution short of a domain model?

who would be the owner? "Me" from the remote machine or "Me" from the machine that the directory is on?
It appears that the credentials change when I connect over the network. Not to mention that the only prompt I get when I connect the the remote share is "guest".
"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
Sure, you should be able to do that. If you can't make changes, you may want to take over owner.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<(E-Mail Removed)> wrote in message news:%(E-Mail Removed)...
Is it possible to use NTFS permissions for file security in an XPpro
workgroup environment?
Lets say I have four machines and I set all the users and passwords
identical on each one.
I set a directory to be only available to me.
Should I be able to manipulate that directory from another machine on the
workgroup using my login password? Similiar to the way a domain works but
without the centralized administration.
I tried, and at best was greeted with a greyed out Guest prompt which
allowed me access but I couldn't change anything.
Turning on simple file sharing resolved that but now the doors are wide
open. Any solution short of a domain model?

If you are using a workgroup configuration each machine maintains its
own account permissions. So if you want all the members of the
workgroup to be able to access resources on all the other machines you
will need to replicate their accounts on each machine where a resource
resides that you want them to have access to. This is a pain in the
butt. This is one of the biggest deficiencies in using workgroups
instead of a domain. You have no centralized management.

John Strohecker
MCSE

I get that part, and yes it's a pain but there are only four machines on it,
the other 30 are on a domain but these needed to be isolated.
The problem I have is that even though the accounts are hand replicated to
each machine, the only way to access them is to use the "simple file
sharing" mode and a blank guest password. It seems the credentials, though
identical locally, get modified (possibly to identify the sending machine)
over the network.
i.e.
User1 on Machine1
User2 on Machine2
If User1 tries to access a directory on Machine2, the credentials that
Machine2 sees become "Machine1\User1" instead of just "User1".
Does that make sense? Am I getting this right?



"John" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> If you are using a workgroup configuration each machine maintains its
> own account permissions. So if you want all the members of the
> workgroup to be able to access resources on all the other machines you
> will need to replicate their accounts on each machine where a resource
> resides that you want them to have access to. This is a pain in the
> butt. This is one of the biggest deficiencies in using workgroups
> instead of a domain. You have no centralized management.
>
> John Strohecker
> MCSE
>

You got that 100% right. Using a peer-to-peer newtorking setup (which
is precisely what workgroups are) there is no central repository of
user rights and permissions....without that centralized info machine2
will never allow machine1\User1 to access any information without
entering credentials that are specific to machine2's security database.


As long as the usernames and passwords are identical then the user's
shouldn't be bothered by this...except for the fact that each time they
need to access a shared resource on another computer they will be
promoted for username and password.

John

You got that 100% right. Using a peer-to-peer newtorking setup (which
is precisely what workgroups are) there is no central repository of
user rights and permissions....without that centralized info machine2
will never allow machine1\User1 to access any information without
entering credentials that are specific to machine2's security database.


As long as the usernames and passwords are identical then the users
shouldn't be bothered by this...except for the fact that each time they
need to access a shared resource on another computer they will be
promoted for username and password.

John

OK thats exactly what I see. Thanks for the confirmation.

"John" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> You got that 100% right. Using a peer-to-peer newtorking setup (which
> is precisely what workgroups are) there is no central repository of
> user rights and permissions....without that centralized info machine2
> will never allow machine1\User1 to access any information without
> entering credentials that are specific to machine2's security database.
>
>
> As long as the usernames and passwords are identical then the users
> shouldn't be bothered by this...except for the fact that each time they
> need to access a shared resource on another computer they will be
> promoted for username and password.
>
> John
>