Mapped Drive vs Actual Drive - Access issues

  • Thread starter Thread starter PDCCnet
  • Start date Start date
P

PDCCnet

Guest
Okay, this is pretty convoluted but I'll try to be clear.

I have a share that exists on a Windows 2003. We'll call it "Folder1". I
have an Access database in that share so multiple users can get to it. If a
user happens to be connected to their TS session, they can navigate to the
actual file on the "local" TS volume (drive D: in the TS session).

Some users need to get to the database via a TS session; others can access
it via the share. Because the database is a front-end/back-end structure, the
drive paths have to be the same for both kinds of users. So, on the users'
local desktops, I have mapped "Folder1" to drive M:. I have done the same
inside the TS session.

However, some users (not all... more on this later) cannot launch the
database via the mapped drive in the TS session. They can, however, launch
the file if they navigate to the "local" D: drive in their TS session.

I have checked privileges and it would appear that all users have the same
access to these files; not "Administrator"-level control (Full Control) but
everything except "Full Control" is checked in the security tab for both the
file and its enclosing folder ("Folder1").

I'm stumped. I would have thought that perhaps... for some reason... maybe
all users needed to be "administrator-level" on the files. But I have one
administrator-level user who still cannot access the database via the mapped
drive in the TS session. They have to go through their desktop drive map or
go to the "local" D:-drive in the TS session.

Anyone have a clue or a potential avenue of inquiry to resolve this?

TIA
 
Re: Mapped Drive vs Actual Drive - Access issues

Do users get an error message when they try to connect to the file
through the mapped drive?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?UERDQ25ldA==?= <PDCCnet@discussions.microsoft.com> wrote
on 25 aug 2008:

> Okay, this is pretty convoluted but I'll try to be clear.
>
> I have a share that exists on a Windows 2003. We'll call it
> "Folder1". I have an Access database in that share so multiple
> users can get to it. If a user happens to be connected to their
> TS session, they can navigate to the actual file on the "local"
> TS volume (drive D: in the TS session).
>
> Some users need to get to the database via a TS session; others
> can access it via the share. Because the database is a
> front-end/back-end structure, the drive paths have to be the
> same for both kinds of users. So, on the users' local desktops,
> I have mapped "Folder1" to drive M:. I have done the same inside
> the TS session.
>
> However, some users (not all... more on this later) cannot
> launch the database via the mapped drive in the TS session. They
> can, however, launch the file if they navigate to the "local" D:
> drive in their TS session.
>
> I have checked privileges and it would appear that all users
> have the same access to these files; not "Administrator"-level
> control (Full Control) but everything except "Full Control" is
> checked in the security tab for both the file and its enclosing
> folder ("Folder1").
>
> I'm stumped. I would have thought that perhaps... for some
> reason... maybe all users needed to be "administrator-level" on
> the files. But I have one administrator-level user who still
> cannot access the database via the mapped drive in the TS
> session. They have to go through their desktop drive map or go
> to the "local" D:-drive in the TS session.
>
> Anyone have a clue or a potential avenue of inquiry to resolve
> this?
>
> TIA
 
Re: Mapped Drive vs Actual Drive - Access issues

Doh! In all the explanation, I forgot to include that.

Yes, when the user tries to open the database, they get a dialog stating:
"Windows cannot access the specified device, path, or file. You may not have
the appropriate permissions to access the item."

This, despite the fact that I can give the user EXPLICIT FULL CONTROL of the
item and they still get that message (qv the reference to a user with
administrator-level privileges).

Doug Starkey
Network Administrator
Pecan Deluxe Candy Company


"Vera Noest [MVP]" wrote:

> Do users get an error message when they try to connect to the file
> through the mapped drive?
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*
>
> =?Utf-8?B?UERDQ25ldA==?= <PDCCnet@discussions.microsoft.com> wrote
> on 25 aug 2008:
>
> > Okay, this is pretty convoluted but I'll try to be clear.
> >
> > I have a share that exists on a Windows 2003. We'll call it
> > "Folder1". I have an Access database in that share so multiple
> > users can get to it. If a user happens to be connected to their
> > TS session, they can navigate to the actual file on the "local"
> > TS volume (drive D: in the TS session).
> >
> > Some users need to get to the database via a TS session; others
> > can access it via the share. Because the database is a
> > front-end/back-end structure, the drive paths have to be the
> > same for both kinds of users. So, on the users' local desktops,
> > I have mapped "Folder1" to drive M:. I have done the same inside
> > the TS session.
> >
> > However, some users (not all... more on this later) cannot
> > launch the database via the mapped drive in the TS session. They
> > can, however, launch the file if they navigate to the "local" D:
> > drive in their TS session.
> >
> > I have checked privileges and it would appear that all users
> > have the same access to these files; not "Administrator"-level
> > control (Full Control) but everything except "Full Control" is
> > checked in the security tab for both the file and its enclosing
> > folder ("Folder1").
> >
> > I'm stumped. I would have thought that perhaps... for some
> > reason... maybe all users needed to be "administrator-level" on
> > the files. But I have one administrator-level user who still
> > cannot access the database via the mapped drive in the TS
> > session. They have to go through their desktop drive map or go
> > to the "local" D:-drive in the TS session.
> >
> > Anyone have a clue or a potential avenue of inquiry to resolve
> > this?
> >
> > TIA
>
 
Re: Mapped Drive vs Actual Drive - Access issues

I thought you would report that message :-)
Check this out:

When users start a program, they get an error message: "Windows
cannot access the specified device, path, or file. You may not have
the appropriate permissions to access the item."
http://ts.veranoest.net/ts_faq_user_issues.htm#IEESconfig

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?UERDQ25ldA==?= <PDCCnet@discussions.microsoft.com> wrote
on 26 aug 2008 in microsoft.public.windows.terminal_services:

