Home Network and FXP problem

[reaver]

Hi there,
I met with a FTP problem

Initially I have only 1 PC connected to my cable connection and FXP did not give me any problem

However recently I created a home network LAN with my lappy using crossover ethernet cable/2 NICS method to share the internet connection

The internet connection and pinging between the 2 systems are OK.

However when I am using the HOST system trying to FTP any sites using FXP, it gave me "CONNECTION FAILED (CONNECTION REFUSED" error message.

Is there anything I can do to solve this problem ??
Thanx alot !!

[bigstar]

Site to Site transfers are not compatible with most home network solutions. This includes most software/hardware that uses Network Address Translations (NAT).

NAT will effect site to site transfers in both instances.
FTP SERVER > NAT > INTERNET or FTP CLIENT > NAT > INTERNET

The problem arises from NAT's protocol helpers, which monitor most common protocols for common commands that often send the wrong IP address to the server. In the case of the FTP protocol this happens to be the PORT command. When performing normal FTP transfers the PORT command contains your local machine IP, behind a NAT firewall/router this IP is incorrect so NAT modifies the IP to that of the router/firewall. However when the same rules are applied to site to site transfers it causes them to fail. One of FTP server ends up trying to connect to your router/firewall and not the other FTP server.

The only solution I am aware of is to run both FTP servers on a non-standard port, Most NAT firewall/router only monitor port 21, so if the FTP server was run on port 2121 it would not be effected. But this also has a catch 22, now that you're running the FTP server on port 2121 you will not be able to use the PORT command for file listing without NAT.

[reaver]

That means I have to change my PORT setting in FXP ??
Will that solve my problem ?

[bigstar]

No--The FTP server needs to change its port number.

[reaver]

Originally posted by bigstar
No--The FTP server needs to change its port number.

Okie...
I managed to solve the problem and it lies with my Norton Internet Security.

Disable the NIS and FXP works like charm.

Thanx alot !!