wifi problem

Soldato
Joined
13 Mar 2011
Posts
7,484
Location
Bada Bing
i have a netgear dgn2200 router and my mothers computer has an edimax wireless n pcie adapter

i connect to the network and everything is fine, good signal strength, good connection, etc

but when i go to load a webpage it never loads, when windows try to download updates it can never download

ive rebooted the computer and the router, checked it is getting a valid IP, checked the router has internet access etc etc

i am at my wits end! what is up with this wifi!? :confused::mad::confused:
 
Have you checked your virus checker?

yep, no viruses

Do your other computers connect to the internet on the same wifi?

i have one other computer (this one) connected via ethernet and it is perfectly fine on the internet and has a similar IP


Have you tried pinging a server to see if it connects?

yes, i tried google.co.uk and it timedout
 
Sorry, I should have explained better.

Some virus checkers have agressive firewalls that can interfere badly with internet connections. They're always worth checking. Another thing is Norton, for example, doesn't react well to being uninstalled (there's a special tool to do it properly) and will lock down various functions of your PC if you don't do it the right way. It might be worth (briefly) turning off your virus checker completely to eliminate that as the cause.

Have you tried that computer wirelessly or just wired?

How about trying other browsers?

I'm using avast that I have on all my machines and I always recommend it, I've never had an issue with it

I always avoid Norton, it is worse then no antivirus!

anyway, the computer has been fine fir the past months on the wireless, it is just the past two days

yeah, all browsers, it can't even ping google:confused::confused:
 
Try ping 8.8.8.8

Try doing an nslookup www.google.co.uk

Could well be a DNS problem

these are the results of the ping

C:\Windows\system32>ping -t 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=27ms TTL=48
Reply from 8.8.8.8: bytes=32 time=27ms TTL=49
Request timed out.
Reply from 8.8.8.8: bytes=32 time=26ms TTL=48
Reply from 8.8.8.8: bytes=32 time=26ms TTL=48
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=48
Reply from 8.8.8.8: bytes=32 time=26ms TTL=48
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=73ms TTL=48
Reply from 8.8.8.8: bytes=32 time=27ms TTL=48
Reply from 8.8.8.8: bytes=32 time=66ms TTL=48
Reply from 8.8.8.8: bytes=32 time=112ms TTL=49
Reply from 8.8.8.8: bytes=32 time=25ms TTL=49
Reply from 8.8.8.8: bytes=32 time=27ms TTL=48
Reply from 8.8.8.8: bytes=32 time=26ms TTL=48
Reply from 8.8.8.8: bytes=32 time=25ms TTL=49
Reply from 8.8.8.8: bytes=32 time=28ms TTL=48
Reply from 8.8.8.8: bytes=32 time=27ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=27ms TTL=48
Reply from 8.8.8.8: bytes=32 time=27ms TTL=49
Reply from 8.8.8.8: bytes=32 time=27ms TTL=49
Reply from 8.8.8.8: bytes=32 time=27ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=27ms TTL=48
Reply from 8.8.8.8: bytes=32 time=26ms TTL=48
Reply from 8.8.8.8: bytes=32 time=25ms TTL=48
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=48
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=30ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=25ms TTL=48
Reply from 8.8.8.8: bytes=32 time=26ms TTL=48
Reply from 8.8.8.8: bytes=32 time=87ms TTL=48
Reply from 8.8.8.8: bytes=32 time=26ms TTL=48
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=25ms TTL=48
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=169ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=48
Reply from 8.8.8.8: bytes=32 time=28ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=48
Reply from 8.8.8.8: bytes=32 time=108ms TTL=48
Request timed out.
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=47ms TTL=49
Reply from 8.8.8.8: bytes=32 time=25ms TTL=48
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=48
Reply from 8.8.8.8: bytes=32 time=26ms TTL=48
Reply from 8.8.8.8: bytes=32 time=26ms TTL=48
Reply from 8.8.8.8: bytes=32 time=25ms TTL=48
Reply from 8.8.8.8: bytes=32 time=27ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=49
Reply from 8.8.8.8: bytes=32 time=26ms TTL=48

Ping statistics for 8.8.8.8:
Packets: Sent = 63, Received = 61, Lost = 2 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 169ms, Average = 34ms

and the results of the nslookup

C:\Windows\system32>nslookup www.google.com
Server: UnKnown
Address: 192.168.0.1

Non-authoritative answer:
Name: www.l.google.com
Addresses: 74.125.230.144
74.125.230.148
74.125.230.145
74.125.230.146
74.125.230.147
Aliases: www.google.com

i notice a lot of long ping times and timeouts - is this the problem?
 
Just open command prompt and type netstat

Count the connections it shows, generally over 10 will cause issues and could be signs of virus

i will do, but there is no virus on it, it is a recent install with avast and comodo fully updated - and ive scanned it numerous times etc
 
Certainly is a head scratcher indeed, best thing to do after checking all this with no success would be to have a different laptop and side by side when it starts to go iffy and check that ones status, if both show issues then it's the wifi/ISP but if one is fine and other is borked then it's computer issue (somewhere)

well i have this computer wired up to the same router and network and i never experience any of these issues! :confused::mad::confused:
 
have tried changing the wireless channel?
you said its only happened recently so maybe some in you area got new wireless which is affecting yours?

So it's wireless then for sure, try cycling through the router channels and see if any of them resolve it, could also point to computers wireless

Back when I worked for a ISP tech support I rem something about FireWire driver crippling the wifi, check device manager and make sure there no driver issues there or the 1394 driver is being the culprit

ok, ive changed from channel 6 to 9

there are no 1394 drivers/ports on this board :)
 
Back
Top Bottom