Welcome to the VanDyke Software Forums

Join the discussion today!


Go Back   VanDyke Software Forums > File Transfer

Reply
 
Thread Tools Display Modes
  #1  
Old 11-26-2014, 08:45 AM
Jasper_SG Jasper_SG is offline
Registered User
 
Join Date: Nov 2014
Posts: 1
VShell Bug

I have VSHELL Version 4.0.2 (x64 build 519) installed on a 2K8 R2 Std machine.

We utilize a combination of Password and Public Key authentication and recently came across this issue.

Our Client raised an issue of not being able to SFTP to our system (using their usual Private Key). Upon investigation we saw this in the log files.

Quote:
2014-11-25 00:10:24 VShellSSH2 conn 4445 IPADDRESS 27919 - - - 0 0 0 0 SERVERIP 22 "04445: Connection accepted from IPADDRESS:27919"
2014-11-25 00:10:25 VShellSSH2 auth 4445 - - USERNAME - - 0 0 0 0 - - "04445: Client specified user name USERNAME, resolved as USERNAME"
2014-11-25 00:10:25 VShellSSH2 auth 4445 IPADDRESS 27919 USERNAME - - 0 0 0 0 - - "04445: none for user USERNAME rejected because it is unavailable"
2014-11-25 00:10:25 VShellSSH2 auth 4445 IPADDRESS 27919 USERNAME - - 0 0 0 0 - - "04445: Received unsigned public key (ssh-rsa); checking authorization (fingerprint: **FINGERPRINT**)"
2014-11-25 00:10:25 VShellSSH2 auth 4445 - - USERNAME - - 0 0 0 0 - - "04445: Searching 'C:\Program Files\VShell\PublicKey\USERNAME' for matching public key for authentication"
2014-11-25 00:10:25 VShellSSH2 auth 4445 - - USERNAME - - 0 0 0 0 - - "04445: 'PUBLICKEY' contains matching public key for user USERNAME"
2014-11-25 00:10:25 VShellSSH2 auth 4445 IPADDRESS 27919 USERNAME - - 0 0 0 0 - - "04445: Received signed public key (ssh-rsa); attempting authentication (fingerprint: **FINGERPRINT**)"
2014-11-25 00:10:25 VShellSSH2 auth 4445 - - USERNAME - - 0 0 0 0 - - "04445: Searching 'C:\Program Files\VShell\PublicKey\USERNAME' for matching public key for authentication"
2014-11-25 00:10:25 VShellSSH2 auth 4445 - - USERNAME - - 0 0 0 0 - - "04445: 'PUBLICKEY' contains matching public key for user USERNAME"
2014-11-25 00:10:25 VShellSSH2 auth 4445 IPADDRESS 27919 USERNAME - - 0 0 0 0 - - "04445: Could not get authentication token for user USERNAME; further authentication is necessary: The user's account was not found, or a failure occurred looking up the user's account information"
2014-11-25 00:10:25 VShellSSH2 auth 4445 - - USERNAME - - 0 0 0 0 - - "04445: publickey for user USERNAME accepted, further authentication needed"
2014-11-25 00:10:25 VShellSSH2 auth 4445 - - USERNAME - - 0 0 0 0 - - "04445: password for user USERNAME rejected"
2014-11-25 00:10:25 VShellSSH2 auth 4445 - - USERNAME - - 0 0 0 0 - - "04445: password for user USERNAME rejected"
2014-11-25 00:10:25 VShellSSH2 auth 4445 - - USERNAME - - 0 0 0 0 - - "04445: password for user USERNAME rejected"
Looking at this VSHELL server+config, it was no different to the VSHELL server next to it, which was working and used the same public/private keys.

I restarted the vhsell service, to no avail. Rebooted the server also didn't fix the issue. Using the credentials, (username + password) worked correctly ye when i configured the server and my account to use public key, error-ed in the same way, making this issue with how VHSELL dealt with public key authentication.

I then specified an IP address to listen to, and this fixed it. I removed the IP address and reverted to the original setting (Default), and it was still fixed. Effectively I changed nothing, but it fixed.

This has happened to three separate servers. (all with the same configuration, the same testing and the same resolution).

Is this a known issue, that the Software seems to have a disconnect from the config.

How can this be resolved, as I will not release this software to our production servers with this current unknown issue.
Reply With Quote
  #2  
Old 11-26-2014, 10:44 AM
rtb rtb is offline
VanDyke Technical Support
 
Join Date: Aug 2008
Posts: 4,306
Hi Jasper_SG,

Thanks for the post.

VShell is asking the machine where it is installed to resolve the username. The log line below is the result of what the machine is returning to VShell.
Quote:
2014-11-25 00:10:25 VShellSSH2 auth 4445 IPADDRESS 27919 USERNAME - - 0 0 0 0 - - "04445: Could not get authentication token for user USERNAME; further authentication is necessary: The user's account was not found, or a failure occurred looking up the user's account information"
We have seen this problem in the past, but it has not been a VShell problem.
Quote:
I then specified an IP address to listen to, and this fixed it. I removed the IP address and reverted to the original setting (Default), and it was still fixed. Effectively I changed nothing, but it fixed.
We have not had any reports of a listen address modification fixing a problem resolving a user account. This sounds like an unrelated event.

If you would like to further troubleshoot this issue, please send a complete VShell debug log file to support@vandyke.com with a subject of Attn: Todd - User Account Lookup Problem. Please attach a VShell debug log reflecting the problem. You will need to enable Debug and LSA authentication module options in the Common / Logging category to capture the necessary data.
__________________
--Todd

VanDyke Software
Technical Support
support@vandyke.com
505-332-5730
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -6. The time now is 10:57 AM.