mkkoskin

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...

I was just about to link GV-IP LPR 5R to this thread, it does have motor zoom (only 3~9mm, 3x optical) over ONVIF (new firmware required), and we've been testing one to replace old analog lpr cams we've used until now. Image is clear, IR reacts fast, camera works well with any resolution (mainly tested the full 1280x1024). We do not have any red lettered plates to test with but it should not matter as long as it is not reflective but has a reflective background. This is also the only IP LPR cam i've ever tested, so there might be better ones around, i just haven't found any yet.

Dahua comes with or without a logo, to make sure it's dahua product, check the MAC address, if it starts with one of the following 6 characters, it's a dahua. MAC Vendor 4C11BF ZHEJIANG DAHUA TECHNOLOGY CO.,LTD 9002A9 ZHEJIANG DAHUA TECHNOLOGY CO.,LTD

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).

When you have the software running and recording the camera, what does resource monitor tell you about CPU/MEM/NETWORK/DISK usages? Things that could cause even the recording to slow down: - Slow CPU (shouldn't be the case with that Xeon and a single 15fps FullHD cam) - Slow network (you can check if you get all the frames on another pc, or straight to VLC on recorder, you should be able to get a live stream straight to VLC by opening a network stream from url: rtsp://cam-ip:554/axis-media/media.amp) - Slow disk, if for some reason the disk is having trouble writing all the data, it might slow everything down.

Could you give more detail about the network configuration on your windows? Multiple NICs? Multiple IPs?

The codec is H.264, MPEG-4 or MJPEG in most cases, .mp4 is just an file extension. It's up to the manufacturer which file extension they use. From most system nowadays you can get and .mp4 or .avi out, so oyu can use any universal media player. Some manufacturers force you to use their own player and only let you export a .some_file_extension they use. So no recommendations from me, but when you choose the device, look at specs and look for info about video exporting format.

Your port forwarding should look like this: START -> END -> TO OP 8081 -> 8081 -> IP_OF_XPROTECT_PC So when you connect to your externalip:8081, your router forwards it to IP_OF_XPROTECT_PC:8081. Each incoming port (on the left) can be only used once, as it is externalip:incomingport -> internalip:anyport. From wifi(lan) you dont need the port forwarding and it is working because of that, no external ip is used. But when connected from internet over 4G, external ip is required to enter your network, then portforwarding handles the traffic to correct internal ip.

I think you have to install a Mobile Server on the pc. It should be included in the Xprotect Go installer. If it's not included, http://www.milestonesys.com/downloads has a Milestone Mobile Server 64bit download. You shouldnt need any of the Hikvision software (IVMS 4200 or such) since its only mobile client to xprotect.

It should be pretty simple. I've never even seen Milestone myself, but since its probably a pretty basic remote connection, i can try to help: Step 1: Install and enable Mobile Server Step 2: You need to figure out your external IP address, go to wimi.com (from the Milestone PC) to see it. Step 3: You need to figure out which port is Milestone using for remote connections, apparently by default its 8081. Step 4: Access your router and configure port forwarding, http://portforward.com/english/routers/port_forwarding/routerindex.htm probably has your router listed, pretty much any guide for any game/program will guide you thru the same process Step 5: Enter your external IP and port you just forwarded to your Mobile client. Step 6: Hopefully enjoy your pictures. Now if these steps wont for some reason get you your pictures, check your firewall (for testing purposes, if nothing else helps, turn it off). If its not firewall, your ISP might block some ports/all ports. In this case, this method of connection probably wont work. If any of the steps is giving you hard time, ask for more detailed info.

What ak357 said. IP cameras -> PoE Switch -> PC NIC 2, PC NIC 1 -> Router -> Modem Say your router has a DHCP server, assigning 192.168.0.1-100 IP's, put PC NIC 1 to DHCP so it gets internet access automatically. Put the PC NIC 2 IP to 192.168.1.1, cameras 192.168.1.2-100. Playing with more than one router is way too complicated for simple task like this one. If your PC doesn't have 2 NICs by default, one costs 30-40 bucks/euros/which ever currency you're using. If you wish to access the cameras (not PC NVR) from the internet, situation will be different. After all these connections you probably will also need to do some port forwarding: http://portforward.com/english/routers/port_forwarding/routerindex.htm Guides for most routers out there.

No. I've not come up with one IP PTZ camera that only has one speed. It might be the joystick causing this? Do you have any software in between? I've only used usb joysticks connected to our own software to control it, we're doing it via manufacturers own protocol or ONVIF (if camera supports that), so i dont really know how an IP joystick works. Which manufacturer/model is the IP joystick? Does it come with a software? Seems unlikely that it only has on/off joystick for one speed. Also which IP PTZ camera are you using?

Useful tools for all kind of IP related problems: NMap (Network and Port scanning/mapping) (http://nmap.org) Easily scan all the devices on the network, or subnets. Easily scan which ports are open on which devices, even tells you OS and other information on intense scan. Command-line tool for most linux distros. Zenmap (NMap with GUI) (http://nmap.org/zenmap/) Nmap with GUI, cross-platform so works on Windows. paping (ping ports!) (https://code.google.com/p/paping/) Easily check if a device has a specific port open. Windows 7 for example by default has ICMP pings blocked by firewall, so if you know you should have a service using port 80 (webserver usually) on the windows machine, you can ping the port 80 and it will go thru, even though normal ping might not. All kinds of camera configuration softwares, there are so many manufacturers around that configuring them might be a pain. Hoard as many configuration softwares you can, store them on USB stick and have them ready as you go. I've gathered few on my own (sorry, no links for downloads): Axis IP utility Sony IP setup program & SNC Toolbox Avigilon camera installation tool Dahua general config tool Dynacolor Device search Hikvision SADP Panasonic Easy IP setup Pelco Config tool Shany MyFinder Wodsee IP cam suite ONVIF device manager (http://sourceforge.net/projects/onvifdm/) There are probably many many more, and most cameras work well with default IP and browser config.

By default i would expect it to use TCP connections, so UDP shouldn't matter. It would seem the connection is working. You could try forwarding another port, port 80, otherwise identical to the 9101 forward, and see if you can access the device via browser. It might be the app you are using is the problem, if it cant connect thru internet for some reason. Any other app you could try? Also make sure you're trying this from phone via 3G/4G, not when you're in wlan in the same network. I've tried with browser on my phone and it just tries to download something. I've also tried several apps and it still doesnt work. What if I gave you my ip? Sure, I can take a look and see if i can connect to it with something (use PM). Could you also give a more specific model of the DVR?

You said the camera is "sitting on our stair railing", is it upside down compared to normal installation (when connectors are facing the sky and the dome facing to ground). Some PTZ cameras i've seen/tried have made weird sounds (clicking, grinding, scratching) under heavy movement when facing to sky. I believe this is because the lens (and everything connected to it) are rather heavy and gravity pulls them down, causing more friction and making the motors work harder.

By default i would expect it to use TCP connections, so UDP shouldn't matter. It would seem the connection is working. You could try forwarding another port, port 80, otherwise identical to the 9101 forward, and see if you can access the device via browser. It might be the app you are using is the problem, if it cant connect thru internet for some reason. Any other app you could try? Also make sure you're trying this from phone via 3G/4G, not when you're in wlan in the same network.

Many PTZ IP Cameras run some kind of routine check when they're powered up. So this might be caused by powerloss. Especially when camera is powered up by PoE, and the PoE switch cannot produce enough power to the camera, it might get stuck in a loop of restarts. One camera i saw this problem with booted up, ran a 270 degrees back and worth movement, then flipped once and stopped for few seconds, then booted up again and same routine ran on startup, until i switched it to external power.

According to images, everything should be configured correctly. Maybe your ISP blocks some ports? Are there some firewalls inbetween to mess things up? Does canyouseeme.org tell you the port is open? You could also try downloading PF Port Check from http://portforward.com/help/portcheck.htm , i've gotten different results with these 2 services.

My guess is the app works in LAN with the ID codes, but requires IP address for internet connection. Does the app allow you to enter IP instead of the ID code? If so, check your external IP address (http://checkip.dyndns.org/), enter that to your app, if it ask a port, enter 9101. Then the port forwarding. Locate a guide for your router from www.portforward.com, any app will do. Follow the guide to forward port 9101 from external IP to your Floureon H.264 LAN IP. Connection should work now. If the app does not support IP addresses, it might need some setup from the account of the service it uses.

I cant think of anything else to do, usually the software that comes with cameras can find the camera even if the IP is is lost. Chances are the camera is bricked and inaccessible. I actually managed to "brick" a cheap noname camera, I cannot access it from web/configuration software, but i do get RTSP-stream out of the default IP. Camera doesn't have any reset button etc, but since it cost around 15$, cant expect much

I got mine a week ago. I agree, it's impressive. I use it with Blue Iris 3. I can get the warped stream and the panoramic stream, but the other views (PTZ) don't seem to work in BI. I've got a 64Gb micro-sd on order with the idea of recording the warped stream in-camera, in case I need to go back to it, but only recording the dewarped streams in BI. Any thoughts on getting the PTZ streams working in BI would be welcome. -- Pete I don't really know anything about BI, but if they support ONVIF (Took a quick look at their website and didn't see ONVIF being mentioned anywhere though.), it should work. Maybe there is someone on the forums with better knowledge of BI that can help you out.

"arp -a" dumps your ARP cache data, telling you if your PC sees your camera in the network, go thru the list it prints and look for your IP cameras MAC address. It might also tell you the IP it has at the moment. "arp -h" (help) gives you more details.

Is there a reset button visible? Or perhaps under the backplate if you unscrew it? You could try holding (for 10 seconds maybe?) that while powering it up for hard reset. If you find a button, press it before you plug the power back on. If you cannot reset it, you could try if you see it from commandline with "arp -a" command. If you do, you could try setting the ip via arp command: "arp -s " and hope the camera supports it. You might have to use this command within the first 1-2 minutes after you plug in the power.

If you would record 45 cameras (3Mbit/s bitrate) 24/7, to keep recordings for a week you would need around 10-15TB or storage. Same amount with record on motion and motion ~50% of the day would need around 5TB. Best option would be PC based NVR and since its 45 3mp cameras you probably need some processing power, so depending on software you're gonna use, you probably need quadcore i5/i7 and some 4-8GB of ram (ram is cheap so i would go with 8GB). Then the software. We're developing a VMS on our own, and i'm not too familiar with other VMS software, so someone else might be better answering this question. Pick something that can handle all your 45 cameras and has useful features you need. I think most VMS manufacturers have some kind of trial or free version you can try out. If its supposed to be a recorder that sits in server room and is only used when a crime (or such) happens, features for big control rooms are not necessary and choosing a VMS that doesnt have these might be cheaper. If its gonna be on everyday use, make sure it's very easy to use and has all the features that are required.

You have to provide a bit more information. Manufacturer/model of the DVR? When and where does it give authentication issues? When trying to access web-ui? When trying to login locally? On some remote software?