HELP!!! Random dropped packets and uneven ping on wireless ::SOLVED:: but new problem!!!

Toggle sidebar Toggle sidebar

Amused

Elite Member
Apr 14, 2001
56,382
15,727
146
When pinging my router over both 802.11 a and g I get random dropped packets and uneven pings. Any ideas what may cause this?

Router: D-Link DI-774

Client: IBM mini PCI a/b/g

Latest drivers and firmware.

Signal strength ranges from 80-95%

Is there a setting I don't know about that can effect this?

edit:

OK, I discovered what is causing it. I disabled Windows Wireless Zero Config in services.msc and all my ping problems disappeared.

However, if I turn off WZC so it doesn't load at boot, IBM's Access Connections software takes 5 minutes to load at boot, thus making me wait that long before I get connected. I believe it's looking for WZC and has to time out before it starts without it. Not only that, but IBM's Access Connections software requires WZC to search for wireless networks. So if WZC is disabled, I am only able to connect to networks I have profiled already in the Access Connections software.

So I solved one problem, only to find another.

I hope MS fixes the WZC problem. I believe the high pings were caused by WZC regularly and automatically looking for new networks every minute or so.

I wish I could find software for my IBM wireless miniPCI card that did NOT depend on WZC.
 
A

AFB

Lifer
Jan 10, 2004
10,718
3
0
Can you post you pings with an a time of ~ 2-3min.

Use the command :

ping -t

Hit control-c to stop it and paste the results.
 
S

spidey07

No Lifer
Aug 4, 2000
65,469
5
76
interferance? (sp?)

wireless should have not dropped packets and uneven pings with a good strength/quality.

Try changing channels to (1, 4, 8, 11)
 

Amused

Elite Member
Apr 14, 2001
56,382
15,727
146
it's actually not doing so bad now. Min-0 Max-63 Avg-12

No lost packets. I switched to channel 149 (a)

How do you copy from a command window?
 

Amused

Elite Member
Apr 14, 2001
56,382
15,727
146
OK, look at this: WTF???

Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time=2ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=2ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=3ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=4ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=110ms TTL=127
Reply from 192.168.0.1: bytes=32 time=104ms TTL=127
Reply from 192.168.0.1: bytes=32 time=106ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=105ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=105ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=3ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=104ms TTL=127
Reply from 192.168.0.1: bytes=32 time=113ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=102ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time=103ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=5ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127
Reply from 192.168.0.1: bytes=32 time=1ms TTL=127

Ping statistics for 192.168.0.1:
Packets: Sent = 158, Received = 158, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 113ms, Average = 26ms
Control-C
^C
 
A

AFB

Lifer
Jan 10, 2004
10,718
3
0
You don't have any losses, but thats a nasty ping you have there. Was it always like this or did it just happen and what did you do? (ie update the software)
 

Amused

Elite Member
Apr 14, 2001
56,382
15,727
146
Originally posted by: amdfanboy
You don't have any losses, but thats a nasty ping you have there. Was it always like this or did it just happen and what did you do? (ie update the software)
Click to expand...

Well, I'm dealing with a new card in this machine (a/b/g mini PCI in an IBM R40), and a new router (DI-774).

This is very confusing. I tried playing with some settings in my router last night, and nothing changed. (Though I did succeed in completely losing all wireless activity, and having to reset the router to factory defaults to get it back :|) I think I'll try moving the router around.
 
Z

Zelmo3

Senior member
Dec 24, 2003
772
0
0
Are you using WinXP? If so, try this:
Once your wireless gets a connection, go into your services and stop the Wireless Zero Configuration Service. The connection will stay up, but the OS will stop looking for new access points every minute. Any time you reboot or otherwise drop the connection, turn the service back on long enough to reconnect and then turn it off again.
 

Amused

Elite Member
Apr 14, 2001
56,382
15,727
146
Originally posted by: Zelmo3
Are you using WinXP? If so, try this:
Once your wireless gets a connection, go into your services and stop the Wireless Zero Configuration Service. The connection will stay up, but the OS will stop looking for new access points every minute. Any time you reboot or otherwise drop the connection, turn the service back on long enough to reconnect and then turn it off again.
Click to expand...

It's already off since I'm using IBM's Access Communications program (really nifty, because it allows you to keep location profiles). However, I get the same results using Windows wireless config or IBM's config program.
 
D

d3n

