[cvsnt] SSPI and "Can't authenticate - perhaps you need to login first?" error.

[Michael Kennedy [UB]]

Hi Tony,

Please see my inline comments.

"Tony Hoyle" <tmh at nodomain.org> wrote in message
news:calc1t$cdn$1 at paris.nodomain.org...
> Michael Kennedy [UB] wrote:
>
>   > Now isn't that strange considering you don't login with SSPI
> authentication?
>
> You can... it's useful for logging in over the internet.

I see. Does it speed up the communication? Since technically it logs in
every time automatically using the SSPI procedures and all.

> > What's more strange is it just worked perfectly for years and now just
went
> > batty. I didn't update any of the software (client or server) in at
least a
> > few weeks and then I get that error. Here's the actual error output:
>
> Has your domain password expired?  (technically it just means that the
> SSPI negotiation failed before you had an authentication token...  it
> could be kicking you out for any number of reasons, but password is the
> obvious one).

No, I checked that my password might have expired but it had not. Another
thing tell us for sure that it's not the password is by switching to version
1.3b13-2 (or whatever is beta 13.2) of WinCVS makes it work again still
using SSPI. That wouldn't have any effect if my password or account had
expired / was disabled.

Since this part of the original post isn't here, I'll just reiterate the
situation a bit for other readers:

    WinCVS 1.3b16, b17, b17.2 used to work using SSPI then stop suddenly
    WinCVS 1.3b13.2 continues to work using the exact same settings

I have tried to use the option Admin->Login and I get exactly the same
message:

     "Can't authenticate - perhaps you need to login first?"

I should mention also that I have had my password expire on the server and
you do get a failed SSPI authentication but it's a different message. It's
something about authentication failed or login failed or something. But not
this message.

Strange stuff. Hope someone has some ideas. Thanks for the ideas Tony.

Thanks,
Michael