"brush-head" <brushh***@discussions.microsoft.com> wrote in message
news:5B428771-5FB6-4BDE-80DF-CC0A5A7EE959@microsoft.com...
> We have a temp who must have access to files and folders on a home drive
> (h:)
> on an NT4 Server belonging to the person she is standing in for - in other
> words the temp didn't create them. Even though the temp has been given
> full
> rights at folder level and share level documents would only open as read
> only. The only way we have found to get around the situation is to make
> the
> temp a domain admin!!!!!
>
> It seems to be some sort of rights issue between NT4 domain and XP
> workstations. Everything in the share shows as read only under XP. If you
> have any suggestions I will gladly take them on board and test them so we
> can
> get a proper resolution to this issue.
>
> Many thanks.
>

> "brush-head" <brushh***@discussions.microsoft.com> wrote in message
> news:5B428771-5FB6-4BDE-80DF-CC0A5A7EE959@microsoft.com...
>
>>We have a temp who must have access to files and folders on a home drive
>>(h:)
>>on an NT4 Server belonging to the person she is standing in for - in other
>>words the temp didn't create them. Even though the temp has been given
>>full
>>rights at folder level and share level documents would only open as read
>>only. The only way we have found to get around the situation is to make
>>the
>>temp a domain admin!!!!!
>>
>>It seems to be some sort of rights issue between NT4 domain and XP
>>workstations. Everything in the share shows as read only under XP. If you
>>have any suggestions I will gladly take them on board and test them so we
>>can
>>get a proper resolution to this issue.
>>
>>Many thanks.
>>
>
>
>
> You need to go to the server, and go to the folder which is being mapped as
> the temp's H drive.
>
> Check both the share permissions and the NTFS permissions ( security tab )
> and add her as necessary with 'change' permissions.
>

"Ron Lowe" wrote:

> "brush-head" <brushh***@discussions.microsoft.com> wrote in message
> news:5B428771-5FB6-4BDE-80DF-CC0A5A7EE959@microsoft.com...
> > We have a temp who must have access to files and folders on a home drive
> > (h:)
> > on an NT4 Server belonging to the person she is standing in for - in other
> > words the temp didn't create them. Even though the temp has been given
> > full
> > rights at folder level and share level documents would only open as read
> > only. The only way we have found to get around the situation is to make
> > the
> > temp a domain admin!!!!!
> >
> > It seems to be some sort of rights issue between NT4 domain and XP
> > workstations. Everything in the share shows as read only under XP. If you
> > have any suggestions I will gladly take them on board and test them so we
> > can
> > get a proper resolution to this issue.
> >
> > Many thanks.
> >
>
>
> You need to go to the server, and go to the folder which is being mapped as
> the temp's H drive.
>
> Check both the share permissions and the NTFS permissions ( security tab )
> and add her as necessary with 'change' permissions.
>
> --
> Best Regards
> Ron Lowe
> MVP - Windows Networking
>
>
>

>> "brush-head" <brushh***@discussions.microsoft.com> wrote in message
>> news:5B428771-5FB6-4BDE-80DF-CC0A5A7EE959@microsoft.com...
>> > We have a temp who must have access to files and folders on a home
>> > drive
>> > (h:)
>> > on an NT4 Server belonging to the person she is standing in for - in
>> > other
>> > words the temp didn't create them. Even though the temp has been given
>> > full
>> > rights at folder level and share level documents would only open as
>> > read
>> > only. The only way we have found to get around the situation is to make
>> > the
>> > temp a domain admin!!!!!


>> You need to go to the server, and go to the folder which is being mapped
>> as
>> the temp's H drive.
>>
>> Check both the share permissions and the NTFS permissions ( security
>> tab )
>> and add her as necessary with 'change' permissions.


> Sorry Ron we'd already tried that I'm afraid and it doesn't work. If you
> have
> any other ideas about where we might look we'd be really grateful.
> If we get an answer we'll post back to the group.
>

"Ron Lowe" wrote:

> >> "brush-head" <brushh***@discussions.microsoft.com> wrote in message
> >> news:5B428771-5FB6-4BDE-80DF-CC0A5A7EE959@microsoft.com...
> >> > We have a temp who must have access to files and folders on a home
> >> > drive
> >> > (h:)
> >> > on an NT4 Server belonging to the person she is standing in for - in
> >> > other
> >> > words the temp didn't create them. Even though the temp has been given
> >> > full
> >> > rights at folder level and share level documents would only open as
> >> > read
> >> > only. The only way we have found to get around the situation is to make
> >> > the
> >> > temp a domain admin!!!!!
>
>
> >> You need to go to the server, and go to the folder which is being mapped
> >> as
> >> the temp's H drive.
> >>
> >> Check both the share permissions and the NTFS permissions ( security
> >> tab )
> >> and add her as necessary with 'change' permissions.
>
>
> > Sorry Ron we'd already tried that I'm afraid and it doesn't work. If you
> > have
> > any other ideas about where we might look we'd be really grateful.
> > If we get an answer we'll post back to the group.
> >
>
>
>
> There is nowhere else, I'm afraid.
>
> The access permissions are determined on the server.
> You need to look at the permissions more closely.
>
> First, you need to be sure of who she is logging in as.
> She's got an account on the domain, and logging in to that, right?
> Are there any errors during the logon?
>
> Looking at the user and groups that have access,
> can you see where the temp fits in to the existing permissions?
>
> Do you know what groups she is a member of?
>
> You need to be able to answer the question:
> Why exacly *should* she have permission?
> Exactly which entry in the list of permissions *should* be granting her the
> access, but is not?
>
> This needs checked on both the share and NTFS permissions.
>
> The concept of making a temp a Domain Admin is fairly ludicrous!
> This just goes to demonstrate that it *is*  a permissions issue on the
> server, as far as I can see.
>
> --
> Best Regards
> Ron Lowe
> MVP - Windows Networking
>
>
>