Network issues - Ping test?

gordie

n3wb
Apr 18, 2017
4
0
I'm having constant networking issues with my HIKVision camera (DS-2CD2532F-IWS), I thought it was due to me using wifi at first but i've since changed to a wired connection and the issues are still there.

If I reduce the video output to 720p 10 FPS it seems to be better but i'm just trying to rule out other network factors that could be involved.

Could someone with a camera on their network try pinging their camera 50 times from DOS and post the results?

ping <ipaddress> -n 50 - from the command line.

I just wanted to see if there is some kind of flood prevention in place on the camera or if I have network issues with the below results from my camera:

Pinging 192.168.1.64 with 32 bytes of data:
Request timed out.
Reply from 192.168.1.64: bytes=32 time=4ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Request timed out.
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.64: bytes=32 time=5ms TTL=64
Reply from 192.168.1.64: bytes=32 time=4ms TTL=64
Reply from 192.168.1.64: bytes=32 time=4ms TTL=64
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Request timed out.
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Request timed out.
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Request timed out.
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.1.64: bytes=32 time=4ms TTL=64
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Request timed out.
Reply from 192.168.1.64: bytes=32 time=4ms TTL=64
Reply from 192.168.1.64: bytes=32 time=4ms TTL=64
Request timed out.

Ping statistics for 192.168.1.64:
Packets: Sent = 50, Received = 29, Lost = 21 (42% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 5ms, Average = 3ms

These results seem replicated in SADP as the camera appears and disappears with every refresh.

Any thoughts on possible culprit?
 
For these sorts of network issues you really have to go back to basics instead of looking for a bigger problem...

Take camera from where it is to a test bench and ping direct from a PC to camera.... No dropouts camera is fine and the problem is with cabling / switch. Dropouts from the test environment then you are looking at camera, camera rj45 connector (dirt or corroded). Try a factory reset and try again.

If it's your cabling / switch then diagnose appropriately (new cable / test on another port etc)