
Contributor
•
3 Messages
Unable to open port for security camera
AT&T replaced my gateway with a Pace 5268ac. I was previously able to access by security camera DVR by opening a port. I followed all of the steps on AT&T's website for port forwarding to open the port on the new gateway, but port checking tools tell me that the port is blocked.
I called AT&T support. The support rep accessed my gateway and told me that it was set up properly for port forwarding on the DVR, but he was also unable to access that port through the Internet. He told me that there is a group at AT&T that specializes in opening ports and he forwarded me to them. After taking all my information they told me that they could only help me if I paid them - port forwarding is outside the scope of free technical assistance because my Internet service is working properly.
I disagree - the AT&T support rep agreed that I did everything correctly to open the port. So, it must be an issue with AT&T blocking the port. How can I open the port without paying for AT&T to fix something that is not working properly?
ATTU-verseCare
Community Support
•
6.7K Messages
8 years ago
Hi @tmRoth,
We apologize about the issues you are having accessing your security cameras, but we will be glad to help. To start, are you able to access your security cameras with the internal private IP inside your house?
-ATTU-verseCare
0
0
tmRoth
Contributor
•
3 Messages
8 years ago
Yes, I am able to access the cameras on the internal network using the assigned static IP address.
0
0
ATTU-verseCare
Community Support
•
6.7K Messages
8 years ago
It may be worth trying to setup the security camera in DMZ mode. You can do so by following these instructions. Also, when accessing through a public IP, are you doing it inside your house or in a different location? Finally, try performing a trace route to see if you are reaching your gateway.
Let us know how it goes.
-ATTU-verseCare
0
0
jwpurdy
Teacher
•
19 Messages
8 years ago
I had to open the following ports to the security camera NVR:
TCP 80, 443, 554, 37777, & 37778
UDP 80, 443, 554, 37777, & 37778
These weren't all required for access inside the house but were required for access from the internet outside of the house via the public IP.
0
0
MicheleLP
Contributor
•
1 Message
7 years ago
ATT also told me that I could pay for someone to troubleshoot-not going there. I can see the feed from outside my network using port forwarding and DYNDNS, but to see the feed from inside my network, I need to use the private IP. I discovered this while I was away from home and using the hotel's WI-FI. I was shocked to find that I could view my camera feeds. When I came home, I found that those same settings would not work, but if I set the IPs to the private IPs, it worked. Within your home network ( any private IP,e.g., 192.x.x.x. 172.x.x.x, or 10.x.x.x) use that IP, when you are away from home, use the public DNS with the port that you set up in port forwarding. It has to do with the PACE Router. I haven't wanted to deal further, but when I do, I'll check out the info on the PACE router.
0
0
JefferMC
ACE - Expert
•
33.6K Messages
7 years ago
The U-verse Gateways do not provide NAT loopback, thus this is the expected behavior.
If you wish this to work, then you can acquire your own router that supports NAT loopback, install it between your cameras and the U-verse Gateway (in IP Passthrough/DMZplus mode), and then it would work.
0
0