The Solution: The solution depends from the network administrator of the client network to use high-quality network address translation software. The big problem is that when a client program is using network address translation to hide behind a routing device on an internal network, when using PORT the client tells a server on the external network to connect to an address on the client's internal network. I found the solution! Under google cloud network is not possible to establish an active ftp connection with an external ftp server. TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 There are no firewall rules in the local machine. The server accept only active mode connections (no passive). In the "google firewall" I opened all ports from (ftp server address). In my opinion there are some problem in the NAT / port forwarding rules between local and public IP. I saw another post without any solutions about active mode connection from google cloud. it seems impossible to establish an active ftp connection with an external ftp server. Running a Google Compute Instance with an internal interface mapped to a temporary public IP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |