logging into camera help (IE icon)

[dcmkii]

Hi guys
So i switched over to a new modem and it seems i cannot log into my first camera via the web view (clicking the internet explorer icon), see attached pic.
The other cameras are fine. I haven't changed anything, been using static IP for my main NVR then the other cameras are assigned automatically.
I believe issue is the subnet? It says page not available or has moved when I click on the IE icon for the first camera. I'm not sure if you call it subnet of the ip address. I'm sure the problem is the last digit 1080 which is unavailable. The other cameras following the sequence 1081, 1082 etc are fine.

192.168.0.1:1080

Any ideas how to mitigate this issue?

 

[cbt20]

I'd recommend using ConfigTool.

 

[TonyR]

Dahua cams come with a static IP of 192.168.1.108, it may need to be set to DHCP so the POE NVR can assign it an IP from it virtual server.

1. Note existing PC network settings, then set PC to static IP of 192.168.1.22, subnet mask of 255.255.255.0.
2. Run patch cable from cam to PC's LAN port.
3. Power cam with 12VDC adapter.
4. Open browser on PC to 192.168.1.108.
5. Set login credentials if asked and write that down.
6. Change the cam's network=>TCP/IP settings from static to DHCP
7. Save those cam settings.
8. Disconnect power from cam.
9. Set PC network settings back to the way it was, plug back into LAN.
10. Plug cam back into NVR.

 

[dcmkii]

Dahua cams come with a static IP of 192.168.1.108, it may need to be set to DHCP so the POE NVR can assign it an IP from it virtual server.

1. Note existing PC network settings, then set PC to static IP of 192.168.1.22, subnet mask of 255.255.255.0.
2. Run patch cable from cam to PC's LAN port.
3. Power cam with 12VDC adapter.
4. Open browser on PC to 192.168.1.108.
5. Set login credentials if asked and write that down.
6. Change the cam's network=>TCP/IP settings from static to DHCP
7. Save those cam settings.
8. Disconnect power from cam.
9. Set PC network settings back to the way it was, plug back into LAN.
10. Plug cam back into NVR.

Hi Tony

I tried your suggestion but couldn't get it working on steps 3 and 4.
I thought plugging into the computer LAN would power it up? Perhaps not. I don't have any other PoE switch.
My set up has been working for a year until i switched over to a new router/modem.

Something i did find from more testings today.
Through the web browser I changed the IP of the camera from Static to DHCP and then rebooted.
The camera with the issue got reassigned with a new 4 digit behind the ip address when i click into the internet explorer icon.
192.168.0.xx:10080 to 192.168.0.xx:10082
I can log into that camera now but the issue has now gone to another camera where it has been assigned with the :10080 on the end of the ip address.
I somehow have to prevent my cameras from picking up :10080 when it gets rebooted each time.

 

[dcmkii]

hello, was wondering if anyone have any further insights to tackling this issue.

Thanks

 

[IPCamer]

hello, was wondering if anyone have any further insights to tackling this issue.

Thanks

You mentioned that the issue started when you did change your modem/router. So the question is , do you know what was the DCHP ip range of your old modem/router? Was it 192.168.0.1 - 192.168.0.254 ??
In the screen shot you posted , it looks your new modem/router uses a DHCP ip range of 192.168.1.1 - 192.168.1.254.
This explains why you where able to access your camera again when changing from static ip to DHCP ip.
If possible you could change the DHCP range in your new modem/router into the old range and see if this solves your issues. The other solution is to change all static ip addresses from your cameras into 192.168.1.xxx , but then you need first access to your cameras!

 

[dcmkii]

You mentioned that the issue started when you did change your modem/router. So the question is , do you know what was the DCHP ip range of your old modem/router? Was it 192.168.0.1 - 192.168.0.254 ??
In the screen shot you posted , it looks your new modem/router uses a DHCP ip range of 192.168.1.1 - 192.168.1.254.
This explains why you where able to access your camera again when changing from static ip to DHCP ip.
If possible you could change the DHCP range in your new modem/router into the old range and see if this solves your issues. The other solution is to change all static ip addresses from your cameras into 192.168.1.xxx , but then you need first access to your cameras!

Hi @IPCamer
I checked my current modem/router and it shows the current DHCP range is 192.168.0.1 to 192.168.0.254
Also for the cameras see attached screenshot, it has been set to static in the pattern of 192.168.1.xx all along for it to work.
I'm able to change it to DHCP or static from the camera menu screen when i search all devices.
The only issue is when i click on the internet explorer icon (first camera), on the address bar it shows 192.168.0.20:10080 which isn't able to load the camera log in screen (192.179.0.20 is my nvr log in address). For the other cameras which are randomly assigned to 10081, 10082 etc, they work perfectly fine.

 

[IPCamer]

Hi @dcmkii

Seems I overlooked you are using an NVR with PoE and your NVR uses internal 192.168.1.XX range for the connected cameras.
Your NVR can be reached on 192.168.0.20 on your LAN ( typing error (192.179.0.20 is my nvr log in address) ??)
To connect to your camera's , clicking on the IE icon, it opens a redirected web page 192.168.0.20:XXXXX for a specific camera, where XXXXX is just a assigned port number. Did you assign these ports yourself? ( I am not familiar with NVR with PoE.)
If only your first camera does not work on port one, then it should not be related to your modem/router change.
When interchanging the cameras on the NVR PoE port 1 and 2 , what is then the result?

 

[dcmkii]

Hi @dcmkii

