Windows 2000 Server and truly permanent network mappings?

[Guest G.T.]

I'm stuck here.

 

I have a crappy little app that is going to run on our server. It doesn't

do UNC but I can have that changed in a future release. It only is aware of

regular old Windows drive letters. It will work connecting to network data

if the drive has been mapped. But...

 

....if I log off of the server I lose my mapping. I've searched and the only

answers I've found are summed up in "The concept of having mapped drives

available when no one is logged in really doesn't make much sense in the

context of NT operating systems" or "Network drives wont be available when

no one is logged on. Try using UNC paths instead."

 

I need to be able to log off and to continue using the drive letter. Ack.

 

Do I have to wait until I can get my enhancement for this app or is there

some trick to keep my Y: drive mapped while no one is logged on? Right now

I need to keep the server logged in so I'm dead in the water if another

admin comes by and logs me off.

 

Greg

 

--

Ticketmaster and Ticketweb suck, but everyone knows that:

http://ticketmastersucks.org

Dethink to survive - Mclusky

[Guest Richard Mueller [MVP]]

Re: Windows 2000 Server and truly permanent network mappings?

 

Drive mappings are for users. A security principal (user) must have

permissions to access the mapping. If there is no user, there cannot be a

mapping because there are no permissions (credentials).

 

Still, your app must run as someone, perhaps System. When you are logged on

and run the app, the app uses your credentials to access the mapped drive.

When you log off, what credentials does the app have? In Task Manager who is

the owner (user name)? That security principal must map the drive.

 

--

Richard Mueller

Microsoft MVP Scripting and ADSI

Hilltop Lab - http://www.rlmueller.net

--

 

"G.T." <getnews1@dslextreme.com> wrote in message

news:13l1j5limbpdid6@corp.supernews.com...

> I'm stuck here.

>

> I have a crappy little app that is going to run on our server. It doesn't

> do UNC but I can have that changed in a future release. It only is aware

> of regular old Windows drive letters. It will work connecting to network

> data if the drive has been mapped. But...

>

> ...if I log off of the server I lose my mapping. I've searched and the

> only answers I've found are summed up in "The concept of having mapped

> drives available when no one is logged in really doesn't make much sense

> in the context of NT operating systems" or "Network drives wont be

> available when no one is logged on. Try using UNC paths instead."

>

> I need to be able to log off and to continue using the drive letter. Ack.

>

> Do I have to wait until I can get my enhancement for this app or is there

> some trick to keep my Y: drive mapped while no one is logged on? Right

> now I need to keep the server logged in so I'm dead in the water if

> another admin comes by and logs me off.

>

> Greg

>

> --

> Ticketmaster and Ticketweb suck, but everyone knows that:

> http://ticketmastersucks.org

> Dethink to survive - Mclusky

>

[Guest G.T.]

Re: Windows 2000 Server and truly permanent network mappings?

 

Richard Mueller [MVP] wrote:

> Drive mappings are for users. A security principal (user) must have

> permissions to access the mapping. If there is no user, there cannot be a

> mapping because there are no permissions (credentials).

 

I guess I should switch to NFS then. NFS and other network file sharing

protocols are for hosts not just users.

 

Oh well.

 

Greg

[Guest Dave Patrick]

Re: Windows 2000 Server and truly permanent network mappings?

 

Are you running it as a service? This article may help.

 

http://support.microsoft.com/default.aspx?scid=kb;[LN];243486

 

 

--

 

Regards,

 

Dave Patrick ....Please no email replies - reply in newsgroup.

Microsoft Certified Professional

Microsoft MVP [Windows]

http://www.microsoft.com/protect

 

"G.T." wrote:

> I guess I should switch to NFS then. NFS and other network file sharing

> protocols are for hosts not just users.

>

> Oh well.

>

> Greg

>