Dear all,
I have a problem regarding to password case sensitivity.
Our company's servers are configured to use plain text passwords
with PAM due to historical reasons. My collegues encountered a long
delay each time they boot their PC and map the network shared disks.
They sometimes even failed connection. The server always says:
Jul 18 17:54:37 atlas PAM_pwdb[30192]: authentication failure; (uid=0)
-> imacat for samba service
or
Jul 18 17:59:52 atlas samba(pam_unix)[30197]: authentication failure;
logname= uid=0 euid=0 tty=samba ruserrhost=streetwalker.pristine.com.tw
user=imacat
After several days of debugging, I found that the server had
received the password for 3 times: The client sent an upper-cased
version of the password and failed twice, and then the untouched password
(which is correct and successful).
I guess it's the historical compatibility reason that Windows 98
does so. I can try the "password level", though, but it can't fix
the
delay (and maybe timeout) problem.
Since it will send the untouched password at last, is there a way to
tell Windows 98 clients to send the untouched password first? Is there
a possible way to modify some registry entries on this? Or, should I
turn to encrypted passwords and make the hard way instead?
I'm using samba 2.2.5 with linux 2.4.18, Red Hat 7.3, glibc 2.2.5,
pam 0.75, clients Windows 98 SE.
--
Best regards,
imacat ^_*'
imacat@mail.imacat.idv.tw
PGP Key: http://www.imacat.idv.tw/me/pgpkey.txt
<<Woman's Voice>> News: http://www.wov.idv.tw/
Tavern IMACAT's: http://www.imacat.idv.tw/
TLUG List Manager: http://www.linux.org.tw/mailman/listinfo/tlug
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 240 bytes
Desc: not available
Url :
http://lists.samba.org/archive/samba/attachments/20020721/4cd7d5f0/attachment.bin
?????? wrote:> > Dear all, > > I have a problem regarding to password case sensitivity. > > Our company's servers are configured to use plain text passwords > with PAM due to historical reasons. My collegues encountered a long > delay each time they boot their PC and map the network shared disks. > They sometimes even failed connection. The server always says: > > Jul 18 17:54:37 atlas PAM_pwdb[30192]: authentication failure; (uid=0) > -> imacat for samba service > > or > > Jul 18 17:59:52 atlas samba(pam_unix)[30197]: authentication failure; > logname= uid=0 euid=0 tty=samba ruser> rhost=streetwalker.pristine.com.tw user=imacat > > After several days of debugging, I found that the server had > received the password for 3 times: The client sent an upper-cased > version of the password and failed twice, and then the untouched password > (which is correct and successful). > > I guess it's the historical compatibility reason that Windows 98 > does so. I can try the "password level", though, but it can't fix the > delay (and maybe timeout) problem.The delay is due to the PAM module. Look into the doco for your pam modules for somthing like 'nodeley'> Since it will send the untouched password at last, is there a way to > tell Windows 98 clients to send the untouched password first? Is there > a possible way to modify some registry entries on this? Or, should I > turn to encrypted passwords and make the hard way instead?Win98 sends the passwords only once. In UPPER case. We then try and figure out what case the password really is in. You sould turn on encrypted passwords, as it makes this all 'go away'. -- Andrew Bartlett abartlet@pcug.org.au Manager, Authentication Subsystems, Samba Team abartlet@samba.org Student Network Administrator, Hawker College abartlet@hawkerc.net http://samba.org http://build.samba.org http://hawkerc.net
Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 240 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20020722/8909254d/attachment.bin
Yo there, I am not sure if this is going to help. Check how you configured your win98 client to log in. Try using poledit tool to configure windows to log in to a specific domain. This mght solwe the problem. I am thinking your win98 client is configured to log in in a workgroup invoirment therefore it does not care in witch case it sends passwords. Just look at logon types for win98. Maybe you will get lucky. regards, admir "¨Ìº¿¿ß" <imacat@mail.imacat.idv.tw> wrote in message news:20020722030504.583C.IMACAT@mail.imacat.idv.tw...