I keep seeing a problem occassionaly with users not being able to login. According to my radius logs below, it appears that the password is arriving corrupt in some way. The users do NOT have CHAP enabled. I am running DSPs with 2.0.51 code: (Radius :00238) 7/5/2000 13:26:14 ODBC_AUTH: Invalid Password Attempt [Jû¼^5® ñLÂBà d"] - username-xxxx (Radius :00070) 7/5/2000 13:26:14 ODBC_AUTH: Invalid Password Attempt [d°£0ÃÂ%t xZN Nn¾] - username-xxxx (Radius :00238) 7/5/2000 13:26:18 ODBC_AUTH: Invalid Password Attempt [Jû¼^5® ñLÂBà d"] - username-xxxx (Radius :00070) 7/5/2000 13:27:31 ODBC_AUTH: Invalid Password Attempt [=ÂãZd] - username-xxxx (Radius :00238) 7/5/2000 13:27:32 ODBC_AUTH: Invalid Password Attempt [¨xX¸¡'.à ~;)ATZ] - username-xxxx (Radius :00070) 7/5/2000 13:27:35 ODBC_AUTH: Invalid Password Attempt [=ÂãZd] - username-xxxx Aside from line noise, what could be causing this? The username comes through fine every time without corruption, so something tells me it might not be line noise. It happens to a variety of users throughout the day, to a variety of phone numbers. Any thoughts? -- Scot - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.