Pace Pic 5268AC pinhole not working

Let's help with getting your camera system set up, @wgseaton!

The first recommendation we have is to perform a factory reset on your gateway. This can be done by following these steps:

• Locate the small red button & pinhole on the lower rear of the gateway
• Depress for ~15 seconds

WARNING: This will return all gateway settings to a default state. Any custom Wi-Fi passwords, Wi-Fi names, SSID, Static IP, and Port Forwarding rules will be lost. Settings can be restored, scroll to accepted solutions in the article above for steps to restore settings.

Once you've done that, we suggest setting up port forwarding once more for your camera system. You'll want to make sure to use the drop down menu in the article above to select your gateway model. This will help to ensure that you're following the correct steps for set up. 

Let us know how it goes!

Lacey, AT&T Community Specialist 

Reset device.

When back online, verified I could ping the unit by enabling and disabling external ICMP response.

Put pinholes back in and still did not work.

Verified port and host were valid and responding.

Hi there, wgseaton. We understand that you are unable to establish your pinholes through the AT&T firewall for your camera system.

Let's probe just a bit more about your equipment set-up. We do know that you have a Pace 5268AC and that is what you are trying to do the pinholes on. Do you have any other devices, such as another router or firewall or switch?  The reason why we ask that is the correct protocol is that you need to do DMZ+ and then do the pin holing or port forwarding on the other device. To help you further along, here are the steps needed: 

1. Go to your gateway settings and choose Settings.
2. Scroll to Software Version. If you have version 11.1.0.xxxx or above, continue with these steps. If you have earlier versions, you don’t need to do anything else.
3. Select LAN and then LAN IP Address Allocation.
4. Scroll to Devices. Check Device Status for one identified as DMZ device.
5. In Address Assignment, choose Private from Pool or Specific Private IP.
6. Select the Firewall tab and scroll to Edit firewall settings for this computer.
7. Choose Add a new user-defined application. You’ll see the Firewall Application Profile Definition window.
8. In Application Profile Name, enter All UDP and do the following:
   • In Protocol, select UDP.
   • In Port, enter 1 in From and 50999 in To.
   • Select Add to List and then Back.
9. In Application Profile Name, enter All TCP and do the following:
   • In Protocol, select TCP.
   • In Port, enter 1 in From and 50999 in To.
   • Select Add to List and then Back.
10. In Select a computer, choose the device you want to forward all traffic to. Or, enter the IP address of the device.
11. In Hosted Applications, select All UDP and All TCP, then Add them.
12. Select Save.

Also, have you considered static IP addresses? Most cameras, at least the cameras that need the DVR of the camera system to be remotely viewed, can be done with static IP's? What that means is that you will use a specific IP address to remotely view the camera and the DVR all from the that static IP address instead of pin holing. 

Our last option is that the router itself, could be at the end of its shelf life. Normally that means that router itself needs to be replaced. If you think that could be what is going on, we most certainly help you replace the router. Just let us know and we wll take care of it for you.

Looking forward speaking with you soon. 

Matthew, AT&T Community Specialist

The version is 11.14.1.533851-att

The instructions were all not valid.

I do not have a DMZ device.

I did create ALL TCP and All UDP

I got an warning doing 1-50999 when saving Warning ATT TV will stop working, they do not have ATT TV

I got an error selecting ALL TCP or ALL UDP with ports 1-50999 that it was blocking port 3479.

I can not find when port3479 is assigned, picture below is my allocation

I had to change the port range to start at 4000 to apply.

The port I need is 37777.

Still Does not work.

We appear to have a fixed ATT IP.

The target is fixed at 192.168.1.111.

This is a new replacement ATT Router we just installed last week.  Port forwarding on the old one quit working last year.

Could there be an internal ATT block on all unsolicited  inbound port connections?

Thanks for coming back, wgseaton. Let's dig just a bit deeper because there is something that is unclear.

Everything according to the screenshot looks correct. We are not sure why it is not working. You have followed the correct protocol from at least the AT&T point of view.  

Prior to this event, what were you doing with your cameras? Were you trying to view them remotely? We need to know what your end goal is, so we can drive this to a proper resolution. 

In order for us to get to that resolution, we are going to move this conversation to our AT&T Direct Message space. After our next message has been sent, in the upper right of this thread you will see a chat icon, next to a bell icon. 

If you are unable to view the message right away, please log out of your forums account and back in. 

Looking forward to speaking with you more. 

Matthew, AT&T Community Specialist

Matthew,

I am new to ATT Forum and did not know this was move to direct message service.  I found where you reached out but I did not know to answer.

This had been working until a little over a year ago.

When we got the replacement a few weeks ago, this worked after install and configuring.  

We declared success and new unit must have fixed something.

Two days later when they went to use it, it did not work and has not since.  It could have not been working a few hours later or the next day for all we know.

Glenn