The network mapping feature for the job should work for Novell. Please post details of how it "isn't working."

If it should be working, then I guess I'm doing something wrong :)

Network path to connect: \\server\volume
Assign drive letter: on (N:)
Domain: Emtpy (is this correct? A Netware server doesn't have a domain)
User ID: Fully Qualified Distinguished Name (.user.context)
Password: Password

When I start the job I get error 138: Cannot load network connection '\\server\volume'. Logon failed for user '.user.context'. Logon failure: unknown user name or bad password.

I also tried to put the context at the domainfield, but I receive the same error.

btw. What will happen if 2 Netware jobs are running at the same time?

Thanks for your reply,

Jeroen

I apologize for responding without thinking. I forgot about this problem: http://www.arcanadev.com/support/article.asp?a=K00000156, which probably is preventing the login from working correctly.

A fix is available to correct that problem; download www.arcanadev.com/supportfiles/adtempus202hf1.zip and follow the instructions in the readme.htm found in that ZIP.

After applying the fix, see if the Novell login works. You are correct that you should leave the domain field empty.

If you have more than one job running at the same time under the same credentials, the jobs share the same login context and therefore the same network connections, so adTempus does not attempt to make a second connection to the network for the user.