Forum Thread

Trouble with INTRANET viewing of IP Cameras (Foscam) connected to ASUS Router

HoCoAmish 5 10 April 18, 2014 at 05:54 PM
I switched from a Linksys E1000 to the Asus RT-AC56U.
I have 6 webcams, some are wired to the network, some are wireless.
I use IP Cam Viewer on my cell phone (which, in the past, was able to connect to the cameras using my home wifi or using 3G/4G). The address I use for IP Cam Viewer is ***.dyndns.org:xxxx. I do not use the IP address (192.168.x.x:xxxx) to connect.


Since the switch from Linksys to Asus, I have had issues:

I have not been able to WIRELESSLY access my IP cams from my INTRANET using the ***.dyndns.org:xxxx address with IP Cam Viewer.....BUT
I can connect WIRELESSLY to my IP cams from my INTRANET using the 192.168.x.x:xxxx address with my IP Cam Viewer.

I have not been able to access my IP cams when WIRED to my INTRANET using the ***.dyndns.org:xxxx address on Chrome.....BUT
I can connect to my IP cams when WIRED to my INTRANET using the 192.168.x.x:xxxx address on Chrome.

I can access the cameras when connected through the INTERNET (using ***.dyndns.org:xxxx, obviously).



WHAT GIVES!?!? I assume this has something to do with NAT, but if I turn it off in the Asus settings, then nothing works!

Has anyone else had this problem? Mad Do you know how to fix it?????

Please help.

9 Comments

1

Sign up for a Slickdeals account to remove this ad.

Joined Jul 2005
Toadally Irrelephant
7,613 Posts
1,199 Reputation
#2
Is the Asus running DD-WRT? If so, you might need to address a "loopback" issue with the firewall.
Reply Helpful Comment? 0 0
Quote from serra View Post :
stoopid serra.
Quote from slickdeals View Post :
How did I end up here...
#3
You have to setup the port forwarding again to your viewer to point to the 192.168.#.#:port# address
Reply Helpful Comment? 0 0
Joined Mar 2004
L11: Monkey's Apprentice
17,196 Posts
2,789 Reputation
#4
Quote from flea View Post :
You have to setup the port forwarding again to your viewer to point to the 192.168.#.#:port# address
Correct, this is a OE (operator error) problem. Just because OP has been "doing it that way" for ages doesn't make it the right way to do it. If you are on the LAN you should be using 192.168.x.x NOT dyndns. When you use dyndns you are essentially trying to access the cameras via the WAN. As an aside dyndns is crap since they started trying to charge everyone. For free accounts it won't let you keep your record unless you log in once a month.

If you want a shorter name, you can create a static DNS record and a custom Hostname on your router. If you try to go to the hostname it will resolve to the IP.
Reply Helpful Comment? 0 0
Quote :
Reading comprehension isn't just for school children!
#5
Quote from brbubba View Post :
Correct, this is a OE (operator error) problem. Just because OP has been "doing it that way" for ages doesn't make it the right way to do it. If you are on the LAN you should be using 192.168.x.x NOT dyndns. When you use dyndns you are essentially trying to access the cameras via the WAN. As an aside dyndns is crap since they started trying to charge everyone. For free accounts it won't let you keep your record unless you log in once a month.

If you want a shorter name, you can create a static DNS record and a custom Hostname on your router. If you try to go to the hostname it will resolve to the IP.
You are not reading the OP's post correctly. OP can access the cameras over the internet so the port forwarding is set up correctly. VorlonFrog is correct that there is a nat loopback issue here. That router has a know issue with some firmware versions. OP are you running the latest firmware?
With nat loopback working correctly OP should not have to use a local ip when connected locally. That would mean op would have to set up double the amount of cameras in ipcamviewer and only half would show up at any given time wasting half the screen in matrix view. That's silly.
As far as dyndns, I just bit the bullet paid 24 bux for 2 years (With coupon) and have 10 hosts (they allow for 26 or something like that), and don't have to deal with logging in etc...

