× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Vern 
Indeed on both AS/400 is the reference used and the fact the server crashed has been squashed.
We are at least getting some attention and having a conversation now. 
I greatly appreciate everyone's attention on this.
Regards,Laura


Laura Ubelhor

President

Consultech Services, Inc.

Office: (248) 628-6800 

ubelhor@xxxxxxxxxxxxx | www.consultechservicesinc.com


On Thursday, February 3, 2022, 03:50:31 PM EST, Vern Hamberg via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Hi Laura

Sounds like the network folks are taking the usual tack - blame the
AS/400 - yes, they will not know the current name, right?

Of course, what is the first rule in troubleshooting? What changed? But
they won't go there, I bet!

Good luck!
Vern

On 2/3/2022 11:54 AM, Laura Ubelhor wrote:
Hello:
I don't believe so.
The weird thing is the FTP worked for several years.  They had a network server crash and it stopped.  Of course on the network side they are not being very helpful.   They came up with slow the data transfer down response,  They finally shared a log but have not been real helpful.
The weird thing is if you send the file manually it works just fine.
If you send it automatically (which worked for years) it does not.
The ids are the same the ports the same.   I really think it is on the network side.

What do you think about this response from midrange

"Unable to setup for an active data connection to the server reason code 2.

Passive FTP is all driven by the client.
Active FTP requires the remote server to open a second socket connection
back to the client.
No doubt the enterprise firewall prevents such an action.

If I understand by what I see on the logs the Passive is the manual send which works.
The active is the batch that does not.
Does you think this is accurate?  Does active require a second socket connection back to the client?
Thanks for jumping in.  Cindy is working on this and is quite frustrated.  It's the usual conversation the network group is not being very helpful although it happened after the server went down (crashed we hear) and after it was back  up.  The server is used to collect feeds from around the world and resides in Germany.   I have no insight into whether other transfers are crashing although I have asked.
It's a winter wonderland here in Michigan.  Very pretty but not much outside activity.   It looks like we got about a foot of snow.
Hope you're doing well.
ThanksRegards,Laura

Laura Ubelhor

President

Consultech Services, Inc.

Office: (248) 628-6800

ubelhor@xxxxxxxxxxxxx | www.consultechservicesinc.com
 

      On Thursday, February 3, 2022, 12:07:27 PM EST, Richard Schoen <richard@xxxxxxxxxxxxxxxxx> wrote:
 
  Maybe I missed this but have you tested the FTP with something like FileZilla ?

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
----------------------------------------------------------------------

message: 1
date: Thu, 3 Feb 2022 09:48:22 -0700
from: Jack Woehr via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
subject: Re: FTP to fast

On Thu, Feb 3, 2022 at 9:43 AM Laura Ubelhor <ubelhor@xxxxxxxxxxxxx> wrote:

"Unable to setup for an active data connection to the server reason code 2.

Passive FTP is all driven by the client.
Active FTP requires the remote server to open a second socket connection back to the client.
No doubt the enterprise firewall prevents such an action.

--
Jack Woehr, IBM Champion 2021
<https://www.youracclaim.com/badges/528d23d6-087f-4698-8d17-d59688106ac4/public_url>
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.