Hi,

I'm trying to get the secure FTP working, and I've got only these two lines so far:

FTPConfig ( "FTP PROTOCOL", "SECURE" )
FTPPutFile ( "ftps.******.com", "username", "password", "C:\test.txt", "test.txt" )

I know the SFTP site is working since I can connect to it with a secure FTP client.
This is the error message I get when I run the debugger on it:

Line 2: Could not connect to server ftps.******.com.
Service not available. Extended error code: 4.

Could you please shed some light on this?
Thanks!

There are 2 problems in one place "C:\test.txt"

Problem 1: FTP servers don't use absolute path names; they use names relative to the "FTP root" directory. FTP root could be different for different servers. For IIS the default root is C:\Inetpub\ftproot, but it can be and should be changed. So every file name should be relative to that path. If you have a subfolder "data" within the root and then inside that subfolder file "myfile.txt" then the file name to be used with FTP would be "data/myfile.txt" or "data\\myfile.txt"

Problem 2: Usage of backslashes in 24x7. In run-time if you didn't change the default escape symbol value "C:\test.txt" will convert to "C:[tab character]est.txt". Use double-backslashes to escape backslash ("C:\\test.txt") or change the escape symbol in options. For more info please see FAQ section in the on-line help.

: Hi,

: I'm trying to get the secure FTP working, and I've got only these two lines
: so far: FTPConfig ( "FTP PROTOCOL", "SECURE" )
: FTPPutFile ( "ftps.******.com", "username",
: "password", "C:\test.txt", "test.txt" )

: I know the SFTP site is working since I can connect to it with a secure FTP
: client.
: This is the error message I get when I run the debugger on it: Line 2: Could
: not connect to server ftps.******.com.
: Service not available. Extended error code: 4.

: Could you please shed some light on this?
: Thanks!

Ok, I made those changes, but I still can't connect to the secure FTP server.
I put the error message in my original post.
Note, that I'm using a Put statement.

: There are 2 problems in one place "C:\test.txt"

: Problem 1: FTP servers don't use absolute path names; they use names relative
: to the "FTP root" directory. FTP root could be different for
: different servers. For IIS the default root is C:\Inetpub\ftproot, but it
: can be and should be changed. So every file name should be relative to
: that path. If you have a subfolder "data" within the root and
: then inside that subfolder file "myfile.txt" then the file name
: to be used with FTP would be "data/myfile.txt" or
: "data\\myfile.txt"

: Problem 2: Usage of backslashes in 24x7. In run-time if you didn't change the
: default escape symbol value "C:\test.txt" will convert to
: "C:[tab character]est.txt". Use double-backslashes to escape
: backslash ("C:\\test.txt") or change the escape symbol in
: options. For more info please see FAQ section in the on-line help.

Can you ping it from DOS prompt? What do you get when doing

PING ftps.[your_site].com

: Ok, I made those changes, but I still can't connect to the secure FTP server.
: I put the error message in my original post.
: Note, that I'm using a Put statement.

If I ping the site, I get a response. I changed the script to use the IP address also, and same result.
I also tried to set the secure FTP Connection Type to Passive and that did not work either.

This secure FTP site uses SSL certs.

What does this mean? "Extended Error Code: 4"

: Can you ping it from DOS prompt? What do you get when doing

: PING ftps.[your_site].com

If I ping the site, I get a response. I changed the script to use the IP address also, and same result.
I also tried to set the secure FTP Connection Type to Passive and that did not work either.

This secure FTP site uses SSL certs.

What does this mean? "Extended Error Code: 4"

: Can you ping it from DOS prompt? What do you get when doing

: PING ftps.[your_site].com

I think I know what is going on. You are not dealing with a secure FTP protocol (SFTP protocol based on SSH v2). You are dealing with a regular FTP over SSL connection (FTP SSL). This is not the same thing.
For more information about SFTP see http://www.faqs.org/rfcs/rfc2228.html

24x7 currently supports regular FTP and SFTP only. It does not support FTP SSL. However there are many utilities available on the internet that support FTP SSL and can be used together with 24x7. For example, try free command line utility MoveIt (download at http://www.stdnet.com/products/?category_number=7&subcategory_number=1). This utility can be called with parameters from 24x7 program type and script type jobs.

: If I ping the site, I get a response. I changed the script to use the IP
: address also, and same result.
: I also tried to set the secure FTP Connection Type to Passive and that did
: not work either.

: This secure FTP site uses SSL certs.

: What does this mean? "Extended Error Code: 4"

Thank you for your response, and thank you even more for suggesting a solution!
I have another question, but I'll start a new thread.

: I think I know what is going on. You are not dealing with a secure FTP
: protocol (SFTP protocol based on SSH v2). You are dealing with a regular
: FTP over SSL connection (FTP SSL). This is not the same thing.
: For more information about SFTP see http://www.faqs.org/rfcs/rfc2228.html

: 24x7 currently supports regular FTP and SFTP only. It does not support FTP
: SSL. However there are many utilities available on the internet that
: support FTP SSL and can be used together with 24x7. For example, try free
: command line utility MoveIt (download at
: http://www.stdnet.com/products/?category_number=7&subcategory_number=1 ).
: This utility can be called with parameters from 24x7 program type and
: script type jobs.