ps. op, check out our forum at www.ipcamtalk.com if you have any other ip camera related questions or issues.
Reply Helpful Comment? 0 0
Joined Mar 2004
L11: Monkey's Apprentice
17,196 Posts
2,789 Reputation
#6
Quote from fenderman View Post :
You are not reading the OP's post correctly. OP can access the cameras over the internet so the port forwarding is set up correctly. VorlonFrog is correct that there is a nat loopback issue here. That router has a know issue with some firmware versions. OP are you running the latest firmware?
With nat loopback working correctly OP should not have to use a local ip when connected locally. That would mean op would have to set up double the amount of cameras in ipcamviewer and only half would show up at any given time wasting half the screen in matrix view. That's silly.
As far as dyndns, I just bit the bullet paid 24 bux for 2 years (With coupon) and have 10 hosts (they allow for 26 or something like that), and don't have to deal with logging in etc...

ps. op, check out our forum at www.ipcamtalk.com if you have any other ip camera related questions or issues.
My bad, I think OPs phrasing threw me. If indeed ipcamviewer works that way then indeed that would be undesirable. That being said, as you stated, NAT loopback seems to be supported in the latest Asus firmware release. I've become accustomed to not using NAT loopback since some of my WiFi routers have supported it and some have not.
Reply Helpful Comment? 0 0
Joined Jan 2008
L1: Learner
5 Posts
10 Reputation
Original Poster
#7
Quote from VorlonFrog View Post :
Is the Asus running DD-WRT? If so, you might need to address a "loopback" issue with the firewall.
No, my Asus is not running DD-WRT...yet.
Reply Helpful Comment? 0 0
Joined Jan 2008
L1: Learner
5 Posts
10 Reputation
Original Poster
#8
Quote from fenderman View Post :
You are not reading the OP's post correctly. OP can access the cameras over the internet so the port forwarding is set up correctly. VorlonFrog is correct that there is a nat loopback issue here. That router has a know issue with some firmware versions. OP are you running the latest firmware?

With nat loopback working correctly OP should not have to use a local ip when connected locally. That would mean op would have to set up double the amount of cameras in ipcamviewer and only half would show up at any given time wasting half the screen in matrix view. That's silly.

As far as dyndns, I just bit the bullet paid 24 bux for 2 years (With coupon) and have 10 hosts (they allow for 26 or something like that), and don't have to deal with logging in etc...

ps. op, check out our forum at www.ipcamtalk.com if you have any other ip camera related questions or issues.

I initially was running the Asus without downloading the newest firmware, but I eventually allowed the Asus to "check" for the latest firmware and download it. This did not fix the problem. I have since looked at the Asus website for manual firmware download (I am running Windows 7, 64bit) and I'm not exactly sure which download version is best. I'm thinking [Version 3.0.0.4.374.4561] is the "correct" choice -- I want stable at this point and don't need any beta releases. Can anyone confirm this would be my best choice and that it has the necessary firmware upgrades to resolve the NAT issue?

Thanks for the link! I will definitely check it out.
Reply Helpful Comment? 0 0

Sign up for a Slickdeals account to remove this ad.

Joined Jan 2008
L1: Learner
5 Posts
10 Reputation
Original Poster
#9
Quote from brbubba View Post :
My bad, I think OPs phrasing threw me. If indeed ipcamviewer works that way then indeed that would be undesirable. That being said, as you stated, NAT loopback seems to be supported in the latest Asus firmware release. I've become accustomed to not using NAT loopback since some of my WiFi routers have supported it and some have not.

Upgraded to the latest stable firmware and it works Great! Thank you everyone!
Reply Helpful Comment? 0 0
Joined Jul 2005
Toadally Irrelephant
7,613 Posts
1,199 Reputation
#10
Thanks for coming back and letting us know!
Glad to hear it's working for you, now.
Reply Helpful Comment? 0 0
Page 1 of 1
1
Join the Conversation
Add a Comment
 
Copyright 1999 - 2016. Slickdeals, LLC. All Rights Reserved. Copyright / Infringement Policy  •  Privacy Policy  •  Terms of Service  •  Acceptable Use Policy (Rules)  •  Interest-Based Ads
Link Copied to Clipboard