Michael C <> wrote:
> I have a small network with 10 computers all in the workgroup
> WORKGROUP (no domain). One of those computers is running Windows
> Server 2003 (I'll call this one theserver), 2 are running Windows
> Vista Premium, 6 others are running Windows XP Pro, and one is
> running Windows 2000.
>
> On theserver, there is a directory (I'll call this directory thedir)
> that I need to give both read and write access to from 4 of those
> computers (both Vistas, one XP, and the 2000), and no access to from
> the others. On theserver, I created a new user (I'll call this user
> bob), and gave it a password (let's say, swordfish).
>
> I shared thedir under the name thedir. Then, I set both the sharing
> permissions and security permissions on it so that only the
> Administrator account on theserver, and bob could read or write to it,
> then I ran this command on each of the 4 computers:
>
> net use z: \\theserver\thedir swordfish /user:bob /persistent:yes
>
> This worked ok, but the next day after all the computer had been
> rebooted, all the z drives remained under "My Computer", but trying to
> open them gave an access denied error. I create a batch file that
> reconnect to thedirs with the above code and put it in the startup
> folder of all computers that needed to access it.
>
> That works, but it seems like a messy workaround that's bound to cause
> problems. So what I'm asking is how to ensure thedir is accessible to
> those 4 computers with the proper permissions, even after restart.
> Thanks in advace for any help you can provide, and thanks for reading.
What you're describing would be a nonissue if you just dcpromo'd the W2003
box and configured AD. I don't see the point of workgroups when you've got
Windows server, nor when you have more than a small handful of PCs.
Workgroups are an immense pain to support, and difficult to secure.
|
Similar Threads
Linear Mode
