Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
FTP problem: one server returns internal IP (incorrect), the other returns external (correct)
182 views
Skip to first unread message
Mr. K.V.B.L.
Apr 12, 2012, 5:30:20 PM4/12/12
to
Two identical i5/OS machines, but their FTP servers are not configured the same way.
One machine returns it's internal IP address in the 227 response. I think this is having issues with certain FTP client. The other machine returns its external IP, and all is right with the world.
Filezilla at least has a fallback mechanism:
Command: PASV
Response: 227 Entering Passive Mode (172,16,10,30,141,5).
Status: Server sent passive reply with unroutable address. Using server address instead.
SmartFTP does as well:
[14:21:36] PASV
[14:21:36] 227 Entering Passive Mode (172,16,10,30,121,95).
[14:21:36] Passive IP address returned from server different from server IP.
[14:21:36] Replacing received PASV address 172.16.10.30 by server address xxx.xxx.xxx.xxx.
So what do I need to change on the incorrect machine, and is simply ending/restarting the FTP server enough or do I have to shut down TCP altogether? I feel like I've been through WRKTCPSTS and CFGTCP but I'm not seeing it or not in the right spot.
Thanks again!
One machine returns it's internal IP address in the 227 response. I think this is having issues with certain FTP client. The other machine returns its external IP, and all is right with the world.
Filezilla at least has a fallback mechanism:
Command: PASV
Response: 227 Entering Passive Mode (172,16,10,30,141,5).
Status: Server sent passive reply with unroutable address. Using server address instead.
SmartFTP does as well:
[14:21:36] PASV
[14:21:36] 227 Entering Passive Mode (172,16,10,30,121,95).
[14:21:36] Passive IP address returned from server different from server IP.
[14:21:36] Replacing received PASV address 172.16.10.30 by server address xxx.xxx.xxx.xxx.
So what do I need to change on the incorrect machine, and is simply ending/restarting the FTP server enough or do I have to shut down TCP altogether? I feel like I've been through WRKTCPSTS and CFGTCP but I'm not seeing it or not in the right spot.
Thanks again!
iseriesflorida
Apr 16, 2012, 8:10:17 AM4/16/12
to
between the servers with no issues, sounds like a firewall routing
issue.
oogla
May 10, 2012, 6:52:07 PM5/10/12
to
I wonder if this IP is being retrieved via a reverse DNS lookup on the
FTP server side. Take a look at CFGTCP option 12 to see what the TCP
host and domain name are. Also check the host name search priority.
If it is *LOCAL, then look at CFGTCP option 10 and see what IP is
listed there for the IBM i's short and long names.
FTP server side. Take a look at CFGTCP option 12 to see what the TCP
host and domain name are. Also check the host name search priority.
If it is *LOCAL, then look at CFGTCP option 10 and see what IP is
listed there for the IBM i's short and long names.
0 new messages