It rather looks like a problem on your server:

No buffer space available (maximum connections reached?): connect

I'm sending you a dev version of WinSCP to your email. Can you please provide me a log using that version?

I have attached a log file. Also, I can't send you a print screen of tghe UNC error because WinSCP is now throwing up an error and it doesn't get to the point where the directory is set. You can see the error in the log file. Like I said, this is new - there must be an issue with the dev version you sent me.

Because when we tried it - it said UNC Mapping wasn't allowed.

Can you please be more specific? What did you try in particular? Can you post an exact error message (there's no similar error message in WinSCP)? Maybe you tried cd to UNC path before you started WinSCP. Windows shell indeed does not support UNC path as a current working directory. But that does not mean you cannot use it in WinSCP script itself.

I have attached a log file

Thanks.
I'm sending you a dev version of WinSCP to your email. Can you please provide me a log using that version?

martin wrote:

sherrireid wrote:

We found out that you can't use a UNC path

Why?

Because when we tried it - it said UNC Mapping wasn't allowed.

The problem that we are having is that WinSCP doesn't seem to be recognizing the mapped drive. The error we get is 'Error changing directory to 'K:\'.'

Is the drive mapped in the session in which WinSCP script is running?

Yes

I wanted to attach a log file from the winscp session but I can't find where to tell winscp that I want it to save a log file and what to name it.

Please read documentation:
https://winscp.net/eng/docs/commandline#logging

I have attached a log file

sherrireid wrote:

We found out that you can't use a UNC path

Why?

The problem that we are having is that WinSCP doesn't seem to be recognizing the mapped drive. The error we get is 'Error changing directory to 'K:\'.'

Is the drive mapped in the session in which WinSCP script is running?

I wanted to attach a log file from the winscp session but I can't find where to tell winscp that I want it to save a log file and what to name it.

Please read documentation:
https://winscp.net/eng/docs/commandline#logging

martin wrote:

That is a whole configuration export (and in this instance there are no session settings at all).
In 5.2.x you can export the configuration using Tools > Export/Backup Configuration on Login dialog.

OK. So we got the FTP working and we are able to ftp the file to the bank.

The next step is that we need to ftp some files FROM the bank and put them out on a share in our network.

We found out that you can't use a UNC path, so we are mapping a drive in our powershell script so that we can refer to that mapped drive in the Winscp.INI file (attached - remove .txt extension).

If I am in the powershell session I can ask it to repeat back to me what the mapped drive is and I can list the contents of the directory. So I know I've got the mapping done correctly.

The problem that we are having is that WinSCP doesn't seem to be recognizing the mapped drive. The error we get is 'Error changing directory to 'K:\'.'

I wanted to attach a log file from the winscp session but I can't find where to tell winscp that I want it to save a log file and what to name it.

That is a whole configuration export (and in this instance there are no session settings at all).
In 5.2.x you can export the configuration using Tools > Export/Backup Configuration on Login dialog.

martin wrote:

sherrireid wrote:

Oh Wait! In the previous version when you edited the sessions preferences, it gave you an option to save the session out to a winscp file. This file you would then use as part of your scripting so you could automate the FTP process. I can't find the option to save the session out to a file anymore.

There is no (and was no) way to save session settings to a file.
If you was to save session settings to a WinSCP configuration, just press the //Save// or //Save As// button.

Yes there was. It created an ini file like I have attached. (I added .txt on the end so I could attach the file to this post)

sherrireid wrote:

Oh Wait! In the previous version when you edited the sessions preferences, it gave you an option to save the session out to a winscp file. This file you would then use as part of your scripting so you could automate the FTP process. I can't find the option to save the session out to a file anymore.

There is no (and was no) way to save session settings to a file.
If you want to save session settings to a WinSCP configuration, just press the Save or Save As button.

Oh Wait! In the previous version when you edited the sessions preferences, it gave you an option to save the session out to a winscp file. This file you would then use as part of your scripting so you could automate the FTP process. I can't find the option to save the session out to a file anymore.

Thanks
Sherri Reid

martin wrote:

Again: Please, make sure you use passive FTP mode (btw, that's default for WinSCP, so just revert the changed configuration):
https://winscp.net/eng/docs/ui_login_connection

Passive mode did the trick - the new version of WInSCP now connects to the FTP site. Thank you so much!

Sherri Reid

Again: Please, make sure you use passive FTP mode (btw, that's default for WinSCP, so just revert the changed configuration):
https://winscp.net/eng/docs/ui_login_connection

I've attached the log file. I'd also like to remind you that I can connect to the site with FileZilla. So I still think there is a problem with WinSCP.

sherrireid wrote:

Well, I am not sure that obvious is the word, since it doesn't appear to have fixed the problem to someone looking at it from this end. :D Let me ask you this. On the new beta version you gave me, it wasn't an installable - so all I did was save the 2 files into the Winscp directory. Was this what I should have done? Maybe this is part of the problem.

That's ok. WinSCP does not need any installation at all.

martin wrote:

Thanks for working on this. Unfortunately the fix did not resolve the problem. I am attaching the latest log file for your perusal.

It obviously did resolve the problem. You have a different one now. Possibly a firewall issue. Make sure you use passive FTP mode. Please attach a new log then (even if it works).

Well, I am not sure that obvious is the word, since it doesn't appear to have fixed the problem to someone looking at it from this end. :D Let me ask you this. On the new beta version you gave me, it wasn't an installable - so all I did was save the 2 files into the Winscp directory. Was this what I should have done? Maybe this is part of the problem.

Thanks for working on this. Unfortunately the fix did not resolve the problem. I am attaching the latest log file for your perusal.

It obviously did resolve the problem. You have a different one now. Possibly a firewall issue. Make sure you use passive FTP mode. Please attach a new log then (even if it works).

Hi Martin:

Thanks for working on this. Unfortunately the fix did not resolve the problem. I am attaching the latest log file for your perusal.

Thanks
Sherri Reid

I have sent you an email with a development version of WinSCP to address you have used to register on this forum.

Hi:

I was wondering if you'd had a chance to look at this yet. This problem is holding our project up.

Thanks
Sherri Reid

Thanks for your report. I'll investigate it.

I am using the GUI to connect with version 5.24. I am using FTP/TLS Explicit Encryption. I can connect to the ftp site, but WinSCP is having problems connecting to the correct directory. The error message I get is "Could not retrieve directory listing '/D:Securelink/Logins/hrbrvwmc/D:/Securelink/Logins/hrbrvwmc/": Not a directory or is not accessable.

I've tried going under Advanced -> Directories and unchceking 'Remember last used directory' and wiping out the Remote Directory but no matter what, I get the error message.

I've tried unchecking 'Cache visited remote directories' and 'Permanent Cache' as well, and I still get the same error message.

I know that there isn't anything wrong with the directory structure that I connect to because I can connect to it with no problems if I use FileZilla. (But I don't want to use FileZilla because eventually I want to turn this into a script and automate the FTP... which I can't do with FileZilla)