Re: can I see how you specified the port?
I am looking for a port specification example of winscp command prompt
sftp://username@example.com:port
See https://winscp.net/eng/docs/session_url
I am looking for a port specification example of winscp command prompt
sftp://username@example.com:port
I found the problem: it was the ; in the password. Eliminating that allowed the password to work....
The previous thread about "scripting syntax to connect to FTP" almost answered my question. I was glad to learn the tip about putting /loglevel=* to see if there is a password failure.
That is what is happening in my case; here is the log file:
2015-04-20 19:28:38.745 Connected with tourism-engine.com. Waiting for welcome message...
< 2015-04-20 19:28:38.776 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
< 2015-04-20 19:28:38.776 220-You are user number 1 of 50 allowed.
< 2015-04-20 19:28:38.776 220-Local time is now 01:28. Server port: 21.
< 2015-04-20 19:28:38.776 220-IPv6 connections are also welcome on this server.
< 2015-04-20 19:28:38.776 220 You will be disconnected after 15 minutes of inactivity.
> 2015-04-20 19:28:38.776 USER automat@tourism-engine.com
< 2015-04-20 19:28:38.806 331 User automat@tourism-engine.com OK. Password required
> 2015-04-20 19:28:38.807 PASS bC3-fpK
< 2015-04-20 19:28:42.175 530 Login authentication failed
However, the above log does *not* show the complete password. I am not going to reveal the complete password here, of course, but the next character in the password is a semi-colon, or ; character.
This password works in the WinSCP GUI login; but the fact that the log stops on that character makes me suspect the problem is the semi-colon in the password, and how it is getting fed to login.
I do not see any documentation saying this character should not be used in a password.
Can anyone help me verify if this is the case?
thanks,
rixter
So the connection string contains both sftp & ftp.
ftp.ohiohealthgroup.com
is just a hostname, it does not specify a protocol.
In the GUI you connect toftp.ohiohealthgroup.com
, what resolves to192.168.30.242
, while in the latest log you connect toohiohealthgroup.com
, what resolves to64.87.23.209
.
ftp.ohiohealthgroup.com
, what resolves to 192.168.30.242
, while in the latest log you connect to ohiohealthgroup.com
, what resolves to 64.87.23.209
.
You are using an SFTP protocol in the interactive session (you do not specify a protocol in anopen
command and WinSCP defaults to SFTP). While you use an FTP protocol in the failed session (you specifyftp://
explicitly).
open
command and WinSCP defaults to SFTP). While you use an FTP protocol in the failed session (you specify ftp://
explicitly).
Can you attach a log of a successful interactive session?
Try to add/loglevel=*
to command-line. It makes the log record the actual password. Check that the password is correct.
/loglevel=*
to command-line. It makes the log record the actual password. Check that the password is correct.
Thank you for your reply. I was able to generate the log file, and I have attached a copy for you. The end of the log says "530 Login or Password incorrect". But this is the same user/password that I enter when I run the commands manually. It works there, just not in the batch file.
/log=path_to_log_file
command-line argument. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.access denied
authentication failed
option batch abort
option confirm off
open ftp://username:password@ftpserver.com