Dumbest. Problem. EVER.
Sep. 26th, 2008 12:55 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
theweaselkingCVS server set up. User connects, remotely, via SSH to the server to do servery-things and also via TortoiseCVS to make CVS checkouts.
User's account worked in the past, with the same software, same PC, same network, etc.
User's settings in Tortoise are correct.
User's account works for me - same software, etc.
User can connect to the server via PuTTY, no problem, using *exactly* the same username, password, and port that Tortoise uses.
However, user's password does not work when his computer's copy of Tortoise submits it. He has reinstalled the program, still has the same problem.
The only weird thing: When you get a password error from Tortoise, it doesn't say that user@servername's password is wrong, is says that @servername's password is wrong - no "user". Despite the fact that Tortoise's settings show that it is submitting username and password (same as my PC), and the CVSROOT showing :ssh:user@servername, and the *password prompt* knowing the right username, the error message shows that no username is being submitted.
The source of this problem, which is the DUMBEST THING EVER?
Tortoise uses PLink to make a connection.
Plink takes two parameters - username and host.
"host" can be either a hostname, *or the name of a connection entry in PuTTY*.
This user, when connecting through PuTTY, had set the name of his saved connection settings to be the same as the name of the server.
Rename that *label* inside *a different program* so that now the *label* says "Companyname server" rather than "server.domain.tld", and suddenly Tortoise's personal, private, hidden-and-included copy of PLink uses the correct parameters it's been passed instead of just kind of guessing.
HATE ALL PROGRAMMERS.
User's account worked in the past, with the same software, same PC, same network, etc.
User's settings in Tortoise are correct.
User's account works for me - same software, etc.
User can connect to the server via PuTTY, no problem, using *exactly* the same username, password, and port that Tortoise uses.
However, user's password does not work when his computer's copy of Tortoise submits it. He has reinstalled the program, still has the same problem.
The only weird thing: When you get a password error from Tortoise, it doesn't say that user@servername's password is wrong, is says that @servername's password is wrong - no "user". Despite the fact that Tortoise's settings show that it is submitting username and password (same as my PC), and the CVSROOT showing :ssh:user@servername, and the *password prompt* knowing the right username, the error message shows that no username is being submitted.
The source of this problem, which is the DUMBEST THING EVER?
Tortoise uses PLink to make a connection.
Plink takes two parameters - username and host.
"host" can be either a hostname, *or the name of a connection entry in PuTTY*.
This user, when connecting through PuTTY, had set the name of his saved connection settings to be the same as the name of the server.
Rename that *label* inside *a different program* so that now the *label* says "Companyname server" rather than "server.domain.tld", and suddenly Tortoise's personal, private, hidden-and-included copy of PLink uses the correct parameters it's been passed instead of just kind of guessing.
HATE ALL PROGRAMMERS.