LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (http://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Extremely slow lan (http://www.linuxquestions.org/questions/linux-networking-3/extremely-slow-lan-502823/)

nukemaps 11-18-2006 01:46 PM

Extremely slow lan
 
I am trying to get started with using Linux and can't seem to get passed an initial problem with my lan connection. I started with the OpenLX Server distro and experienced extremely slow lan transfers. Downloads from the internet were barely making 1KB/s. Small files (~1mb) took an eternity to download. I moved to Centos but the problems remain. Transfers seem equally as slow between WInxp machine and this Linux PC using Samba. This is usually followed by a Samba I/O error after a few succesful (albeit slow) tries.

If someone knows of a few tools or strategies to isolate the cause(s) to the problem I'm having I would greatly appreciate it.

PC - Shuttle AK48N motherboard, VIA Rhine ethernet 10/100Mb.

Current Distro is CentOS.

Local Area network with WinXP pc's, Linksys router to DSL modem. Also, belkin wireless adapter is plugged into the lan.

Again, I can browse the internet and display just about every site I desire (using Mozilla Firefox) but it is just running slow including downloads.

Thanks...

ilikejam 11-18-2006 02:29 PM

Hi.

Could you post the output from the following three commands:

# ifconfig
# traceroute linuxquestions.org
# ethtool eth0

Dave

nukemaps 11-18-2006 05:36 PM

[root@localhost ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0A:E6:DD:4D:9C
inet addr:192.168.1.102 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20a:e6ff:fedd:4d9c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2830 errors:0 dropped:0 overruns:0 frame:0
TX packets:2392 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3166822 (3.0 MiB) TX bytes:338927 (330.9 KiB)
Interrupt:193 Base address:0xa000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1667 errors:0 dropped:0 overruns:0 frame:0
TX packets:1667 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2217532 (2.1 MiB) TX bytes:2217532 (2.1 MiB)

[root@localhost ~]# traceroute linuxquestions.org
traceroute to linuxquestions.org (64.179.4.146), 30 hops max, 38 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
[root@localhost ~]# ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000001 (1)
Link detected: yes
[root@localhost ~]#

ilikejam 11-18-2006 05:42 PM

That looks fine, except for the traceroute.

What does the output from 'route' look like (and is there any delay between running the command and getting your prompt back)?

nukemaps 11-19-2006 03:41 PM

I am noticing a significant improvement in bandwidth last night and again today. I'm wondering if this is a hardware issue (cabling, router, modem) I noticed this and attempted an 'up2date' on my CentOS install. I am getting > 120kB/sec download speed now and internet is noticably faster.

When I do a 'route' test it comes back within 6-8 seconds.

If this happens again, should I be looking for something to stick out in the 'traceroute' or 'ifconfig' results? Does an unusually high number of RX and TX errors, or rate of increase in these errors indicate problems that would relate to reduced bandwidth?

ilikejam 11-19-2006 05:05 PM

Hmmm.

route should return immediately. Usually when route take so long to return it's because one (or maybe more) of the maneserver's in /etc/resolv.conf isn't answering. Can you check that everything listed as a nameserver responds to ping etc.

Dave


All times are GMT -5. The time now is 10:53 AM.