+1, a nice thing if you are connected to a cluster and use Jupyter notebook

Hello @Martin, Thanks ... it helps a lot...

WinSCP can execute remote commands on its own from the script (with some limitations), using a call command.

Duplicate post on StackOverflow:
WinSCP command to execute command on the server

Hi @Martin,
Yes, PuTTY cannot transfer files, but if you want to delete/rename/move files of remote machine then we need to give the read and write permissions for those (permissions in the sense it is different from 0777)

Normally we used to open PuTTY session manually and then we pass this command

Else is there any other way to perform these actions, please suggest.....

Thanks,
Rajendra.

Why do you want to open PuTTY? You wrote that you want to automate file transfers. PuTTY cannot transfer files.

Hi @Martin,

Yes I prepared the script file like this.
sftprun.cmd:

Can you please suggest me to open PuTTY through above mentioned script.

The PuTTY details should be provided under the script file sftpscriptJAC.

Thanks,
Raj

For an automation, you should start here:
https://winscp.net/eng/docs/guide_automation

HI Martin,

As per link you mentioned above I need to open WinSCP to enter the commands.....
I just wanted to automate the file transfers without opening WinSCP, through script.
upto some extent I performed the file transfer operation except PuTTY session.

Regards,
Raj

@Guest: Why don't you use WinSCP console?
https://winscp.net/eng/docs/ui_console

Hi Martin,
Can you suggest me to open PuTTY session through WinSCP commands,
My requirement is to pass the WinSCP command like mount -o remount,rw / without opening PuTTY manually.
All these things to be done with WinSCP command/settings/configuration

It would be great to be able to configure port forwarding with WinSCP sessions rather than keeping a separate folder of batch files to start plink tunnels. +1

+1

Raising priority.

+1 to port forwarding in WinSCP

+1 for easy portforwarding in WinSCP

I'm create a Custom commands to solve my problem with port forward the result is like
https://bitvise.com/port-forwarding

The script require plink.exe
https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html

1. Open the winscp.exe
   
2. Select the "Advanced Options"
   
3. Go Preferences > Commands
   
4. Click "Add ..."
   
5. In Description put: "Mapear Porta"
   
6. In Custom command:
   

   plink -l !U -pw !P -load "WinSCP temporary session" -L !?Endereço Local:?127.0.0.1!:!?Porta Local:?22!:!?Endereço Remoto:?127.0.0.1!:!?Porta Remota:?22!

   
   
7. Click "Local command"
   
8. Click "OK"
   
9. See new button win Tab
   

This request has been added to the tracker:
Issue 262 – Port forwarding

Since WinSCP use PuTTY core for SSH, may be add additional port forwardings for connection settings?
So it will also start SCP transfer, and VNC / Xforward ports for testing.
It will be really helpful – since one empty PuTTY run only for portforward, when only one connection need.

Hello Martin,

no that's not the intended use in this case. But I also very often use the PuTTY toolbar button to start PuTTY directly from WinSCP. The advantage of this usage is that PuTTY starts up already logged in with the authentication data from WinSCP.
In PuTTY it is possible to specify some port forwarding rules. Maybe it is possible to load a PuTTY profile with this port forwarding rules when I'm clicking this toolbar symbol.
Is this workaround possible in WinSCP, maybe to give PuTTY the right command line options?

Greetings,
Michael

No. WinSCP just forwards single port to remote SSH port to facilitate SSH tunneling:
https://winscp.net/eng/docs/ui_login_tunnel

I guess this is of no use for you, isn't it?

I often use WinSCP in combination with VNC. While WinSCP is responsible for file transferring I use VNC as remote desktop functionality. Since the server to which I connect is secure the VNC service is also reachable through an ssh tunnel with port forwarding.

So I connect with WinSCP (Connection through Tunnel since the server is not direct reachable) to get the file connection. After that I use two PuTTY sessions (two because PuTTY has no direct tunnel function). The last PuTTY session has port forwarding enabled and forwards the VNC port to a local port to allow the VNC client to connect.

This is a bit complicated, is there a way to set port forwardings directly in WinSCP?

Greetings,
Michael