I am having trouble setting up a secure folder on a XP Pro box. I have gone
in, created the folder, Set to share permission are everyone.
There are two workgroups. I want one workgroup to have access to these
folders and the other - not-.
I have tried to set it up wide open first. As is is now the folder will
show up on outside machines if found through 'add network place' and digging
through the entire network tree. I can slect and add it but when I try to
access it = 'denied'
Where coudld I go to get the specific procedure for accomplishing this.
The bottom line is I need two computes to have access and the rest = not. I
could change the workgrouop names if that would help.
I am familiar with stright up file sharing. The permissions part has me lost.
There are other forlder set with the name like BOB$ What does the $ do and
can it help in this case.

Thanks = Gaddy

On Wed, 22 Feb 2006 15:30:27 -0800, "Paul Gadebusch (Gaddy)" <Paul Gadebusch
(Gaddy)@discussions.microsoft.com> wrote:

>I am having trouble setting up a secure folder on a XP Pro box. I have gone
>in, created the folder, Set to share permission are everyone.
>There are two workgroups. I want one workgroup to have access to these
>folders and the other - not-.
>I have tried to set it up wide open first. As is is now the folder will
>show up on outside machines if found through 'add network place' and digging
>through the entire network tree. I can slect and add it but when I try to
>access it = 'denied'
>Where coudld I go to get the specific procedure for accomplishing this.
>The bottom line is I need two computes to have access and the rest = not. I
>could change the workgrouop names if that would help.
>I am familiar with stright up file sharing. The permissions part has me lost.
>There are other forlder set with the name like BOB$ What does the $ do and
>can it help in this case.
>
>Thanks = Gaddy

Gaddy,

The "access denied" error is very well known, and can have any of several
possible causes. One of the most common would be a misconfigured or overlooked
personal firewall, or other security component. There are several other
possibilities too, and any might be the cause of your problem. Read this article
with an open mind.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/1...isibility.html

Is Simple File Sharing enabled or disabled?

Bob$ is an administrative share, and can only be accessed by an administrator.
It won't be listed in Network Neighborhood. An administrative share is used
sometimes to prevent unauthorised folks from accessing a share, if by not
telling the undesired folks what the share is will reliably prevent them from
ever accessing it.

You can't restrict access by computer, you need to do so by user. You'll have
to disable Simple File Sharing, and setup accounts on the server (where the
shares are), and the 2 clients (where the 2 users are). And you'll have to
synchronise passwords on all 3 computers.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help>
http://nitecruzr.blogspot.com/2005/0...s-xp.html#Help

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.