A network drive cannot be mapped to a drive ERROR

[HwyStarJoe]

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

Hi all,
I searched but did not see this exact problem anywhere.
Recently I've been plagued with login errors with my Win2000 and XP users not getting their 'H' home directories mapped. I'm running a 5.1 SP5 server.

This is a portion of my different containers login scripts:
WRITE "Good %GREETING_TIME, %FULL_NAME"
WRITE " "
MAP ROOT H:=%HOME_DIRECTORY

When users login, they get the error I placed at the top. I get this error as well and it's intermittant. If I have them right-click the Big Red N and login again, 80% of the time all it does is add another SYS\Public drive with a new drive letter. No biggy. Sometimes it'll work and map their 'H' drive. At first I thought it might be the NW Client v 4.9 so I reved back to v4.8 with and without SP's and it didn't change a thing. The issue still happens.

All users Environments definitely show the correct Volume and Path for each users Home Directory. I've run Full Unattanded Repairs and got no errors in DSREPAIR. This issue cropped up out of the blue a month or so ago for no reason. Nothing has been changed or added that would cause this.

On a side note, and I don't know if this is related but I run Zenworks Starter pack (and have done so for the past 4 years). It throws the Application Explorer on the desktop and also the Novell Printer Manager icon for all of the users NDPS printer(s). At the same time I noticed the login script errors, I noticed that the Printer Manager icon was NOT being placed on the desktop. That issue is also intermittant. But it's not consistant.... if the Home Directory does not map, it doesn't mean that the NPM icon won't show up and vice versa.

I'm at a loss here as to what to look at next! Any ideas?
Thank you!

Joe

 

[TheLad]

As you have guessed, the H: map command is not being interpreted properly as it is only issuing the command "MAP ROOT H:=" - if you type this from a DOS box you get a similar error.

Are your home directories longer than 8 characters in length? If so, put the map command in quotes so the long path will be interpreted properly .. eg.

"MAP ROOT H:=%HOME_DIRECTORY"

Another cause of this could be a users lack of rights to their home area set in the environment tab.


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

 

[HwyStarJoe]

Thanks for the reply Lad....

But the answer to your question is negative. One in particular is 'jmchugh'. It happens whether their directory name is less than 8 charactors or not. Mine does the same thing and is exactly 8.
And all users have all rights including Supervisor to their home directories.

SERVER_VOL_1.Townname.XXX\Users\Homedirectory where Homedirectory is their login name, so it can be more or less than 8 charactors.

I'm beginning to think it's an OS corruption of some sort. I just have no other symptoms! :/

 

[TheLad]

Try adding a WRITE command which displays the Home Directory variable, this will allow you to determine whether the login script is interpreting the command properly

For example, add the following in:

WRITE "%HOME_DIRECTORY"

and check next time you login to ensure the path shown is the correct one.

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

 

[HwyStarJoe]

That makes sense.
I've made the change to my script and will watch it. Today things are working fine and that added command displays the correct path and directories.... Tomorrow? Who knows!

If for some reason something changes which causes the issue to reappear.... like the server or server and VOL, what could be the cause? I have a second 5.1 SP5 server in another building that's in the same tree as mine, but with a slightly different name.
Can a schema difference on one or more replicas cause this type of thing? I'm sure they could be the cause of all sorts of problems. I'm just not sure what to do to remedy them if there are any.

Thanks again Lad!

Joe

 

[terry712]

i prefer using the %cn for the home drives

 

[HwyStarJoe]

Well.... all was well all week until this morning.

All week, each time I or someone that's experienced the issue logged in, the WRITE "%HOME_DIRECTORY" command worked as it should, of course, and showed the mapping to the H drive.

Today I log in and the error LOGIN-LGNWNT32.DLL-400: A network drive cannot be mapped to a drive that is designated as a local drive.
[ROOT H:=] pops up in the script window and the WRITE "%HOME_DIRECTORY" line is ignored and doesn't show the mapping.

So that didn't tell me anything. I tried typing MAP ROOT H:=%HOME_DIRECTORY in a DOS window and get "MAP-4.13 (970813) PTF-400: You attempted to map a network drive to unmapped drive or to a local drive."

I can't find a reference to that error anywhere.

Ideas??
Thanks all!

 

[TheLad]

You won't be able to use the %HOME_DIRECTORY variable from the command line as the variable is a NetWare variable and can only be used in login scripts

The only TID I can find that is close is the one below. It's not specific to your problem, but may be worth a shot anyway:

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10085167.htm

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

 

[got2xlr8]

you need to put the %home directory in qoutes, the proper syntax is

MAP ROOT H:="%HOME DIRECTORY

 

[HwyStarJoe]

OK, but without them it's worked just fine for 4 years. I'll make the change and see what happens.
Why would it suddenly stop working, and be intermittant for intermittant users?

 

[Kratzyman]

The problem is after you install NW Client 4.9. Sometimes it does not like the / in the script. Replace your / with \ in your login scripts and it will work. I had MAP ROOT M:=Servername_DATA.:HOME/%1 and changed it to MAP ROOT M:=Servername_DATA.:HOME\%1 and now it works. By the way "%LOGIN_NAME" may be 10 characters, but it can only represent 8. So, if your user names are 9 characters or more, the folder names can only be composed of the first 8 characters in the users login name.
Use %1 as the login name variable. This is a Windows session variable created by the NW Client, so as to be exempt from the 8 character limit.

 

[HwyStarJoe]

Thanks Kratzyman, but the issue started with v4.9 and prior but was fixed for me by v4.9 SP2. It had nothing to do with my scripts.

But I made the mistake if installing the v4.9 SP2 Post SP2 fix and now my Application Explorer won't present my users with the Netware Printer Manager that I have set to show on their desktops! In fact it causes a SPOOLSV.EXE error when logging in!

I just can't win!