During the distribution procedure atvise Builder uses the standard FTP ethernet protocol .The connection will be established using the passive FTP mode. The atvise Builder initiates a described here https://en.wikipedia.org/wiki/File_Transfer_Protocol. Read on for details in the active/passive FTP connection chapter. When the distribute command is used within atvise Builder the connection will be executed across a 'passive' FTP mode connection by an FTP client running as a Windows service in the backgound. The FTP client initiates this connection using a PASV command over port 21 while the netSCADA device replies over a free port >1023.You may . So make sure that the port 21 is opened from communications from atvise PC->netSCADA device. The passive protocol defines that with a FTP passive connection the server (netSCADA device) replies with a port beyond >1023. So make sure that this port netSCADA device->atvise PC is also opened. This port will be determined dynamically by netSCADA device and cannot be predicted. Either you make a local ethernet frame analysis to get knowledge of this port or you configure a range of ports in your router to be opened. To make tests if a proper FTP connection works you can use a standard FTP client such as Filezilla https://filezilla-project.org/ to get access to a netSCADA device alternatively. The client software needs to be configure in passive mode with authentication using the login user: admin and password: ftpnetlink Summary: In case you want to a establish a connection over Internet across a router to a local netSCADA device then you have to open or forward the port 21 and AND the specific netSCADA FTP reply port in order to allow a proper connection from remote. |