Your best friend for file transfer.
Fetch
Alesis HD24 etch (2 posts)
This is an archived topic. The information in it is likely to be out-of-date and no longer applicable to current versions of Fetch.
- Started 19 years ago by Freedomsound
- Latest reply 19 years ago from Jim Matthews
-
Freedomsound Member
-
Jim Matthews Administrator
Have you tried unchecking the "Use passive mode transfers (PASV)" box in the Firewall section of Preferences?
Would you be willing to try a test version of Fetch to see if it works around this problem? If so send an email to bugs @ fetchsoftworks.com.
Thanks,
Jim Matthews
Fetch Softworksp.s. To respond press the Post Reply button below; that way your postings won't get spread across multiple topics.
- Page 1
Topic closed
This topic has been closed.
Hi; I just uploaded 24 tracks on my PC using a Cute FTP program. Thus I know the HD24 is working correctly. I did not get any errors nor did I have to re-enable the transfer option after receiving each file. I like the Fetch program and am trying to understand why it does the disconnect thing at the end of a transfer as it is annoying to have to walk across the studio every three minutes to upload a track where in the PC, I can do 24 tracks while having lunch? Please help. Thanks in advance
John
Here are the results
Connecting to 192.168.1.100:21
Connected to 192.168.1.100:21 in 0.060, Waiting for Server Response
220 Alesis HD24 FTP server ready.
Host type (1): Automatic detect
USER anonymous
331 User name okay, need password.
PASS (hidden)
230 User logged in, proceed.
SYST
215 UNIX .
Host type (2): UNIX (standard)
FEAT
500 Syntax error, command unrecognized.
PWD
257 "/" is current directory.
TYPE A
200 TYPE Command okay.
PASV
227 Entering Passive Mode (192,168,1,100,178,90).
connecting data channel to 192.168.1.100:45658
data channel connected to 192.168.1.100:45658
LIST
150 File status okay; about to open data connection.
transferred 329 bytes in < 0.001 seconds, 2570.313 Kbps ( 321.289 KBps), transfer succeeded.
CWD WAV
250 CWD requested file action okay, completed.
PWD
257 "/WAV" is current directory.
PASV
227 Entering Passive Mode (192,168,1,100,129,104).
connecting data channel to 192.168.1.100:33128
data channel connected to 192.168.1.100:33128
LIST
125 Data connection already open; transfer starting.
transferred 64 bytes in < 0.001 seconds, 500.000 Kbps ( 62.500 KBps), transfer succeeded.
CWD Drive1
250 CWD requested file action okay, completed.
PWD
257 "/WAV/Drive1" is current directory.
PASV
227 Entering Passive Mode (192,168,1,100,169,35).
connecting data channel to 192.168.1.100:43299
data channel connected to 192.168.1.100:43299
LIST
150 File status okay; about to open data connection.
transferred 79 bytes in < 0.001 seconds, 617.188 Kbps ( 77.148 KBps), transfer succeeded.
CWD Project01 - Proj Name
250 CWD requested file action okay, completed.
PWD
257 "/WAV/Drive1/Project01 - Proj Name" is current directory.
PASV
227 Entering Passive Mode (192,168,1,100,242,142).
connecting data channel to 192.168.1.100:62094
data channel connected to 192.168.1.100:62094
LIST
150 File status okay; about to open data connection.
transferred 538 bytes in 0.050 seconds, 84.063 Kbps ( 10.508 KBps), transfer succeeded.
CWD Song07 - Song Name
250 CWD requested file action okay, completed.
PWD
257 "/WAV/Drive1/Project01 - Proj Name/Song07 - Song Name" is current directory.
PASV
227 Entering Passive Mode (192,168,1,100,135,99).
connecting data channel to 192.168.1.100:34659
data channel connected to 192.168.1.100:34659
LIST
125 Data connection already open; transfer starting.
transferred 1680 bytes in 0.490 seconds, 26.786 Kbps ( 3.348 KBps), transfer succeeded.
REST 1024
502 REST command not implemented, or not allowed.
TYPE I
200 TYPE Command okay.
PASV
227 Entering Passive Mode (192,168,1,100,146,88).
connecting data channel to 192.168.1.100:37464
data channel connected to 192.168.1.100:37464
RETR Track15.wav
150 File status okay; about to open data connection.
transferred 25878666 bytes in 54.160 seconds, 3732.959 Kbps ( 466.620 KBps), transfer succeeded.
226 Closing data connection.
REST 1024
502 REST command not implemented, or not allowed.
PASV
227 Entering Passive Mode (192,168,1,100,182,57).
connecting data channel to 192.168.1.100:46649
data channel connected to 192.168.1.100:46649
RETR Track16.wav
125 Data connection already open; transfer starting.
transferred 25878666 bytes in 53.940 seconds, 3748.185 Kbps ( 468.523 KBps), transfer succeeded.
226 Closing data connection.
Transfer request completed with status: Finished
REST 1024
502 REST command not implemented, or not allowed.
PASV
227 Entering Passive Mode (192,168,1,100,128,139).
connecting data channel to 192.168.1.100:32907
data channel connected to 192.168.1.100:32907
STOR Track16.wav
150 File status okay; about to open data connection.
transferred 25878666 bytes in 63.430 seconds, 3187.405 Kbps ( 398.426 KBps), transfer succeeded.
226 Closing data connection.
REST 1024
502 REST command not implemented, or not allowed.
PASV
227 Entering Passive Mode (192,168,1,100,197,86).
connecting data channel to 192.168.1.100:50518
data channel connected to 192.168.1.100:50518
STOR Track15.wav
150 File status okay; about to open data connection.
transferred 25878666 bytes in 63.440 seconds, 3186.902 Kbps ( 398.363 KBps), transfer succeeded.
226 Closing data connection.
Transfer request completed with status: Finished
TYPE A
200 TYPE Command okay.
PASV
227 Entering Passive Mode (192,168,1,100,234,206).
connecting data channel to 192.168.1.100:60110
data channel connected to 192.168.1.100:60110
LIST
125 Data connection already open; transfer starting.
transferred 1680 bytes in 0.380 seconds, 34.539 Kbps ( 4.317 KBps), transfer succeeded.
PASV
227 Entering Passive Mode (192,168,1,100,217,206).
connecting data channel to 192.168.1.100:55758
data channel connected to 192.168.1.100:55758
LIST
125 Data connection already open; transfer starting.
transferred 1680 bytes in 0.380 seconds, 34.539 Kbps ( 4.317 KBps), transfer succeeded.
Posted 19 years ago #