Seems I overlooked you are using an NVR with PoE and your NVR uses internal 192.168.1.XX range for the connected cameras.
Your NVR can be reached on 192.168.0.20 on your LAN ( typing error (192.179.0.20 is my nvr log in address) ??)
To connect to your camera's , clicking on the IE icon, it opens a redirected web page 192.168.0.20:XXXXX for a specific camera, where XXXXX is just a assigned port number. Did you assign these ports yourself? ( I am not familiar with NVR with PoE.)
If only your first camera does not work on port one, then it should not be related to your modem/router change.
When interchanging the cameras on the NVR PoE port 1 and 2 , what is then the result?

Hi @IPCamer
Your understanding is absolutely correct. I am using an NVR to power the cameras and the internal address to access them is 192.168.1.XX
And yes the NVR is reached by 192.168.0.20.
I did not assign the redirected web page address 192.168.0.20:xxxxx, I wonder if anyone knows how to avoid it assigning 10080 as it seems to be the problem.
I just rebooted my NVR and the funny thing is that the last camera on my list is now assigned with the 192.168.0.20:10080
I didn't seem to have this issue last year on my old modem/router, I don't really think it's a modem/router issue either.

 

[IPCamer]

Hi @dcmkii

Well, that behavior on a NVR with PoE seems normal. When ever you connect a camera to one of the NVR PoE ports it will assign automatically an internal IP address.
The link of the IE icon is then generated automatically by the NVR in a format: "NVR-IP":"port#" ( port number from 10080 till 100XX (max of # PoE ports)).
Don't know if there is a logic behind the numbering , but if all IE icons of all your cams show up a valid link (you can access that camera) things are working correct.
If only the expected order of port numbers has changed , then a reboot of the NVR or a camera loss could have lead to this as you just experienced.
Expected order : first camera connected to any NVR PoE port will get IP(10.1.1."X") and port 10080, next camera will get IP(10.1.1."X+1") and port 10081. IP address depends on Switch config and free addresses in NVR.

 

[dcmkii]

Hi @dcmkii

Well, that behavior on a NVR with PoE seems normal. When ever you connect a camera to one of the NVR PoE ports it will assign automatically an internal IP address.
The link of the IE icon is then generated automatically by the NVR in a format: "NVR-IP":"port#" ( port number from 10080 till 100XX (max of # PoE ports)).
Don't know if there is a logic behind the numbering , but if all IE icons of all your cams show up a valid link (you can access that camera) things are working correct.
If only the expected order of port numbers has changed , then a reboot of the NVR or a camera loss could have lead to this as you just experienced.
Expected order : first camera connected to any NVR PoE port will get IP(10.1.1."X") and port 10080, next camera will get IP(10.1.1."X+1") and port 10081. IP address depends on Switch config and free addresses in NVR.

Hi @IPCamer

Thanks for your explanation. Could this article explain why I'm experiencing trouble connecting to port 10080

Google Chrome blocks port 10080 to stop NAT Slipstreaming attacks (April 2021)

Google Chrome blocks port 10080 to stop NAT Slipstreaming attacks

Google Chrome is now blocking HTTP, HTTPS, and FTP access to TCP port 10080 to prevent the ports from being abused in NAT Slipstreaming 2.0 attacks.

www.bleepingcomputer.com

 

[IPCamer]

Hi @dcmkii ,
You mentioned : "I just rebooted my NVR and the funny thing is that the last camera on my list is now assigned with the 192.168.0.20:10080". Is it then possible for you to access that camera on 192.168.0.20:10080?
If so , then there is no problem with port 10080, the ports are then just configured in a different order then you where used to.

 

[dcmkii]

Hi @dcmkii ,
You mentioned : "I just rebooted my NVR and the funny thing is that the last camera on my list is now assigned with the 192.168.0.20:10080". Is it then possible for you to access that camera on 192.168.0.20:10080?
If so , then there is no problem with port 10080, the ports are then just configured in a different order then you where used to.

hi @IPCamer
I am unable to access the the camera that is now assigned to 192.168.0.20:10080
I understand that the order isn't important. Hence just wondering whether the inability to access port 10080 is related to google chrome

 

[IPCamer]

hi @dcmkii

Are you using Google Chrome browser when trying to connect? Try an other browser, see if that works?

Update: Seems you nailed it down to the correct root cause , indeed port 10080 is blocked by web browser ! Did a verification.
Edge:

Firefox:

Chrome:



I tried then Pale moon (32bit) and IE11 , both do still work for now !! (21-aug-2021)




Seems all major browsers are blocking port 10080 due to NAT Slipstreaming attacks ! Good you found that article and linked it to your problem.

Update2: Same issue was report in this topic: No Access to one CAM Web GUI behind NVR | IP Cam Talk

 

[dcmkii]

Hi @IPCamer
Thanks for going to the effort to test this out for me.
Unfortunately i couldn't find a safe link to download 32 bit Pale Moon for Mac.
However, good news is when i tried Safari (Version 13.1.2) which comes default with Mac, I was able to log into the camera with port 10080.

Appreciate your help all along

 

[just some dude]

Why are people still using this port (10080)? It seems that we should not have to find a work around to enable us to use a frequently exploited port. I am not using all 8 ports on my new Dahua NVR so I guess I'll just start from port 2 and go up.

 

[wittaj]

Would suggest you run a port scanner first and see which ports are currently being used in your network.

 

[just some dude]

I know exactly what ports are in use. It's not 10080. Any way to make the NVR skip this port?