Creating a symlink directory on a network share to a path below a mapped drive letter, local path, or UNC path does not work

Am I correct in assuming I can not create a `symlinkd` to a network share, local path, or a UNC path on a network share that will be accessible by clients?

###Mapped drive letters don't work:

1) navigate to a network share:

pushd \\windows2008server\share\

2) make a hardlink:

   

mklink /d test_sharedir t:\directory\
dir .\test_sharedir 
#Directory of Z:\test_sharedir
#File Not Found

UNC paths don't work:

1) navigate to a network share:

pushd \\windows2008server\share\

2) make a symlink:

mklink /d test_dirunc \\windows2008server\share
dir .\test_dirunc
#Directory of Z:\test_dirunc
#File Not Found

I can create a functional `symlinkd` on a local drive to a mapped drive letter or a UNC path.

Are my assumptions above correct?

We are in the middle of a migration and have created two symlinkd to UNC paths for shared DLLs, one below c:\windows\system32\ (directing to a share containing 64-bit DLLs) and one below c:\windows\syswow64 (directing to a share containing 32-bit DLLs).

On the file server, we have had a path to 32-bit DLLs (from Windows 7 clients: s:\dll\).  I am attempting to rename this directory so that it is accessible via "s:\dll32\" and would like to create a symlinkd that links "s:\dll" to"s:\dll32" [again where S: is a mapped drive on a Windows 2008 server].  How do I do this?

Thanks,

Matt