Member Avatar for jheidelberger

:'(

  • 4 Contributors
  • 3 Replies
  • 340 Views
  • 4 Years Discussion Span
  • Latest Post Latest Post by TheNNS

Dani AI

Generated

Short summary and practical advice that builds on and without repeating their exact steps.

There are two common ways to handle XP + Novell Client dual-login: make the Windows logon primary (the Microsoft GINA) or keep Novell’s NWGINA but stop it from forcing a login at boot so users sign into Windows first and then run Novell manually. The Novell client supports a formal “passive”/deferred-login mode where NWGINA defers to the Microsoft logon and then attempts Novell authentication using the workstation credentials — useful when Windows and eDirectory usernames match, but problematic when they do not. Novell’s docs and TIDs explain the passive behavior and the possible side effects (extra Novell prompts or splash screens if not adjusted). (novell.com)

If usernames differ, the safer route is to leave the Novell client as the primary GINA and disable its automatic initial login (so the desktop comes up on the normal Windows logon). Then make Novell Login available after logon — either put a Novell Login shortcut in Startup or call the Novell login utility at sign-on so scripts and mappings run in the proper session. A common one-line startup command is:

loginw32.exe %username% /NA /CONT

That approach runs the Novell login for the signed-on user and lets you control whether scripts show or run silently. Novell/NetIQ documentation describes these command-line options and the recommended workarounds when using passive/deferred modes. (netiq.com)

Troubleshooting and cautions: test the chosen method on a lab machine, confirm the Novell Client build is compatible with the XP build you’re running, and back up any registry/configuration before changing login behavior. Remember that passive/deferred login can skip NWGINA-run login scripts unless you explicitly run the Novell login utility afterwards, so plan drive mappings and script execution accordingly. See the Novell client readme and TIDs for version-specific caveats. (novell.com)

Recommended Answers

All 3 Replies

Member Avatar for Tekmaven

This is a simple answer. Goto regedit, navigate down this path: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon. Find the key: GinaDLL, which should have the value NWGINA.DLL (or similar). Change it to MSGINA.DLL. This will bring up the windows login first (2k style, not the xp style.. this is impossible to do with the NW client installed), and if the username dosent exist on the NW server, or the password dosent match the one on the NW server for the user name, the NW client will come up asking for a login. I hope this solves your problem.

Member Avatar for Compum

It is not so good solution in case you have different user names (Novell and MS account), because MSGINA puts MS login name into Novell Client user name field.
Better solution is to leave NWGINA as first login engine and to set Novell Client parameter "Initial Novell Login"=OFF. Just go to Novell Client properties - Advanced login - Initial Novell Login - OFF.

Put Novell Client shortcut icon on Desktop or into Starup menu.

Member Avatar for TheNNS

It is not so good solution in case you have different user names (Novell and MS account), because MSGINA puts MS login name into Novell Client user name field.
Better solution is to leave NWGINA as first login engine and to set Novell Client parameter "Initial Novell Login"=OFF. Just go to Novell Client properties - Advanced login - Initial Novell Login - OFF.

Put Novell Client shortcut icon on Desktop or into Starup menu.

Yeah, he's absolutley right.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.