Okay, color me confused. Here is the FTP from last Saturday that worked:
EZA1456I Connect to ?
EZA1736I public.dhe.ibm.com
EZA1554I Connecting to: dispby-112.boulder.ibm.com 170.225.15.112 port: 21.
Snipped disclaimer...
220 service.boulder.ibm.com FTP server (Version wu-2.6.3(5) Custom Tue Jul 2
15:15:19 MDT 2013) ready.
>From Sunday through yesterday that did not work:
EZA1456I Connect to ?
EZA1736I public.dhe.ibm.com
EZA1554I Connecting to: dispmy-112.mul.ie.ibm.com 129.35.224.112 port: 21.
>From this morning with NO CHANGES made on my end:
EZA1456I Connect to ?
EZA1736I public.dhe.ibm.com
EZA1554I Connecting to: dispby-112.boulder.ibm.com 170.225.15.112 port: 21.
220 ProFTPD 1.3.5b Server (proftpd) [170.225.15.112]
My firewall did not like: dispmy-112.mul.ie.ibm.com 129.35.224.112 port: 21.
IBM, at least for this morning, reverted back to dispby-112.boulder.ibm.com
170.225.15.112 port: 21 and my FTP worked like a charm.
In my joy at a good FTP, I almost missed the second line of: ProFTPD 1.3.5b
Server (proftpd). A quick search revealed where it came from. Perhaps the
developers should ask IBM if they can list them as one of the sites powered by
ProFTPD. :-)
Bob
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
