Alan DeKok wrote:
Why are you looking at the client side? The README, INSTALL, FAQ, and daily messages on this list say that you should run in debug mode. What do we have to add to the documentation to convince you that this is a good idea?
Why is the password displayed in plain text instead of hashed as on the old server?
Because it helps with debugging.
I think you didn't get the point of my question. I was wondering about the difference on two clients querying the same server for the same data.
So... the passwords don't match?
They do but the lookup seems to be incorrect. What I have in the file is the outout of "smbencrypt" but maybe that's not what the server is expecting.
Post it here.
Ready to process requests. rad_recv: Access-Request packet from host 127.0.0.1:65271, id=108, length=57 User-Name = "fwvpn" User-Password = "XXX" NAS-IP-Address = 255.255.255.255 NAS-Port = 10 try to find in file rlm_passwd: Added LM-Password: '624AAC413795CDC1AAD3B435B51404EE' to config_items rlm_passwd: Added NT-Password: 'C5A237B7E9D8E708D8436B6148A25FA1' to config_items try to find in file Login incorrect: [fwvpn/cu@34t] (from client localhost port 10) Sending Access-Reject of id 108 to 127.0.0.1 port 65271 The password is displayed in plain text. Regards fw