>I'm pretty sure that I'm up a creek here but I figured I would ask anyway. I have a NFS server running on a Windows NT server. This NFS server allows a UNIX NFS Client to access Windows NT shares. The problem is that the NFS server only allows drive letters and paths, not UNCs. So everything works fine if I have the NFS server running on the same server as the directory I want to place files as it is a local drive and therefore rights are not an iisue. However, if I move the NFS server to a different server and set up the NFS Server service as a domain account I can then a map a drive on the new server to the folder I want. This works fine until someone walks by and logs out the server. Then the mapped drive is no longer available for the NFS server to output to. Is there any way possible for a Windows NT server to maintain a mapped network drive while not logged on? I'm guessing the answer is no but I haven't been able to find a yes or no out on the regular net. Thanks for any input.

I believe drive mappings are local to the current user desktop context - ie if I have WTS running, each desktop has its own mapping set available to it. You might investigate if it's possible to run the NFS server in the context of the SYSTEM user as a service, or under Win2K, creating your own tree on the server and publishing it via NFS.