> Doh! In all the explanation, I forgot to include that.
>
> Yes, when the user tries to open the database, they get a dialog
> stating: "Windows cannot access the specified device, path, or
> file. You may not have the appropriate permissions to access the
> item."
>
> This, despite the fact that I can give the user EXPLICIT FULL
> CONTROL of the item and they still get that message (qv the
> reference to a user with administrator-level privileges).
>
> Doug Starkey
> Network Administrator
> Pecan Deluxe Candy Company
>
>
> "Vera Noest [MVP]" wrote:
>
>> Do users get an error message when they try to connect to the
>> file through the mapped drive?
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> *----------- Please reply in newsgroup -------------*
>>
>> =?Utf-8?B?UERDQ25ldA==?= <PDCCnet@discussions.microsoft.com>
>> wrote on 25 aug 2008:
>>
>> > Okay, this is pretty convoluted but I'll try to be clear.
>> >
>> > I have a share that exists on a Windows 2003. We'll call it
>> > "Folder1". I have an Access database in that share so
>> > multiple users can get to it. If a user happens to be
>> > connected to their TS session, they can navigate to the
>> > actual file on the "local" TS volume (drive D: in the TS
>> > session).
>> >
>> > Some users need to get to the database via a TS session;
>> > others can access it via the share. Because the database is a
>> > front-end/back-end structure, the drive paths have to be the
>> > same for both kinds of users. So, on the users' local
>> > desktops, I have mapped "Folder1" to drive M:. I have done
>> > the same inside the TS session.
>> >
>> > However, some users (not all... more on this later) cannot
>> > launch the database via the mapped drive in the TS session.
>> > They can, however, launch the file if they navigate to the
>> > "local" D: drive in their TS session.
>> >
>> > I have checked privileges and it would appear that all users
>> > have the same access to these files; not
>> > "Administrator"-level control (Full Control) but everything
>> > except "Full Control" is checked in the security tab for both
>> > the file and its enclosing folder ("Folder1").
>> >
>> > I'm stumped. I would have thought that perhaps... for some
>> > reason... maybe all users needed to be "administrator-level"
>> > on the files. But I have one administrator-level user who
>> > still cannot access the database via the mapped drive in the
>> > TS session. They have to go through their desktop drive map
>> > or go to the "local" D:-drive in the TS session.
>> >
>> > Anyone have a clue or a potential avenue of inquiry to
>> > resolve this?
>> >
>> > TIA
 
Re: Mapped Drive vs Actual Drive - Access issues

Eureka! Thanks, Vera! Worked like a charm.

-Doug

"Vera Noest [MVP]" wrote:

> I thought you would report that message :-)
> Check this out:
>
> When users start a program, they get an error message: "Windows
> cannot access the specified device, path, or file. You may not have
> the appropriate permissions to access the item."
> http://ts.veranoest.net/ts_faq_user_issues.htm#IEESconfig
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?UERDQ25ldA==?= <PDCCnet@discussions.microsoft.com> wrote
> on 26 aug 2008 in microsoft.public.windows.terminal_services:
>
> > Doh! In all the explanation, I forgot to include that.
> >
> > Yes, when the user tries to open the database, they get a dialog
> > stating: "Windows cannot access the specified device, path, or
> > file. You may not have the appropriate permissions to access the
> > item."
> >
> > This, despite the fact that I can give the user EXPLICIT FULL
> > CONTROL of the item and they still get that message (qv the
> > reference to a user with administrator-level privileges).
> >
> > Doug Starkey
> > Network Administrator
> > Pecan Deluxe Candy Company
> >
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Do users get an error message when they try to connect to the
> >> file through the mapped drive?
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> *----------- Please reply in newsgroup -------------*
> >>
> >> =?Utf-8?B?UERDQ25ldA==?= <PDCCnet@discussions.microsoft.com>
> >> wrote on 25 aug 2008:
> >>
> >> > Okay, this is pretty convoluted but I'll try to be clear.
> >> >
> >> > I have a share that exists on a Windows 2003. We'll call it
> >> > "Folder1". I have an Access database in that share so
> >> > multiple users can get to it. If a user happens to be
> >> > connected to their TS session, they can navigate to the
> >> > actual file on the "local" TS volume (drive D: in the TS
> >> > session).
> >> >
> >> > Some users need to get to the database via a TS session;
> >> > others can access it via the share. Because the database is a
> >> > front-end/back-end structure, the drive paths have to be the
> >> > same for both kinds of users. So, on the users' local
> >> > desktops, I have mapped "Folder1" to drive M:. I have done
> >> > the same inside the TS session.
> >> >
> >> > However, some users (not all... more on this later) cannot
> >> > launch the database via the mapped drive in the TS session.
> >> > They can, however, launch the file if they navigate to the
> >> > "local" D: drive in their TS session.
> >> >
> >> > I have checked privileges and it would appear that all users
> >> > have the same access to these files; not
> >> > "Administrator"-level control (Full Control) but everything
> >> > except "Full Control" is checked in the security tab for both
> >> > the file and its enclosing folder ("Folder1").
> >> >
> >> > I'm stumped. I would have thought that perhaps... for some
> >> > reason... maybe all users needed to be "administrator-level"
> >> > on the files. But I have one administrator-level user who
> >> > still cannot access the database via the mapped drive in the
> >> > TS session. They have to go through their desktop drive map
> >> > or go to the "local" D:-drive in the TS session.
> >> >
> >> > Anyone have a clue or a potential avenue of inquiry to
> >> > resolve this?
> >> >
> >> > TIA
>
 
Back
Top