T
Tim David
We have an NT Domain with NT and W2k Servers and XP clients. We
currently use WINS for name resolution
We have many shared folders on the servers, our standard way of
setting the permissions is to allow the required NT groups Full Contol
at the Share level and then Modify/Read etc at the NT level.
One particular user, a member of the 'HR' NT group, reported that they
could not access a (non-hidden) share (\\server1\HR) that they needed
to update. They previously could access it. The error message they
were receiving was the same as the one you get when you do not have
Share level permissions to a shared folder.
Checking all the setting revealed that the permissions were set
correctly, the 'HR' group had Full Control at the Share Level and
Modify at the NT level. I also checked that there were no Deny
permissions at a higher level. The share in question is four levels
down the NT folder structure on the server's drive, there is also a
hidden share a couple of levels up (\\server1\Resources$) which has
Everyone Read permissions so if you know how to you can drill down to
the share in question.
I, as Domain Admin, checked that I could access the share from
Start>Run on my PC, which I could.
I then set up a copy of the user's user account, in the same NT groups
and tested access on a standard build PC, which was OK
I then logged onto the user's PC with my account and attempted access
to the \\server1\HR share and got 'network path not found' error.
Strangely the only share on server1 that I could 'see' from the user's
PC was \\server1\Resources, however this only showed one of the folder
it contained. When I say 'see' I mean the list of available shares
that appear once the \\server part of the path has been type into the
Run command. This share is supposed to be hidden and thus hould not
appear, also there are several other shares that should and did not.
All this implies that the problem lies with the PC rather than the
use's account.
Does anyone have any ideas?
Tim
currently use WINS for name resolution
We have many shared folders on the servers, our standard way of
setting the permissions is to allow the required NT groups Full Contol
at the Share level and then Modify/Read etc at the NT level.
One particular user, a member of the 'HR' NT group, reported that they
could not access a (non-hidden) share (\\server1\HR) that they needed
to update. They previously could access it. The error message they
were receiving was the same as the one you get when you do not have
Share level permissions to a shared folder.
Checking all the setting revealed that the permissions were set
correctly, the 'HR' group had Full Control at the Share Level and
Modify at the NT level. I also checked that there were no Deny
permissions at a higher level. The share in question is four levels
down the NT folder structure on the server's drive, there is also a
hidden share a couple of levels up (\\server1\Resources$) which has
Everyone Read permissions so if you know how to you can drill down to
the share in question.
I, as Domain Admin, checked that I could access the share from
Start>Run on my PC, which I could.
I then set up a copy of the user's user account, in the same NT groups
and tested access on a standard build PC, which was OK
I then logged onto the user's PC with my account and attempted access
to the \\server1\HR share and got 'network path not found' error.
Strangely the only share on server1 that I could 'see' from the user's
PC was \\server1\Resources, however this only showed one of the folder
it contained. When I say 'see' I mean the list of available shares
that appear once the \\server part of the path has been type into the
Run command. This share is supposed to be hidden and thus hould not
appear, also there are several other shares that should and did not.
All this implies that the problem lies with the PC rather than the
use's account.
Does anyone have any ideas?
Tim