Bindery Login Script problem

[Joe K. Bales]

My situation is that I have 3 users who need to login using Microsofts
client for Netware. The other users will use CLietn32 for Novell.

Login for these 3 users is fine and I have set the context to the OU in the
NDS that the users belong too. When I browse Network neighbor hood I have
only the rights that the OU unit is suppose to so my context for this is
working fine.

Obviuosly the Login Script at the OU container level is not being loades as
we are not using CLient 32 for these 3 users.

SO my question is how do I setup a login script for these 3 users using
MSClient for Netware. I have had users here talk about the login file in
the sys:mail\userid sub directory where i see login and login.os2 and I have
put mappings into theser empty files and the do not executre. I ahve also
created the NET$log.dat file under sys:public and that does not execute. I
have enable login scripting checked on the workstation properties for the
Client.

I must be missing something simple here.

What is the correct way for me to setup the user Login Script and the System
Login Script for users using MS client for netware logging into a NDS
server.

any help would be appreceiated.

thanks

joe bales

[Hansang Bae]

"Joe K. Bales" <joeb...@home.com> writes:
[snip]

>SO my question is how do I setup a login script for these 3 users using
>MSClient for Netware. I have had users here talk about the login file in
>the sys:mail\userid sub directory where i see login and login.os2 and I have
>put mappings into theser empty files and the do not executre. I ahve also
>created the NET$log.dat file under sys:public and that does not execute. I
>have enable login scripting checked on the workstation properties for the
>Client.
>I must be missing something simple here.
>What is the correct way for me to setup the user Login Script and the System
>Login Script for users using MS client for netware logging into a NDS
>server.

Are there multiple servers involved? To test things, did you try adding
MS verions of NDS client?

*********** Remove the REMOVE if emailing me directly **************
Hansang Bae Director of Network Operations, Eastern Region
Richey Systems Main Office: (800) 776-5145
hb...@richeysystems.com Reg. Office: (718) 352-9021
Specializing in Network Design/Troubleshooting and Protocol Analysis
********************************************************************

[Joe K. Bales]

Only One Server Here.

Not sure what you mean be MS version of NDS Client. THe clients are Win-98
and as I understand it the NDS service is built into Win-98 MS Clietn for
Netware. I assume this is working but not sure. The rights to the Volumes
are fine I am just not getting a Login Script for these users using MS
Client for Netware.

Hansang Bae <hb...@primenet.com.REMOVE> wrote in message
news:80v17c$6tb$1...@nnrp02.primenet.com...

[Hansang Bae]

"Joe K. Bales" <joeb...@home.com> writes:
>Only One Server Here.
>Not sure what you mean be MS version of NDS Client. THe clients are Win-98
>and as I understand it the NDS service is built into Win-98 MS Clietn for
>Netware. I assume this is working but not sure. The rights to the Volumes
>are fine I am just not getting a Login Script for these users using MS
>Client for Netware.

By default MS' NDS is not enabled. You have to add it yourself. If you
haven't, then adding it may fix your problem. On my test machines, the
login script runs just fine.

If you already have the MS NDS enabled, then perhaps W98 service pack
one will fix it for you. Again, my Win98 (and Win98SE) boxes run the
login script just fine.

[Joe K. Bales]

Okay
I loaded the NDS and now how a differnet log in. It is much like the client
32 login and it is running the login script from the OU container with one
BUT

it says path invalid in the mappings I have any thoughts on this my mapping
settings are as follows

map root H: = \\vhs1\user
map root P: = \\vhs1\data\Info Sys
map root S: = \\vhs1\data\Shared

looks like I am almost there if the above mappings would work without the
path invalid commin up.

Once logged in I can go to a DOS prompt and do the above mappings fine.

Any thoughts here.

Thanks for you input on this issue

joe

Hansang Bae <hb...@primenet.com.REMOVE> wrote in message

news:80v9in$m68$1...@nnrp02.primenet.com...

[Hansang Bae]

"Joe K. Bales" <joeb...@home.com> writes:
>I loaded the NDS and now how a differnet log in. It is much like the client
>32 login and it is running the login script from the OU container with one
>BUT
>it says path invalid in the mappings I have any thoughts on this my mapping
>settings are as follows
>map root H: = \\vhs1\user
>map root P: = \\vhs1\data\Info Sys
>map root S: = \\vhs1\data\Shared
>looks like I am almost there if the above mappings would work without the
>path invalid commin up.
>Once logged in I can go to a DOS prompt and do the above mappings fine.

Don't use UNCs. Jsut do it as "map root h:=vhs1/user:" or "map root
s:=vhs1/data:shared" I'm assuming that vhs1 is the server name and user
and data are volume names.

"Info Sys" may cause you grief becuase of the space. So you can
probably put it in quotes, or user the DOS equvalent name, or use an
underscore.