As always, it's the little things...
This did the trick, thank you very much! :wink:
This did the trick, thank you very much! :wink:
- Pirm
Post a reply
Topic review
- martin
Re: Creating a session list by editing .ini file with PuTTY port tunneling
Just encode the spaces in session name as
%20.
- Pirm
Re: Creating a session list by editing .ini file with PuTTY port tunneling
Why don't you just create the INI file in GUI?
Because that is a lot of work and using xml/csv-files as data sources is much more convenient.
I would have to add sessions for about 80 servers (some newly installed) manually.
- martin
Re: Creating a session list by editing .ini file with PuTTY port tunneling
Why don't you just create the INI file in GUI?
- Pirm
Sorry, could you move this to the Support/Bug-Section of the Forum please? :|
Also: WinSCP 5.5.3 Build 4214 on Windows 7 Enterprise
Also: WinSCP 5.5.3 Build 4214 on Windows 7 Enterprise
- Pirm
Creating a session list by editing .ini file with PuTTY port tunneling
Hello,
I'm currently preparing a sharable WinSCP.ini-File which co-workers can easily import to have the same WinSCP settings as me.
However I can't seem to get the sessions to use the settings I described in my WinSCP.ini.
I've converted our Server list into the following format (actual names and numbers converted to variables for privacy reasons):
and added these Session-Sections to WinSCP.ini.
However when restarting WinSCP with the newly created WinSCP.ini I can see the properly created sessions but they don't use HostName and PortNumber but instead use defaults (blank HostName and PortNumber of 22).
A working Session in my current WinSCP.ini looks similar:
I've changed HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions\Tunnelsession\PortForwardings accordingly.
Could it be parts of the current configuration interfering with the new structure?
Deleting entries in the SshHostKeys and Configuration\CDCache-Sections did not help.
Thanks for your help,
Pirm
I'm currently preparing a sharable WinSCP.ini-File which co-workers can easily import to have the same WinSCP settings as me.
However I can't seem to get the sessions to use the settings I described in my WinSCP.ini.
I've converted our Server list into the following format (actual names and numbers converted to variables for privacy reasons):
[Sessions\Servers/Service/user@FQDN (Section)]
HostName=localhost
PortNumber=$local_Port_for_PuTTY_tunneling
Username=$USERNAME
LocalDirectory=C:%5CUsers%5C
RemoteDirectory=/
and added these Session-Sections to WinSCP.ini.
However when restarting WinSCP with the newly created WinSCP.ini I can see the properly created sessions but they don't use HostName and PortNumber but instead use defaults (blank HostName and PortNumber of 22).
A working Session in my current WinSCP.ini looks similar:
[Sessions\Servers/user@server1]
HostName=localhost
PortNumber=1234
UserName=root21b
I've changed HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions\Tunnelsession\PortForwardings accordingly.
Could it be parts of the current configuration interfering with the new structure?
Deleting entries in the SshHostKeys and Configuration\CDCache-Sections did not help.
Thanks for your help,
Pirm