***This is the 2nd instance of this post. I had to post it again, as I had inadvertently hit "ANSWERED" on the original post. The question is still "NOT ANSWERED".
Here is the original post...
I have a very interesting problem at a client site this morning. Here is a summary of the problem in a nutshell.
This specific client has set up FTP to an FTP server in a DMZ at their Headquarters building. They have two Production servers that send FTP data to the box in the DMZ. The 1st of the two servers sending FTP data is located on the inside network (they use an ASA with a inside, outside, DMZ, WAN) and sends the FTP data into the box on the DMZ.
The 2nd of the two production servers is located across the WAN interface of the ASA.
The issue is as follows: Server 1 can perform all of its ftp commands correctly once it has connected to the FTP server in the DMZ. Server 2 can log into the FTP server and authenticate successfully, but when a "ls" command or and "dir" command is issued, there is no response (the contents of the root folder are not listed as they are when the same command is issued on the 1st server).
I have been running sniffer on the FTP server in the DMZ, but cannot tell from the traces what is wrong. I have a hard time beleiving that this may be an ACL issue, as if FTP was not allowed coming in from the WAN interface, then they would not have the ability to authenticate.
I am wondering if anyone has seen behavior like this before...
Thanks for any help or insight.
Kevin
