Shop Now, Avoid Delays - Get Our Best Holiday Deals!
moygrego's profile

Voyager

 • 

2 Messages

Wed, Jun 11, 2014 2:27 AM

Remote security camera - Not port forward issue, please read

I am having a frustrating problem connecting to my remote security cameras (ISP is not AT&T Uverse) from my home network (AT&T Uverse). Any other network I connect from works fine - wireless hotspot, phone hotspot, neighbors wireless. I know how to configure port forwards and have verified that they are configured correctly by testing on the other networks. Previous to AT&T Uverse I had AT&T DSL and it worked fine. So now the only difference is the Uverse and an NVG510 device.

 

The cameras are Honeywell and port 8000 is default. The port has since been changed to 4000. To date I have done the following:

  1. Called tech support. Agent did a remote login and added a custom service with global port: 8000, base host port: 800, protocol: both. He did not assign the custom service to a device - he only created it. When asked about an explanation for what he did he seemed hesitant and did not provide any detail. This change allowed the cameras to be used for about a week before returning to the current non-working state. 
  2. Changed port to 4000 because there was some information suggesting AT&T uses port 8000 for other applications. This change did not fix the problem.
  3. Bridged NVG510 to Cisco E3200 to eliminate the NVG510 router as the source of the problem. This change did not fix the problem.
  4. Repeated calls to tech support who now insist that the problem is either port forwarding or not within the scope of their support. They want me to pay for Connectech service.

I've done a lot of searching on this forum and there are a lot of topics that apply to the case where the cameras are behind the NVG510 and port forwarding is the issue - this doesn't apply to me as I see it. I found only one or two topics where someone had a similar issue to mine, but they had few responses and zero resolutions. 

 

Does anyone have similar issues or hopefully a fix?

Contributor

 • 

1 Message

7 y ago

An option to try would be to purchase static IP and setup one of the 5 static ip's directly on the device.  This would essentially open all ports to the device and ensure you dont have an issue with any ports.

After purchasing a static IP block you would want to.....

Reset Your RG (Press the reset button on the back of the NVG for more than 30 seconds)

Once the NVG has solid green sync/service, connect to the device
Browse to 192.168.1.254
Click Home Network
Click Subnet & DHCP
Under the Public Subnet Section update the following:
>>>>>Public Subnet Enable: On

>>>>>Public IPv4 Address: enter from your static block
>>>>>Public Subnet: 255.255.255.248
>>>>>DHCPv4 Start Addres: enter your first usable static ip (first of the 5 usable IPs)
>>>>>DHCPv4 End Address: enter your last usable static ip (last of the 5 usable IPs)
>>>>>Primarty DHCP Pool: Private

Click Save (ensure you receieve a message in red saying settings saved)

Next step is to hard code one of the 5 usable IPS on the camera system (make sure the camera system is connected directly to the NVG).  this will intern open all ports to the device and make it a "open connection" to the device and ensure there isnt a "port forwarding issue".

 

Hope this helps

Voyager

 • 

2 Messages

7 y ago

The cameras are not connected to the NVG510.

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