Ok here is my issue. For the last year my network cams have been fine. I can view them from work or while connected to my home network via ipad apps and such. We had a big storm that smoked my modem and while the cable company replaced my modem with a cisco dpc3208. I updated the firmware on my router and bridge. Now I can only view my network cams when not connected to my home network, we'll kinda at least. From work or attached to my mobile network I connect through my wan ip and port number. I used to be able to view from home on my network using the same address bun now it shows nothing. Here is what I mean. My router address is 192.xxx.x.xxx. My wan ip is 96.xx.xxx.xx. From work or mobile devices I can view using 96.xx.xxx.xx:xxxx. But when connected to my home network that address won't work, I have to use the network IP address such as 192.xxx.x.xx. And I can see the image. Pain in the but to have to set the different address up to see them for home and away. What could have changed that won't allow me to see the cams using the same address no matter if I'm at home or away?
I can view my IP cameras from devices outside my home network, but not when connected to home network?
- Thread starter Tjferris
- Start date
abailey
Distinguished
- Mar 23, 2014
- 944
- 0
- 20,960
In order to do what you want your router needs to support a feature called hairpin NAT. Most consumer routers do not support this. Thus you will have to use different addresses for when you are outside your network or inside your network.
As stated above the IP address is tricky and you need a special feature on your router. The more common version of this question is related to the use of a DNS name. Since your WAN address might change many people use something like dyndns so they can use a name rather than a IP.
Now you still have the same issue since when you look up the name of the camera it resolves to the external wan ip. The trick is to go into the host files on the internal machine and map the name to the internal IP address which likely will never change. You can then always access the camera with the same name no matter where you are.
Now you still have the same issue since when you look up the name of the camera it resolves to the external wan ip. The trick is to go into the host files on the internal machine and map the name to the internal IP address which likely will never change. You can then always access the camera with the same name no matter where you are.
It's the same router I was using which for the past year has been working just fine using the wan ip in all locations to access cams. Something changed either with the new modem or the new firmware on my buffalo router. I am running dd-wrt if that helps
It will be the firmware upgrade that did it. DD-wrt tends to have way too many things you can set so it does not take long to get lost. The new version of firmware may do something different or changed the way the defaults work. It could be either a firewall option or a nat option hard to say. In way it is lucky that both firewall and nat options are done in the same place. The bad part is it uses the IPTABLES to do all this. If there is not some magic check box on some screen you are going to have to look though the iptables chains and figure out if its being blocked or if you need to add something. iptables is one of most confusing commands I have ever seen.
Miguel_934
Commendable
- Jun 28, 2016
- 2
- 0
- 1,510
Hi all I don't have a answer but I am having the same problem, for years I have been able to view my cameras either from with in my home network or outside my network by login using my wan IP address and the port assign to each camera or connecting to one and using the multiple screen, for a while my Comcast modem has had to be reset three to for times a week so last Saturday following the recommendations of the Comcast Customer Service person I went to Comcast a exchange my modem router TC862 for a new one and I was given the latest TG1682G modem from Arris, which I setup properly to do my port forwarding for each camera with the proper addresses and port numbers. but when I try to view my camera I only con see the ones that are in a different network the ones with in my network won't show but if I use my cell phone application and turn my wifi off on it to force it to connect using the 4G the I can see all the cameras fine but if I turn the wifi on and force the phone to use my wifi then I can't see them.
Since Saturday at 6:00pm I have been on the phone with Comcast tear one, tear two and had two technician on site and they haven't been able to figure it out.
I can believe that changing a modem would be such a painful experience.
Any input or work around would be greatly appreciated.
Since Saturday at 6:00pm I have been on the phone with Comcast tear one, tear two and had two technician on site and they haven't been able to figure it out.
I can believe that changing a modem would be such a painful experience.
Any input or work around would be greatly appreciated.
You should not really post in 2yr old threads most are ignored. Still the answers are the same read the first 2 replies. Your new device likely does not support hairpin nat and there likely is no way to change that. Your only option is to not use the external ip.
TRENDING THREADS
-
Question User RX 580 8gb red devil powercolor, asking original BIOS- Started by PizzaInGame
- Replies: 7
-
-
-
News Microsoft updates Windows 11 24H2 requirements, CPU must support SSE4.2 or the OS will not boot- Started by Admin
- Replies: 19
-
Facebook
Twitter
Instagram