|
FTP<F4> Tab to Port, <F1>
*DFT
The value 00021 is used.
So, yes, unless you're really into that kind of configuration, port 21
should be it.
Another thing that we used to do here is restrict ftp to only certain
addresses. Originally if a customer wanted to ftp something to us it was
a big pain in the a$$ because we had to find out their IP address (or
whatever their network NATted it to). Then talk to the firewall
consultant and have him open it up. When our customers started getting
more mobile we stopped doing that. And now any IP address can get in. We
do block a few ChiComms and what not that keep banging away on it.
Want to test ftp on the i locally? Try this.
telnet to the i (or open a 5250 session)
once there try this:
ftp '127.0.0.1'
that's the loop back port and should work just fine.
Might try a simple put like this:
CRTSAVF MYLIB/MYSAVF1
CRTSAVF MYLIB/MYSAVF2
SAVOBJ OBJ(MYSAVF2)
LIB(MYLIB)
DEV(*SAVF)
OBJTYPE(*FILE)
SAVF(MYLIB/MYSAVF1)
FTP '127.0.0.1'
bin
put mylib/mysavf1 mylib/mysavf2
quit
DSPSAVF FILE(MYLIB/MYSAVF2)
Because if you've verified the port. And you verified that it's not
blocking by IP address. Then you might have to check for the existence of
"Exit Point" programs:
WRKREGINF
Exit
Exit Point
Point Format Registered Text
QIBM_QTMF_SERVER_REQ VLRQ0100 *YES FTP Server Request Validation
QIBM_QTMF_SVR_LOGON TCPL0100 *YES FTP Server Logon
QIBM_QTMF_SVR_LOGON TCPL0200 *YES FTP Server Logon
QIBM_QTMF_SVR_LOGON TCPL0300 *YES FTP Server Logon
8=Work with exit programs
If you have something in there, let us know. We can spot certain vendors.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From:
Vinay Gavankar <vinaygav@xxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
04/29/2009 10:36 AM
Subject:
Re: Sending a SAVF using Operations Navigator
Sent by:
midrange-l-bounces@xxxxxxxxxxxx
@Natahan,
Thanks. But there is no network guy as such with this client and the
person
helping me there has no clue. He will open up any port for me on the
server,
but he doesn't know which one (and neither do I). The iSeries Access and
Operations Navigator work fine. Any idea which ports to look for? I think
one of them is 21. Anything else?
@Evan,
I did try that, but got a message saying that operation was invalid. Maybe
because it was a savf (with an extension of .savf). I was told that when
you
FTP such files, the i takes handles it correctly.
Vinay
On 4/28/09, Nathan Andelin <nandelin@xxxxxxxxx> wrote:
they
Vinay,
If it were me, I'd begin by asking a network administrator why FTP won't
work. It may be that they've used a Firewall to block the port. If
won't open it, then find out what ports are open. Maybe they've blockedonly
ports used by iSeries Access and Operations Navigator too. Maybe they
allow VPN connections. Who knows? Those network guys get prettyparticular
about how the network is used.live
Nathan.
----- Original Message ----
From: Vinay Gavankar <vinaygav@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, April 28, 2009 4:30:08 PM
Subject: Sending a SAVF using Operations Navigator
Hi All,
I have a SAVF on my PC which I want to send to the i. I am not on the
network the i is on, and am accessing it using Client Access and the
address (65.xxx.xx.xxx)."ftp
FTP is the simplest, but I can't get the FTP to work. When I go to the
command prompt of my pc (Start, Run, cmd) and type in the real address
65.xxx.xx.xxx", I get an error message "ftp: connect: unknown errorto
number".
FTP server on the i is definitely started.
I can ftp to other sites from my pc as well as from the i - e.g.
ftp.microsoft.com
I also tried to ftp to this i from another i, but no luck.
Is there anything else that needs to be done on the i so that I can ftp
it?list
Otherwise, is it possible to send the savf using Operations Navigator?
Thanks in advance for any help
Vinay
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxlist
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.