Member Avatar for sboothman

Situation

I am new to Novell but I do have experience with Linux and Windows. I have recently downloaded a evaluation copy of Novell OES, and I am trying to set it up on a Dell PowerEdge 1800 with a Windows XP Client.

So far I have installed the software onto the server and set up user accounts, Tree, Context, user volumes and licenses for the users. I have also installed the latest Novell Client software onto the Windows XP machine.

The Problem

When I start the Windows XP client I am presented with the Novell Client, I click on advanced and fill in the Tree, Context and server IP fields. Then I put in a username and password and it logs in fine, very fast and no problems. However when I log out, I am unable to log back in again as the Novell client cannot find the server. I log in locally and I can still ping the server however. The only way to allow me to log in again, is if I restart the client machine, then it lets me log in again.

Has anyone had this problem before or know why it might be occurring.

Thanks for your help

Sam

  • 2 Contributors
  • 2 Replies
  • 130 Views
  • 6 Days Discussion Span
  • Latest Post Latest Post by sboothman

Dani AI

Generated

This problem often turns out to be a client-side configuration or image issue rather than an OES/server fault. later reported that other workstations worked normally, and suggested splitting the Windows/Novell logon as a diagnostic. Those outcomes point toward something on the specific XP machine (drivers, third‑party software, or a corrupted client install) that breaks Novell client discovery/authentication after the first session.

Quick checklist to isolate the cause:

  • Confirm the Novell Client version/build and Windows updates on the broken machine match a working one.
  • Inspect Windows Event Viewer and the Novell Client logs around the failed logon attempt for error codes or timeouts.
  • Try a clean boot (disable nonessential services and security software) to rule out anti‑virus/firewall interference.
  • Update NIC drivers and check adapter settings (power management and multiple adapters can cause intermittent connectivity).
  • Compare installed login/SSO components or image customizations between the good and bad workstation; custom logon hooks commonly cause this kind of symptom.
  • If needed, run a packet capture during a failed logon to see whether the client is sending discovery/auth packets and whether the server replies.

Practical workflow: reproduce the failure, collect logs and a packet trace, perform a clean boot test, and then a controlled repair or reinstall of the Novell Client. If a repair fixes it, use a binary/registry diff against the known‑good workstation to identify the offending change. Always back up system state before making low‑level changes.

Note: dual‑logon/split logon can be a useful diagnostic but is a workaround rather than a root‑cause fix. Since confirmed the problem was isolated to one workstation image, focus on comparing that image to a working one and on client‑side diagnostics before changing server settings.

Member Avatar for Ram Appsense

hi,

try to have dual logon, i.e., u can set the logon screen such that ur windows logon will be first and the novell logon will be second.. its just breaking a single logon window into two.

try with that and come back if the same problem occurs....


u can change the logon by changing
HKEY_LOCAL_MACHINE\software\Microsoft\Windows NT\currentversion\winlogon

change the value of the key GinaDLL to MSGINA.DLL


cheers

Member Avatar for sboothman

OK i have solved the problem now thank, I tried a different workstation and another one and it seems to work fine on both of them, I didn't set up the client I was working with so there must of been a configuration problem.
Thanks for your help.

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.