Fetch Softworks

Error -1 with 4.0.3 with socks5 on OS 10.2.3 (17 posts)

• Started 20 years ago by jeffdurand
• Latest reply 17 years ago from Scott McGuire

• jeffdurand Member

  I get an Error -1 when I try to connect using a socks 5 gateway. The machine is running 10.2.3.

  Posted 20 years ago #

• jeffdurand Member

  The Socks 5 server part of iPlanet Web Proxy Server 3.6, using authentication. This is running on Sparc Solaris 7. I tried NEC Socks5 running on Solaris 8, without authentication and it worked fine.

  I've never had a problem with the iPlanet Socks 5 server with any other app. I have a lot of people you use it with AOLIM, CuteFTP, SecureCRT, Sockscap and eBorder.

  I also tested the client machine with as early as Mac OS 8.1 and received the same results.

  Posted 20 years ago #

• Jim Matthews Administrator

  Could you post the contents of the Fetch Transcript window after you get the error? Also, what SOCKS userid are you using?

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 20 years ago #

• jeffdurand Member

  Fetch 4.0.3 System 0x1023 Expires 02/01/2003 TR
  Using SOCKS v5 gateway host: [insert proxy server here], port: 1080
  Connecting to [insert ftp site here] port 21 (1/21/03 12:06:32 PM)

  I'm connecting using my Socks username and password.

  Posted 20 years ago #

• Jim Matthews Administrator

  It looks like the socks server is rejecting the connection, but it isn't clear why. Have you entered your SOCKS username and password in the Firewall section of Preferences?

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 20 years ago #

• jeffdurand Member

  Yeah, everything is setup right. It has to be a compatibility issue between authentication methods in Fetch and Sun's Socks 5 implementation. Here is the error I get from the Socks Server:

  [23/Jan/2003:14:44:50] 718 debug: request from [insert ip here]:49360
  [23/Jan/2003:14:44:50] 718 debug: auth: no auth offered by client is acceptable
  [23/Jan/2003:14:44:50] 718 debug: auth: failed on [insert ip here]:49360

  Fetch is the only app I have this problem with. I have hundreds of people using a ton of different apps and this is the first time I've seen this.

  Posted 20 years ago #

• Jim Matthews Administrator

  Can you collect a packet trace of Fetch's connection attempt, and one from a client that works, and email them to support@fetchsoftworks.com? I'd like to see what Fetch is doing differently.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 20 years ago #

• deejemon Member

  I get the same thing. SOCKS5 server, Mac OS X 10.3.9, Fetch 4.0.3 configured with the same settings as I use for everything else (iChat, MSN Messenger, etc), username and password entered into the proxy user id and password boxes, and I get "Error -1" when attempting to connect.

  Transcript reads:
  Using SOCKS v5 gateway host: [our server], port: 1080
  Connecting to mirror.aarnet.edu.au port 21 (16/5/05 1:50:11 PM)

  Then nothing. Have also tried passive and non-passive transfers.

  Tried the following to capture a packet trace:
  sudo tcpdump -i en0 -s 0 -w ~/proxydump.txt port 1080

  ... but I ended up with an empty file. Also tried tracing port 21, but still an empty file.

  Posted 18 years ago #

• Jim Matthews Administrator

  deejemon: Do you see anything in the packet trace if you connect with iChat?

  Also, is built-in ethernet your primary network interface (i.e. does the Network panel of System Preference say that you are connected to the Internet via built-in ethernet)?

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 18 years ago #

• deejemon Member

  > deejemon: Do you see anything in the packet trace if you connect with iChat?

  Yes, have a 24K file with a tcpdump from iChat.

  Apparently I tell a lie - just re-did a tcpdump from Fetch 4.0.3 and didn't end up with an empty file; not sure what happened there, maybe I mis-typed the port or something. Will send to the support address.

  >Also, is built-in ethernet your primary network interface
  >(i.e. does the Network panel of System Preference say that you are
  >connected to the Internet via built-in ethernet)?

  Yes.

  I've found that Fetch 5 also does not handle SOCKS5 servers (with authentication) properly, having greyed-out username/password fields in the preferences when SOCKS5 is chosen.

  Posted 18 years ago #

• Jim Matthews Administrator

  Thanks for the report; we will try to fix that for a future release.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 18 years ago #

• deejemon Member

  Seem to still be a few SOCKS5 bugs in 5.0.2. Still unable to enter a username/password when SOCKS5 is chosen as the proxy type, and Fetch doesn't prompt for one when it's trying to connect.

  Posted 18 years ago #

• Jim Matthews Administrator

  That's right, we did not add SOCKS 5 username/password support to 5.0.2. That's still on our list of things to do. Thanks for the reminder.

  Jim Matthews
  Fetch Softworks

  Posted 18 years ago #

• deejemon Member

  Not enabled in 5.1b1 either.

  Posted 17 years ago #

• deejemon Member

  Or 5.1b3.

  Posted 17 years ago #

• deejemon Member

  SOCKS5 also still broken in 5.1 full release version.

  Posted 17 years ago #

• Scott McGuire Administrator

  Hi,

  I'm happy to report that Fetch 5.1.1 includes support for SOCKS5 authentication.

  Thanks,

  Scott McGuire
  Fetch Softworks

  [This message has been edited by ScottMcGuire (edited 10-02-2006).]

  Posted 17 years ago #