Hi all,

I'm a in linux and want to move from Windows. I've recently installed fedora core 6 and found that the internet connection speed is very low. When I'm using Windows XP there is no problem and is quite fast, but on fedora is (desperately) slow. I'm using a Modem ADSL DUAL (Ethernet-USB-DSL600EU) and an Encore Wireless-G Router ENHWI-G in order to have internet connection in two pcs. One of the pcs seems right but not in the one I'm using. When I do a traceroute I get the following message:

[XXXXXX@localhost ~]$ traceroute XXX.XXXXXX.XXX
traceroute to XXX.XXXXXX.XXX (64.233.161.103), 30 hops max, 40 byte packets
Unable to look up 192.168.1.1: Temporary failure in name resolution
1 192.168.1.1 0.380 ms 0.377 ms 0.387 ms
2 login.modem (10.0.0.2) 2.399 ms 2.391 ms 1.785 ms
Unable to look up 200.3.60.10: Temporary failure in name resolution
3 200.3.60.10 51.339 ms 60.990 ms 69.942 ms
4 host10.200 (200.3.81.10) 208.355 ms 212.804 ms 218.555 ms
5 core1 (198.32.124.133) 223.629 ms 231.377 ms 237.301 ms
Unable to look up 72.14.238.57: Temporary failure in name resolution
6 72.14.238.57 256.877 ms 262.973 ms 269.848 ms
Unable to look up 72.14.238.137: Temporary failure in name resolution
7 72.14.238.137 282.856 ms 290.614 ms 295.525 ms
Unable to look up 64.233.175.169: Temporary failure in name resolution
Unable to look up 64.233.175.171: Temporary failure in name resolution
Unable to look up 64.233.175.169: Temporary failure in name resolution
8 64.233.175.169 189.383 ms 64.233.175.171 182.458 ms 64.233.175.169 181.021 ms
Unable to look up 216.239.49.214: Temporary failure in name resolution
Unable to look up 216.239.48.190: Temporary failure in name resolution
Unable to look up 216.239.49.214: Temporary failure in name resolution
9 216.239.49.214 185.729 ms 216.239.48.190 184.299 ms 216.239.49.214 183.784 ms
10 XXX.XXXXXX.XXX (64.233.161.103) 184.518 ms 204.353 ms 207.670 ms
[XXXXXXX@localhost ~]$



I get the connection at the (very) end but here you can see that I get a lot of: Unable to look up XXX.XXX.XX.XXX: Temporary failure in name resolution... Can anyone help me???? Please!

Thanks!!!

Is your internet interface up? You can check that with ifconfig. Also, does it have an IP address and a default gateway (a "default" line in the output of "route"? You might also want to take a look at /etc/resolv.conf.

You can see if it's your computer that's causing the problem by pinging your router and seeing if it fails, if it's your router by pinging your ISP, or your ISP by pinging Google (Google is never down).

Thanks for your answer burninGpi but I must admit that i didn't understand everything you told me. If I ping google I get:

[xxxxx@xxxxxxx ~]$ ping xxx.xxxxxx.xxx
PING xxx.xxxxxx.xxx (64.233.161.147) 56(84) bytes of data.
64 bytes from xxx.xxxxxx.xxx (64.233.161.147): icmp_seq=1 ttl=245 time=178 ms
64 bytes from xxx.xxxxxx.xxx (64.233.161.147): icmp_seq=2 ttl=245 time=187 ms
64 bytes from xxx.xxxxxx.xxx (64.233.161.147): icmp_seq=3 ttl=245 time=184 ms
64 bytes from xxx.xxxxxx.xxx (64.233.161.147): icmp_seq=4 ttl=245 time=210 ms
64 bytes from xxx.xxxxxx.xxx (64.233.161.147): icmp_seq=5 ttl=245 time=175 ms
64 bytes from xxx.xxxxxx.xxx (64.233.161.147): icmp_seq=6 ttl=245 time=188 ms
64 bytes from xxx.xxxxxx.xxx (64.233.161.147): icmp_seq=7 ttl=245 time=186 ms
64 bytes from xxx.xxxxxx.xxx (64.233.161.147): icmp_seq=8 ttl=245 time=175 ms
64 bytes from xxx.xxxxxx.xxx (64.233.161.147): icmp_seq=9 ttl=245 time=190 ms

--- xxx.xxxxxx.xxx ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 9064ms
rtt min/avg/max/mdev = 175.669/186.355/210.711/10.060 ms

When I do ifcongig I get

[xxxxxx@xxxxxxxxx ~]$ ifconfig
bash: ifconfig: command not found

and the content of the file resolv.conf is

[xxxxx@xxxxxxxx ~]$ more /etc/resolv.conf
; generated by /sbin/dhclient-script
nameserver xxx.xxx.x.x

Can you help me with this please!!???? I'm pretty confused... or mention some tutorial or post (for newbies)!!!
Thanks!!!!!!!!!!

Install the package that contains ifconfig. You can use route -n to show the routing table, the route described as 0.0.0.0 is the one for the default gateway. It should contain an IP address assigned by your ISP. The resolv.conf seems to be fine, it was configured by the DHCP client.

why have you gone to the trouble of x'ing out google.com ? it's *your* ip address you should keep secret, not googles!

and xeneize78, please be careful what advice you give... ifconfig isn't an optional thing, it *WILL* already be installed, as will the route command. he'll just be having path issues meaning he can't access them without being su'd to root properly.

i'm aware that this thread is a little old now, but there's no real reason to think there is a network problem. traceroutes aren't really a great way to show a problem. what's often very useful are little tools like mtr, which is seemingly found on most systems, which will ping a ping (actually traceroute it...) a few thousand times and give you loss percentages and such as it goes, so you can better see a patttern over a period of time.

I had root access to that machine and both ifconfig and route commands were unavailable. So I guess the net-tools package are not installed.

even i am facing the same slow network connectivity in FC6 while the same runs pretty fast on windows !! i feel its the name resolution which is taking time. I concluded the same as when i tried accessing the website directly through the ip address the pages came up pretty fast.

can anyone provide me with a solution or a good reason why is this happening ?

xeneize78, i'd be fairly confident that there was another reason...

Morpheus, please don't try to hijack threads, start your own if you have your own question to ask.

I really don't mean to hijack here but I seem to be having the exact same problem in Fedora Core 6 as astrosebas and Morpheus do: slow internet with rather "spiky" behaviour in network usage. I actually was able to run ifconfig on this machine and here's the output:

eth0 Link encap:Ethernet HWaddr 00:E0:4C:E7:6A:96
inet addr:82.139.82.44 Bcast:82.139.82.255 Mask:255.255.255.0
inet6 addr: fe80::2e0:4cff:fee7:6a96/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:46295 errors:8146 dropped:0 overruns:0 frame:0
TX packets:28773 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:36016500 (34.3 MiB) TX bytes:3128610 (2.9 MiB)
Interrupt:185 Base address:0xc000

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:1471 errors:0 dropped:0 overruns:0 frame:0
TX packets:1471 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2262366 (2.1 MiB) TX bytes:2262366 (2.1 MiB)

Might this be of any help to someone in solving "our" problem? Thanks, Ton