linux sles 12 file transfer to windows slow using winscp
 

hi all,

using sles 12 on power
when i transfer files from windows to suse its quick using winscp
sftp protocol

but when i transfer the same file from suse to linux it takes very long..its very very slow

Regards
suraqah

That is confusing. SUSE is a Linux distribution (distro). What OTHER "linux" are you transferring the file to?

As to differences in transfer rates many things can be involved.
Are all 3 systems on the same subnet?
Do all 3 systems have the same speed NIC?
Is there a virus scanner on the target "linux"?
When you do the transfer from "suse" to "linux" how exactly are you doing it? i.e. What command or utility are you using and what flags are you passing?

sorry it was my mistake

again

sles 12 on power 8
and windows 2012
only 2 machines

when transfering files to sles 12 from windows 2012 its quick

when transfering from sles to windows 2012 its v. slow

using sftp thru utiliy winscp

networkd speed on windows 1gigbit ethernet
sles is on power vio shared 4gigbit

Is the Windows machine running an anti-virus software? Does the transfer run any faster if you temporarily disable that?

Are there many files in the directory on the Windows machine that you're trying to transfer into? It may be the filesystem itself is slowing you down. What if you try transferring to a different folder?

Are you by any chance transferring the file into a shared folder mounted on the Windows machine from a separate Windows server or NAS? The double network hit of transferring in might be slowing you down as might the anti-virus and filesystems settings of the separate Windows server.

I'm not familiar with the vio 4GB you mention. It could simply be that the network on the Linux system is receiving more quickly than the one on the Windows system.

i even checked from other windows machine.. its the same.

no antivirus

its not shared folder.

And the answers to my other questions/suggestions are?

I'm not familiar with the vio 4GB you mention. It could simply be that the network on the Linux system is receiving more quickly than the one on the Windows system.
__________________

could b..

but is there any procedure to check it out

Read the LQ Rules about text-speak, and about not using it; please spell out your words.

Testing network speed can be done with the iperf command. Install it if you don't have it.

You say this is a VIO interface on PowerPC...that's IBM hardware, and you're using SLES 12. You are paying for support from both IBM and SuSE; have you contacted either of them? Have you read the documentation on the VIO system, and how to configure the interfaces properly?
https://www.ibm.com/developerworks/c...ge/VIOS+Detail
https://www.ibm.com/developerworks/c...tual+IO+Server

You still don't answer the other questions about your system, or say whether this is a new installation or old, and if this problem is new or not. Could be that there has been an OS update that has modified some network driver/value and is causing problems. Have there been? Anything updated on the IBM Side?

yes i have read now LQ rules and will be carefull from next time.. thanks for letting me know about it.

yes i have read vios documentation.

this environment is new environment and all servers are newly implemented and configured.

i have implemented such systems quite a number of times but its a strange issue that i m facing..

to come to main point.

SLES 12.1
using ethtool i have seen that network adapter is full duplex. with auto negotiation on.. MTU 1500
windows 2012
auto negotiation is on --> on the network adapter.. jumbo packet is disabled which means MTU is not set. transfer buffer is 256.. receiving buffer is 512..

Generally windows drives are NTFS partition but i have created a FAT32 drive and tried copying a file from SLES to windows that is also very slow.

Things in my mind to be checked are following
check switch ports if they are set for auto.
check switch ports tx and rx if both are configured as full duplex
secondly jumbo packet can be tried to be enabled and set to 9044bytes then on sles i will set MTU to same 9044bytes

finally i can disable auto negotiate and set same speed on both servers. and then try..

The above is my plan..

if there is anything in specific you want to know. pls let me know..

Thanks

So it's a new environment...and you've done this before? If you've done this before, then you must ALREADY KNOW how to troubleshoot/diagnose issues with networking already, don't you?
None of this points to a disk issue, but a networking issue. Again, you're using SLES with IBM hardware...you are PAYING FOR SUPPORT from both parties. You should call them and ask for assistance, but I'd start with IBM.
Great, but doing all of this should have been your FIRST thing, since all of this is troubleshooting.
Seriously???? We tell you about not using text-speak, and you end with "pls"????

please let me know other text-speak mistakes..
the problem resolves or not.. at least my text-speak will improve..

Already in touch with IBM.. anything else you have to recommend me other than text-speak..

Good to know.
You were asked numerous questions above, which you still haven't answered, and were given suggestions as to how to troubleshoot your network problem, and were even given a utility name to run. You seem to ignore all of those things, and instead want to be borderline insulting with your "anything else you have to recommend me other than text-speak." comment.

You didn't answer most of the questions from post #2, and seem to contradict yourself by saying that this is a new installation..that you have done before. Unless ALL of the hardware/software is identical, there could be a LOT of different reasons things could be happening. You also indicate that you haven't performed basic network troubleshooting as of yet. Until you actually have some data to work with, everything is just speculation.

post # 2 was answered in Post # 3.

I am not contradicting my statement.. read it carefully. it will tell you that i have implemented similar systems at different sites. not this system

iperf will give me bandwith measurements.. which i have already said it is slow.. in specific from sles to windows... so i didnt feel like spending my time on iperf.



I have insulting way.. and you have a appreciation style where you dont look at the whole text.. and just found pls and started taunting on it..
anyways TB0ne thanks a lot..

with all due respect.. pls leave me alone

Really?? You were asked in post #2

• Are all 3 systems on the same subnet?
• Do all 3 systems have the same speed NIC?
• Is there a virus scanner on the target "linux"?
• When you do the transfer from "suse" to "linux" how exactly are you doing it? i.e. What command or utility are you using and what flags are you passing?

You have not answered ANY of these, with the exception of saying you're using winscp...but you don't tell us what flags/options you're using. You say nothing about the subnets, NIC's, or any Linux virus scanners.
I did, and it was not clear. Now it is. So this is a new installation, and **NOT** the same, but SIMILAR. Again, different hardware/software=different results.
Seriously??? "Slow" can be because of poor upload or download times...and unless you ACTUALLY RUN TESTS, you won't know which you have to look at. You're admitting you got a suggestion, didn't use it because you already knew it was slow....so you didn't think diagnostics/troubleshooting were worth looking at??? How do you think you're going to solve the issue?? Iperf is a pretty comprehensive tool, so if you didn't want to spend your time on it...what HAVE you actually done then?? What tests have you run, and what were the results??

Again, unless you actually DO some testing and gather data, what do you think anyone will be able to tell you?
Grow up, please. You were asked "Please" in my first post to read the LQ Rules and not do it...and you continued to do it, and still are. The LQ Rules are there for a reason, and doing something in a public forum where it is not only against the rules, but something other members are asking you not to do, is just plain rude.

Good luck getting help from anyone; I'm done with you.