• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 932
  • Last Modified:

Netout Ftp issues

I have a very strange issue here. We recently upgraded our Linux server (Hardware and OS) and moved from proftp to vsftp. prior to the upgrade ms ftp had no issues connecting and could send large files from a remote server. Now when using ms ftp from any PC on the remote network with file over a half a meg we get a "NetOut: Connection reset by peer" error. Here is where it begins to get strange using core ftp I can put files of any size on the new box. Now it is getting even stranger. I can us msftp from any machine at home and put large files on the new box and I can ftp with ms ftp any file to my home server (Windows 2000, IIS5). Naturally I thought it was my firewall at the office (Linksys RV016) not liking the new server but I cannot for the life of me figure out where it could be going wrong. I have adjust the MTU from Auto to manual set at 1492 and 1500. I am at a loss and need to get this thing up and running as I have several batch files that put report data on the Linux box nightly.

Any insight would be great.

Thanks
Dan
0
panhead802
Asked:
panhead802
  • 3
  • 2
1 Solution
 
owensleftfootCommented:
Have you had a look at http://www.dslreports.com/faq/6264
0
 
panhead802Author Commented:
The firewall in front of my ftp server does not accept icmp requests. So I cannot pint it to test like this.

Not so sure why changing servers would have this affect.

Dan
0
 
jccs0519Commented:
FTP uses 2 tcp ports 20 & 21, sometimes it's pretty hard to troubleshoot especially w/ firewall involved.  Your new linux server may have its firewall enabled, w/ 2 tcp ports back and forth maybe a problem.  Sometimes passive FTP will work but sometimes it won't.  When you refer to msftp, you're talking about Windows Explorer FTP feature, right?  You can go to Internet Explorer options and change to Passive FTP and see if that works.

Personally, I recommend using WinSCP (it's free).  It uses ssh port (22) and it encrypts the data, so it's safer to transfer and you don't have to worry about the TCP 20/21 port issue.  All you have to do is have your firewall allow 22 open for ssh/scp for your server.  Then on your PC install WinSCP, then you can transfer files and shouldn't have problem.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
panhead802Author Commented:
By msftp I mean command line ftp, most of the ftp work is done through batch files so I need something I can call from the command line. Not so sure it can be a firewall port issue as I can send small files all day long but as soon as I get over 1mg it transfers for a while the I get the Netout error.

I can also transfer files from my home server to the new linux box no issues and I can transfer large files from my server at the office to my home server. (Home Server W2K)

I am at a loss.

Thansk
0
 
jccs0519Commented:
Hmm, that does seems kinda weird.

I just re-read your question in detail.  So based on that, you used another FTP software "CoreFTP" and it works fine?  That sounds to me, the ms ftp software is not compatible w/ the vsftp on linux?

As a wild shot, try disable Linux firewall see if that helps.  If not, something not compatible w/ ms ftp w/ vsftp.  Try another command ftp program on Windows, maybe ncftp window client will work for you?

http://www.ncftp.com/download/

Although it's weird that ms ftp work from your home.  You may just have to tried several things different and try to troubleshoot one step at a time.
0
 
panhead802Author Commented:
Thanks for the input, I am going to look at ncftp and will let know how we make out.

Do you think I should set it up to transfer in Passive mode?

Thanks
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now