From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 11054966 for ecs-isp@2rosenthals.com; Mon, 30 Sep 2024 17:49:50 -0400 Received: from secmgr-va.2rosenthals.com ([50.73.8.217]:33129 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1svOH5-000000006LD-1xwm for ecs-isp@2rosenthals.com; Mon, 30 Sep 2024 17:49:48 -0400 Received: from mta-101b.earthlink-vadesecure.net ([51.81.61.61]:60799 helo=mta-101a.earthlink-vadesecure.net) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.97.1) (envelope-from ) id 1svOH3-000000000UZ-1bon for ecs-isp@2rosenthals.com; Mon, 30 Sep 2024 17:49:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=3FTQlyXe6qQTk9KZdGY+KS9Yw/b1n7RLpyd87O ZLJIA=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-unsubscribe-post: list-subscribe:list-post:list-owner:list-archive; q=dns/txt; s=dk12062016; t=1727732985; x=1728337785; b=otIyqst42MrUtfyUjoKmaCyf5yJ 1djPZx0mOtZm+P5Fb+u6T0aBj3E5eW6lgL+i4xEpjTPXuakb0MKViGJTNSoiCL+2TTWxmjh dmNCkjFnVvsFrz/gd5RgIdy8W5OxZb6dzzq06ebUYgMFML34N76vOZAu7vfdvAGJL25g7jz N1Erd7dEEK9als/8s5BEP1lOndW9rirgV5bGApvVBVVkLkLd59kaYrhuIeHqPM0ocMiNeR2 WO1qnj7xEmhO2x0NkByX50gpoeOrAZhzBzmmcPCRqCOJ7zp2lbxjdte7sKPywtTIZwBL36L HVZh1RKTrHSnZ8fTj8Xxnv1Wuh/nFDg== Received: from slamain ([172.58.119.108]) by vsel1nmtao01p.internal.vadesecure.com with ngmta id 1d99b97a-17fa23fee9d61ca5; Mon, 30 Sep 2024 21:49:45 +0000 Message-ID: <66fb19e5.23.mr2ice.fgrirsq@earthlink.net> Date: Mon, 30 Sep 2024 14:36:37 -0700 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] FTP problem X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 09/30/24 at 05:05 PM, "Lewis G Rosenthal" said: Hi all, >Surely. As good a place as any. There's always Peter's FTPServer list, but it seems that almost everyone is on all the lists and the lists are low traffic, so it really does not matter, IMO. >Bear in mind that the Zeitgeist is that FTP is evil. It is quite possible > that a router along the way blocked your FTP traffic. While it's possible, the failure's I've seen are typically something else. Most often a firewall requires the client to toggle between active/passive mode. Another less likely case is that the ports specifed for use by FTPServer don't match the open ports. See Setup->Options->Restrict PASV data port numbers. >difficult to determine which intervening hop is blackholing your >traffic. tracerte uses UDP, so even specifying the port (tracerte -p 21) >may not get you reliable results (timed out for me around hop 12, even >specifying a longer wait time). My experience is that tracerte fails more often than not these days. The routers are not configured to support it. My workaround is telnet ftp.foo.com 21 This tests if a connection is even possible. It takes login issues and data port issues out of the mix. If you want a bit more data, iptrace can provide some. On the client end it will show you if the SYN packet gets a response. On the server side it will show you if the SYN packet ever makes it to the server. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------