Map drive to Windows Server via Novell login sript?

Discussion in 'Networking & Security' started by VeeDubbs, Jan 8, 2008.

  1. VeeDubbs

    VeeDubbs Limp Gawd

    Messages:
    398
    Joined:
    Dec 9, 2005
    Is this possible?

    As the title says...I need to map a drive to a Windows 2003 Server (used for a certain app, only to be used by certain people) and we run a Novell network. Is this possible?
     
  2. MorfiusX

    MorfiusX 2[H]4U

    Messages:
    3,007
    Joined:
    Feb 13, 2004
    If you have the Novell client on the server, then it shouldn't be a problem. It's been a long time since I've had to deal with a Novell network. (Thank God) IIRC, you should be able to do it as the Novell client uses the Windows API to perform the mapping. Create a test user and modify the script for that user and test it out.
     
  3. SpaceHonkey

    SpaceHonkey Gawd

    Messages:
    984
    Joined:
    Jan 25, 2007
    I think the command to use is '#' in the Novell login script. Runs an external program. In this case, net. So a line like the following will do. Assuming the user has rights via their domain account to connect to the share.

    #net use \\servername\sharename /persistent:no

    Test before delpoyment, it's been over a year since I've modified a novell login script... ;)
     
  4. VeeDubbs

    VeeDubbs Limp Gawd

    Messages:
    398
    Joined:
    Dec 9, 2005
    Thanks! This seemed to do most of what I needed! First off, what does

    Code:
    /persistent:no
    do?

    Secondly, as I said before, this does most of what I need. But now it brings up the command prompt asking for a username and password to this share - which I was expecting. Is there any way I can pass this information via the login script so the users will NOT have to enter this everytime they login?

    Thanks again!!
     
  5. atomiser

    atomiser Gawd

    Messages:
    619
    Joined:
    Jun 12, 2004
    iirc '/persistent:no' just means that the workstation itself wont remember the mapping after a reboot. this way it is always called by the login script, and not by the workstation trying to be 'clever'. the only other *potential* issue that i can see is that there will need to be an account on the 2003 server with the same username/password as the novell account otherwise they will get a login box to authenticate against before they can access the share. you may have admin overhead here due to password sync issues. you could always just use a generic account (using /user:[username] [password]) directly within the login script but this isn't best practice from a security standpoint. hope this helps.

    edit: beaten to it with reference to the login issue. as i said, using a generic account is bad practice but you may have sync issues otherwise. you could create an account on the box with a generic username and password but only grant it access to the specific files required and then call this within the login script. hope this helps.
     
  6. VeeDubbs

    VeeDubbs Limp Gawd

    Messages:
    398
    Joined:
    Dec 9, 2005
    Thanks atomiser. That does work in the login script and got me to where I need to be. Now, as you said, I just need to talk to my boss and see if we should actually go this route - as it is unsecure.