Re: Windows 2003 services don't have access to mapped drives
- From: "Roger Abell [MVP]" <mvpNoSpam@xxxxxxx>
- Date: Wed, 18 Jul 2007 03:46:09 -0700
You probably are not going to like this, but the best thing you
could, and should, do is to rewrite the app to use UNC access.
http://support.microsoft.com/kb/180362/EN-US/
<mogorr@xxxxxxxxxxx> wrote in message
news:1184719556.017053.74140@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am working on a W2K3 server and I have an older application that
requires a network drive mapping. I have created a Domain Admin
account and set the service to run as this account. The application,
then tries to access the "L:\" drive but is unable to access it. The
funny thing is that if I use the UNC path, it works just fine.
Unfortunately, I can not use the UNC path without recoding this
application which I really dont want to do.
Also, if I run the application using the LocalService Account logged
into the server as the Domain Admin account, and start the application
(by Start->Run->Programs, etc...) the application can see the L:\
drive and the UNC. Obviously, I cant run this application like this
(what happens if the user account logs off the server?)
I should also mention, all of these options worked in 2000 but not
2003.
Where can I adjust the security to allow a domain account to access a
mapped drive as a service?
.
- Follow-Ups:
- Re: Windows 2003 services don't have access to mapped drives
- From: Al Dunbar
- Re: Windows 2003 services don't have access to mapped drives
- References:
- Prev by Date: Windows 2003 services don't have access to mapped drives
- Next by Date: Re: NT4 password limited to 14 characters ?
- Previous by thread: Windows 2003 services don't have access to mapped drives
- Next by thread: Re: Windows 2003 services don't have access to mapped drives
- Index(es):
Relevant Pages
|
|
