I did some serious Googling about this, but I haven't found a solution that works. I work in IT, but networking is my weakest
I'm getting very slow DNS lookups (60+ seconds with lots of page timeouts)in Firefox and Chromium on my Kubuntu laptop. Windows
clients (xp and 7) work fine.
I just replaced a Vonage D-Link wireless phone modem combo that died with a Netgear N300 (WNR2000, more specifically WNR2000v3)
and a Vonage wired phone modem.
The Netgear arrived before the Vonage box, so I immediately hooked it up. The Vonage box has since arrived and is now connected between the cable modem (Comcast) and the wireless router. This did nothing to change the problem.
The Netgear automatically checks for firmware updates, so no love there. I changed it from the default settings to enable N mode with WPA2 (AES), made all of the IP addresses for the clients static, changed the DNS servers to OpenDNS (I also tried Google and Comcast DNSes) and changed the admin password ;)
Restoring to factory settings didn't fix the problem, nor did switching to G-only mode.
I'm using Kubuntu Natty 11.04 AMD64, fully updated. My laptop is an Acer Aspire 5741G-6883 with a Broadcom wireless N adapter:
On my machine, I disabled specifying my preferred DNS servers, since I can now specify them at the router. Changing that back didn't help.Code:steve@bender3:~$ lspci -nn | grep "802.11" 03:00.0 Network controller : Broadcom Corporation BCM43225 802.11b/g/n [14e4:4357] (rev 01)
I disabled IPv6 on my machine and in the two browsers. Nothing.
I tried disabling the Broadcom STA driver in favor of the one in the kernel. I also tried using two of the open-source Broadcom drivers (my memory gets fuzzy here, I can't remember the names) with no success.
I got a good deal at Newegg on the router, but I'm about ready to send it back. Before I go even more days without wireless (shudder), does anyone have any ideas about how to fix this? I'd really appreciate it. Thanks.
To future visitors looking for a solution:
I booted my machine with an older kernel and the problem went away. When I rebooted with the now-current kernel, the problem was still gone, even after several more reboots. I have no idea why this worked or if it will work for you.