New UVERSE Customer - Can't Setup DDNS
Hi. I switched from DSL / Phone service through AT&T to UVERSE Internet and UVERSE Phone. On my old system i was bridging my old RG to Linksys E3500 Router and handling the ports to be opened for my CCTV at home.
Now, with the new Pace 5031NV i have no idea how to setup my DDNS. We are going on vacation in 2 days and this is really a concern of mine. Can anyone help me?
For the most part your IP won't change on uVerse. Once you have been assigned an IP address by AT&T for your gateway your IP address won't change unless the gateway is swapped (the Pace device) or you're swapped to a new DSLAM port.
So in your case, just set the IP manually and it won't change.
Tom's Tech Blog
|reply to ozdemir23 |
If i understand you correctly, even though i am not paying for a static IP, i pretty much am receiving a static ip? And, if i do a "what is my ip" to find out my IP address, i should just plug that in to my DVR? Then what? How does the setup work for my local network to be visible on the WAN?
Yes, you are basically receiving a static IP. The only difference is that you can't customize the hostname whereas you can do that with a true static IP address.
As for getting your home LAN to be viewable on the WAN you would have to go into the Pace device and forward the appropriate ports.
Tom's Tech Blog
Tom- I setup an application and titled it DVR Surveillance and opened ports 8100 and 8180 just like i did with my DDNS service. I changed my software to point to my static ip and left the port alone, but it did not work.
I just realized that no ports are open and i tried having someone outside of the network (sister) ping my IP and the request timed out. I also tried a port checker and none of my ports show as open. It responds with a connection timed out.
What else am i missing in the Pace RG? Does it have a firewall setting as well that i need to consider?
|reply to trparky |
After some more research, I have gone in and turned off the "Block Ping" and "Stealth Mode" under Enhanced Security. This finally got me to at least acknowledge the device on the WAN. But still no dice on the port being open for 8100 or 8180 even though they are listed in the Hosted Application for the specific DVR.