peaceflwr

Is it possible to have everything set up, ports forwarded okay, connection and port being verified as okay and open with Internet utilities available and then, somehow being blocked by your ISP upstream? I've wondered about that since I have a great picture on my local network, seemingly have ports open, forwarded, and available and yet - cannot access the camera on the Internet. YES the ISPs do have a habit of blocking ports.. call them and speak to tier 3 tech support and explain you need a port opened for a security system.

Thanks for the reply - I've used two separate port checkers. One within the utilities of Port Forward util and the second, canyouseeme.org. To be honest though, this is the first I've heard of a need to have an rtsp port open, I'll have to check that out. you do not have to open the rtsp port

you wont be able to view the cameras WITHIN the network using the public IP, you will get a conflict. you can only view it with the local camera IP within the network. common HTTP ports are 80, 8080, 8000 and 8001... once you port forward go to canyouseeme.org to verify the port IS open. if it is not open, then your ISP has blocked the port on their end (they like to do this to protect the network). the only other thing you need to worry about after the port forward is DDNS. if the public IP (174.169.19.321) is dynamic (residential public IPs are dynamic unless youve paid for a static) then you will need to go to dyndns (for a small fee) or noip.com (free but you have to log in once a month) to set up the DDNS. OR you can get a static IP address from the ISP (internet service provider)

effio-e and effio-a are for image adjustment..not so much for noise. you need DNR or 3D-DNR (better) for noise reduction

you can easily upgrade to AHD (HD over coax) for not much money if you need better resolution in the future... you can use your existing cable and AHD has recently evolved to 1080p http://www.amazon.com/iSmart-Outdoor-Security-1500TVL-Connection/dp/B00TAB0DRK/ref=sr_1_1?ie=UTF8&qid=1430515737&sr=8-1&keywords=AHD+kit

you can connect with serial id regardless of where you are at because this is a direct connection to the camera... I am actually wondering if you have the correct serial numbers, the camera serial is too short... normally it is between 14-16 characters.. more often 16

It doesnt show up on SADP . However, it does show up on the hikvision ivms 4200 software in the configuration setup only after a few seconds but it wont connect or let me do remote configuration (I feel like both softwares use the standard port 80 information for http to do some sort of configuration). In fact after I do try to connect to it via ivms configuration page it disappears from online cameras list and i have to restart program to get it to show up again. Do you have any other ideas on how I can connect in to get this stuff straightened out. I do not know why they would let me change http port if I wouldnt be able to connect afterwards. I mean I am 99% sure I set the http port to 9821 and figured just adding that port after colon in url would work. Now that its not working maybe I typed something else and am going crazy? I dont know what to do and am getting nervious cuz these are cameras I installed for my gf dad! Its the hikvision DS-2CD2132-I dome camera if that helps. I read there might not be a reset button so am I am guessing I am screwed now ? I mean the camera was working just fine and I changed that http port and then this all happens.... Thanks for the reply port 9821 is not an HTTP port... HTTP ports are 80, 8000, 8001 and 8080. 9000 ports are normally for video chat or video conferencing. It may be that that port was assigned to something else when you assigned it to the camera and now youre getting a conflict. reassign the port to 8080

i have basic CMS software I can send you for a computer based NVR. private message me

The most important thing about clear night vision is make sure you get good noise reduction... 3D DNR is a great choice, but for that price point you should look into HD over coax options such as TVI or AHD... AHD will be the most cost effective and they are now coming out with 1080P AHD. But, for night vision you are correct... resolution is not as important... noise reduction is what you want to have for that, otherwise the darker areas will seem blotchy or grainy

at the bottom you choose by device... skip the user name password thing and go to the second tab... my network here sucks so I will try to log in when I get to a better spot.

i dont know much about that app... but you can remote with the CMS software you have. If you download it on a computer outside of the network you would add with 'cloud id', which is the serial number. I know you had said that the equipment you are using doesnt have a serial... but, EVERY IP device has one. From the CMS software, you will add it under 'cloud id'.. You really need to look into the serial number, have you gotten it yet? once you do if you want I can try to log in to see if it will work, it should. as far as the app, I will always recommend the VmeyeCloud app... under 'by device'. That is the only app that I use now because it is more stable than most

