Server 2003 and UNC paths

Running Windows Server 2003, we have a batch file executed by a user
other than the server user account. I understand from Microsoft that
"redirected drives cannot be shared between processes that are runing
under different user accounts". It seems though that a batch file
should be able to go to a different server using a UNC path rather than
a hard-coded drive letter:

PUSHD \\newservername\dirname\subdirname\

Is there a reason why that shouldn't work? General network resources
like a UNC path aren't "redirected drives", are they?

It's treated the same way. It per connection from computer to
computer. That is why you can't map to two different shares on the
same user with two different sets of credentials.

--
Jeffrey Randow
(E-Mail Removed)
Windows Networking MVP 2001-2006

http://www.networkblog.net

On Fri, 29 Sep 2006 12:23:10 -0400, Rick Charnes
<rickxyz--(E-Mail Removed)> wrote:

>Running Windows Server 2003, we have a batch file executed by a user
>other than the server user account. I understand from Microsoft that
>"redirected drives cannot be shared between processes that are runing
>under different user accounts". It seems though that a batch file
>should be able to go to a different server using a UNC path rather than
>a hard-coded drive letter:
>
>PUSHD \\newservername\dirname\subdirname\
>
>Is there a reason why that shouldn't work? General network resources
>like a UNC path aren't "redirected drives", are they?