Reply to: FTP woes

[Sysman]

SFTP != FTPS

One is using SSH and the other is using FTP through SSL

hth

Yeah, I have no idea why Nick assumed I was using a GUI FTP.

[Ardesco]

SFTP != FTPS

One is using SSH and the other is using FTP through SSL

hth

[Durbs]

Have you tried using a different client than Filezilla? Its normally a solid client but try just accessing the FTP site through 'My Computer' using Windows FTP and see if any different then at least you can rule out the client FTP app as the cause.

[Sysman]

FTPS === Secure FTP: it's the FTP equivalent of HTTPS. FWIW, none of my Macs have ever tried to go to that by default, whether I'm using Transmit (the best Mac GUI FTP app) or command-line FTP from a shell (=== Terminal window, for Mac users who don't know what a shell is).

No, when I mentioned "Super FTP" mode, it was maybe "Extended mode" or some such. I've never seen it with any other FTP mix.

By sftp I meant this:

SFTP(1)                   BSD General Commands Manual                  SFTP(1)

NAME
     sftp -- secure file transfer program

and then there's

SCP(1)                    BSD General Commands Manual                   SCP(1)

NAME
     scp -- secure copy (remote file copy program)

I just think it's a good habit to get into using them where I can, even on local machines.

Nor have any of my Macs ever had any problem with negotiating between active and passive FTP without me having to lift a finger. I can only assume that there was something odd on your system.

It was 4 years ago, and I found a workaround. It was a pretty ropey set up on the ISP's side from other points of view, so I sought an alternative pronto.

(And you should always get into the RFCs. They're the most important documentation there is when it comes to t'Internet. If you haven't read and understood the RFCs, you can't be sure of anything.)

Even if you have read 'em they may not help when it comes to IE

[darmstadt]

(And you should always get into the RFCs. They're the most important documentation there is when it comes to t'Internet. If you haven't read and understood the RFCs, you can't be sure of anything.)

Especially this one

[NickFitz]

When I moved to my present ISP they gave me 100MB space so I thought "Why not use it?". FTP on the Mac wanted to go into some "Super FTP" mode, which the other end didn't want to know about, so I used a non-Mac system instead.

Tricky stuff and you really don't want to get into the RFCs here.

Is sftp an option?

FTPS === Secure FTP: it's the FTP equivalent of HTTPS. FWIW, none of my Macs have ever tried to go to that by default, whether I'm using Transmit (the best Mac GUI FTP app) or command-line FTP from a shell (=== Terminal window, for Mac users who don't know what a shell is).

Nor have any of my Macs ever had any problem with negotiating between active and passive FTP without me having to lift a finger. I can only assume that there was something odd on your system.

(And you should always get into the RFCs. They're the most important documentation there is when it comes to t'Internet. If you haven't read and understood the RFCs, you can't be sure of anything.)

[xoggoth]

Ta for offer pzz.

Horribly complex program for us not networky sorts and not sure this is what you mean but I got two text reports for a successful upload of a small image and a typically incomplete one of a larger image. Can't see any obvious difference myself.

http://www.xoggoth.org/temp/ftpok.txt

http://www.xoggoth.org/temp/ftpfail.txt

Just search for .jpg to find start of upload. The larger one is here.


http://www.xoggoth.org/temp/temp%20tree.jpg

Larger html files get bashed too. On downloading again they can often look ok but comparison with original shows bits missing, as likely to be in middle as at start or end.

[pzz76077]

When I moved to my present ISP they gave me 100MB space so I thought "Why not use it?". FTP on the Mac wanted to go into some "Super FTP" mode, which the other end didn't want to know about, so I used a non-Mac system instead.

Tricky stuff and you really don't want to get into the RFCs here.

Is sftp an option?

Buh, RFC959 is one of my favorites of all time....


PZZ

[Sysman]

I have different symptoms, in various programs including server-based like eBay's image uploader, files appear to upload ok but are incomplete. Using Explorer is ok for some reason. So can certainly be a PC problem but no idea on solution.

When I moved to my present ISP they gave me 100MB space so I thought "Why not use it?". FTP on the Mac wanted to go into some "Super FTP" mode, which the other end didn't want to know about, so I used a non-Mac system instead.

Tricky stuff and you really don't want to get into the RFCs here.

Is sftp an option?

[pzz76077]

I have different symptoms, in various programs including server-based like eBay's image uploader, files appear to upload ok but are incomplete. Using Explorer is ok for some reason. So can certainly be a PC problem but no idea on solution.

Explorer will probably use anonymous FTP, but if you can post a wireshark fragment I can tell you what the problem is.


PZZ

[xoggoth]

I have different symptoms, in various programs including server-based like eBay's image uploader, files appear to upload ok but are incomplete. Using Explorer is ok for some reason. So can certainly be a PC problem but no idea on solution.

[Zippy]

Please post back when you have fixed it and tell us what the problem was.

[suityou01]

Easy one...run wireshark ( www.wireshark.org )while you are trying to connect and see which end the reset is coming from.

Once you have this vital bit of info, you will know if its your end, the other end or the ISP.

My bet is on you either not having sufficient permissions or out of disk space based on what you have said in the OP.


PZZ

Or you could try running wireshark?

HTH

[pzz76077]

Easy one...run wireshark ( www.wireshark.org )while you are trying to connect and see which end the reset is coming from.

Once you have this vital bit of info, you will know if its your end, the other end or the ISP.

My bet is on you either not having sufficient permissions or out of disk space based on what you have said in the OP.


PZZ

[suityou01]

If someone else can use it from their PC it's a start - are they behind the same firewall?. They can PUT and GET files right? They are trying to transfer the same files as you are?
If it is a firewall issue it will be at your end (assuming the above is correct). I would expect that to mean that you coudn't transfer to/from any FTP site though.
Having said all that, I have encountered situations where traffic (i.e. your request) is allowed out but the response is not allowed in - whch could tie in with what JoJoGabor was saying.
Suggest you try from your home PC and see how far you get.

If someone can PUT the same file from another PC, using the same account, then this would rule out space, permission and lockout permissions for me. If both PCs are behind the same firewall then that would rule out firewall for me also, although you could try telnetting to port 21 (that's FTP right - sorry, rusty on this) and if you get a banner then connection is ok.

You could try running a packet sniffer such as wireshark. That would help you track down connection problems. You need to have an understanding of the three step TCPIP handshake process, but a quick wikipedia should sort that.

SYN
SYN-ACK
ACK

That's about all I can add. Good luck.

etc etc