Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 297
  • Last Modified:

map to drives in Novell domain on boot

I have a situation where the users W2K machines need to have a drive mapped automatically to a W2K server that sits in a different Novell domain.  The actual mapping of the drive (domain login, etc.) should be transparent to the user.  
Presently I have a .cmd file containing the net use command sitting in the \Start Menu\Programs\Startup directory to map the drive on boot up.  The problem is that this file can be opened in edit mode revealing the login and password for the other domain.  

How can I set up automatic mapping of this drive so that the domain login is transparent to the user?  I believe there is something that can be done with a script with the userid and password hidden in a registry key but I don't know how to do this.
Thanks.
0
subgenius
Asked:
subgenius
  • 3
  • 3
1 Solution
 
jimshoeCommented:
Easiest way would be to place a pointer in the users login script calling up this other cmd file stored on the logon server.



 
0
 
hesseltinedCommented:
Since W2K is secure and nobody can see the logged in users registry hive, it is generally safe to store a login and password there.    What I have done to get around this is to create a VB script to read the login and pass to the registry, then use the pass that information to the cmd file, or send it directly to the Novell login prompt.   Either way should work, but you will need a little VBS knowledge.
0
 
subgeniusAuthor Commented:
I apologize, I made an error in asking my question.  The W2K server is in an NT domain not Novell. The user workstations (W2K Pro)are in a Novell domain.
Can anyone provide an example script or direct me to links which will help solve this problem?
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
jimshoeCommented:
So you have Win2k Pro workstations logging into a Win2k server that need drives mapped to a novell server?

If thats the case, place the cmd file on the Win2k server, in the login script of the users place a line pointing to the location of the cmd file that you just stored on the win2k server.

If I'm not understanding this correctly please correct me.

Is there a logon script on the Win2k server?
0
 
subgeniusAuthor Commented:
Sorry for not being very clear on this.
The W2K Pro user workstations need a drive mapped to a W2K server that is in an NT domain.  The users are in a Novell domain and normally would not need access to the NT domain (it is a domain for system ops and databases only).  When the users log in in the morning, they do so via a Novell login.  I'm told by the guys responsible for the Novell domain that they can't set up the Novell login script to map drives to the NT domain.  So I use a .cmd file that contains NET USE commands to map the drives.  
My goal is to make this as secure as possible and foolproof to the user. Right now the drives do get mapped automatically but it's not very secure. The users do have accounts set up in the NT domain. What I'm looking for is a way to bury this process in the API or in an executable that runs on startup.  I just don't know how to do that part.

Thanks
0
 
jimshoeCommented:
Ask the Novell guys to execute your cmd file from the login script.

#SYS:PUBLIC\YOURCMDFILE.CMD

Or if you'd rather stay away from them :-)

You could place the cmd file on each workstation in a directory of your choice.  Then using regedit:

Registry Key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

Create the Value Data Type(s) and Value Name(s) as detailed below.

Data Type: REG_SZ String Value // Value Name: Enter the Name of Program Executable

Value Data: Enter the Path to the Program Executable
Exit and Reboot

Or you could take up programming :)

0
 
subgeniusAuthor Commented:
This answers part of my question but I still have the problem of how to secure the login information which is in the cmd file on the client machines.  I think that is a problem that requires a programming solution so I'll address that in the programming area.
0

Featured Post

Get your problem seen by more experts

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

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