remote access problem

[ryanc]

I have two Amcrest ProHD cameras - model IP2M-841. One camera is working great, the other isn't accessible beyond my home network. They are each set up on unique ports (tcp/udp/rtsp/http) and I have port forwarding turned on in the router with no overlap. I have dynamic DNS set up through noip.com.

One curious thing I've noticed is that the camera with the problem shows P2P as enabled (checked box), but shows the status as "Offline". The camera that is working outside the home network also has P2P as enabled, but shows the status as "Online".

If I run a open port checker on my IP, the ports with the working camera show as open and the ports with the other camera show as being closed. My phone can connect to both cameras within the home network using the Amcrest View app (and the camera's LAN IP address), but cannot connect to the problem camera when connecting from outside the network using the WAN IP address and port #. Push notifications are also not working on the problem camera.

Is there some setting somewhere that prevents the camera from talking to anyone outside the home network? From everything I can see, the two cameras are set up EXACTLY THE SAME (except for port numbers), so they should yield the same results. I don't understand why they're not. Any help would be appreciated.

Thanks!

[nayr]

Anyone with ANY suggestions? I don't know what else to do, but I need to be able to access both cameras from beyond my home network.

[Mark]

Did you take a look at the ports on your router to see if the port the problem camera is attempting to use is blocked ?

[Melvin]

Hello nayr ,

Could you please contact our support team? We would be happy to help you out with this.

https://amcrest.com/contacts

[jferringer]

Hello nayr ,

Could you please contact our support team? We would be happy to help you out with this.

https://amcrest.com/contacts

What was the resolution to this issue? I have a similar issue, I am running two IP2M-841B's and a IP2M-842B with a NV4108. I have it set up through NO IP DDNS and anytime I attempt to come from the WAN to the 842B, I connect, I can tell by the menu it is the camera and I can validate it using the information SN. However, the image I receive is that of another camera, an 841B, channel 1. I do not have this issue from the WAN to either 841's which are channel 1 and 2. When I have the trouble issue up on my remote WAN access, I shut off the NVR and I lose the image, I logout and attempt a WAN access, no image, I am logged into the camera, no image. With NVR off, I can log into the other two and have their respective images. SOOOO, I have scrubbed in great detail all the configurations from the DNS to the port forwarding, even to the point of doing a factory reset on the 842 and rebuilding it, same issue. I can LAN IP to the units fine, I can IP config to them fine, I can WAN IP to them however the 841's are fine the 842 displays the image of one of the 841's. HELP!!!!!

[Melvin]

Hello jferringer ,

So the issue is when you try to access the cameras individually using the public IP address? Please set different TCP ports for the cameras that does not work and ensure that those TCP ports are forwarded and open on your router.

[jferringer]

All 3 cameras have different TCP ports and all 3 different ports are port forwarded to the respective LAN IP associated with the camera. This is a strange one. I am making it to the 842, I know this because the menu is different and when I go to information it is the SN of the 842. However, the video image I am getting is that of one of the 841's. If I leave it up on my computer and power down the NVR, I get image lost. This is a strange one, it has to do with the NVR. I think it something between the main stream and sub stream.

[Melvin]

Hello jferringer,

This appears very strange. I believe the cameras are connected wireless not to thr router directly? Also go to the url canyouseeme.org and ensure all the TCP ports for different cameras are open. Also please give us a call if possible so that we can try some more trouble shooting.

[jferringer]

Never mind, I figured it out, has to do with doing DNS on 4 devices with the external and internal TCP ports and getting all the numbers hosed up, we are good, got it all figured out, sorry....