PeteCress 0 Posted December 15, 2014 A couple of HikVision DS-2CD2032-I's. When I ping and/or do a NetScan, they seem to be there one minute and not the next. Also, they should be exposing ports - which NetScan says are not being exposed. Devoid of any real knowledge, the best I can come up with is dirty connections (salt-water environment) and I'm going to drive down there on Wednesday with a ladder, some contact cleaner and a tube of dielectric grease. Until then, can anybody hazard another guess? Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Windows\system32>ping 10.0.0.145 Pinging 10.0.0.145 with 32 bytes of data: Reply from 10.0.0.145: bytes=32 time=4ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Ping statistics for 10.0.0.145: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 4ms, Average = 1ms C:\Windows\system32>ping 140.0.0.146 Pinging 140.0.0.146 with 32 bytes of data: Reply from 202.73.96.125: TTL expired in transit. Reply from 202.73.96.125: TTL expired in transit. Reply from 202.73.96.125: TTL expired in transit. Reply from 202.73.96.125: TTL expired in transit. Ping statistics for 140.0.0.146: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), C:\Windows\system32>ping 10.0.0.146 Pinging 10.0.0.146 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 10.0.0.146: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Windows\system32>ping 10.0.0.145 Pinging 10.0.0.145 with 32 bytes of data: Request timed out. Request timed out. Reply from 10.0.0.145: bytes=32 time=1008ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Ping statistics for 10.0.0.145: Packets: Sent = 4, Received = 2, Lost = 2 (50% loss), Approximate round trip times in milli-seconds: Minimum = 3ms, Maximum = 1008ms, Average = 505ms C:\Windows\system32>date The current date is: Mon 12/15/2014 Enter the new date: (mm-dd-yy) C:\Windows\system32>time The current time is: 16:28:00.93 Enter the new time: C:\Windows\system32>ping 10.0.0.145 Pinging 10.0.0.145 with 32 bytes of data: Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.145: bytes=32 time=4ms TTL=64 Ping statistics for 10.0.0.145: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 4ms, Maximum = 4ms, Average = 4ms C:\Windows\system32>time The current time is: 16:28:20.73 Enter the new time: C:\Windows\system32>ping 10.0.0.146 Pinging 10.0.0.146 with 32 bytes of data: Reply from 10.0.0.146: bytes=32 time=5ms TTL=64 Reply from 10.0.0.146: bytes=32 time=2ms TTL=64 Reply from 10.0.0.146: bytes=32 time=1ms TTL=64 Reply from 10.0.0.146: bytes=32 time=4ms TTL=64 Ping statistics for 10.0.0.146: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 5ms, Average = 3ms C:\Windows\system32>time The current time is: 16:28:42.58 Enter the new time: C:\Windows\system32>ping 10.0.0.146 Pinging 10.0.0.146 with 32 bytes of data: Reply from 10.0.0.146: bytes=32 time=3ms TTL=64 Reply from 10.0.0.146: bytes=32 time=1ms TTL=64 Reply from 10.0.0.146: bytes=32 time=1ms TTL=64 Reply from 10.0.0.146: bytes=32 time=10ms TTL=64 Ping statistics for 10.0.0.146: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 10ms, Average = 3ms C:\Windows\system32>time The current time is: 16:28:59.34 Enter the new time: C:\Windows\system32>ping 10.0.0.145 Pinging 10.0.0.145 with 32 bytes of data: Request timed out. Request timed out. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Ping statistics for 10.0.0.145: Packets: Sent = 4, Received = 2, Lost = 2 (50% loss), C:\Windows\system32> Share this post Link to post Share on other sites
mkkoskin 0 Posted December 16, 2014 Could you give more detail about the network configuration on your windows? Multiple NICs? Multiple IPs? Share this post Link to post Share on other sites
Brenning 0 Posted December 16, 2014 looks to me like they're rebooting based on the ping output. Share this post Link to post Share on other sites
PeteCress 0 Posted December 16, 2014 Could you give more detail about the network configuration on your windows? Multiple NICs? Multiple IPs? Single NIC, single IP: http://tinyurl.com/mkfmvcx Zero problems with the "Parking Lot" cam and various bandwidth/speed tests are OK - so I do not think it's an issue with the radio link. Going down there tomorrow with a ladder, a can of contact cleaner, and a tube of dielectric grease.... so maybe I'll have something useful to say that evening. Share this post Link to post Share on other sites
brian89gp 0 Posted December 16, 2014 Active (802.3af) or passive POE? Are you able to see if the camera has any sort of uptime/log that would help determine if it is a power or a network issue? 802.3af must negotiate POE and cabling issues affecting the power wire pairs can cause bouncing which will appear like the camera is continually rebooting. Wire issues can affect networking too run "ping -t 10.0.0.147" to see if there is a pattern on the ping/no ping timeframes. Share this post Link to post Share on other sites
PeteCress 0 Posted December 16, 2014 run "ping -t 10.0.0.147" to see if there is a pattern on the ping/no ping timeframes. The "Active/Passive" is above my current pay grade... but I will dig in to it later. Hopefully cleaning contacts tomorrow will resolve this. Dunno if "Pattern" is too strong a word, but there is a certain repetitious nature to the Ping responses: C:\Windows\system32>ping -t 10.0.0.145 Pinging 10.0.0.145 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Request timed out. Reply from 10.0.0.145: bytes=32 time=1003ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Reply from 10.0.0.145: bytes=32 time=4ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Request timed out. Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=5ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=6ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Request timed out. Request timed out. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.145: bytes=32 time=2001ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=4ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Request timed out. Request timed out. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.145: bytes=32 time=1004ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Request timed out. Request timed out. Reply from 10.0.0.33: Destination host unreachable. Request timed out. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.145: bytes=32 time=2005ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=5ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=5ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1131ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Request timed out. Request timed out. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.145: bytes=32 time=1993ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=213ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=4ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=2ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Reply from 10.0.0.145: bytes=32 time=1ms TTL=64 Reply from 10.0.0.145: bytes=32 time=3ms TTL=64 Reply from 10.0.0.145: bytes=32 time=201ms TTL=64 Request timed out. Request timed out. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.33: Destination host unreachable. Reply from 10.0.0.145: bytes=32 time=4ms TTL=64 Share this post Link to post Share on other sites
mkkoskin 0 Posted December 17, 2014 From where are you testing these pings from? From PC connected to PoE Switch (dark blue box)? If not, you should test it locally (laptop attached to PoE switch) first to rule out the wireless link. If the ping pattern is still the same, try to check for logs in camera web-settings, see if it restarts constantly (due to not enough power from PoE for example). Share this post Link to post Share on other sites
brian89gp 0 Posted December 17, 2014 run "ping -t 10.0.0.147" to see if there is a pattern on the ping/no ping timeframes. The "Active/Passive" is above my current pay grade... but I will dig in to it later. Hopefully cleaning contacts tomorrow will resolve this. Dunno if "Pattern" is too strong a word, but there is a certain repetitious nature to the Ping responses: Get us the make/model of the switch and/or the make/model of the camera's. Chances are it is active POE (802.3af). From the latency I am guessing you are pinging from the Blue Iris server or some other computer at the server location? Looking at the ping output there are a couple timeouts and then the destination host unreachable messages. The "Destination host unreachable" means that there is no route to the host, either on layer 3 IP or layer 2 ARP. Since you have a bridged network it more then likely is layer 2 ARP. The unresponsive timeframe is roughly the same which seems to be about as long as a camera boot time My supposition. Due to cable length, poor cable, poor connections, or a bad switch, you are having your 802.3af POE power drop in and out causing the camera to reboot. The first couple seconds you get the ICMP timeout since the ARP entry still exists on the switch and after that it flushes and you get the destination host unreachable. Camera boots back up, ARP entry added to the switch, and all is good. Share this post Link to post Share on other sites
PeteCress 0 Posted December 17, 2014 run "ping -t 10.0.0.147" to see if there is a pattern on the ping/no ping timeframes. Thanks for that one!.... the -t is *really* useful. Went down there today, did the -t thing locally to take the radio link out of the picture and they just ticked along.....no problem. OOPS!.... how could a radio link problem be camera-specific??? So I did it again, only with the radio link in the picture.... -t on the cam server PC a half mile away instead of on the shop PC. Oops again... It also worked perfectly, ping-after-ping on both cams. I'm pretty sure my mistake was forgetting to do the shop/server ping comparison before wiggling cables. Bottom line, I cleaned every connection and slathered it with dielectric grease and all seems to be well. In fact, a couple of the RJ-45 plugs were so nasty that I just cut them off and re-terminated. For the sake of people searching for info about use of dielectric grease at later times, I will start a separate thread with that in the subject line. Edit 2014 12-17: After about three hours of running A-OK, three of the cams have reverted to being intermittently unreachable - although the pings look much, much better than they did before all this. Long runs of "Reply from.....with 1-2ms times". And, what's probably informative is that the Replies/timeouts/unreachables seem to be in some sort of synch between all 3 problem cams: I've got three console windows open with a Ping... -T running against each camera and the Replies, Timeouts, and Unreachables are pretty much in parallel. It's as if something in the POE switch or above is injecting something harmful to communication into the system. But what's boggling my mind is that a fourth camera - on the same POE switch - is getting 100% good replies.... viz: http://tinyurl.com/ouqrd95. So much for the "injecting something harmful hypothesis".... Now I'm *really* confused.... I think it's time for Yours Truly to dig into the POE (802.3af) thing and see if maybe the problem cameras (HikVision DS-2CD2032-I's) are one standard and the "Good" camera (TrendNet TV-IP67wP) is the other standard. On one hand, the theory about the cams' rebooting bco faulty connections seems supported by the improvement (but not total cure) following connection cleanup/retermination. OTOH, it would seem to beg the question of why the camera's good/bad responses are so well synchronized.... unless that's pointing to a connection problem further upstream than the camera/POE switch connections.... some common element like the POE switch's connection to the radio... or even the server end's connection it it's radio.... ??? Edit 2014 12-17 19:56: Nope... looks to me like both the problem and "Good" cams are 802.3af. Share this post Link to post Share on other sites
PeteCress 0 Posted December 18, 2014 OTOH, it would seem to beg the question of why the camera's good/bad responses are so well synchronized. I have to retract that statement. After watching pings to all 3 cams in parallel for about 20 minutes, I see that the patterns are similar - with 30-33 Replies interspersed with a few "Timed outs" and "Unreachables".... So the lists align every so often and then slowly precess out of phase depending on 30 or 33 Replies and minor variations in # of Timed Outs and Unreachables.... eventually drifting back into synch or near-synch every so often. viz: http://tinyurl.com/nz8oq3x http://tinyurl.com/l4fsv3x So it looks to me like we are back to the idea of the cams re-booting and the boot sequences being the same in terms of Replies/Timed Outs/Unreachables. Next time I go down, I'm going to blindly swap out the POE switch - without worrying about why the TrendNet is not showing any problems. Share this post Link to post Share on other sites
TheUberOverLord 0 Posted December 18, 2014 1. Make sure the static IP Address is actually being assigned in the cameras configuration using the Router/AP's local IP Address for the Gateway and DNS values in that configuration vs. by any MAC Address games in the Router/AP. 2. Make sure that UPnP is disabled in the cameras configuration. 3. Double/Triple check your static IP Addresses ("Especially those assigned by MAC Address in the Router/AP") and Port Forwarding entries, to make sure there are no conflicts/duplicities. Check any current UPnP entries in the Router/AP's UPnP tables and delete any that are still referencing any cameras. Don Share this post Link to post Share on other sites
brian89gp 0 Posted December 18, 2014 So, the Hikvision camera's have issues but the Trendnet does not? Are the Hikvision camera's on longer cable lengths then the Trendnet? What brand/model is the switch? And are you able to confirm that it drops pings locally? Or only when going over the wireless? Turn on logging on the Nanostations and attach the logs with the time of when the problem happens. Share this post Link to post Share on other sites
PeteCress 0 Posted December 21, 2014 So, the Hikvision camera's have issues but the Trendnet does not? Yes.Are the Hikvision camera's on longer cable lengths then the Trendnet?Yes and no. Two are longer, the other's is about the same as the TrendNet's. But, to cut to the chase, when I connect the switch directly to my laptop, no problems. The ping Replies just keep rolling down the window - as opposed to http://tinyurl.com/l4fsv3x (the one on the right being the TrendNet). What brand/model is the switch?TrendNet (not tb confused w/cam of same name) Model TPE-S44 (4 POE ports, 4 regular ports). I swapped it out for a more recent model whose power supply is 1.5 amps instead of the TPE-S44's .8 amps thinking I had struck gold when I noticed the diff in power.... but no change. And are you able to confirm that it drops pings locally? Or only when going over the wireless?I am now pretty sure that it's only over the wireless because of the direct-connect-to-laptop described above. But there's a zinger: when I got down there all 3 cams were running A-OK. This seems coincident with my having somehow provoked the Comcast cable modem into putting the camera server on a "Parental Control | Managed Devices" list as a blocked device - which took it offline WAN-wise, but left it working on the LAN. Again, I thought I had struck gold..... but after flipping that setting back-and-forth a few times, I have been unable to replicate the situation. Turn on logging on the Nanostations and attach the logs with the time of when the problem happens.All I see on the Nano setup is Services | System Log | Enable, but when I set Enable = True, all I get by clicking Main | Log are these 3 very old entries: System Log May 28 12:55:15 system: Start May 28 12:55:16 FileSystem: Start check... May 28 12:55:34 FileSystem: End check. I will let it cook for a few hours - or even overnight - and post anything that turns up. an Edit (3 hours later): Same 3 log entries. I am guessing there is another logging facility that I have not found yet. Share this post Link to post Share on other sites
PeteCress 0 Posted December 31, 2014 It was the radio link (Ubiquiti Nanostation Loco M5's). Fooled around changing bandwidth from 30 back to 40, raised/lowered the signal strengths... managed to lose the connection totally a couple of times... Finally came back to original settings and re-booted the AP radio. All cams now online. Lessons Learned: Radio link problems *can* be camera-specific. I have no clue why, but that seems to be the case.. One of the first things to do in a case like this is to re-boot the radio links. Kind of like troubleshooting a Windows PC issue: when in doubt, re-boot. Share this post Link to post Share on other sites
mkkoskin 0 Posted January 2, 2015 It was the radio link (Ubiquiti Nanostation Loco M5's). Fooled around changing bandwidth from 30 back to 40, raised/lowered the signal strengths... managed to lose the connection totally a couple of times... Finally came back to original settings and re-booted the AP radio. All cams now online. Lessons Learned: Radio link problems *can* be camera-specific. I have no clue why, but that seems to be the case.. One of the first things to do in a case like this is to re-boot the radio links. Kind of like troubleshooting a Windows PC issue: when in doubt, re-boot. Thanks for posting your results and how you fixed it. I've always thought all sorts of wireless stuff (except phones i guess) are way too unreliable to be used when something actually needs to work (security for example), sadly it's not always possible to go wired... Share this post Link to post Share on other sites
