FTP Problem (10.6.8) Can't Upload .txt or .html Files

Question

Level 1

61 points

FTP Problem (10.6.8) Can't Upload .txt or .html Files

I have OSX 10.6.8 on a 2.2 GHz Intel Core 2 Duo. I'm managing a website hosted by Network Solutions. Two days ago I was suddenly unable to upload, via FTP, any .txt or .html files larger than 1K or so. (Specifically, via file mapping, I am able to upload an .html file of length up to 1364 characters, but once I add the 1365th character it will not copy; it just struggles and times out. Via binary, I am able to upload an .html file of length up to 1424 characters, but once I add the 1425th character it will not copy; it just struggles and times out.) It appears as though 'most' of the file uploads, then it just struggles and times out. I have no problems with .pdf files of any size. My "webspace" is not full -- I can upload new .pdf files, dozens of MB in size, with no problem. Yes I'm using passive mode.

I tried FTP using Interarchy, Fetch, and Firefox/FireFTP with the same results on each. I called Network Solutions tech support and the tech was able to upload a large test.html file successfully from his PC to my website. He said it must be my FTP client software (but I've tried three different clients with the same results). He said my files may have a virus (but I've created new test files with TextWrangler, TextEdit, and Word/SaveAs/Text with the same results every time). Amazingly, he came up with a work-around: The "File Manager" tool, online, within my account on their website, will indeed browse/upload my .html files.

My files are not locked, and "Everyone" has Read access. I went into Time Machine and retrieved older versions of .html files that I had uploaded successfully last week, using my FTP client software -- now, they won't upload (using any of the clients mentioned above).

Where should I be looking for a solution (other than, yes, get a newer Mac and upgrade to the latest OSX)? How is it that I can still FTP any size .pdf file, but not my own .html files, except with the "File Manager" tool on the Network Solutions website? Technically, what's different about .pdf files and .html (text) files that could be causing this problem? Why would a file "almost finish" uploading, then struggle and time out? What could have changed, suddenly, two days ago?

I still believe it's some glitch on the server/host side, but since the tech was able to FTP from his PC, that's an unacceptable conclusion. And since I can upload using their "File Manager" tool, that's their only solution. Unfortunately, I don't have another host site to test an upload; I connected to a number of 'public' ftp sites that came up in a Google search, but none of them (not surprisingly) would permit an upload.

Any suggestions?

MacBook, Mac OS X (10.6.8)

Posted on Sep 12, 2014 11:19 AM

Reply

Answer 1

Loner T

Level 9

59,536 points

Sep 12, 2014 11:28 AM in response to SkokieCatDad

1. Please try DropBox as a test with files which have 1365/1425 characters.

2. You may also want to run Wireshark on your side and capture packets (including possible connection resets, if any).

3. You can also try using the Hash command.

4. Can you use WinSCP and try FTP through WinSCP?

Reply

Answer 2

SkokieCatDad Author

Level 1

61 points

Sep 12, 2014 1:07 PM in response to Loner T

1. DropBox works fine -- no problems with any files of any size.

2. Wireshark capture completed -- see below. I used a text editor to filter the packet stream by hand.*.

3. I am not savvy enough to use Hash; I don't operate at the Terminal level.

4. I am not set up to run Windows applications on my Mac. I don't have a PC available.

* I could not figure out how to use Wireshark to filter on the specific remote IP address.

Using File Mapping mode in Interarchy:

I copied the 1,364 character file -- successful.

I copied the 1,365 character file -- started, almost complete, struggle, time out.

Here is the Interarchy Transcript:

SIZE index1364charactersOKviafilemap.html

550 Could not get file size.

PASV

227 Entering Passive Mode (206,188,192,160,92,22)

STOR index1364charactersOKviafilemap.html

150 Ok to send data.

226 Transfer complete.

MFF Create=20140911132938;Modify=20140911164219;UNIX.mode=33188 index1364charactersOKviafilemap.html

500 Unknown command.

SIZE index1365charactersNOviafilemap.html

550 Could not get file size.

PASV

227 Entering Passive Mode (206,188,192,160,95,235)

