Fetch Softworks

server responce; Illegal port comment (8 posts)

• Started 22 years ago by Main
• Latest reply 22 years ago from Jim Matthews

• Main Member

  Under OS X I'll get the above server responce. Under 9.2.2 everything seems to be OK. Try'd several things like switching off firewall, reinstall but nothing seems to help to make contact with the server. Any suggestions?
  main

  Posted 22 years ago #

• Jim Matthews Administrator

  I would recommend unchecking the "Use Internet Config" box in the General section of Preferences and checking the "Use passive mode transfers (PASV)" box in the Firewall section of Preferences.

  Does that help? If not, could you post a transcript (from the Fetch Transcript window)?

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 22 years ago #

• Main Member

  Originally posted by JimMatthews:

  I would recommend unchecking the "Use Internet Config" box in the General section of Preferences and checking the "Use passive mode transfers (PASV)" box in the Firewall section of Preferences.

  Does that help? If not, could you post a transcript (from the Fetch Transcript window)?

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 22 years ago #

• Main Member

  Just opened the preferences, checked my settings and and went to the fetch url. Got in............ whent to my own site, got in...........
  It's great that it's working now but, what was the problem?

  Thank Jim!

  Posted 22 years ago #

• Jim Matthews Administrator

  Selecting passive mode transfers works around a Fetch bug on Mac OS X; the bug itself will be fixed in Fetch 4.0.2.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 22 years ago #

• mordac Member

  Jim

  I also get the 'illegal port command' with Fetch 4.01 and MacOS 10.1.3 . No problems with 4.01 or 3.03 under OS 9. Our ftp server doesn't work with passive, and I'm having a hard time working with 9 anymore - so I'm stuck right now.

  I connect via cable modem (internet <---> 192.168.100.1), and SMC Barricade 4 port router (192.168.100.2 <---> 192.168.2.xxx).

  If the previous art work confused things, the side of the router that talks to the modem is 192.168.100.2 .

  From our server's logs:

  Mar 25 16:04:51 holman ftpd[26637]: refused PORT 192.168.100.2,46407 from c-24-118-133-120.mn.client2.attbi.com [24.118.133.120]
  Mar 25 16:05:01 holman ftpd[26637]: refused PORT 192.168.100.2,28324 from c-24-118-133-120.mn.client2.attbi.com [24.118.133.120]

  Note the IP in the port number.

  Is this the OSX bug you refer to working around in 4.02, or is this another problem?

  Thanks,

  Steve

  Posted 22 years ago #

• mordac Member

  Jim

  I also get the 'illegal port command' with Fetch 4.01 and MacOS 10.1.3 . No problems with 4.01 or 3.03 under OS 9. Our ftp server doesn't work with passive, and I'm having a hard time working with 9 anymore - so I'm stuck right now.

  I connect via cable modem (internet <---> 192.168.100.1), and SMC Barricade 4 port router (192.168.100.2 <---> 192.168.2.xxx).

  If the previous art work confused things, the side of the router that talks to the modem is 192.168.100.2 .

  From our server's logs:

  Mar 25 16:04:51 holman ftpd[26637]: refused PORT 192.168.100.2,46407 from c-24-118-133-120.mn.client2.attbi.com [24.118.133.120]
  Mar 25 16:05:01 holman ftpd[26637]: refused PORT 192.168.100.2,28324 from c-24-118-133-120.mn.client2.attbi.com [24.118.133.120]

  Note the IP in the port number.

  Is this the OSX bug you refer to working around in 4.02, or is this another problem?

  Thanks,

  Steve

  Posted 22 years ago #

• Jim Matthews Administrator

  One of the tricky things about using PORT (rather than passive mode transfers) is that if you are behind a Network Address Translation (NAT) device, such as your SMC router, the router has to rewrite the PORT command. The PORT command tells the server where to connect, but if your Mac is behind a NAT device its IP address is not valid on the Internet at large -- the NAT device has to substitute one that is.

  The logs show your SMC box rewriting the address Fetch is sending in the PORT command with another private address (192.168.100.2) rather than your network's public address (24.118.133.120). Since this setup is working from Mac OS 9 I believe this is caused by Fetch sending the wrong address in the PORT command. That's the bug that will be fixed in 4.0.2.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 22 years ago #