How to login to windows and authenticate to novell automatically

by: AndrewW5Posted on 2009-01-14 at 10:00:59ID: 23375465

Are you using the Novell client for Windows?

http://www.novell.com/products/clients/windows/xp2000/overview.html

From the bullets:

"Use a single, synchronized login"

by: pumpuyPosted on 2009-01-14 at 10:06:44ID: 23375524

Yes we are using Novell client for windows version 4.91. Thank you.

by: pumpuyPosted on 2009-01-14 at 10:23:06ID: 23375697

We would like to find out if there is a way in windows xp/2000 to be able to login to windows and have novell authenticate automatically. We currently are able to login to novell 4.91 and windows authenticates automatically, but we would like to reverse it. Thank you.

by: ChiefoftheChissPosted on 2009-01-14 at 10:27:05ID: 23375742

I've never done this reversed, but you might try to map a network drive to the Novell server in a login script (either in startup or via group policy) with the username and password stored in that.

by: ShineOnPosted on 2009-01-14 at 18:47:41ID: 23380113

You can't log in to Windows and have the Novell authentication take place seamlessly. Windows is stupid - it assumes that it is the only thing in the world you might want to authenticate to.

You can, as suggested by ChiefoftheChiss, have a Novell resource - a NetWare/OES drive mapping, an iPrint/NDPS printer as your default printer, etc - force the login dialog, but that's what will happen. After you log in to Windows, when the Novell-provided resource is requested and the Windows requester can't handle the connection, another login dialog will appear.

It could have the user ID filled in already, but the password won't pass from the Windows login to the Novell login.

However - if you have a modern NetWare or OES server, you could configure CIFS - and even join the NetWare server to your domain - and have "native" access without using the Novell Client32. You lose the advanced features of the Novell filesystem - it makes it look like a Windows share - and none of the other features Client32 provides will be available, but it will work. You could even do any mapping with your WSH Windows login script.

by: ZENandEmailguyPosted on 2009-01-26 at 20:17:23ID: 23473653

Is this resolved? If not, consider looking at this TID and its solution: I've used a free third party app to do auto-admin login to a Novell client and into the workstation via autoadmin and it worked quite well.

http://support.novell.com/docs/Tids/Solutions/10052847.html

by: ShineOnPosted on 2009-01-26 at 21:07:27ID: 23473866

I was wrong. There is a way, using the client you're already using. Dang, that's my one for the year...

With the 4.91 client, you can do a registry tweak and set it up for "passive mode" login, so the Novell client's login is secondary to the MSGINA. http://www.novell.com/documentation/noclienu/noclienu/index.html?page=/documentation/noclienu/noclienu/data/hxccolpj.html#hxccolpj

Snippet is excerpted from the page linked to.

Note that login scripts do NOT process when in passive mode.
Also note that this functionality requires 4.91 SP3 or later. Current is SP5.

7.6 Enabling Passive Mode Login
 
When configured for passive mode login, the Novell Clients NWGina defers to the Microsoft Graphical Identification and Authentication Dynamic Link Library (msgina.dll) for the initial workstation login. After authentication to the workstation, NWGina attempts to authenticate to the Novell environment. The username and password used for workstation authentication are also used for the Novell authentication.
 
To successfully authentication to the Novell environment, the username must exist in eDirectory, and the default location profile must be properly configured with the Tree and Context information.
 
To enable passive mode login, set the following registry keys:
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\NWGINA] PassiveMode=dword:00000001
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Login] PassiveModeNDSLogin=dword:00000001 PassiveModeNDSLoginSilent=dword:00000000 or 00000001 PassiveModeNDSLoginRequired=dword:00000000 or 00000001
Registry Setting Descriptions
 
    *
 
      PassiveMode: (0/1) default is 0 0 = normal mode 1 = passive mode
    *
 
      PassiveModeNDSLogin: (0/1) default is 0 0 = don't do Novell login 1 = do Novell login
    *
 
      PassiveModeNDSLoginSilent: (0/1) default is 0 0 = report Novell login errors 1 = don't report Novell login errors
    *
 
      PassiveModeNDSLoginRequired: (0/1) default is 0 0 = don't require Novell login 1 = require Novell login
 
Notes:
 
    *
 
      If the PassiveModeNDSLoginRequired setting is True (1), the GINA login experience requires a successful Novell authentication in order to succeed.
    *
 
      The PassiveModeNDSLoginSilent setting requires functionality released in the Novell Client for Windows XP/2003 4.91 SP3 or later.
    *
 
      Login scripts are not processed in passive mode. A workaround is to run them after the GINA login. You can do this by placing a run entry in the registry, or you can create an entry in the startup folder.
 
      The following in a run key example:
 
      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] nwscript=reg_expand_sz:loginw32.exe %username% /NA /CONT

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:

Select all Open in new window

by: ZENandEmailguyPosted on 2009-01-27 at 05:44:57ID: 23476144

Here is a link to one of the apps I've used in the past to do the auto-login through the Novell client:

http://www.novell.com/communities/node/322/autolog+3+0+1+3

It appears to be free.

by: ShineOnPosted on 2009-01-27 at 15:40:42ID: 23482341

ZENandEmailguy - the asker is looking for how to switch from NWGINA to MSGINA and have the authentication to NetWare/eDirectory take place seamlessly subordinate to the MS login.

They're not looking for an autologin process. If they're going to a Windoze domain, then autoadminlogon is the last thing they want to do. Autoadminlogon is great in a NetWare environment to automate login to NetWare and the local administrator account at bootup, for "service" PC's - but not for a swap of NWGINA for MSGINA while allowing the end users to seamlessly authenticate to both Windows/AD and NetWare/eDirectory...

That would be the registry tweak for the Novell Client32 4.19 SP3 or later I posted. I originally said "can't be done" because before 4.91SP3 it couldn't - because of the reasons I mentioned. Apparently 4.91SP3 and later handles the intelligence the MS client lacks, and forces a workaround of the MS client's shortcomings with regard to acknowledging and working with non-Microsoft systems and clients...

by: ZENandEmailguyPosted on 2009-01-27 at 16:32:20ID: 23482628

Ok...thanks for the clarification.

Question

How to login to windows and authenticate to novell automatically

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

Novell Netware Network Software

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Need individual assistance?

Our experts are ready to help.

Want to learn from the best?

Read articles from industry experts.

Working on a long term project?

Store your work and research.

What Makes Experts Exchange Unique?

Trusted by the world's most respected brands.

Faithfully serving IT professionals since 1996.

Related Solutions

Free Tech Articles

Cloud Class Webinars

Join the Community

Give a Little. Get a Lot.

Answers

3 Ways to Join

The Experts

The Experts

Testimonials

Testimonials

Testimonials

Business Clients

Business Clients

In the Press

In the Press

In the Press