Overclock.net › Forums › Software, Programming and Coding › Networking & Security › Nonnormal ( high ) ping times
New Posts  All Forums:Forum Nav:

Nonnormal ( high ) ping times

post #1 of 8
Thread Starter 
Hello

I seem to have a problem pinging my router. I have between =1ms and =10ms ping response which for a router is not common.

We are about 10 - 15 equipment connected in a single office. We have 2 wireless networks (one on WPA another on WPA2, they can communicate with each other). The equipment is

ZyXEL ZyWall USG-50 (This is the router mentioned giving high ping times)
DLink DGS 1016D (A switch)
DLink DGS 1100-24 (A smart switch giving me even HIGHER ping times: 4ms, 4ms, 4ms, 5ms...Ive even seen this in the 20ms!)
A strictly eletrical rack that is a switch but has no logic. No model number.

I have no problems pinging one PC to another.

This high ping to the router (and smart switch) happens on all PCs. This also discards it being the cable.

Ive tried directly plugging one PC into the router with nothing else plugged in and pinging it. Same results.
Ive tried directly plugging one PC into the smart switch and pinging it. Same results.

What could be the problem? What further tests can I do?
PC
(7 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E6400 Asus P5B Deluxe Geforce GTX 650 Ti 4GB 
OSMonitorAudio
Windows 7 SP1 Ultimate U2312HM Audigy 2 ZS 
  hide details  
Reply
PC
(7 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E6400 Asus P5B Deluxe Geforce GTX 650 Ti 4GB 
OSMonitorAudio
Windows 7 SP1 Ultimate U2312HM Audigy 2 ZS 
  hide details  
Reply
post #2 of 8
That's common for wireless clients, although it sounds like you're getting this from wired as well.

If you do a traceroute do you exhibit the same behavior through multiple hops? I'm mainly wondering if the device is prioritizing traffic itself and queuing/delaying the need to respond to ICMP since it's a more frivolous function, so it'd be more of a delay in replying but not a delay in forwarding traffic. You can use something like mtr (mytraceroute) in Linux to get a good view on how all hops in a certain data path are responding with pretty rapid updates. The switch likely won't show up since it doesn't have a layer 3 SVI, but you can see the times to the router and beyond if they correlate appropriately.

On the other hand this is usually why you go with higher end equipment for a business. In my home/lab environment, from a DD-WRT router > 2960G w/ L3 route > ASA 5505 > 1231G Wireless AP has echo-reply times in the sub 1 ms range.
Waiting on X399
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II B57 @ X4 3.9 Gigabyte 790FXTA-UD5 Sapphire Radeon 290 8 GB G.Skill 2133 
Hard DriveCoolingOSKeyboard
250 GB 840 EVO Noctua NH-D14 Windows 10 Logitech K350 
PowerCaseMouseMouse Pad
Seasonic x750 Corsair 600T Logitech G100s Razer Goliathus Speed 
Audio
Plantronics Gamecom 788 
  hide details  
Reply
Waiting on X399
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II B57 @ X4 3.9 Gigabyte 790FXTA-UD5 Sapphire Radeon 290 8 GB G.Skill 2133 
Hard DriveCoolingOSKeyboard
250 GB 840 EVO Noctua NH-D14 Windows 10 Logitech K350 
PowerCaseMouseMouse Pad
Seasonic x750 Corsair 600T Logitech G100s Razer Goliathus Speed 
Audio
Plantronics Gamecom 788 
  hide details  
Reply
post #3 of 8
Thread Starter 
ALL of this is wired. Im not testing to/from any wireless client/station.

Quote:
Originally Posted by beers View Post

That's common for wireless clients, although it sounds like you're getting this from wired as well.

If you do a traceroute do you exhibit the same behavior through multiple hops? I'm mainly wondering if the device is prioritizing traffic itself and queuing/delaying the need to respond to ICMP since it's a more frivolous function, so it'd be more of a delay in replying but not a delay in forwarding traffic. You can use something like mtr (mytraceroute) in Linux to get a good view on how all hops in a certain data path are responding with pretty rapid updates. The switch likely won't show up since it doesn't have a layer 3 SVI, but you can see the times to the router and beyond if they correlate appropriately.

On the other hand this is usually why you go with higher end equipment for a business. In my home/lab environment, from a DD-WRT router > 2960G w/ L3 route > ASA 5505 > 1231G Wireless AP has echo-reply times in the sub 1 ms range.

tracert shows me nothing.

Results (switch):

C:\Users\Me>tracert 192.168.100.24

Traza a 192.168.100.24 sobre caminos de 30 saltos como máximo.

1 4 ms 5 ms 4 ms 192.168.100.24

Traza completa.

C:\Users\Me>ping 192.168.100.24

Haciendo ping a 192.168.100.24 con 32 bytes de datos:
Respuesta desde 192.168.100.24: bytes=32 tiempo=4ms TTL=64
Respuesta desde 192.168.100.24: bytes=32 tiempo=4ms TTL=64
Respuesta desde 192.168.100.24: bytes=32 tiempo=4ms TTL=64
Respuesta desde 192.168.100.24: bytes=32 tiempo=4ms TTL=64

Estadísticas de ping para 192.168.100.24:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 4ms, Máximo = 4ms, Media = 4ms


Results (router):

C:\Users\Me>tracert 192.168.100.100

Traza a 192.168.100.100 sobre caminos de 30 saltos como máximo.

1 2 ms 1 ms 1 ms 192.168.100.100

Traza completa.

C:\Users\Me>ping 192.168.100.100

Haciendo ping a 192.168.100.100 con 32 bytes de datos:
Respuesta desde 192.168.100.100: bytes=32 tiempo=2ms TTL=64
Respuesta desde 192.168.100.100: bytes=32 tiempo=1ms TTL=64
Respuesta desde 192.168.100.100: bytes=32 tiempo=2ms TTL=64
Respuesta desde 192.168.100.100: bytes=32 tiempo=1ms TTL=64

Estadísticas de ping para 192.168.100.100:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 1ms, Máximo = 2ms, Media = 1ms


Results from one PC to another:

C:\Users\Me>tracert 192.168.100.199

Traza a 192.168.100.199 sobre un máximo de 30 saltos:

1 <1 ms <1 ms <1 ms 192.168.100.199

Traza completa.

C:\Users\Me>ping 192.168.100.199

Haciendo ping a 192.168.100.199 con 32 bytes de datos:
Respuesta desde 192.168.100.199: bytes=32 tiempo<1m TTL=64
Respuesta desde 192.168.100.199: bytes=32 tiempo<1m TTL=64
Respuesta desde 192.168.100.199: bytes=32 tiempo<1m TTL=64
Respuesta desde 192.168.100.199: bytes=32 tiempo<1m TTL=64

Estadísticas de ping para 192.168.100.199:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 0ms, Máximo = 0ms, Media = 0ms




Shows nothing intresting and/or that calls my attention.

Further opinions?
PC
(7 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E6400 Asus P5B Deluxe Geforce GTX 650 Ti 4GB 
OSMonitorAudio
Windows 7 SP1 Ultimate U2312HM Audigy 2 ZS 
  hide details  
Reply
PC
(7 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E6400 Asus P5B Deluxe Geforce GTX 650 Ti 4GB 
OSMonitorAudio
Windows 7 SP1 Ultimate U2312HM Audigy 2 ZS 
  hide details  
Reply
post #4 of 8
Thread Starter 
Any ideas on this?
PC
(7 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E6400 Asus P5B Deluxe Geforce GTX 650 Ti 4GB 
OSMonitorAudio
Windows 7 SP1 Ultimate U2312HM Audigy 2 ZS 
  hide details  
Reply
PC
(7 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E6400 Asus P5B Deluxe Geforce GTX 650 Ti 4GB 
OSMonitorAudio
Windows 7 SP1 Ultimate U2312HM Audigy 2 ZS 
  hide details  
Reply
post #5 of 8
Thread Starter 
Also I have a question:

Is this device a switch, a hub, or what is it?

All it is are network ports with networking wiring behind them. Nothing else.




Could this be a bottleneck in the network?
PC
(7 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E6400 Asus P5B Deluxe Geforce GTX 650 Ti 4GB 
OSMonitorAudio
Windows 7 SP1 Ultimate U2312HM Audigy 2 ZS 
  hide details  
Reply
PC
(7 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E6400 Asus P5B Deluxe Geforce GTX 650 Ti 4GB 
OSMonitorAudio
Windows 7 SP1 Ultimate U2312HM Audigy 2 ZS 
  hide details  
Reply
post #6 of 8
Thread Starter 
We have one like this and since Im not 100% sure what it is, I wanted to confirm.
PC
(7 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E6400 Asus P5B Deluxe Geforce GTX 650 Ti 4GB 
OSMonitorAudio
Windows 7 SP1 Ultimate U2312HM Audigy 2 ZS 
  hide details  
Reply
PC
(7 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E6400 Asus P5B Deluxe Geforce GTX 650 Ti 4GB 
OSMonitorAudio
Windows 7 SP1 Ultimate U2312HM Audigy 2 ZS 
  hide details  
Reply
post #7 of 8
Thread Starter 
Anyone have any ideas or maybe questions they would like to ask so I can post more information?

Thank you
PC
(7 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E6400 Asus P5B Deluxe Geforce GTX 650 Ti 4GB 
OSMonitorAudio
Windows 7 SP1 Ultimate U2312HM Audigy 2 ZS 
  hide details  
Reply
PC
(7 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E6400 Asus P5B Deluxe Geforce GTX 650 Ti 4GB 
OSMonitorAudio
Windows 7 SP1 Ultimate U2312HM Audigy 2 ZS 
  hide details  
Reply
post #8 of 8
Thread Starter 
Using Wireshark and a switch that has port mirroring, I see several PCs giving out SPOOLSS portocol messsages about ClosePrinter and OpenPrinterEx and related......

Any idea on this?
PC
(7 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E6400 Asus P5B Deluxe Geforce GTX 650 Ti 4GB 
OSMonitorAudio
Windows 7 SP1 Ultimate U2312HM Audigy 2 ZS 
  hide details  
Reply
PC
(7 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E6400 Asus P5B Deluxe Geforce GTX 650 Ti 4GB 
OSMonitorAudio
Windows 7 SP1 Ultimate U2312HM Audigy 2 ZS 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Networking & Security
Overclock.net › Forums › Software, Programming and Coding › Networking & Security › Nonnormal ( high ) ping times