perfect! the original video file with save as H.264, but the backup will save it as an AVI file that can be played by windows media player. I save my backups to a folder on my desktop which I've named 'videos'

did you set up the record plan on the local config menu? you need to select where you want the recordings to be saved also. And if you right click on DVR you can choose to automatically connect the device BEFORE you select the camera.

if you send me a private message I will forward you the CMS software I use, with the user manual. Its pretty user friendly and I use it everyday for remote view of my cameras at home. It also has a pretty simply record/playback feature

is there a tab for serial id? this one would require the DDNS/ port forwarding... you need an app with QR scan or serial ID otherwise you're back where you started :/

the cms is basically an nvr for you computer... it should play the videos, but also local record and remote playback

hmmm.. yeah, it looks like your cameras arent compatible with this... I always use this site to test my cameras, not sure why its not working for this one. Unfortunately, you are stuck with DDNS/port forwading unless the manufacturer has their own software. I would call the tech support for the system you have and see what they offer in way of connecting their equipment via serial number (app or CMS software?)

that doesnt look like the correct site... http://xmeye.net/login.do?method=goLogin go to 'by device'. It will ask to download software... after it downloads you can log in with the serial number Yep, that's is the site I signed up with. As I recall over the weekend, after I signed up and logged in, it did download something but I'm not sure what it was. I think it was CMS but I can't swear to it. Then it went the page that shows the Device manage and my devices where I put in the ip address of my dvr and ip camera. When I log back in, it automatically does a search for them but says that I am not connected. log in on the second tab.. 'by device' and use the serial number of the camera/nvr. The tab you are on is for a cloud account... log in with 'by device' and you dont have to set anything up

that doesnt look like the correct site... http://xmeye.net/login.do?method=goLogin go to 'by device'. It will ask to download software... after it downloads you can log in with the serial number

youre welcome! anytime

use the serial number! use the app vMeyeCloud and go to the by device tab. While in the same network as the IP system, click add and then on log in mode make sure it is 'Serial'. Then search and add the camera/NVR... when you go back to the device list, the serial number will be listed... go to xmeye.net for browser access (go to the 'by device' tab) you CAN put it in the DMZ, but then the whole system is unprotected because it is outside of the firewall, by device (serial) is MUCH simpler.. no DDNS needed and no port forwarding required!

yes, it is a bad idea... if you are going to port forward, only forward the NVR IP... for connection to the cameras use the serial number. you can also use the serial number of the NVR to connect too though.. then you dont have to port forward anything!

the serial number is the best way to connect directly to an IP camera or NVR. It is basically like the MAC address of the device. It does not require port forwarding or DDNS because you are logging directly into the device, not the network. The connection will still depend on the network for stability though, because that is what carries the data.

no-ip will still have your public (remote) IP address, it updates in the system automatically when you log into no-ip. But the host (the URL you set up before) may not be saved unless you log in once a month to keep it active. If it gets deleted, simply make a new URL. Using canyouseeme.org will only tell you the public IP address of whatever network you access it with. Unfortunately, there is no way to find the public IP unless you are within the network. as far as port forwarding goes, port 80 is the http port for web access, so it could be assigned to another device, so alot of times we will suggest using 8080 or 8082... 6000-9000 are the ports which surveillance systems normally use, because they are not assigned to other things (normally). The local port in the network page of the DVR/NVR will have to be the same port that you forward the DVR/NVR IP address to, that is what sets the path. you actually really dont have to port forward or set up a DDNS... IP cameras and NVRs actually have a serial number that you can put into the mobile app to connect with. You put your serial number and the username/password of the DVR/NVR. Port forwarding WOULD be needed if you are viewing remotely through a browser though. As far as local access, the IP address to the camera or NVR in the browser would take you directly to it, you wouldnt need to worry about the port. There is a site you can try for remote access in a browser without DDNS or forwarding. It also uses the serial number. xmeye.net ... log in under 'by device'. The id is the serial number

it is probably the port you are trying to use.. try 465 or 587