Networks

Ask something
Discussion Locked

Mapping to drives in a different context

0 helpful
7 replies

by rboyer 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am running Netware 5.1 at 2 sites. Each site has its own server. The servers are in the same tree but different context. I can access the files from a different context, but mapping is a problem. I have been able to map one folder to a root drive, but when I do another one I get the 8804 error. Novell's knowledgebase doesn't provide any help. Has anyone experienced this also? What did you do to fix it?

7 replies

by budthegrey

8804 errors are usually eDir/NDS related.

Run DSREPAIR on all server involved to make sure sync is OK

Make sure TIMESYNC is ok -- One SINGLE server, all others SECONDARY

Make sure there's a R/W replica of NDS on each of the servers

Of course, check permissions on the folder.

Use the NDS volume name when mapping.

by rbgnr111

this could also be a licensing or rights issue.
when users login do you get any errors on the server too?
do the users have any rights to objects in the other servers context, or the file system on the other server?

by erekose mcne

If you look on Novell site there are some answers for this. If the mapping works for one and not another then you should run a DSREPAIR on the server it is not working on. You may have an invalid Volume object ID on the one that you cannot map to. You may have to delete the volume and wait for the obits to synch out. Then run a DSREPAIR ..Advanced options and Check volume objects and trustees. Thsi will recreate the objects in the tree. The caveat is you may lose user home directories and print queues so backup first! And do it after hours.

This discussion is closed to new replies.