Not running Login Scripts

[basil3legs]

We are migrating a network from a Novell 3.12 Server to a 5.1 Server but are having problems with the login scripts not running. They run fine on the 3.12 system but when the same machine (Windows 98) is plugged into the Novell 5.1 server, the Netware Login Script does not run. We have loaded Novell's client on one machine rather than using the Microsoft version and this machine does now run the script fine but we have some very temporamental software so would prefer to use the Microsoft Netware Client if possible.

Does anyone have any suggestions?

Thanks in advance...

 

[marvhuffaker]

If your clients are now logging in to the 5.1 server, they will grab the Login script from the tree the 5.1 server belongs to.

Have you copied the login script from the 3.12 system to the container script in the 5.1 tree?

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[basil3legs]

Hi Marvin,

This server was sort of dumped on me and I don't know much about version 5. I have created a new login script within each users properties. The tick is in the box in the network settings on the 98 machines that says "run login script" but only the one with the Novell client does. Are you saying this is the wrong place to put the scripts for 98 logins? That would make sense as it doesn't work with them there.

 

[terry712]

never created user script's
they are the work of the devil

put the script in the container
and use if member of group then map blah blah

 

[TheLad]

That's where the good old EXIT command at the end of the container login script comes in really handy. Then if anyone has created a user script, the bloody thing won't run!

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[marvhuffaker]

Whenever I find an admin that sets up User Login scripts, I put them in a straightjacket and tie them to my bumper. It's really for their own good.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[terry712]

i would also tried to get rid of the ms client
it is very restrictive and is pretty bindery based


the software should work just as well with the novell client

use a container script with properly setup groups if required and an exit at the end
user's scripts are an admin nightmare and shouldnt be used
there are enough variables available that even the most complex situation can be catered for

 

[marvhuffaker]

Hey I missed the part about using the MS client for Novell. Get rid of that garbage. Novell client all the way. The more microsoft pieces you can replace with Novell, the better.

When you use the MS CLient, you are logging in with Bindery services, and so even if you have a container script, the login scripts won't always run depending on how you have bindery services setup. Plus you're losing out on all of the cool features of NDS.

I'd bet a dollar that your "Tempermental" apps will run just fine with the Novell client.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[basil3legs]

I have used seperate user scripts as there are only about 5 users on the network and also because the container script wasn't running anyway. All the scripts are the same so can soon be put back but as they don't run antway, what's the point .

However, this is a REALLY temporamental application and we daren't risk using the Novell client. It is uor main manufacturing and invoicing software and whoever originally wrote it (in MS FoxPro for DOS!) appear to have left a few glitches, although they are possibly down to Microsoft! It lpays up if NetBEUI is on the machine or if the Hard Drive is formatted with Fat32 and various other reasons we have yet to discover and stuffs up the invoices. The company is too reliant on the software to replace it as it has been ammended over the years to do just what we want.

So, Marvin, it would probably be the easiest dollar I'd ever make if I bet you that it wouldn't work with the Netware Client instead.

However, you mention the scripts won't always run depending on how the Bindary Services are set up. How do they need to be set up for the login scripts to run as this sounds like the cause of the problem if this is something that has changed between versions 3.12 and 5.1