Why won't this one drive map? 2

[JBruyet]

Hey all,

I have some users who are unable to map a drive to the server. the errror message is as follows:

Your current context is LINK_ORG
User: Angie Context: LINK_ORG
Your current tree is: LINK_TREE
You are attached to server LINK_SERVER.
Drive I: = LINK_SERVER_SYS: Drive P: = LINK_SERVER_MACASS Drive S: = LINK_SERVER_MAC:USERS\SHARED Drive H: = LINK_SERVER_MAC:USERS\SHARED\NOT_SH~1\ANGIE Drive U: = LINK_SERVER_MAC:USERS\SHARED\SHARED\DEPART~1\HUMAN_~1\ANGIE LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed.
[ROOT U:=MAC:USERS\SHARED\SHARED\DEPART~1\OPERAT~1\ANGIE]
The error code was 8804.
S1: = Z:. [LINK_SERVER_SYSUBLIC \]

As you can see only one drive doesn't map. I thought it might be a rights issue but that's not it either. I've been to Novell with the error and their fixes don't apply (wrong OS or names ARE different or blah blah blah). I'm trying to see if the user who are having this drive mapping problem have anything in common but no luck yet. Has anyone seen this problem and been able to fix it? Any ideas are appreciated.

Thanks,

Joe Brouillette

 

[JBruyet]

Oops! Our workstations are Windows XP SP1 machines with Client32 4.9 and the server is Netware 5.0.

Sorry,

Joe Brouillette

 

[marvhuffaker]

I can think of 3 specific things that might cause something like that....

- Sometimes an error like that means the drive is already assigned to something else, like a CDROM.

- Incorrect Rights.. Check them again. check Angie's effective rights in this directory. Make sure she at least has RF

- Typo in the path, or the client is interpretting the long name incorrectly. Can you verify what the 8.3 name format of the "HUMAN_~1" directory is? I think the '_' means it put a space in there and I have a hunch that may have something to do with it.

All the TIDs point to the volume object being corrupt in NDS, but it appears other mappings to the same volume are working. check and see if the above applies.. if not, you should probably run a DSrepair, check volumes and trustees.. and see what kind of errors you get. Maybe the trustee assignment for that one directory got hosed.


BTW, thanks for giving us your Tree, context, server name, and volume structure. Now if you could just give us your IP address and admin password, we'd be set Hey, and I'm not trying to make fun here, but your file structure makes me want to reminisce. One time I saw a file structure like this:

Server\SHAREData\shared\share\files\shared. Wow, what a nightmare.


Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[JBruyet]

It's not a CD-ROM, I'll double-check the rights, and I'll double-check the wording in the login script. As to the extent of the info I posted, I usually tweak it so I don't give out real data but I figured since this is unconnected and on the inside I'm pretty safe. I guess we'll see...

Thanks,

Joe Brouillette

 

[TheLad]

Looking at your script above, isn't the U: already getting mapped to: LINK_SERVER_MAC:USERS\SHARED\SHARED\DEPART~1\HUMAN_~1\ANGIE ???

So basically wouldn't this indicate that your script is mapping the U: then trying to map it again to a different path? Try a different drive letter ....

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[JBruyet]

Hmmm... You're absolutely right. I had to add them to another group because they needed access to one of the locked down programs and I see now that's the problem--two separate group memberships trying to map to the same drive. Sheesh! I was looking for something else! I guess I should have sat down and looked more closely at the error message. Now I need to create a different group and put them in it without that group mapping drives.

Thanks Lad!

Joe Brouillette