02-02-2013 3:33 PM
Since switching to Uverse I cannot get my three Trendnet IP cameras to connect remotely, as I could before with my previous neetwork setup. I've managed to set them up within the 2wire RG with the port forwarding and all, and can connect to them from the LAN, as well as the app that I have on my Android phone, but I cannot get them to connect from any remote computer.
I can connect to them from my local computer using the local IP (192.168.1.xx:xxxx), but when I type in the broadband address with the port number it will not connect. And I find that odd since this address is the same exact address that I have plugged into the app on my phone...where it works great.
I've tried everything I can think of including putting them in the DMZ, to no avail. They will not connect using the broadband address of 172.xx.xx.xx:xxxx.
I'm thinking that maybe I should connect my DLink router back in through the DMZ and reconnecting everything back to it as it was before, but I'm not even sure that would work.
Does anyone have any other ideas?
Solved! Go to Solution.
02-02-2013 7:59 PM
02-02-2013 11:17 PM
Thanks for the reply Greg, but as I stated in my original post, I have already done the steps that you have suggested, and they still do not work from a remote computer.
Just so there's no confusion, when at the remote computer I entered the public address, followed by a colon and then the port number. For example, 123.456.78.90:8181, where 8181 represents the port that I assigned to each camera in the port forwarding section of the router.
This setup works great on my Android phone (wifi turned off) but for some strange reason it doesn't work from a remote computer, or even my own computer that is connected to the network.. The browser just times out.
I know how to do this. I had them setup for years on my other network but they're not working the same with this uverse router, for some reason.
02-02-2013 11:45 PM - edited 02-02-2013 11:49 PM
Double check the info in the Firewall tab, per the info at portforward.com. Just realized that when I put down the website for Portforward, I put in .net, not .com as it should be. Look for the Trendnet camera in this list http://portforward.com/english/routers/port_forwar
02-03-2013 1:09 AM
Thanks, but I've already done all that. I've given each camera a static IP and assigned each a different port in their web server page, and I've forwarded those ports in the router page to the camera IP address. That all seems to work through my phone but will not work from any computer.
OK, here's an example. In my phone camera app settings page(I'm using the IP Cam Viewer Basic app) I entered 123.456.78.90:8181...bam, I have the camera image and can manipulate the pan and tilt with no problem. But, if I enter that same address, 123.456.78.90:8181 into my computer's web browser I get nothing.
Because I am getting the video stream on my phone that tells me that I have the ports open and working correctly. What I can't figure out is why not from a computer web browser?
02-03-2013 8:11 AM
02-03-2013 12:54 PM
I thought about the DHCP thing so I went ahead and set one of the cameras to DHCP and I let the router assign the IP. No change. Still cannot connect using the public address. Works fine with the LAN address.
As far as going to each cameras webserver, how do you think that I assigned them their static IP's?
So, let me reiterate something here. With my previous setup I had local cable modem broadband internet with a DLink DIR655 router. I assigneed each camera a static address and then forwarded their ports in the DIR655 router webserver, and they all worked great. I could access my cameras from any computer that had internet by using the public address. I have done essentially the same thing with the RG3801hgv, but I cannot access my cameras using the public address that I get from the 3801hgv. For some reason the firewall in the 3801hgv is still blocking them. I have even set them to DMZ in the router and they don't work.
Here's a screenshot of one of my cam's network setup page. As you can see from it it is set to DHCP.
And here's a screenshot of the 3801hgv firewall status page showing the cams with their ports forwarded.
02-03-2013 6:31 PM
I had same problem with my Foscams after switching from DSL to UVerse. I could access on my LAN, but not remotely, nor would emails of motion alerts go out. I tried everything and finally called tech support. After 2 hours trying to get my cameras to work through a 2wire 3600 RG, the tech added static IP to my account and solved the problem. I did not want to add the extra cost of static IP, but the problem wore me out. Working fine now. Apparently the UVerse IP assignments work differently than with DSL. I don't like spending the extra money for static IP and am hoping there is a way to connect remotely without. Interested to hear what you figure out.
02-03-2013 7:43 PM
02-03-2013 7:44 PM
02-03-2013 9:30 PM
Yes, ithe cams worked fine with DSL using dyndns.org for the DDNS service, which is configured on the cams. But no luck with the UVerse service until the static IP range was created.
02-03-2013 11:12 PM - edited 02-03-2013 11:13 PM
Please don't take this the wrong way. I am very happy and pleased that you are trying to help me, but I have posted on a number of times that I DO know how to access the cameras web server pages, and I have ALREADY accessed them to set them up.
If you go back and read through my posts you will see that. For some reason you keep missing that and keep telling me how to go into the camera web server pages and to set them up according to Trendnet's instructions. I have had these cameras for many years and have done that many, many times in the past. I even posted a screenshot of one of them.
Maybe gregzoll is just a bot and the replies are just canned responses to key words that people post.
Guess I'm on my own with this one.
02-04-2013 1:54 AM
Ureka!! I got it to work finally! At least, I think. I won't know for sure until I go off site to a remote computer and try it from there, but it has all appearances that it is working now.
What I ended up doing is I bridged my DLink router back into the network. I really didn't want to do that but it was the only thing that I could think of to do at this point. It was actually pretty easy. All I had to do was to go back into each camera and reset them back to the static IP's as they were before Uverse. And since my router was already setup for them, once I connected the cameras back to the DLink router, and the Dlink router to the RG through the DMZ, they were all working again as before. This should work fine until a power outage, or I power cycle the RG for anything and it gets a different public IP address, as I am not on a static IP address
These are the instructions that I found from another site regarding bridging the routers with Uverse:
There are a couple ways of doing it. First, disable NAT and disable DHCP. The second is to bridge the router. The third, is to buy an actual switch.
To "Bridge" the router:
1. Set your router's WAN interface to get an IP address via DHCP. This is required at first so that the 2Wire recognizes your router.
2. Plug your router's WAN interface to one of the 2Wire's LAN interfaces.
3. Restart your router, let it get an IP address via DHCP.
4. Log into the 2Wire router's interface. Go to Settings -> Firewall -> Applications, Pinholes, and DMZ
5. Select your router under section (1).
6. Click the DMZPlus button under section (2).
7. Click the Save button.
8. Restart your router, when it gets an address via DHCP again, it will be the public outside IP address. At this point, you can leave your router in DHCP mode (make sure the firewall on your router allows the DHCP renewal packets, which will occur every 10 minutes), or you can change your router's IP address assignment on the WAN interface to static, and use the same settings it received via DHCP.
9. On the 2Wire router, go to Settings -> Firewall -> Advanced Configuration
10. Uncheck the following: Stealth Mode, Block Ping, Strict UDP Session Control.
11. Check everything under Outbound Protocol Control except NetBIOS.
12. Uncheck NetBIOS under Inbound Protocol Control.
13. Uncheck all the Attack Detection checkboxes (7 of them).
14. Click Save.
02-05-2013 12:03 AM
02-05-2013 9:36 AM
Well, no luck with this. It worked on my local computer when I enter the public address, but when I got to work and tried it it wouldn't connect. But, it did work from my phone, which is really perplexing, as it is the same address that I have to enter. So, back to the drawing board. I think I'm going to try another forum since there's not much help here.
Guess the fact, that I pointed you to the Trendnet documentation was not enough, same with following the info at portforward.com. There really is not much more anyone else is going to say or do, but repeat what I explained repeatedly to you in how to make this work.
Welcome to the internet boards! Check out our troubleshooting articles below and don’t forget to search the forums - your question may have been answered already!
Service acting up? Click here to troubleshoot now!
© 2017 AT&T Intellectual Property.This link will open a new window All rights reserved. AT&T, Globe logo, Mobilizing Your World and DIRECTV are registered trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. All other marks are the property of their respective owners.
Congratulations! You earned the Liz badge!