Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

disable win 2000 login

Status
Not open for further replies.

Parmb

Technical User
Dec 17, 2001
89
GB
Were running an novell netware 5.1 network. One PC had no NW client, hence was using win 2000 to login and map n.work drives. this works fine but, then i have 2 set up each user on that machine.

Ok, i tried 2 install NW client however on login it request both NW login and win 2000 login. I tried 2 diable the users from control pannel - so no login required, but the machine now asks for both NW cliet login and win 200 login.

How do i stop this and run completly on NW client.

Any help appreciated
Thanks In advance
Parm
 
Installing ZenWorks and using DYNAMIC USERS, which is configurable from a policy setting, may solve this problem for you. As users log into NW a user is dynamically created on the local workstation, and optionally deleted when they log out. ZenWorks starter pack is free with NW5.1. Using the Dynamic Users feature worked well for me with NT4 workstations, but behaved somewhat erratically with Win2k machines, the full product I suspect is more compatible with Win2k workstations. Kind Regards,
Beeappy.
 
I'm afraid you can't just use the NetWare client, NT/2K insists that the interactive user has to have some sort of local account to log on with. You could of course just have ALL the users of this machine using one and the same NT account, but then you lose any benefits of profiles and the like.

But as you've already created each user a local account, if you ENABLE a policy called "Do not display last user name in logon screen" on the local machine, this may help.

It can be found in...
\Start\Settings\Control Panel\Administrative Tools\Local Security Policy\Local Policies\Security Options

All this is basically doing is forwarding the username and password that the user gives to the NetWare client on to the NT/2K logon dialogue box, which if they are valid accepts them without showing anything on the screen. So the user only ever sees the NetWare logon box.

The local NT account names and passwords have to be identical to the NetWare ones.

The NetWare clients Gina is being used to log on with, which it probably will be unless you've intentionally changed it.

One gotcha though is if your using password ageing on NetWare, because the passwords are NOT automatically being sync'd. So each user will have to use CTR-ALT-DEL to change his local NT password when NetWare forces him to change his NetWare one.

Hope this makes sense.

Kind Regards,
BeeAppy.

Kind Regards,
Beeappy.
 
Here's how I solved this problem.

- In the Novell Client on the 'Advanced Login' Tab activate 'Location List'.

- Next select 'Location Profiles' Tab

- In 'New Location Profile' type the Name of your User, not the Login Name but the actual Name and then click 'Add'

- In the window that pops up next under 'Service Instance' type the Name of your user again and click 'add'.

- In the window that pops up next you have to fill in the following tabs: credential, NDS, Windows. The other you can leave at the default setting. Also check 'Save Profile after successful login'.

- Now hit ok everywhere and do a logout and you'll see what happens then. Each user can then select him/herself from a drop-down list at login.´

Hope this helped.

n7262
 
Good for a small amount of users, bad if you have 1000 users onsite! -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
Usually there aren't a 1000 users logging in from the same workstation. Mostly it's 1-2 public PC's in the department, so you only have to set up the department users.

That way it's also sort of a security measure.

nt262
 
Don't you suffer from the two passwords going out of sync? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
Actually they have to be in sync otherwise you're getting a second login box for W2K.

This mechanism is nothing more than a help to not have to enter your login name and password twice, but helps you prepare your login for both the network and the local machine so that you only have to enter your password once.

Try it and you'll see how it works.

nt262
 
I would still suggest Dynamic Local User, however you can also do what the following Microsoft TID suggests to get W2k to automatically login:

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
We solved this problem using the auto admin logon feature of Windows 2000. Doing this, you store the username and password of a local account in the registry. We then use Zenworks to handle the security settings, giving each user rights through group policies. The problem we had with dynamic users is when the local account was created and removed at logout, certain software packages we use reset also, returning them to the default settings. Using auto admin logon, we can feel confident that each user that logs in to the machine will have a consistent interface.

Go to support.novell.com and search for "autoadminlogon".

Hope it helps.
 
Er... isn't that what I posted in my previous post??? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top