Question : net use z: won't work w/95 clients

I am stumped! I created a logon script for my users.
I am attempting to map Z: to the users home share.
My NT Workstation clients map it fine.
But my 95 clients won't map it,however,
If run the script under Win95 from the command prompt "after" logging on it works.
If I make the share map to H: it also works...
Does this have to do with the old LASTDRIVE=Z caveat from WIN/DOS????

How do I make this work? I am going nuts!
I want to use Z: as many of our users have 2 HD's & have physical drives that go up as far as F,G & H!
This makes no sense to me...
I have drives mapping at L: & Q: just fine, but mapping Z: via the logon script chokes the 95 logon...
To confuse me even more, when I select (under User/Properties/Profile) to map to Z: with User Manager, it works like a charm...
What the heck is going on???
I wish we were %100 NT but 95 still lingers in our midst so my logon script must cater to both clients...

Answer : net use z: won't work w/95 clients

Hello.

I'm using Kickstart scripting engine.
I'm too had this problem and I have tested this issue.
I've come to folowing conclusion:

During the login script execution z: is mapped to the athenticating server's NETLOGON directory like
z: = \\SERVER\NETLOGON.

After the script executes win95 automaticaly disconnect this drive.

You cannot connect z: drive by using login scripts.
This is the limitation of windows 95.

Gorbag