Hi all, I just installed Win2K cli

[KenB]

Hi all,
I just installed Win2K client 4.90 an several Win2K machines and at the first User login it asks for a GW password (V6.02) even though the user has no password set. I did not notice this when I installed the client after the reboot as I have a password. It has forced me to go to ConsoleOne and set a password to get the user into their mailbox. Once in the user can change their password and all in OK! I haven't yet tried having a user remove the password and see if it worked. I was hoping someone knew of what changes to the client are causing this.

TIA
Ken

 

[terry712]

user should always set a password and when they set it they should tick the no password required with nds

are you sure it's not going into caching mode or remote

in 4.9 client - there is the single sign on option as well - now i know if you dont have the no password with nds option you arent asked you password and its seamless - perhaps if you enable this and you dont have a pwd then it's prompting as it can store a blank ?

 

[KenB]

Hi Terry712,
Thanks for the prompt reply. I haven't responded back as I've been away from work because of the huricane on the East Coast and just got to try your sugestions. The client is setup in local mode so Cache and Remote are not active. This has not affected users who already had GW passwords but most of the users can't manage to find the settings to turn on a password SO.... I have found out that if a user who has a password on their account opens GW they can proxy to a mailbox that has no password but they can not open the mailbox directly.
I've tried checking/unchecking the boxes under the Groupwise password options and still nogo. I am forced to set a password. I can then show the user how to pick their own pw but we have a lot of mailboxes that are shared by internal groups (they collect mail from our web site) and I will have to set a commonly used pw on them also. I will start looking for the client documentation on the Novell support site to look for clues. In the meantime I guess I will halt the client 4.90 rollout.

Ken

 

[KenB]

Update:
I traced the problem to the NMAS module that was installed by the 4.9 client. When this was removed from the PC's everything went back to normal with the GW password. I did a custom install of the client but there was no option to turn this off, I had to uninstall it.

FYI
Kenb