• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 205
  • Last Modified:

net use in netware script for NT 4.0 Share

I am migrating from Netware to NT 4.0 server and I plan to migrate groups of users at a time.  I would like everyone to use the NT shared drive instead of Netware shared drive right away and then slowly move home directories to NT.  I tried to put a net use command in the Netware login script to connect users to NT server's shared drive , but it did not work.  In the login script I put the name of the batch file to run.  

This is what I put in my Netware login script:
     #command.com /c "k:\ntlogin.bat"

Inside the ntlogin.bat file is this:
     net use x: \\ntserver\share

I get an error saying that you have to log in first in order for this to work.  But it works fine when I am logged into Netware and run a net use command manually, so the syntax of the net use is fine but it doesn't work in the Netware script.  Any help that anyone can give me would be greatly appreciated.  Thank you in advance.
  • 2
1 Solution
According to KB Article # Q135167, the Netware Login Script Processor is not good with realising UNC path names.  This is probably why you are unable to connect to a NT Server share.  You should find an alternate way to do this.
Secondly, it might be caused for another reason.  Check your CONFIG.SYS file on the clients for the setting of LASTDRIVE.  Usually this gets set for 'P'.  Change this to 'Z' or disable it totally.  This might cause the problem, too.
Good luck...
bfarahi1Author Commented:
I do not have a lastdrive line in my config.sys.  I am able to run logical drive batch file in the login script.  For example I am updating users McAfee DAT files with a batch file in the login script.  Although the batch file is being run from a Netware drive.  I think there should be a way to connect to an NT shared drive in the Netware login script.  Thank you in advance.
ok your problem is well known.

at time of running netware logon scripts you're not validated to NT network. this wil be done after netware logon has finished.

to solve this problem change network provider order on your workstation. then you are valid logged onto your NT network but without execution of a script and you can now log onto your netware with execution of your script as you've created.

better is to create to separate scripts for each network placed on NT for NT network and NW server for netware. in this case you're independend of each server system. if you want to shutdown one of them, all from other is running as expected.
And you have to administrate each system with tools designed for it. only as long as you have two different system you have to know about source server (NT or NetWare)

bfarahi1Author Commented:
It worked great.  Thank you.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now