Your best friend for file transfer.

Fetch application logoFetch

-1 Error (5 posts)

  • Started 8 years ago by xenobug
  • Latest reply 8 years ago from Jim Matthews
  • xenobug Member

    I'm getting a -1 error when I try to connect to my site. What does that mean?

    Posted 8 years ago #

  • Jim Matthews Administrator

    It is hard to tell without more information. Could you choose "Fetch Transcript" from the Window menu and post the contents after you see this error?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 8 years ago #

  • MDP Studio Member

    Hi Jim,

    I have recently bought a serial number for Fetch as we have used trial versions before on our Macs (about 1 year ago) and it worked really well. However I too am now experiencing -1 error when trying to connect to an ftp site.

    here is my Fetch transcript:

    Fetch 4.0.3 System 0x921 Expires 10/08/2005 TR
    Connecting to ftp.dk.com port 21 (26/7/05 11:18:08)
    Connecting to ftp.fetchsoftworks.com port 21 (26/7/05 11:19:49)
    Connecting to 192.9.100.135 port 21 (26/7/05 11:21:16)
    Connecting to 192.9.100.135 port 21 (26/7/05 11:21:24)
    Connecting to ftp.dk.com port 21 (26/7/05 11:22:37)
    Connecting to 195.69.213.24 port 8080 (26/7/05 11:32:46)
    Using SOCKS v4.3 gateway host: 192.9.100.2, port: 8080
    Connecting to ftp.dk.com port 21 (26/7/05 11:34:39)
    CStreamOTSocks::Connect(id = ffffffff) connecting to 192.9.100.2 port 8080 srcport 0 (name = ftp.dk.com, real_remote_addr = 0x1, port = 21)
    Sent SOCKS request (version = 4 cmd = 1 port = 21 addr = 1 userid = fetch@ hostname = ftp.dk.com), result = 0
    Using SOCKS v4.3 gateway host: 192.9.100.2, port: 8080
    Connecting to ftp.dk.com port 21 (26/7/05 11:37:00)
    CStreamOTSocks::Connect(id = ffffffff) connecting to 192.9.100.2 port 8080 srcport 0 (name = ftp.dk.com, real_remote_addr = 0x1, port = 21)
    Sent SOCKS request (version = 4 cmd = 1 port = 21 addr = 1 userid = fetch@ hostname = ftp.dk.com), result = 0
    Connection dropped waiting for SOCKS reply
    Using SOCKS v4.3 gateway host: 192.9.100.2, port: 8080
    Connecting to ftp.dk.com port 21 (26/7/05 14:44:08)
    CStreamOTSocks::Connect(id = ffffffff) connecting to 192.9.100.2 port 8080 srcport 0 (name = ftp.dk.com, real_remote_addr = 0x1, port = 21)
    Sent SOCKS request (version = 4 cmd = 1 port = 21 addr = 1 userid = fetch@ hostname = ftp.dk.com), result = 0
    Connection dropped waiting for SOCKS reply
    Using SOCKS v4.3 gateway host: 192.9.100.2, port: 21
    Connecting to ftp.dk.com port 21 (26/7/05 15:01:59)
    CStreamOTSocks::Connect(id = ffffffff) connecting to 192.9.100.2 port 21 srcport 0 (name = ftp.dk.com, real_remote_addr = 0x1, port = 21)
    Sent SOCKS request (version = 4 cmd = 1 port = 21 addr = 1 userid = fetch@ hostname = ftp.dk.com), result = 0
    Got bad SOCKS reply code id = 24ce5434 reply.response = 0x32

    i am sure that it is related to how our internet connection/firewall is set up, but any help you can offer is appreciated.

    Regards

    Dave Bennett

    Posted 8 years ago #

  • MDP Studio Member

    Fetch 4.0.3 System 0x921 Expires 10/08/2005 TR
    Connecting to ftp.dk.com port 21 (26/7/05 11:18:08)
    Connecting to ftp.fetchsoftworks.com port 21 (26/7/05 11:19:49)
    Connecting to 192.9.100.135 port 21 (26/7/05 11:21:16)
    Connecting to 192.9.100.135 port 21 (26/7/05 11:21:24)
    Connecting to ftp.dk.com port 21 (26/7/05 11:22:37)
    Connecting to 195.69.213.24 port 8080 (26/7/05 11:32:46)
    Using SOCKS v4.3 gateway host: 192.9.100.2, port: 8080
    Connecting to ftp.dk.com port 21 (26/7/05 11:34:39)
    CStreamOTSocks::Connect(id = ffffffff) connecting to 192.9.100.2 port 8080 srcport 0 (name = ftp.dk.com, real_remote_addr = 0x1, port = 21)
    Sent SOCKS request (version = 4 cmd = 1 port = 21 addr = 1 userid = fetch@ hostname = ftp.dk.com), result = 0
    Using SOCKS v4.3 gateway host: 192.9.100.2, port: 8080
    Connecting to ftp.dk.com port 21 (26/7/05 11:37:00)
    CStreamOTSocks::Connect(id = ffffffff) connecting to 192.9.100.2 port 8080 srcport 0 (name = ftp.dk.com, real_remote_addr = 0x1, port = 21)
    Sent SOCKS request (version = 4 cmd = 1 port = 21 addr = 1 userid = fetch@ hostname = ftp.dk.com), result = 0
    Connection dropped waiting for SOCKS reply
    Using SOCKS v4.3 gateway host: 192.9.100.2, port: 8080
    Connecting to ftp.dk.com port 21 (26/7/05 14:44:08)
    CStreamOTSocks::Connect(id = ffffffff) connecting to 192.9.100.2 port 8080 srcport 0 (name = ftp.dk.com, real_remote_addr = 0x1, port = 21)
    Sent SOCKS request (version = 4 cmd = 1 port = 21 addr = 1 userid = fetch@ hostname = ftp.dk.com), result = 0
    Connection dropped waiting for SOCKS reply
    Using SOCKS v4.3 gateway host: 192.9.100.2, port: 21
    Connecting to ftp.dk.com port 21 (26/7/05 15:01:59)
    CStreamOTSocks::Connect(id = ffffffff) connecting to 192.9.100.2 port 21 srcport 0 (name = ftp.dk.com, real_remote_addr = 0x1, port = 21)
    Sent SOCKS request (version = 4 cmd = 1 port = 21 addr = 1 userid = fetch@ hostname = ftp.dk.com), result = 0
    Got bad SOCKS reply code id = 24ce5434 reply.response = 0x32

    Posted 8 years ago #

  • Jim Matthews Administrator

    MDP Studio:

    Your transcript shows you trying to use a SOCKS 4.3 gateway at port 8080. That's a very unusual set up -- SOCKS gateways are typically at port 1080. So my guess is that the proxy server running at port 8080 is not a SOCKS gateway.

    I would need more information about your proxy server in order to suggest a correct configuration. Did the proxy server come with documentation suggesting how to configure FTP software? Is there a firewall administrator who might know?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 8 years ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.