25-50% packet loss

#1 hackman2007

Member

Group: Members
Posts: 26
Joined: 28-June 09

Posted 17 October 2009 - 11:39 AM

On one of my computers, I'm having a very frustrating packet loss problem. It only happens on one computer and seems to happen to all sites.

I turned off the wireless security and reset the router and that seemed to work for a bit because the packet loss stopped. I turned the wireless security back on and the performance was still great. Today, I'm back to losing packets again. It even happens when I ping the router.

Anyone have any clues as to how to solve this issue? Moving away from wireless on this computer is not possible.

Router
Linksys WRT54G with DD-WRT

Computer
It is using a Linksys WUSB54GSC. It does have 64 bit drivers.
Operating system is Windows 7 RTM 64 bit

This post has been edited by hackman2007: 17 October 2009 - 11:42 AM

#2 CaveDweller2

Forum Addict

Group: Members
Posts: 1,309
Joined: 02-July 09
Gender:Male

Posted 18 October 2009 - 12:04 AM

You are saying you have packet loss when you ping some websites and/or your router? Can you post what you are seeing?

How long did you disable the wireless security? Without resetting the router if you turn off the security do you still have packet loss?

Hope this helps Posted Image

OlllllllO

#3 hackman2007

Member

Group: Members
Posts: 26
Joined: 28-June 09

Posted 23 October 2009 - 09:19 PM

Updating this thread.

There isn't really anything to show about the ping results. I send 4 packets using the ping command and about half of them just say "Request Timed Out", even when I ping the router.

I had the wireless security off for about a week or so, then turned it back on as a test.

Right now, I've just about given up on the security. I configured the router to not show the SSID, I put a MAC filter on so only the wireless computer could access, disabled remote administration, blocked ICMP packets, and limited the amount of DHCP users to 4 (4 computers).

I think it is some sort of authentication issue. Unfortunately, I don't have the time to test out exactly what the problem is, so this will have to do, for now.