One camera won't connect via DDNS

[ckronengold]

Frustrating AF situation.

I have 4 cameras and a doorbell. 3 cameras and the doorbell all work. But I can't figure out why the 4th camera (IP2M-841) won't work with the amcresddns URL.

Software Version2.520.AC00.18.R, Build Date: 2017-06-29
WEB Version3.2.1.453504
ONVIF Version2.42(V2.2.2.428697)

I have followed the exact methodology for setting up, each with their own port ranges being forwarded.
I can access the camera locally (192.168.x.x:port) with no problem, but nothing will resolve the DDNS so that I can access the camera remotely or through the app.

My 3 P5M-T1179EW-28MM cameras all work fine, including with their own amcrestddns addresses.

Where to start?

[Revo2Maxx]

Hate to say it but it really could be an issue with your camera being used with a 2017 FW, where your 1179's are using a newer FW and that might be why one is working and the other isn't. I mean in theory if you were able to do all other devices (Not really sure why you wouldn't use the Simple and easy to use P2P) on DDNS then the 841 should be able to as well..

[ckronengold]

Don't hate. Thats a good suggestion. I assumed the camera stopped receiving firmware updates because hitting "check for updates" never shows any updates avail. Maybe I'll update it manually.

Setting up P2P isn't possible if you aren't able to scan the bar code / qr code. With the cameras mounted, there's no way that I'm aware of to give access to a non-admin. But also, it should just work.

[Revo2Maxx]

You can enter the sn manually in app and some have qr code in web ui

[ckronengold]

upgrading firmware did not solve the issue.

[Revo2Maxx]

My guess is there is something wrong with the setup. I would Reset the camera and try again..

However there are somethings that maybe you could try. Here is a picture saved from one of my 841's WebUI Network, TCP/IP and then P2P tab you can see it offers the QR code to scan from your desktop. You can see mine shows status of Online. If there is an issue with the connections it would show offline.. I personally would try to use P2P it is Free and works for me very well even able to access my cameras over P2P on ASP.. Less of a headache..

Screenshot (4387).png (129.75 KiB) Viewed 2307 times

[ckronengold]

Mine is showing as offline. I did find one problem with my settings. My DNS settings were pointing to my old pihole, which I'm not using for DNS. But changing to my other DNS settings (1.1.1.1, 8.8.8.8.). Looks like I had a conflict between the wired and wireless settings. Bumped the wired IP address out of the reserved range and got it to show the camera as online.

Still wont connect through the app, though. Tried the P2P QR code, too, and thats not working either.

[Revo2Maxx]

Almost sounds like it is connected via Wifi on a Mesh Network?

I am not sure. If there is no blocking and no Router Tricks then the camera should be able to connect using normal settings from camera after a reset. If the camera comes up after setting up with your routers gateway as the DNS I would change that to 8.8.8.8 and 8.8.4.8 and save and see if it connects then.

However if it is a mesh network then it is just a whole different issue that I won't be able to help with because I don't have Mesh because of these issues.

[ckronengold]

Not wireless mesh. But yes, multiple access points.
And yes, I'm trying to connect this camera via wifi, while the others are connected via ethernet / PoE.

TP-Link ER605 router > 3x EAP225 APs.

Just strange since it will connect to the LAN local address (192.168.x.x), but not the amcrest DDNS.
Will try changing the DNS server.

[Revo2Maxx]

Yeah I hate to say it, That system is more Complex then Mesh to be honest. Mesh is a Mess. Your Setup there is just a lot there that someone would have to dive into at a Network Level. My guess is there is something going to be in your connection that is blocking your wifi connected device. Either there is a setting in the 605 that needs to be granted for the AP or maybe the AP's are setup with their own range out side of the normal range and while it will have access from the normal because of system design, there has to be something that is un checked in the settings somewhere that is keeping the camera denied.