Windows 2003 services don't have access to mapped drives



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?

.



Relevant Pages

  • Re: SQL account rights
    ... Please advice what is the best, suitable rights rather than domain admin ... issues, such as a server that might have IIS running on the same machine, ... applicable to SQL 2000 environment, ... files, or backups, make sure that the service account has Full ...
    (microsoft.public.sqlserver.security)
  • Re: Server Security
    ... In my opinion you want accountability for administrators and each administrator ... "The" administrator account should not be used and given a very long ... make sure that if there is sensitive information on that server, ... > name with domain admin rights on each. ...
    (microsoft.public.win2000.security)
  • Re: Re-Post - "the trust relationship between this workstation and the
    ... "the trust relationship between this workstation and the primary domain ... only problem is adding a new user account on the station. ... Client computer must use STRICTLY the INTERNAL DNS server which can ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)
  • Re: Same question, still no answer!!!
    ... Sounds then like we are all paying for a feature set only large companies ... The "proxy server" pc is actually an older box stuffed ... Expectation #1) keep the ethernet more or less as is. ... The kids account would be ...
    (microsoft.public.windowsxp.basics)
  • Re: Re-Post - "the trust relationship between this workstation and the
    ... "the trust relationship between this workstation and the primary domain ... only problem is adding a new user account on the station. ... This would be on the DNS server 172.20.100.2 ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)