Password question

Morning,
Yesterday I got a call from a developer, telling me that the MSSQL Login
(for a application) that I set up for him on ServerA was not letting him
login. This exact same MSSQL Login was also set up on ServerB and it works
fine. After, a bit of time, of looking into it I stumbled on the problem and
fix. The fix was the password length for the SQL Server login account.
According to BOL, the password can be from 1 to 128 & alpha-numeric. The
password was a 19 alpha-numeric character password. This worked with no
problems on ServerB but failed on ServerA.
ServerB is a Windows 2000 server while ServerA is NT4 SP6.
So, I'm thinking that even though this was a MSSQL login and not a OS login,
the OS layer is playing a role in the authentication process. Does anyone
know if this is so and what are the limitations of NT4 password length?
Thanks for you time,I forgot to add, both are SQL2000 SP3.
"JoeyDBA" <JoeyDBA@.yahoo.com> wrote in message
news:uQErEJmbEHA.716@.TK2MSFTNGP11.phx.gbl...
> Morning,
> Yesterday I got a call from a developer, telling me that the MSSQL Login
> (for a application) that I set up for him on ServerA was not letting him
> login. This exact same MSSQL Login was also set up on ServerB and it works
> fine. After, a bit of time, of looking into it I stumbled on the problem
and
> fix. The fix was the password length for the SQL Server login account.
> According to BOL, the password can be from 1 to 128 & alpha-numeric. The
> password was a 19 alpha-numeric character password. This worked with no
> problems on ServerB but failed on ServerA.
> ServerB is a Windows 2000 server while ServerA is NT4 SP6.
> So, I'm thinking that even though this was a MSSQL login and not a OS
login,
> the OS layer is playing a role in the authentication process. Does anyone
> know if this is so and what are the limitations of NT4 password length?
> Thanks for you time,
>|||If it's a SQL login account we don't interact with the OS.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||As Kevin already pointed out, a SQL Login doesn't interact
with the OS.
One possibility, If the server uses a case-sensitive
collation, then your passwords are case sensitive as well.
-Sue
On Tue, 20 Jul 2004 09:02:59 -0500, "JoeyDBA"
<JoeyDBA@.yahoo.com> wrote:

>Morning,
>Yesterday I got a call from a developer, telling me that the MSSQL Login
>(for a application) that I set up for him on ServerA was not letting him
>login. This exact same MSSQL Login was also set up on ServerB and it works
>fine. After, a bit of time, of looking into it I stumbled on the problem an
d
>fix. The fix was the password length for the SQL Server login account.
>According to BOL, the password can be from 1 to 128 & alpha-numeric. The
>password was a 19 alpha-numeric character password. This worked with no
>problems on ServerB but failed on ServerA.
>ServerB is a Windows 2000 server while ServerA is NT4 SP6.
>So, I'm thinking that even though this was a MSSQL login and not a OS login
,
>the OS layer is playing a role in the authentication process. Does anyone
>know if this is so and what are the limitations of NT4 password length?
>Thanks for you time,
>|||ok - thanks for the feed back. I'll go back and play with it again.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:8SC7MkobEHA.2924@.cpmsftngxa06.phx.gbl...
> If it's a SQL login account we don't interact with the OS.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>