Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
I have two computers, one is Suse 9.1 and the other is XP.
I have an ADSL modem/router that connects the two machines.
Internet speeds are fine on both machines.
I managed to set up Samba and am able to browse the shares from both computers.However, if i try and copy a file from one machine to another it takes forever. For example, a 1mb file takes about 4-5 mins to transfer.
My smb.conf file looks like:
Code:
code:[global]
workgroup = IVESNETWORK
interfaces = 127.0.0.1 eth0
security = user
encrypt passwords = yes
passdb backend = smbpasswd
server string = Samba Server
netbios name = samba1
socket options = TCP_NODELAY
[ives data]
comment = ives_home_folder
path = /home/ives
writeable = yes
browseable = yes
read only = no
I've read of similar problems with samba being slow, but despte browsing google for quite a time, I haven't found a reason that pertains to my situation.
Does anyone have any insight as to what might be casusing the very slow file transfers?
Fedora very slow getting LAN date after Service pack 2!
I hope some one knows what is wrong. I have 2 Windows XP pro computers. After I installed service pack 2 on my main windows XP pro PC I wanted to save the service pack 2 file to myserver4 that run Fedora cord 2 on it with a intel gigabit Ethernet card. It's a 266 MB file. Sending it from XP to Fedora with samba says it will take 240 minutes! I used my other Windows XP and it was 2 minutes to send it. But this Windows XP did not have service pack 2 install in it. So I installed service pack 2 on this 2nd XP. Then went to save the 266MB file to my Fedora Linux PC. It said it would take 143 minutes! I have 2 other linux but not running Fedora. It only takes about 2 and the other only, DEC 35 sec. for them to send that same 266MB file to them. I tested it with Windows XP both service pack 2 in them and it did it in 20 sec.
So it must be something with Fedora. The network card is a "Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller (rev 02)" it was fast at sending it files before installing service pack 2. But service pack 2 can still send files fast to two other Linux box's I have but not running Fedora. One is running Trustix Linux on a Netgear ND508 with a on-board Ethernet of "Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)" and the other is on a Hewlett-Packard digital entertainment center de100c, DEC for short. It has Redhat Linux 7.1. I can send the same 266MB file to them in less then 2 minutes. But not my Fedora core 2 that has a way faster gigabit network. I have a netgear gigabit GS105 switch with this PC on-board gigabit. It can get the file in 10 sec from it. But it will say 240 to send the same file to it.
All I can tell you is that I did fix my problem after spending a week trying differnet things.
In the end, out of desperation, I decided to put in an old NIC in my SUSE box instead of using the onboard ethernet port.
Well, that solved the problem.
I still don't know why the ethernet port on my mobo wasn't working as it should.It's a damn cheap mobo (PC CHips, so maybe that explains it)
This may be way off, but SP2 will firewall your NIC to all incoming connections by default. I had a problem browsing for my Samba server after installing SP2. I simply disabled the firewall and everything returned to pre-SP2 performance.
Still can't get it to get a file fast! All this did not fix it. Install a new version of samba because I had core 1 and updated with a DVD to core 2. "up2date -u" has all the updates. Stopped all services that could be stopped. Rebooted. Nothing helps. Tested with FTP and it sent the 266MB file in about 7 sec. So it must be something with samba. Even used the default samba configure. Did not help. It now says 142 minutes to send the 266 MB file with samba. Why is FTP fast and samba way slow? Maybe because I did a update to core 2. Because I had a friend help with this and he has Fedora cord 2 that he loaded fresh on a box and he tested the same file and it said about 30 sec to send it. He all so has XP service pack 2 installed.
I can only guess any one that did a update from core 1 to core 2 my have this slow send to samba with WinXP service pack 2.
I turned the fire wall off on Windows XP too.
It all worked good before service pack 2.
I hope some one can find a fix.
Last edited by Raymond Day; 08-10-2004 at 08:59 PM.
Look for a service called web client and turn it off.
I have 10 samba servers running in a vpn environment and unfortunately xp clients (for now). When web client was running file trasfers were slow. After I stopped that service everything ran faster. My friend has a theory that web client works with windows servers but any other file server, ie samba, would run slow becuase of web client. In other words microsoft could say microsoft servers run faster than any other file server. I don't know if this will help your problem, just a thought.
> PLease read in - line
workgroup = IVESNETWORK
interfaces = 127.0.0.1 eth0
--> remove 127.0.0.1, Better remove nething, unless u are having two network cards.. the defaults are ok. Rest seems to be OK... Tell us more of the Network you are running... if this does not solve.
# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
socket options = TCP_NODELAY
I have a on board 10/100 Ethernet. I had turn off in the BIOS. To test I turned it on and unplugged my Gigabit Ethernet cord. Using samba that same file it says 30 sec. Way faster. Here is the info. of Ethernet connections on this computer:
The 10/100 works fast. The Gigabit one does work very fast using FTP but not Samba.
I guess I have to install some other driver for my Gigabit card. I went to intel download and found a linux driver for it named "inic-snmp-1.8.4.tar.gz" I like it to be a RPM because I don't know good how to install it any other way. But a friend I think can install it for me later when he gets home to day. I hope it will work then. I will post back here if it does.
Last edited by Raymond Day; 08-12-2004 at 03:03 PM.
My friend uninstalled the driver for the Gigabit and installed the "e1000-5.3.19.tar.gz" but same thing it take 142 minutes on a Gigabit LAN to send a 266MB file. But with the 100 Ethernet card the same file only takes 30 sec. I guess Intel has to make a new Linux driver for it. I have Kernel 2.6.7-1.494.2.2 The drive is for Kernel 2.4 that Intel has now.
It's something that this all started when installing server pack 2 on windows XP. I guess any one using a "Intel Corp. 82540EM Gigabit Ethernet Controller (rev 02)" on a Linux box with service pack 2 on windows XP samba will be very slow sending a file to the linux box.
I will just FTP to it till a fix is found. FTP works very fast.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.