Available Now: Buy the new iPhone 14, iPhone 14 Pro and iPhone 14 Pro Max from AT&T!
Need help with your equipment?
J

New Member

 • 

3 Messages

Mon, Jan 31, 2022 6:55 PM

Unable to see Foscam cameras remotely on Pace 5268AC, internally all is well.

After several years without issues, all external access to my 8 various Foscam cameras and Synology NAS stopped working abruptly on my 2 iPhone apps as well as access remotely to the camera’s/NAS web interface.   My entire network was powered off and restarted.  Multiple calls to ATT Technical Support resulted in ATT swapping out my modem (for the same model modem) and I readded all port-forwarding entries.  NSLOOKUP and TRACERT confirm my Public IP Address, which matches my NO-IP DDNS address.  All cameras work internally via port forwarding, but when checking the ports using my Public WAN Address with such tools as (canyouseeme.org, whatismyipaddress.com, ipchecktoo.com) they all show the ports as being closed)!  ATT states that everything looks fine and claim they have no tools to verify the status of my closed ports.  I am embarrassed to state how much time I’ve spent on this issue.  Any suggestions would be greatly appreciated.  

JefferMC

ACE - Expert

 • 

29.9K Messages

8分前

A recent update to the 5268AC has created some unexpected (at least for the customer) issues with Port Forwarding.

Doing a factory reset and setting your Port Forwards back up using device naming (instead of using static IP address) seems to be solving the issue for most 5268AC users who have reported this.

New Member

 • 

3 Messages

8分前

Thank you JefferMC for taking the time to respond.  Unfortunately, I do not know what you mean by using 'device naming (instead of using static IP addresses).  Could you please elaborate?  

JefferMC

ACE - Expert

 • 

29.9K Messages

8分前

Since I don't have a 5268AC myself, I'm not intimately familiar with the User Interface for port forwarding.  Here is a rather long thread discussing the issue:

https://forums.att.com/conversations/att-internet-equipment/recent-att-firmware-upgrades-breaking-application-pinholes/5efbf4bd72a09d42a31b0215

The best summary, from @george1077 is:

From what I’ve seen, it appears that everyone having this problem, myself included, used a manually entered IP address to configure the pinhole. If you want to get this working again, assign your pinhole configuration using a selected device instead of a manually entered IP address. This may require switching your device to a DHCP configuration for its IP address, but appears to work for everyone that’s done it. 

New Member

 • 

3 Messages

8分前

JefferMC, first, thank you for pointing me in the right direction.  I'm relieved that I'm not the only one with a 5268AC with FW ver. 11.14.1.533851-att with this issue as lead to believe by ATT Technical Support.  I'm beyond disappointed in them for not knowing the issues as described by my detailed findings.  I too was promised a new (different model) modem, but was sent the same 5268AC which brought down the same faulty FW.  I used the "unknownMACADDRESS" and associated the port-forwarding entry with success!  Now the port is also opened as noted in Portchecktool.com.  I don't know the ultimate resolution, as this is still an issue, nor how long this will take to resolve as you noted.  Again, I am truly relieved to know I'm not on an island (with internet access) by myself.      

I'll wait to see what happens.  If you're ever in Miami, beers are on me.

Thank you again,

Jack 

JefferMC

ACE - Expert

 • 

29.9K Messages

8分前

Yeah, for a communications company, AT&T doesn't communicate very well, inside or outside.  But yeah, quite a few people here and on DSLReports stumbled across this new "feature" of the 5268AC firmware.

Need help?
New to AT&T Community?
New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.