Red Hat

One quick question, you have mentioned here that Redhat is doing ASCII transfer, but the issue we face is when I transfer the file from windows to Linux and not Vice Versa.
Also,
as mentioned previously, in the command window of dos, during ftp tp linux, I had mentioned ascii. So the ftp client on dos must have sent the file in ascii mode OR here the target(Linux) FTP server dictated terms and forced in binary?

Regarding contents of /etc/vsftpd/vsftpd.conf, I cannot put it here due to restrictions but, can you please tell me what exact thing to look into it?

---------- Post updated at 10:52 AM ---------- Previous update was at 10:42 AM ----------

One more thing, even if Redhat Linux forces the use of Binary mode, I also faced the issue when sending a proper binary file to Redhat. It also had the dos chars. Hows that possible then?

Not quite, I'm afraid. Back in those days when you had DOS PCs and code pages like 437 or 850, I had a long sed script to convert extended DOS char sets to *nix local char sets, which later was done by dos2unix on the fly (if I remember correctly, that is). It also converts between UTF-8 and UTF-16, I hear say.
But nowadays, when windows uses UTF-8 as well, it may reduce to just removing the <CR> characters.

I'd be looking for things like:

Code:

 
 allow ascii upload=no

and/or

Code:

allow ascii download=no

Something on those lines

Yes, found these line, but they are commented. So I guess its forcing binary as you said. But will these settings, which hare on the target Linux box, have any effect on the ftp which we do from a windows machine to it?

Yes, sure they can. The config determines how the whole service behaves, in both directions. I am guessing but I reckon the Redhat default setup is different to the Solaris setup. You haven't changed anything on the Windows end have you? You've just changed the Unix/Linux end which infers the Linux end has caused the problem.

Remember though if you change any of the config that you need to restart the service for it to take effect. Be professional and take a copy of the whole damned thing before you mess with it.

No changes on the windows side. But on Linux file I see that it forces binary as it fears denial of service attack. Not sure why Solaris didnt fear it, so may be it had some other protection.

So now what solution can we have for it?

Also the fact that Redhat is forcing binary is still not answering the other question as to why even files such as encrypted files which are sent from win to redhat in binary mode (explicitly chosen) still has dos chars. When we run dos2unix on them the size decreased and decryption happened successfully. Initially I had thought that those files were sent on Redhad in ascii mode by mistake. But now it is clear that they indeed went in binary (due to forcing). Then how they had dos chars issue?

As I already said, the vsftpd.conf file determines how ftp behaves (and it can be quite a large file).

If you can't post the contents here then I think you are into researching the configuration options yourself. At least you know where to look.

Do appreciate that it's difficult for us to chip in with the answers when we aren't given all the information.

I'm not a RedHat expert. If you don't get any fairly immediate answers then perhaps ask moderators to move this thread to the RedHat specialist forum where it will more likely be noticed by RedHat specialists. There are already members subscribed to this thread who are also moderators with the clout to make that happen and who will read this anyway.