×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I have come across a situation that I need some help with. Our scanning
package uses FTP to move images into the IFS. It recently became terribly
slow at doing this after working fine for months. The software uses a
Microsoft API inside their .NET application to perform the transfer.
In an effort to troubleshoot this issue, I tried a few "normal" FTP
transfers from the CMD window and had no issues with speed. Accessing the
system using the "
ftp://192.168.1.1/Mydirectory"; method is extremely slow
and I presume is the same way the API call does it. It takes over a
minute for the login prompt to appear and even longer for the directory
listing to appear. This is on each attempt.
What is the fundamental difference between the two access methods? Is
Windows influencing the speed when using the "
ftp://"; method? The user's
Windows domain userid and password are not synchronized with the i5.
The network admin swears nothing has changed that would cause the issue.
Thanks,
-Steve
midrange.com