Golden Member
Mar 13, 2004
1,597
0
0
I remember reading an article a while back that some a/g wireless routers had a problem working in mixed mode when multiple clients were trying to access the router at the same time. The competing signals slowed the router down significantly. Sorry, I have no idea where it was except maybe THG in a review done about 6 months ago.

Try setting the router to either A or G mode and try your test again... also make sure no one uses the cordless phone or the microwave
 

Amused

Elite Member
Apr 14, 2001
56,382
15,727
146
Originally posted by: d3n
I remember reading an article a while back that some a/g wireless routers had a problem working in mixed mode when multiple clients were trying to access the router at the same time. The competing signals slowed the router down significantly. Sorry, I have no idea where it was except maybe THG in a review done about 6 months ago.

Try setting the router to either A or G mode and try your test again... also make sure no one uses the cordless phone or the microwave
Click to expand...

I believe that was b/g mode, not a/g. I have the router set to "g only" so b clients cannot connect and slow down the g.

Other than that, I cannot find a way to turn off either radio on the router.
 
Z

zigCorsair

Member
Nov 20, 2001
133
0
0
Actually, I think we've had similar problems with dual speed (b/g) connections (although I'm far from certain that was the cause of it).
 

Amused

Elite Member
Apr 14, 2001
56,382
15,727
146
OK, I discovered what is causing it. I disabled Windows Wireless Zero Config in services.msc and all my ping problems disappeared.

However, if I turn off WZC so it doesn't load at boot, IBM's Access Connections software takes 5 minutes to load at boot, thus making me wait that long before I get connected. I believe it's looking for WZC and has to time out before it starts without it. Not only that, but IBM's Access Connections software requires WZC to search for wireless networks. So if WZC is disabled, I am only able to connect to networks I have profiled already in the Access Connections software.

So I solved one problem, only to find another.

I hope MS fixes the WZC problem. I believe the high pings were caused by WZC regularly and automatically looking for new networks every minute or so.

I wish I could find software for my IBM wireless miniPCI card that did NOT depend on WZC.
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom
sale-70-410-exam    | Exam-200-125-pdf    | we-sale-70-410-exam    | hot-sale-70-410-exam    | Latest-exam-700-603-Dumps    | Dumps-98-363-exams-date    | Certs-200-125-date    | Dumps-300-075-exams-date    | hot-sale-book-C8010-726-book    | Hot-Sale-200-310-Exam    | Exam-Description-200-310-dumps?    | hot-sale-book-200-125-book    | Latest-Updated-300-209-Exam    | Dumps-210-260-exams-date    | Download-200-125-Exam-PDF    | Exam-Description-300-101-dumps    | Certs-300-101-date    | Hot-Sale-300-075-Exam    | Latest-exam-200-125-Dumps    | Exam-Description-200-125-dumps    | Latest-Updated-300-075-Exam    | hot-sale-book-210-260-book    | Dumps-200-901-exams-date    | Certs-200-901-date    | Latest-exam-1Z0-062-Dumps    | Hot-Sale-1Z0-062-Exam    | Certs-CSSLP-date    | 100%-Pass-70-383-Exams    | Latest-JN0-360-real-exam-questions    | 100%-Pass-4A0-100-Real-Exam-Questions    | Dumps-300-135-exams-date    | Passed-200-105-Tech-Exams    | Latest-Updated-200-310-Exam    | Download-300-070-Exam-PDF    | Hot-Sale-JN0-360-Exam    | 100%-Pass-JN0-360-Exams    | 100%-Pass-JN0-360-Real-Exam-Questions    | Dumps-JN0-360-exams-date    | Exam-Description-1Z0-876-dumps    | Latest-exam-1Z0-876-Dumps    | Dumps-HPE0-Y53-exams-date    | 2017-Latest-HPE0-Y53-Exam    | 100%-Pass-HPE0-Y53-Real-Exam-Questions    | Pass-4A0-100-Exam    | Latest-4A0-100-Questions    | Dumps-98-365-exams-date    | 2017-Latest-98-365-Exam    | 100%-Pass-VCS-254-Exams    | 2017-Latest-VCS-273-Exam    | Dumps-200-355-exams-date    | 2017-Latest-300-320-Exam    | Pass-300-101-Exam    | 100%-Pass-300-115-Exams    |
http://www.portvapes.co.uk/    | http://www.portvapes.co.uk/    |