Re: My Documents - repost

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Malke,
Thanks for your further response.
However, there still seems to be some confusion regarding what the problem
is -- probably my fault.

Yes, apparently those permissions are set incorrectly if you are unable to
map to a share on the workstations.

It is not, as you stated that I am unable to map to a share on the
workstations. We have successfully mapped workstations to that share for the
past 5 years -- and at another location for approximately 10 years. The
difference between then and now is that there was only a single
username/password combination used on the file-server -- that is, for
someone who is sitting at the file-server and logging onto that computer.
Now, however, we are attempting to have a second username/password
combination available on the file-server. But, logging on under that second
account seems to (temporarily) invalidate the mapping on the other
workstations. These other workstations had previously mapped their
"P"-drives to that shared folder and at the time of the mapping had to
supply the correct username/password combination in order to complete the
mapping.

Nothing has changed in regards to how the workstations log onto the
network. The accounts they use to log onto the network are unchanged and are
still present in the file-server's User Accounts. Privileges haven't changed
in regards to these accounts, nor do they need to. The only thing that has
changed is that someone sitting at the file-server has logged onto the
file-server with a different username and password than what was originally
used on the workstations in mapping to the share on the file-server.

that simply adding a user account to a computer should not make any
difference to permissions on a share on that computer.

It's not just adding another user account to the file-server's User
Accounts; it's also sitting at the file-server and logging in under a
different username and password than what was used in mapping the
workstations' "P"-drives. Perhaps, as you suggest, this should make no
difference. Perhaps the problem is simply due to my trying to rename the
orginal account on the file-server, instead of creating a brand new account,
etc., as you very helpfully pointed out.

is there a reason you are mapping the share instead of just making a
shortcut to it?

Yes. For database operations, we want access to this shared folder to be
seemless; i.e., no prompting in the middle of an operation. That is why the
workstations have a "P"-drive mapped -- for reading and writing data to the
backend database located on the file-server.

You've got something set wrong, obviously in the permissions

Yes, you are correct. In the permissions for the shared folder, username1
was not specifically listed. This was not a problem during the past 5 years,
as long as whoever physically logged onto the file-server (i.e., sitting at
the file-server) did so using username1/password1. When I clicked properties
for the shared folder and specifically added username1, then the mapped link
continued to function even though someone physically logged off of the
file-server as username1 and logged on under username2 -- the other
workstations did not lose their link to the shared folder. Thanks, Malke,
for pushing me to figure this out!

Concerning My Documents: what user groups and/or permissions need to be set
for two user accounts, both with Adminstrator rights, to not be able to see
each other's My Documents files? I created a brand new user account, but
could still read/write/delete the files from the original user's account.
Should only CREATOR OWNER having any privileges for My Documents?

Thanks for your patience, Malke
Mark


"Malke" <notreally@xxxxxxxxxxxxxxx> wrote in message
news:OGkxpDH9HHA.1900@xxxxxxxxxxxxxxxxxxxxxxx
FPS, Romney wrote:
Thanks, Malke. I appreciate the time you took in making your response.

But you're just repeating what you've already said. Yes, I know the
pseudo-server is XP Pro. Yes, apparently you've set permissions on the
shared folder at the pseudo-server. Yes, apparently those permissions
are set incorrectly if you are unable to map to a share on the
workstations. As an aside, is there a reason you are mapping the share
instead of just making a shortcut to it? You might want to try just
making a shortcut to the share instead.

Access to this shared folder is the issue now that a second user account
has
been added to the file-server and which is intended to be used ON the
file-server by one particular person. That is, Username1/Password1 is
the
original user account used on the file-server by staff who use the
pseudo
file-server as a workstation, as well as being the account that other
workstations use when logging onto their "P"-drive in order to access
the
shared folder.

Again, the above doesn't make any sense to me either from a
what-is-happening standpoint or from a practical day-to-day work
standpoint. Just repeating the information doesn't help. My response is
that simply adding a user account to a computer should not make any
difference to permissions on a share on that computer. You've got
something set wrong, obviously in the permissions or in the quotas or in
the number of concurrent inbound connections, or... Since I can't see
your computers I can't be sure where the tangle is. You also haven't
mentioned what is *in* the share that people are using. Perhaps it is a
database or a program and there are licensing limits or the like.

And if you want to allow someone to use the pseudo-server for work
that's your decision but from a good IT standpoint, it's a bad decision.
I hope you have a backup strategy in place and being implemented because
allowing anyone to touch a server except for maintenance and backup will
cause Tears Before Bedtime sooner or later.

Try making a different user account for the person who is sitting down
at the pseudo-server and adding that user account to the permissions on
the share. Other than that I have no more ideas since as I already said
I don't know exactly what you are doing and why you would allow someone
to use the pseudo-server as a workstation.

If you still can't figure it out, a better solution will be to have a
local professional come on-site and take a look and set you up properly.
This will not be someone from a BigComputerStore/GeekSquad type of
place. Ask friends and colleagues for recommendations. Someone who can
actually see the computers may be able to pinpoint the source of the
troubles immediately where people just reading about it in a newsgroup
cannot.


Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User


.

Relevant Pages

  • Re: permissions in active directory
    ... Then the users need a domain user account to access the shares on the DC. ... Better join the machines to the domain and configure user accounts and dsiable the local machine accounts, move all data from workstations to the server and configure a share security regarding to the needs of your company structure. ... What share permission and what NTFS permission did you configure? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Remotely changing admin group membership on clients
    ... membership of the group and set it to what you want. ... This will add the specific group but will only work when the machines are ... > workstations in the domain. ... > method to be able to place a domain user account or global group in the ...
    (microsoft.public.win2000.security)
  • Re: My Documents - repost
    ... I don't know if you can help with another issue -- This particular computer that now has a second user account, ... You also didn't mention 1) what versions of XP are running, Home or Pro; 2) how many computers are on the network. ... You can create whatever shares you want, such as your "P" drive and because the pseudo-server has Pro, you can set very fine-grained permissions and restrictions on those shares. ... You don't make files private on the workstations. ...
    (microsoft.public.windowsxp.general)
  • Re: Add workstatiosn to the domain is OK, but...
    ... I'm trying to do the same thing: Create a user account which ONLY can Add / ... Re-add machines to the Active Directory. ... The original poster mentioned he " gave 'add workstations to the domain' ... Re-Add machine accounts into the Active directory? ...
    (microsoft.public.windows.server.active_directory)
  • Windows server rsync-like utility
    ... back up all the workstations' partitions. ... software like rsync will make a synchronization from ... E$ and other administrative shares to the file-server. ... Can you say if there is a windows server utility which can do that? ...
    (microsoft.public.windows.server.active_directory)