net use command help Please

[mrtst]

I am mapping a drive across a Netware Network and have a drive mapped thru the Novell Login Script. I get the error that I must log on before completing the task. Any suggestions on how I should change my script. I am using the following format. #net use Q: \\servername\c

Any help would be great.

Michael

 

[TheLad]

If you are mapping to a NetWare server, use the MAP command, syntax as follows:

MAP Q:=SERVERNAME/VOL1IR -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[fluid11]

I take it your trying to map a Windows share through a Novell login script? Are you running a Windows domain, and if so, is your workstation set up to join the domain?

ChrisP

 

[ab2002]

Hi

If you are trying to connect to a windows server you can't run the command in your login script. You can setup system variables that you than can use in a batch file located on the network and put it is your startup folder.

This way you can still have a single point of management

 

[TheLad]

I have always used NET USE in my login script?? Works ok?? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[fluid11]

Yes, you can map a Windows share through a NetWare login script by putting a # before the command.

ChrisP
MCSE (2K/NT4), CNE (NW5), CCNA, Linux+, Server+, i-Net+, Network+, A+, CIWA

 

[mrtst]

I am trying to map to a NT 5 box. I put the net use command in the login script thru NWADMIN, so I am running on a Netware 5 network.

Fluid11: this is the only NT box in our network and I would like the drive to be available at the time of login. I am going to make it a file, picture, PP presentation
dumping ground for my 250+ teachers. That way I can keep all there stuff of my servers. So no, there is no domain.

AB2002: Novell's website says that the only way to map a NT drive in the Novell
login script is with the net use command. If you have a better way could you please
send me the info..

TheLad: How are you doing yours? Could you give me some insight?

michael_ladd@gwinnett.k12.ga.us

thanks for the replies guys

 

[fluid11]

Set up a share on the NT Server and use the command below in the NetWare login script. You will need an account on the NT server for every user who needs to access the NT share. The accounts should have the same username and password as the ones on your NetWare server.

#net use X: \\server\share

ChrisP
MCSE (2K/NT4), CNE (NW5), CCNA, Linux+, Server+, i-Net+, Network+, A+, CIWA

 

[mrtst]

Fluid11,I have already done that and I am getting the error that I must be logged on before I can complete this operation. One I logon and right click on Network Neighborhood and choose Novell login and I logon again I get the response...
the command has completed succesfully. But that is the only way it works.
If you look at my original post I am using the exact format you suggest.
This is driving me crazy. I have the drive shared to everyone and even have
turned on the guest account. I also tried with just my account and same results.

HELP ME BEFORE THIS THING GOES AIRBORN.....LOL!

 

[fluid11]

I don't think that this will work, but try adding the commands below before the #net use command. This will set up your username before you try and execute the net use command.

DOS SET USER = "USERNAME"

Let me know,
Chris

 

[TheLad]

Have you got your workstations installed with the Client for Microsoft Networks? Even though the NetWare Client is your Primary authenticator, you still need the Microsoft Client installed on your workstation in order to connect to NT boxes.

You say your NT server is NT 5? Do you mean Windows 2000 (which is NT 5 in laymens term) or do you mean NT 4?

Our login script is the same as what fluid11 has already said, however if you want the users to attach as a specific user that is a different kettle of fish. What OS are your workstations running? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[mrtst]

the box that we are connecting to thru the login script is Windows XP.
I am not sure that the Microsoft client is installed on the workstations that I
am trying to connect from. I will check that and let you know. However
My test machine that I tried it from is also Windows XP so that might
blow a hole in that one. I am at a different school today so I won't be
able to check it until Monday but I will get back to you guy then.

Thanks

Michael

 

[fluid11]

Oh, its Windows XP. I figured that you accidentally wrote NT5 instead of NT4. The Client for Microsoft Networks is most likely installed because it is installed by default in XP unless you specifically un-installed it. You should definitely check to make sure like TheLad was saying.

Are you running the latest Novell Client for XP 4.82? There are BETA versions out there that have some serious problems.

ChrisP

 

[dan]

If there is no domain, how are you loggin in to the XP box? Do you have a local user account on that box? If not, you won't be able to logon unless you turn off all security on the share (But I wouldn't recommend that).
You also must be sure the user has permissions both to the share and the files.
Dan

 

[mrtst]

Ok, a little more info. All the workstations in the school run Win9X. The WinXP machine in hosting my Tech page for the teachers to go to for things like, my printer won't work and they can look for things to check like I.E. is you printer turned on. Yes I have had this. I also want them to put the pictures of there over weight, well you get the picture. I don't want them putting that kind of virus attaching stuff on my servers.

Dan: We don't logon to the XP box. We run Novell Netware 5 network so everyone logs onto a Netware server. In the login script we can map drives and assign them to different people. I can change the login script in the users container and everyone in there get the share or just individual people like myself. Which is what I am doing to test it out. I have turned off all security on the drive cuz I am the only one trying to access it for now. The only way I could share the drive more is to carry it around with me. The problem I am having is describe in my first post. That should bring you upto speed.

Fluid11: I do have XP client 4.82.
Thelad: once I logon I can relogon and the share work fine. Is there somekind of setting I can put in the login script to put the mapping of that drive off until after ZeN complete it thing? I am kinda at a dead end here.

 

[TheLad]

You could do a ZEN app that on Force Run does the NET USE command in the "Run Before Distribution" or "Run after Distribution" scripts section. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[ab2002]

Hi

Have you looked at Edirectories from Novell. This way you can manage your user connections to both systems through nds (edirectories). This is what we did with win2000 server.

If you are running an domain server the people only loging in on the xp box still can use the microsoft client. but you can install the netware client on those workstations.


This is how we got arround the you have to login problem.

Cheers

Ab

 

[TheLad]

NDS for NT is a good solution - I have used it on several NT Servers and it has worked ok. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[mrtst]

Thelad: How exacly wouuld I do this:
You could do a ZEN app that on Force Run does the NET USE command in the "Run Before Distribution" or "Run after Distribution" scripts section.
Can you give me more detail?

 

[DanMc]

wow, big thread...

I bet you have your Netware client set as the primary network provider in the network control panel. This means that the Microsoft Client for Microsoft Networks is not running yet when you are executing the Netware login script. That is why you get the "must log in" error. It's not that you must log in, it's that Microsoft networking isn't even running yet.

You are on the right track when you ask if you can put off the mapping until later. One way to do this is to copy a shortcut to the user's startup folder. The contents of the startup folder get run after all the network clients load, as the desktop loads.

Consider the following in the login script:
#XCOPY F:\PUBLIC\MAP2NT.LNK C:\WINDOWS\STARTM~1\PROGRA~1\STARTUP

Sometimes this gets tricky if you have different vers of windows out there or if people use roving profiles because the startup folder is in different places. XCOPY is easier to use than COPY because it's an independant program. The regular COPY command is part of COMMAND.COM. You can modify the properties of the shortcut and tell it to "run minimized". There are other solutions too. If you're really slick, you can push a registry change that adds a persistent windows drive mapping.