Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Hi.
> Windows stores the passwords.. the last thing you want is
> the cvs client logging you in with any random username it
> happens to think of.
Ok, that's one way to look at it... but here's some new
insights...
First - when I originally said that the current user's login is
used - I was mistaken. I do not know which login is used -
- only that it is not working, which ever it is.
Second - I tested this same scenario on another client PC,
which should be the same as the previous one, but obviously
is not.
On this new PC everything works as I expected it to:
1. If logging in with :sspi:server:/repository then the login
information stored by Windows was used (not the current
login but the one stored by Windows for their network
connection to the server).
2. If logging in with :sspi:user at server:/repository then the
login information cached locally by CVSNT (login
command) was used.
On the original PC case 1. does not work but the second
one works fine. On that PC the older 2.0.62.1817 CVSNT
version works as I expected as well. The problem appears
only with the later versions mentioned in the earlier posts.
Now, which of these is the expected behaviour? Do you
have any idea what could be different between these two
systems to cause this? They use the same anti-virus, the
same OS, same updates have been applied and are
generally used for the same purpose (development
machines)...
Windows caches only a single username/password
combination, and my guess is that this is the login
information that should be used by default, and not the
local user name. Local user account probably should
(and is) used as a default only when issuing the login
command without explicitly specifying the user name.
Best regards,
Jurko Gospodnetic