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!

Client 4.91 and 4.91 SP1 login getting turned off

Status
Not open for further replies.
Sep 29, 2005
39
US
I'm running XP Pro at the desktop, with Netware 6.5 servers. The client on the desktop is 4.91 and 4.91 SP1.

The issue is that the login window is getting turned off at boot or reboot. I've set it manually to on, in the client, rebooted/powered off/on and it's there. The next reboot/power off/on and it's turned off again.

This is driving me crazy. Any ideas?

Thanks!!!
 
I guess I'll be the one to take one for the team and say that I have no idea what you are talking about.

Can you explain in a little more detail please?

Marvin Huffaker, MCNE
 
Hey Marvin,

I appreciate you responding and asking for more details.

I'll try to be more specific here:

Imagine an XP Pro client without Netware's 4.91 client. You just see the Windows logon screen, not the Netware one.

There is an option, within the Novell Client Properties Right Click My Network Places, Right Click Local Area Connection, select properties, select the Novell Client for Windows, click properties, click the Advanced Login tab, scroll down until you see Initial Novell Login. This setting should normally be on after installing the client. It's somehow automatically getting turned off.

I turn it on, reboot and it's fine. I reboot again and it's turned off again.
 
Well, okay, the thing is.. When you install the Novell client, it defaults to being the primary login. You actually have to go to some effort to make the Windows login come up first.

It seems to me that since you are setting it, it works, then it doesn't work... Something is forcing it to change back. Do you have Group Policies that are interfering with the Windows settings? Or maybe you are pushing some reg hacks out with Zen? In those scenarios, it would work the first time, the policy would be pushed, and then the next time it would be hosed again.


Marvin Huffaker, MCNE
 
Found out what was causing it.

We've started using iPrint to assign printers via a Workstation package and iPrint policy. In each policy, the Zenworks for Desktops Management Agent Policy was being turned on (at this point I don't know what that's really for). I've turned it off which has fixed the initial login prompt.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top