Login script drive map error

[dangermouse68]

I'm getting the following error when trying to map a drive in a container login script.

LOGIN-LGNWNT32.DLL -400: A network drive cannot be mapped to a drive that is designated as a local drive.

The statement in the login script is:

IF MEMBER OF ".60s-Project.student.zbths" THEN MAP ROOT N:=\Server\DATA\60s-project

There is a statement just before this one that is identical, but uses a different group(in the same container), drive letter and mapping (to the same volume but different directory), and it works fine with the same user.

The map statement works fine if used in a user login script or even within a Zen application object. The Zen would work, but it also pops up the message of the day screen, which I don't want.

 

[dangermouse68]

Sorry, that really didn't come across as a question.

Has anyone seen this before or have an idea of what to look at?

I know the old Netware clients used to have a logging option, not sure how to turn it on here. Using client 4.91.0.20050216

 

[LawnBoy]

Don't know how much difference it makes, but I specify the CN and OU of the group. I.E.

IF MEMBER OF ".CN=MP2 Users.O=TAA" THEN
MAP M:=SERVER/VOLUMEIR\PATH
END

hth.

 

[dangermouse68]

Thanks LawnBoy, but it made no difference. Got the same error.

I just had an idea. I am trying to map this drive for students. I tried this with a staff account and it worked. The staff account doesn't have any more rights than a student does to this directory.

I'm leaning toward this being an NDS issue, due to other quirkyness happening (i.e. user has full rights to a directory for serving up web pages, but he can't upload from Dreamweaver. He can do everything from Explorer though, delete, rename, copy, paste ...)

I've run multiple dsrepairs this week already.

 

[LawnBoy]

Does the staff account have any more rights to the tree than the student? The reason I ask is that I noticed when I write a mapping for myself (trustee of ROOT) it doesn't matter whether I use "\" or "/" or the ":" volume separator; but when I write a mapping for my base users it does matter and has to be the exact syntax I posted.

Just shooting in the dark...YMMV.

 

[dangermouse68]

I'll check the rights to the tree.

However, the student account I'm testing with gets a drive mapped to the same server/volume, just a different directory and group.

 

[marvhuffaker]

Idunno if you already caught this, but the syntax in your original post is wrong.. YOu only have one Whack when you need two whacks..

\\server\volume\path NOT \server\volume\path

Stupid syntax mistakes like that will cause the ' designated as local drive' error.



Marvin Huffaker, MCNE

http://www.redjuju.com

 

[dangermouse68]

Marv, you dah man!!

My atttention to detail isn't what it could be here. I work at a school and have constant interruptions.

Anyway, that's no excuse on my part.

This worked on my testing container, but when I checked my prod. container it already had the extra whack. I'll just wait to here if they have any issues. I'm sure it will be fine now.

 

[LawnBoy]

That's odd. Nowhere in any of my mappings do I have either \ or \\ in front of the servername. Yet they all work flawlessly. Is it because I use the /VOLUMEIR\PATH syntax?

 

[marvhuffaker]

Here are a couple different syntax's available:

\\server\volume\path
server\volumeath

Either one should work. I prefer UNC - less things to remember. There are some other more complex methods but they aren't usually required.


Marvin Huffaker, MCNE

http://www.redjuju.com