net use drives for same user

Hello,
I have noticed a difference between W2K and W2K3 over net use drive
letters for the *same* user.

Is there any way on W2K3 to share the net use drive letter between the
two sessions that have the *same* user logged on?

The motivation is that we wish to run scheduled jobs accessing the
drive letter.
On W2K this works fine, on W2K3 this fails.

The simplest way to demonstrate the different behaviour is using
'runas' from two command prompts:

first
1) runas /user:xxx %comspec%
net use F: \\server\path

then
2) runas /user:xxx %comspec%
net use F:
dir F:

On W2K the "net use" doesn't show the drive letter mapped, but the dir
does list the files.

On W2K3 the "net use" shows the drive letter mapped, and
'Unavailable', and the dir fails.

Regards,
Roger.


roger.orr@gmail.com

<(E-Mail Removed)> wrote in message
news:888d44dd-7f47-44da-a8d9-(E-Mail Removed)...
> Hello,
> I have noticed a difference between W2K and W2K3 over net use drive
> letters for the *same* user.
>
> Is there any way on W2K3 to share the net use drive letter between the
> two sessions that have the *same* user logged on?
>
> The motivation is that we wish to run scheduled jobs accessing the
> drive letter.
> On W2K this works fine, on W2K3 this fails.
>
> The simplest way to demonstrate the different behaviour is using
> 'runas' from two command prompts:
>
> first
> 1) runas /user:xxx %comspec%
> net use F: \\server\path
>
> then
> 2) runas /user:xxx %comspec%
> net use F:
> dir F:
>
> On W2K the "net use" doesn't show the drive letter mapped, but the dir
> does list the files.
>
> On W2K3 the "net use" shows the drive letter mapped, and
> 'Unavailable', and the dir fails.

Use 'net use F: \\server\path' in both sessions to re-init the connection
for the second job.

Another solution is to to run the scheduled jobs as separate users with the
same permissions to access the network share.

/Henrik