Initial login normal but unlock after desktop lock requires be to unlock via windows

XP Pro SP 2 running Client 4.91 SP3 logging onto local workgroup.  I log in with tree context or server or just with IP. Logs in fine.  But when desktop is locked, it cannot be unlocked via default eDirectory but requires it be unlocked via Windows.

This is on a computer that was just sysprepped to allow image to be distributed to other machines. Before sysprep, this issue was not there. But after sysprep, it is there on any image we deploy.

Here's how it went:

1. Sever updates client via initial install.
2. I configure using a dingle desktop that anyone who logs on uses.  These are not individual desktops so sync of Windows and User password does not take place.
3. I log onto network and user desktop once configured. I then log off and back onto workstation only and, after releasing dhcp lease, I run syspep mini reseal.
4. When I installed new image, via ghost, and booted, and was well. I have followed this same procedure many times.

But as soon as I lock desktop, I cannot get back in via e-directory. I have to choose windows.  Please do not get into why it is done this way. It just is.  

The question I have is how does this creep into the image creation and is there a way to make sure it does not do it again, or is there a quick fix after the fact.  I have compared Novell login properties between this machine and another based on a different image and I cant see any differences.

Thanks and Merry Christmas/Happy holidays.  I'm not going to get back to this until Tuesday of next week, but I needed to get this in before I forgot the details from too much holiday food.