Hi folks, Knoppix LiveCD 4.0.2 1.5 Mb ADSL broadband via modem I have been spendig couple days to find out the cause of slow web browsing on 1.5Mb broadband connection without result. It took prolonged time to connect a website. The strange thing was web browsing via 56K modem connection worked even better, no need to wait. I changed the network card. ISP even sent his technical staff for site visit checking the cable without any discovery. On the same PC I have other 2 HDs mounted on mobile rack, running WinXP and FC3 respectively. Comparing all of them, web browsing on WinXP worked fastest, not necessary waiting for connecting after pressing <RETURN> and FC3 also not bad, no need waiting for prolonged time to connect. Knoppix LiveCD was the slowest on connecting. I have to sit and wait. All connection were tested with Firefox as browser. I tested Knoppix LiveCD on another PC. The same result was found. 56K modem connection performed better than 1.5Mb broadband connection. Kindly advise. TIA B.R. satimis

check the cacheing settings on the browser the broadband setting may have more virtual memory allocated and thus slow down your system or vise versa it may be aditional cache is actually helping though I would think the more virtual resources you use slower your going to go especially useing knoppix with only 512 mb (dont get me wroing it runs great but it still is virtual and no comparison to a native install)

Hi voldemort, Tks for your advice. The problem was caused by the dead primary nameserver 202.123.77.196. After reverting the order of nameservers on /etc/resolv.conf web browsing on Knoppix LiveCD is now faster than before. Broadband connection; 1.5Mb connected via a ADSL modem dynamic IP I'm running a workstation. What I can't resolve is on Win PC Internet browsing was not affected disregarding the dead primary nameserver. I made following text on a Win PC C:\WINDOWS>ping 202.123.77.196 Pinging 202.123.77.196 with 32 bytes of data: Reply from 202.123.95.81: TTL expired in transit. Reply from 202.123.95.81: TTL expired in transit. Reply from 202.123.95.81: TTL expired in transit. Reply from 202.123.95.81: TTL expired in transit. Ping statistics for 202.123.77.196: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\WINDOWS>ping 202.123.77.213 Pinging 202.123.77.213 with 32 bytes of data: Reply from 202.123.77.213: bytes=32 time=28ms TTL=252 Reply from 202.123.77.213: bytes=32 time=13ms TTL=252 Reply from 202.123.77.213: bytes=32 time=14ms TTL=252 Reply from 202.123.77.213: bytes=32 time=28ms TTL=252 Ping statistics for 202.123.77.213: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 28ms, Average = 20ms The statistics on the dead nameserver was also % loss. But the response was from another nameserver. On complaining to my ISP, he said the primary nameservers was checked active there. Could you please help me to understand this happening. TIA BR satimis