× 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.



There are a number of network issues that can cause this issue. I have seen the negotiation issues,
and I have also seen a problem where the switch stack wasn't chained together properly, causing errors
between switches. Any workstation too far down the chain couldn't do large file transfers
efficiently.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bradley V.
Stone
Sent: Thursday, July 24, 2008 5:19 PM
To: Midrange Systems Technical Discussion
Subject: RE: File Transfer from PC to iSeries Sucks

I had a similar problem years back working for a large company. After
bugging the network admins enough that it appeared there was some sort of
"throttling down" happening, they finally admitted there was. So, it was an
application they had in place that was causing the "problem". We only found
it because we were using FTP to transmit XML with embedded binary images and
it was simply too slow to do any good.

Bradley V. Stone
BVSTools - www.bvstools.com
eRPG SDK - www.erpgsdk.com

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Mike Cunningham
Sent: Thursday, July 24, 2008 4:05 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: File Transfer from PC to iSeries Sucks


Speed and Duplex setting on your PC and the network port it is
connection to have to match. I have seen many articles that say
the network switch side should NEVER be set to autonegotiate yet
nearly every network admin I have met refuse to follow that
advice because it's too much work. Same on the server side. Your
iSeries NIC spend and duplex settings need to match the switch
port, and again no autonegotiation on the switch side. We have
also seen similar issues in the past when there were multiple
switches/routers in place where maximum packet size settings were
different. Normal every day traffic will not reveal these
problems because the number and size of packets are small but
anytime you do big file copies or backups across the wire these
problems will be more evident

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Lukas Beeler
Sent: Thursday, July 24, 2008 4:42 PM
To: Midrange Systems Technical Discussion
Subject: Re: File Transfer from PC to iSeries Sucks

On Thu, Jul 24, 2008 at 10:23 PM, Bruce Collins
<Bruce.Collins@xxxxxxxxxxxxx> wrote:
Using WS-Ftp Pro 2007 it starts at 1500 kbps and drops to 45 kbps.
Using DOS FTP does much better than windows based but still
slower than I think it should be.
Using Client Abscess doing a drag and drop. About the same as windows.

Okay, this means you have a network problem.

I check all the Line descriptions and no Duplex Mismatches. If
I go and ask the network guys could we have faulty switches, NIC
or other stuff they just laugh and no. Their statement is "no one
else has called and complained". I have no control over that group.

Ah, the joy of big companies.

You'll need to narrow down the problem and present evidence.

Do you have a currently unused network card on the system? Plug a
laptop into it, add a line description and IP address, and do a direct
transfer. If your machine can sustain it (specs would help - how many
arms, what model, what cpu, how much memory), you should see up to
12MByte/s on a 100MB Link or up to 120Mbyte/s on a Gigabit Link (at
first - the laptop won't be able to write that fast).

If you can't logon to the switches, you can't check if there are
duplex mismatches. A best practice today is to leave everything at
Auto/Auto (earlier, manual configuration was better than
autodetection).

Lukas you will have to help me with what is "SMB Signing"?

SMB Signing is something that can prevent MITM-Attacks with SMB (aka
CIFS aka Windows Filesharing) - it's what Netserver uses.
Misconfigured SMB Signing can cause the problem you described, but if
FTP exhibits the same problems you can exclude SMB Signing as being
the issue - SMB Signing only effects netserver, not FTP.

--
Read my blog at http://projectdream.org
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.