Search results

Ah. Gotcha. It's for those people that don't brick the camera. :D

@whoslooking - So what was that mtdx talk on another thread about? I was reading that thread and didn't get a clear picture if it's possibly the same issue.

Well that's made my morning.

@whoslooking - I also tried that 4line firmware. No luck and by the way. I'm a idiot. I found the camera boxes and it appears the broken one was made on 06/2015 and 5.3.0 150513. Yet it was loaded with 5.2.5 141201.

Here are my findings. I took a laptop, switch, broken camera and hooked them all up directly. This is by passing my normal poe switch. I took a 12v power supply and powered the camera that way. I addressed the laptop as 192.0.0.128/8 (255.0.0.0). Then ran wireshark and the tftp server. I found...

I went ahead and order the following. http://www.ebay.com/itm/111593270026 http://www.ebay.com/itm/180953299346 http://www.ebay.com/itm/201429406150 Hopefully everything comes sometime mid next week. But overall thanks for the support guys. It looks like the bootloader maybe okay, so it...

I setup a port mirror on the switch last night and didn't see much coming out of the camera. So I'm going to bring a ethernet tap home from work and see if the issue persists. I'm sure that the bootloader is corrupt, just based on how it's acting. Anyone know a place selling a serial cable for...

OK. I can do that after work today.

Same thing.

OK. BTW, no go with that firmware. I don't even see a attempt for any frames to 192.0.0.128. 192 243.579199 192.0.0.128 -> 192.0.0.64 ICMP 74 Echo (ping) request id=0x0001, seq=1126/26116, ttl=128 193 248.579399 192.0.0.128 -> 192.0.0.64 ICMP 74 Echo (ping) request id=0x0001...

I was going to say that sucks. OK. I'll give that a spin. BTW, looking at my switches FDB. I noticed the switch learned two mac address. Not sure if anyone finds that interesting.

@whoslooking - So what you're saying.. is that we have to wait for the successor firmware of 5.30 to fix this?

Yes. I have a POE+ switch. I just disable and enable the poe on the port that the camera is plugged in. - - - Updated - - - 5.25.

@alastairstevenson - I'll try this remotely from work today. I'm wondering if my switch is doing something crazy. Worst case I'm going to bring the Ethernet tap we have at work and watch the mirror port. @whoslooking - I have other cameras (white box) that took the 5.3.0 upgrade without...

@whoslooking - I'll give it another try. It's just weird that it will boot up in its redboot like state. Then go away for about 5 minutes before appearing on SADP as 192.168.1.64. Running a nmap scan doesn't show much of any port listening. Just like others have expressed.

@whoslooking - Then I think this thing is fudged. @alastairstevenson - I turned off the firewall and disabled the windows firewall service. No difference. It just replies to 3 ICMP requests and goes dead.

Okay. I've been thinking and well trying a bunch of different things. Does it matter the distance of the camera? Right now it's 22-30 feet away. The other camera I was able to recover easy because it was only on a 7 foot cable to the switch. Maybe this has anything to do with it?

Already did that. Hooked up a laptop to a switch. Turned off the wifi. Set the ethernet interface to 192.0.0.128/24. Ran the tftp server from hikvision. Made sure the digicap.dav file exist in the same folder as the tftpserver executable. Make sure the firewall was turned off. Rebooted the...

Already tried that and it doesn't work. In certain case I had to configure the laptop as 192.0.0.128/8. A /24 wouldn't work for whatever reason. Then again I really didn't dig into the issue. I'll try again today at work or after. It would be great if I can get a list of things to try...

2132F-IS. The sticker says 5.2.5. Which it was loaded with. I read all the threads. So I'm aware about the min-system state. I just need help figuring out how to recover. Someone was talking about the camera trying to reach 192.168.1.1 but I didn't find that true. At least while half falling...

I'm stuck in the same place. I see my camera in SADP with the 4.0.8 firmware. I tired the TFTP recovery with POE and 12V DC. I am able to see the device respond to pings on 192.0.0.64 but only 2-3 times. Then it appears as 192.168.1.64. No telnet, ssh, or http.

My own fault. Just plain jane electrical tape. Yeah I know about the hole. I was just trying to get these up quick and not have a box on the or near the chimney.

!fenderman - Cool. I guess I need a junction box now. These two camera's are mounted on the brick chimney. Both have suffered the same result. I'm now prompted to check the others. They are under the soffit but still worth the check.

fenderman - Thanks! Looks like the 8th pin is broken (keeps falling down). Plus it looks like either 6,7, or 8 had a arc. I get I have to splice a CAT5/6 cable into one of these water proof pass-thru's...

Hello Everyone, I recently had a bunch of rain get into my POE ethernet connectors for my DS-2CD2132-I camera's. I was able to power the camera up with a 12volt power supply. However the ethernet seems to be dead. Has anyone here seen a store online that sells parts for these camera's? I'm...

Sorry. I'm was talking about ivms4500. It's not in the app store for the firetv. Plus even if it was you still would need to have rotate functionally.

I'll have to take a look. I saw those applications but felt that Hikvision should port over the ezviz application to the firetv.

I have six DS-2CD2132-I's managed by the ASUSTOR NAS Surveillance Center. Along with that I have each camera setup with ezviz. I have the same quest on viewing all feeds on the same screen. Using the Amazon FireTV doesn't work so well in practice. You have to side load APK's and then your left...

It would be nice to have one thread with just firmware.