Although FXPing is very easy, there are a few restrictions to transferring the files. Both hosts have to support PASV mode and must allow PORT commands to foreign hosts. The FXP client tells the destination FTP to listen for a connection by sending a "PASV" command. The source FTP then connects to the data port reported by the destination server (after a success PASV command). So all the data goes directly from the source to the destination FTP and both servers do only report status messages on fail/success to the FTP client. At least one of the two remote hosts has to be a non-NT FTP-server, like a UNIX host or anything else. You can move files from a non-NT FTP-server to a NT FTP-server and the other way around, but you CANNOT FXP from a NT to an NT. One way to get by this limitation is using a Wingate (see the security section).

Another way of hiding your identity and transfer your files is using a wingate. Wingate is installed and run on a Windows 9x/ NT computer and used as a server for a lan. All other pc's connected to the lan will access the internet through this Wingate. Wingates work a little differently then socks proxy servers. If you log onto both sites using the same port , the files you want to transfer between the two sites are going through the wingate. The advantage to this is that it will allow you to FXP files to/from sites you could not before. The disadvantage is, the speed of your transfer is limited by the speed of the wingate you are using. Wingates are usually very busy and because of that very slow. Unless you absolutely can not make two sites FXP to each other, you probably do not want to use a wingate, as it will slow down your transfer 99.99% of the time. Wingates offer you a lot of services, but make sure when you are transferring files you always use port 21, not 23!