Pretty easy answer
When you start an app from a service, it runs as local system (unless you provide credentials -but only this user will be able to access the drive). Local system (note the local~) is obviously not a user known to the network, and has no rights to access the network. W2K server has an option to grant services from other computers to access the servers (trust for delegation) but guess what... it requires W2K clients. And even then, if system were able to map a drive, all users who log on (providing you haven't customized system rights) have no rights to access those drives, because the mapping is made from system, and runs in another environment (you would simply see them as "network drive", but not showing the servername /its content)Why would you even want to let systems map drives???? 
. Logon scripts are extremely handy for this, and i thought KiXtart was all about this in the first place. Use the netlogon share (or sysvol /ad) for finer results.
SO in your case:
-provide the service with credentials who has rights (->from a remote computer this can be done by the XNET utility)
-use Ftp with -s: option as an alternative
-"Trust" the server when you have a W2K domain (dsa.msc -> computers /dc's -> properties)
-check out the service (program should be in "parameters"-section) if you want it to interact with the desktop, assign a reg value of 11 (-> HKLM\SYSTEM\CCS\Services\ServiceName\ "Type=11"
-when using cmd files, note that the system doesn't know about shell extensions yet. Consider using cmd /c "%path%\FileName.BAT"
-As a last resort, you could the system make perform an automatic logon HKLM...\SOFTWARE\MS\W..NT\WINLOGON\entries:
*DefaultUserName=account with (restricted) access
*DefaultPassword=your_pass
*AutoAdminLogon=1
*DontDisplayLastUsername=0
greetz,
Grrrippp!
MCSE 2k
[ 18 October 2001: Message edited by: Stefaan Degroote ]
[ 18 October 2001: Message edited by: Stefaan Degroote ]
[ 18 October 2001: Message edited by: Stefaan Degroote ]
