Bizzare ftp behaviour

[Ray Herbig]

When a file is ftp'd (either get or put), nothing is transferred. The file that is created on the remote end as a 0 byte file. A return code of 226 is given. This also happens on the local network where the only hop is through a switch.
Has anyone seen anything like this. I thought that somewhere in the recesses of my brain I had seen something to the effect where two firewalls both being active or both passive create such a mess.


Thanks.
Ray

[Tom Danzig]

The error code 226 is "Address already in use". Perhaps you could use lsof or netstat -a to find out if the ftp port(s) are already locked by some other process.

[Paula J Frazer-Campbell]

Hi
Try a traceroute to see if your routing is as you think.


HTH

Paula

[Vincenzo Restuccia]

Conflict of IP addresses.

[Brian Hackley]

Ray,

I'd go with the duplicate IP address as most likely cause, should the problem only be between hosts on your local IP subnet, and the all of those hosts can FTP off the local subnet. Look at arp and compare the MAC address for that target host with the MAC/Station address on the target host (e.g. lanscan on that box).

I would also test out other FTP commands to the target system, and if not able to resolve the issue completely at that point, take a nettl network trace or a sniffer trace to pinpoint what's actually happening on the network. This would of course reveal the MAC addresses of the systems which you can then verify again.

Hope all of this helps,

-> Brian Hackley