WINSCP runs as a service ?

Hello,

I need to install WinSCP client. That client will receive some files. The user wants to install that on a server but as far as I understood, WinSCP is a frontend..in other words, it must be lauched to work,listem to TCP port and finally receive the file.
Is that correct ? Is it possible to install WinSCP on a server as a SERVICE so it would require NO interventation at all ?
Thanks

How it should receive the files?

Hi Martin, I have this exact same request. I have a Windows NT 4.0 server that needs to transfer files to a web server running Windows 2003. I am running SSH Tectia server on the web server. I am trying to run a batch file calling WinSCP 3.8.2:

C:\Progra~1\WinSCP3\winscp3 webupload /command "option batch on"
"option confirm off" "put c:\winnt\test.txt users.txt" "close" "exit"

webupload is the name of the session that connects using username/password to the web server. This bat file was scheduled to run every night, but it seems not to work. The file on the web server isn't being updated.

I changed one line in the batch file: C:\Progra~1\WinSCP3\winscp3 to C:\Progra~1\WinSCP3\winscp3.com

Will this help? It seemed to work when I was logged in, but will it work in the background as a service, if the PC is logged off at night?


Thanks, DEKER

It should work. Please read FAQ if it does not.

I checked the FAQ and I made sure that the session was stored under the same user name that will be running the script.

I also manually connected using the session to ensure the hostname got stored.

After that I tried again logging off the PC and seeing if WinSCP would work in the background. It didn't. In Task Manager, WinSCP is listed there as running, but the script commands have not been carried out.

Any help is appreciated.

martin wrote:

It should work. Please read FAQ if it does not.

Turn on logging to see when the script hangs.

martin wrote:

Turn on logging to see when the script hangs.

Hi Martin, thanks for that helpful advice. I turned on logging and it appears that the fingerprint key wasn't stored. I of course had logged in previously and manually logged in, but it didn't seem to work. I changed the preferences to save the key in an ini file instead of the registry. Once I did that, I modified the command line script to include the /ini="C:\Program Files\WinSCP3\WinSCP3.ini tag.

That seemed to do the trick!