STOR index1365charactersNOviafilemap.html

150 Ok to send data.

QUIT

Here is the Wireshark capture file from the first (successful) transfer:

Request: SIZE index1364charactersOKviafilemap.html

21\xe2\x86\x9253324 [ACK] Seq=1 Ack=44 Win=4586 Len=0 TSval=1800168337 TSecr=39516936

Response: 550 Could not get file size.

53324\xe2\x86\x9221 [ACK] Seq=44 Ack=31 Win=65535 Len=0 TSval=39516936 TSecr=1800168338

Request: PASV

21\xe2\x86\x9253324 [ACK] Seq=31 Ack=50 Win=4592 Len=0 TSval=1800168383 TSecr=39516936

Response: 227 Entering Passive Mode (206,188,192,160,92,22)

53324\xe2\x86\x9221 [ACK] Seq=50 Ack=82 Win=65535 Len=0 TSval=39516937 TSecr=1800168384

53326\xe2\x86\x9223574 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=39516937 TSecr=0 SACK_PERM=1

Request: STOR index1364charactersOKviafilemap.html

[TCP Dup ACK 9#1] 21\xe2\x86\x9253324 [ACK] Seq=82 Ack=50 Win=4592 Len=0 TSval=1800168438 TSecr=39516937

23574\xe2\x86\x9253326 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460 TSval=458474731 TSecr=39516937

53326\xe2\x86\x9223574 [ACK] Seq=1 Ack=1 Win=524280 Len=0 TSval=39516937 TSecr=458474731

FTP Data: 1424 bytes

53326\xe2\x86\x9223574 [FIN, ACK] Seq=1425 Ack=1 Win=524280 Len=0 TSval=39516937 TSecr=458474731

21\xe2\x86\x9253324 [ACK] Seq=82 Ack=93 Win=4635 Len=0 TSval=1800168464 TSecr=39516937

23574\xe2\x86\x9253326 [ACK] Seq=1 Ack=1425 Win=17088 Len=0 TSval=458474735 TSecr=39516937

[TCP Retransmission] 53326\xe2\x86\x9223574 [FIN, ACK] Seq=1425 Ack=1 Win=524280 Len=0 TSval=39516938 TSecr=458474735

[TCP Dup ACK 19#1] 23574\xe2\x86\x9253326 [ACK] Seq=1 Ack=1425 Win=17088 Len=0 TSval=458474735 TSecr=39516937

Response: 150 Ok to send data.

53324\xe2\x86\x9221 [ACK] Seq=93 Ack=104 Win=65535 Len=0 TSval=39516938 TSecr=1800168490

23574\xe2\x86\x9253326 [FIN, ACK] Seq=1 Ack=1426 Win=17088 Len=0 TSval=458474738 TSecr=39516937

53326\xe2\x86\x9223574 [ACK] Seq=1426 Ack=2 Win=524280 Len=0 TSval=39516938 TSecr=458474738

[TCP Dup ACK 24#1] 23574\xe2\x86\x9253326 [ACK] Seq=2 Ack=1426 Win=17088 Len=0 TSval=458474742 TSecr=39516938

Response: 226 Transfer complete.

53324\xe2\x86\x9221 [ACK] Seq=93 Ack=128 Win=65535 Len=0 TSval=39516939 TSecr=1800168579

Request: MFF Create=20140911132938;Modify=20140911164219;UNIX.mode=33188 index1364charactersOKviafilemap.html

21\xe2\x86\x9253324 [ACK] Seq=128 Ack=195 Win=4737 Len=0 TSval=1800168642 TSecr=39516939

53324\xe2\x86\x9221 [ACK] Seq=195 Ack=150 Win=65535 Len=0 TSval=39516939 TSecr=1800168642

Here is the Wireshark capture file from the second (unsuccessful) transfer:

Request: SIZE index1365charactersNOviafilemap.html

21\xe2\x86\x9253324 [ACK] Seq=150 Ack=238 Win=4780 Len=0 TSval=1800179198 TSecr=39517044

Response: 550 Could not get file size.

53324\xe2\x86\x9221 [ACK] Seq=238 Ack=180 Win=65535 Len=0 TSval=39517045 TSecr=1800179199

Request: PASV

21\xe2\x86\x9253324 [ACK] Seq=180 Ack=244 Win=4786 Len=0 TSval=1800179243 TSecr=39517045

Response: 227 Entering Passive Mode (206,188,192,160,95,235)

53324\xe2\x86\x9221 [ACK] Seq=244 Ack=232 Win=65535 Len=0 TSval=39517045 TSecr=1800179244

53327\xe2\x86\x9224555 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=8 TSval=39517045 TSecr=0 SACK_PERM=1

Request: STOR index1365charactersNOviafilemap.html

[TCP Dup ACK 64#1] 21\xe2\x86\x9253324 [ACK] Seq=232 Ack=244 Win=4786 Len=0 TSval=1800179297 TSecr=39517045

21\xe2\x86\x9253324 [ACK] Seq=232 Ack=287 Win=4829 Len=0 TSval=1800179300 TSecr=39517045

24555\xe2\x86\x9253327 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460 TSval=458475817 TSecr=39517045

53327\xe2\x86\x9224555 [ACK] Seq=1 Ack=1 Win=524280 Len=0 TSval=39517046 TSecr=458475817

FTP Data: 1425 bytes

53327\xe2\x86\x9224555 [FIN, ACK] Seq=1426 Ack=1 Win=524280 Len=0 TSval=39517046 TSecr=458475817

[TCP Dup ACK 70#1] 24555\xe2\x86\x9253327 [ACK] Seq=1 Ack=1 Win=14480 Len=0 TSval=458475821 TSecr=39517046

Response: 150 Ok to send data.

53324\xe2\x86\x9221 [ACK] Seq=287 Ack=254 Win=65535 Len=0 TSval=39517046 TSecr=1800179345

[TCP Retransmission] FTP Data: 1425 bytes

80\xe2\x86\x9253328 [SYN, ACK] Seq=0 Ack=1 Win=42540 Len=0 MSS=1430 SACK_PERM=1 TSval=2399790227 TSecr=39517057 WS=64

[TCP segment of a reassembled PDU]

80\xe2\x86\x9253328 [ACK] Seq=1 Ack=1418 Win=42880 Len=0 TSval=2399790243 TSecr=39517057

80\xe2\x86\x9253328 [ACK] Seq=1 Ack=1520 Win=42880 Len=0 TSval=2399790256 TSecr=39517057

80\xe2\x86\x9253329 [SYN, ACK] Seq=0 Ack=1 Win=42540 Len=0 MSS=1430 SACK_PERM=1 TSval=555965929 TSecr=39517058 WS=128

80\xe2\x86\x9253329 [ACK] Seq=1 Ack=1368 Win=45440 Len=0 TSval=555965943 TSecr=39517058

[TCP segment of a reassembled PDU]

[TCP Retransmission] FTP Data: 1425 bytes

53312\xe2\x86\x928769 [FIN, PSH, ACK] Seq=1 Ack=1 Win=65535 Len=1425 TSval=39517222 TSecr=458332340

[TCP Retransmission] FTP Data: 1425 bytes

53302\xe2\x86\x9252868 [RST, ACK] Seq=1 Ack=1 Win=65535 Len=0

Request: QUIT

53324\xe2\x86\x9221 [FIN, ACK] Seq=293 Ack=254 Win=65535 Len=0 TSval=39517646 TSecr=1800179345

[TCP Dup ACK 75#1] 21\xe2\x86\x9253324 [ACK] Seq=254 Ack=287 Win=4829 Len=0 TSval=1800239421 TSecr=39517046

21\xe2\x86\x9253324 [ACK] Seq=254 Ack=294 Win=4835 Len=0 TSval=1800239435 TSecr=39517646

[TCP Dup ACK 171#1] 53324\xe2\x86\x9221 [ACK] Seq=294 Ack=254 Win=65535 Len=0 TSval=39517646 TSecr=1800239435

[TCP Retransmission] FTP Data: 1425 bytes

The file name ends up in the remote directory, but with a file size of -zero- bytes.

Reply

Answer 3

Loner T

Level 9

59,536 points

Sep 12, 2014 2:37 PM in response to SkokieCatDad

1. I should have suggested something like CyberDuck, rather than WinSCP. Sorry.

2. You have three re-transmissions of 1425 bytes, that the server does not like and rejects each one. And after that, the client gives up. This ends up in a file name entry, but no bytes because the server did not receive any bytes.

3. Using NS's File Manager fragments the file to less than the MTU (I suspect) and it gets reassembled before being put on the files server.

4. The PDF files are byte-streams.

Based on this, the problem is squarely on the Server side.

Reply

Answer 4

SkokieCatDad Author

Level 1

61 points

Sep 12, 2014 3:06 PM in response to Loner T

Thank you for your attention to this issue today!

1. Downloaded CyberDuck -- same problem.

2. Make sense.

3. Excellent hypothesis.

4. Perfectly clear explanation, and should be a Big Clue to NS that the .html transfer problem is on their end.

Based on your sage analysis I have opened another 'trouble ticket' with NS and provided additional details.

I can't believe I'm the only client having difficulty; sooner or later they will have to fix whatever is wrong on their end!

I will come back to this thread and post again if/when the problem is solved.

Reply

Answer 5

Loner T

Level 9

59,536 points

Sep 12, 2014 3:22 PM in response to SkokieCatDad

You can suggest to NS to look at their FTP server log and figure this out. Another test would be to zip the files, transfer, unzip them on the FTP server. I am not sure if NS will allow it.

Reply

Answer 6

Sep 18, 2014 4:42 PM in response to SkokieCatDad

Hey, I have this same problem. I can upload text and PDF files, and tiny HTML files, but everything else times out. I uploaded a 1.8 MB PDF in seconds. I'm using Fetch 5.7.3 on Mac OS 10.8.5, and this was all fine last week. The Network Solutions tech I spoke with said she'd reset the file permissions and that would fix it sometime between 15 minutes and 4 hours (this was yesterday afternoon). I submitted a second trouble ticket via their online form yesterday, and it remains unassigned. The first ticket (4 days ago) was closed with the advice to try the gadget on their site. It took me a while to configure my system to run unsigned Java applets, but once I finally got the thing to run, it failed too. I am at a loss for what to do. I am not in a position to switch hosts right now, because my site is up now and although I can't edit it, it needs to be up at least. Next week, I can switch if this isn't resolved.

Reply

Answer 7

Loner T

Level 9

59,536 points

Sep 18, 2014 5:22 PM in response to unholycow

Do you want to try Cyberduck?

Reply

Answer 8

Sep 18, 2014 9:31 PM in response to Loner T

It didn't help SkokieCatDad, so, no I don't want to try another client. Fetch worked fine last week. I tried installing Fetch on a different Mac and got the same results. It really seems like a server issue.

Reply

Answer 9

SkokieCatDad Author

Level 1

61 points

Sep 19, 2014 7:49 AM in response to unholycow

NS has not been helpful, and in fact has now told me, "We cannot help you." I asked if they would examine their FTP log for the time frame of my upload errors, or conduct a controlled experiment while I was on the phone, and they have refused. They are convinced I am an idiot using the wrong port, wrong password, or that I'm not using passive mode. Below is their last reply to me -- they don't get it. I am trying to find anyone else with an FTP server so I can rule out my end as the cause of the problem. No luck so far. "unholycow" -- are you saying that you are also unable to get the FileManager tool on the NS website to run? That is what has saved me so far and allowed me to update my websites.

*****

I am sorry to hear that you are having issues with using FTP on your hosting. I tested FTP functionality on your hosting account - it is working correctly. I was able to read, write, overwrite, rename and delete files all without issues. Please ensure you have passive mode enabled and port 21 open on your network. If you are getting an error "530" or "Login failed" ensure you are using the right FTP user and password. If you verify both of these settings, and you are still having issues, your computer technician or network administrator will need to assist you with your FTP issues. We cannot help you further with diagnosing why you may not be able to FTP. We apologize for any inconvenience.

Reply