FTP issues with 11.0

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
Jun 7, 2008
121
0
#1
Hi

Batch files that work with 4NT 8.02.106 seem to fail with 11.0.33 that use FTP.

1. I have found it is necessary to close any connection before attempting to do a new IFTP command

2. Doing

IFTP /C
IFTP /V "ftp://userid:password@80.168.34.151"

results in

Connecting to FTP server.
Connected.
220 ftp.atruk.co.uk FTP server ready
USER userid
331 Password required for userid.
230 User userid logged in.
TYPE I
200 Type set to I
CWD /ToTNS/B20091106.PRG
550 /ToTNS/B20091106.PRG: Not a directory
TCC: 550 /ToTNS/B20091106.PRG: Not a directory "80.168.34.151"

Those last 3 lines, where is it getting that?

Cheers

Stephen Howe
 

rconn

Administrator
Staff member
May 14, 2008
10,099
85
#2
Hi

Batch files that work with 4NT 8.02.106 seem to fail with 11.0.33 that use FTP.

1. I have found it is necessary to close any connection before attempting to do a new IFTP command

2. Doing

IFTP /C
IFTP /V "ftp://userid:password@80.168.34.151"

results in

Connecting to FTP server.
Connected.
220 ftp.atruk.co.uk FTP server ready
USER userid
331 Password required for userid.
230 User userid logged in.
TYPE I
200 Type set to I
CWD /ToTNS/B20091106.PRG
550 /ToTNS/B20091106.PRG: Not a directory
TCC: 550 /ToTNS/B20091106.PRG: Not a directory "80.168.34.151"

Those last 3 lines, where is it getting that?
Not from TCC. That's not reproducible here -- anybody else seeing this?
 
#3
Not from TCC. That's not reproducible here -- anybody else seeing this?
Yes, it was easy to repro:

Code:
v:\> iftp ilucky/4plugins

v:\> iftp /c

v:\> iftp /v vefatica:********@barnyard.syr.edu
Connecting to FTP server.
Connected.
220 Welcome to barnyard FTP service.
USER vefatica
331 Please specify the password.
230 Login successful.
CWD /4plugins
550 Failed to change directory.
TCC: 550 Failed to change directory. "barnyard.syr.edu"
 
#5
I have no idea what that statement is supposed to do ...
Look at what I posted again. That statement (above) made an FTP connection. Then I closed that connection (IFTP /C) and made a new connection to a different host. The point was that in the second connection it tried to CD to a directory remembered from the first connection.


Code:
v:\> iftp ilucky/4plugins

v:\> iftp /c

v:\> iftp /v vefatica:********@barnyard.syr.edu
Connecting to FTP server.
Connected.
220 Welcome to barnyard FTP service.
USER vefatica
331 Please specify the password.
230 Login successful.
CWD /4plugins
550 Failed to change directory.
TCC: 550 Failed to change directory. "barnyard.syr.edu"
 
Jun 7, 2008
121
0
#6
There maybe a 2nd issue

In my original post, the FTP verbose messages said

CWD /ToTNS/B20091106.PRG
550 /ToTNS/B20091106.PRG: Not a directory
TCC: 550 /ToTNS/B20091106.PRG: Not a directory "80.168.34.151"
Well "/ToTNS/" is a directory, but "B20091106.PRG" is a file in that directory. So even if IFTP was resuming the old connection (and restoring the current directory), CWD should not be attempting to change to a file.

If IFTP was correct, that should be
CWD /ToTNS/
and not
CWD /ToTNS/B20091106.PRG

Thanks

Stephen Howe
 

rconn

Administrator
Staff member
May 14, 2008
10,099
85
#7
> ---Quote (Originally by rconn)---
> I have no idea what that statement is supposed to do ...
> ---End Quote---
> Look at what I posted again. That statement (above) made an FTP
> connection. Then I closed that connection (IFTP /C) and made a new
> connection to a different host. The point was that in the second
> connection it tried to CD to a directory remembered from the first
> connection.
I did look at your statement, but the first one is meaningless as-is. I
presume you're using an ftp.cfg configuration or an alias of some type.

I cannot reproduce the problem with the attempted directory change. I am
100% certain it's not TCC doing that. It could be the new version of
ipworks caching the current directory, perhaps in conjunction with certain
ftp sites. I'll pass that on to the ipworks developers and see if they have
any ideas.

Rex Conn
JP Software
 
#8
I did look at your statement, but the first one is meaningless as-is. I
presume you're using an ftp.cfg configuration or an alias of some type.

I cannot reproduce the problem with the attempted directory change. I am
100% certain it's not TCC doing that. It could be the new version of
ipworks caching the current directory, perhaps in conjunction with certain
ftp sites. I'll pass that on to the ipworks developers and see if they have
any ideas.
My ftp.cfg is empty. In my previous example, "ilucky" is a HOST file alias for "lucky.syr.edu". And my examples don't prefix the FTP spec with "ftp://" because it isn't necessary with IFTP (or so it seems .. . if so, let the help and syntax say so). Here's a more complete example of the same phenomenon.

Code:
v:\> iftp ftp://lucky.syr.edu/4plugins

v:\> dir ftp:v*

 Directory of  ftp://lucky.syr.edu/4plugins/v*

2009-10-26  19:03         <dir>    vc9
2008-12-29  00:00         207,000  vfplugins.zip
           207,000 bytes in 1 file and 1 dir
v:\> iftp /c

v:\> iftp /v ftp://vefatica:********@barnyard.syr.edu
Connecting to FTP server.
Connected.
220 Welcome to barnyard FTP service.
USER vefatica
331 Please specify the password.
230 Login successful.
CWD /4plugins
550 Failed to change directory.
TCC: 550 Failed to change directory. "barnyard.syr.edu"
And here's it's abbreviated version (again).

Code:
v:\> iftp ilucky/4plugins

v:\> dir ftp:v*

 Directory of  ftp://ilucky/4plugins/v*

2009-10-26  19:03         <dir>    vc9
2008-12-29  00:00         207,000  vfplugins.zip
           207,000 bytes in 1 file and 1 dir

v:\> iftp /c

v:\> iftp /v vefatica:********@barnyard.syr.edu
Connecting to FTP server.
Connected.
220 Welcome to barnyard FTP service.
USER vefatica
331 Please specify the password.
230 Login successful.
CWD /4plugins
550 Failed to change directory.
TCC: 550 Failed to change directory. "barnyard.syr.edu"
</dir></dir>
 

rconn

Administrator
Staff member
May 14, 2008
10,099
85
#9
> My ftp.cfg is empty. In my previous example, "ilucky" is a HOST file
> alias for "lucky.syr.edu". And my examples don't prefix the FTP spec
> with "ftp://" because it isn't necessary with IFTP (or so it seems .. .
> if so, let the help and syntax say so). Here's a more complete example
> of the same phenomenon.
What happens if you *do* provide a path for the second IFTP? (Even just a
trailing /.)

Rex Conn
JP Software
 
#10
What happens if you *do* provide a path for the second IFTP? (Even just a
trailing /.)
The same thing ("by" is a HOST file alias for "barnyard.syr.edu").

Code:
v:\> iftp ilucky/4plugins

v:\> iftp /c

v:\> iftp /v vefatica:********@by/.
Connecting to FTP server.
Connected.
220 Welcome to barnyard FTP service.
USER vefatica
331 Please specify the password.
230 Login successful.
CWD /4plugins
550 Failed to change directory.
TCC: 550 Failed to change directory. "by"
Likewise (exactly) if I use

Code:
vefatica:********@by/public_html
as the second spec.