Motorola NVG589 port forwarding

And FWIW, in IE I get a "Failed to parse domain" error message when I log in remotely, either via the DDNS or the actual external IP address.

In Firefox or Chrome I get a prompt to allow QuickTime to run and then I choose yes. It appears to try and load the QuickTime plugin in the browser but nothing ever shows.

Q-See claims this to be an AT&T port problem. I'm sure the AT&T tech guy will come on here soon and tell me that's not the case, though I spent hours on the phone of my life that I can't get back now only to have their support guy give up and tell me to call AT&T to open the port.

Go here:

https://forums.att.com/t5/Residential-Gateway/Motorola-NVG589-Port-Forwarding-instructions/m-p/4096200#M16099

There is clearly an issue with port forwarding on the NVG589 router.  I have an TV-IP651W camera, which I could remotel access via timewarner and ATT DSL using own router.  I upgraded from DSL to Uverse and they installed the NVG589 router.   Access to the camera interface is via port 8080.  Per the manual, I setup configured the router to forward port 8080 to the camera.  I verfied the port 8080 was open using canyouseeme.org

Attempting to access the camera produced the login screen and portions of the page rendered.  

Attemps to reload the page produce slightly different results each time (more or few images load). I can access the camera via the local network. As I stated above, I previously accessed the same camera via via timewarner and ATT DSL (both with lower bandwidth limits then I currently have with uverse). It is clear the the NVG589 is not performing correctly.   This is a big problem for me.     

---

@redraidersrule wrote:

 

We're all in the same boat. They close the UDP port, but the http or tcp one at 8080 can  be open.

 

 

Huh?  What?  

---

@JefferMC wrote:

---

@redraidersrule wrote:

 

We're all in the same boat. They close the UDP port, but the http or tcp one at 8080 can  be open.

 

 

Huh?  What?  

---

What do you mean huh? What?

Those of us who are encountering port forwarding problems are in the same boat.

Q-See expressly told me that the UDP port was closed, which any diagnostics run confirms. i.e. canyouseeme.org, the fact that the camera or plug-in doesn't work, etc.

I don't have this NVG model myself, but rather an HVG3810 model or some older 2WIRE model.

This doesn't make sense to you? That's the way it's working (or rather, not).

UDP and TCP ports may be opened or closed separately.   There is no such thing as a model 3810 (3800, 3801 maybe).  Would you care to post a screenshot of your FW configuration page?

First, this Arris device is really obnoxious and I've wasted a lot of time trying to get it working properly with a Tenvis security cam.  That said, I was successful using the NAT/gaming port forwarding.  lapsmith's post helped with some ideas.  I'll try to be concrete with info.

My issue was that I could not get the Tenvis webcam accessible from outside the modem (Arris) - I would validate this at http://www.canyouseeme.org/ (port checker).  Here are things I had to do:

* In my Tenvis configuration, I set it to a static IP (unchecked DHCP).  Pick a higher IP #, which will become apparent below.

** Also ensure the default gateway and DNS server is correct - for this modem it's 192.168.1.254. Many default devices will have this set to 192.168.1.1 so doublecheck.  W/o this, DDNS will fail (though that doesn't affect f/w accessibility).

* On the modem config, under Home Network->Subnets and DHCP, set the DHCPv4 Start and End range so that your device IP (from bullet 1) is outside/above the end of the range.  e.g. set range from .64 to .100 and have your device set to .115.

* After that, retest that your device is acquiring the static IP by restarting your device (in my case the Tenvis).  Under Device->Device List you can clear the list the scan - your device should appear as "static" next to Allocation.  If not, you didn't set your device properly.

* Now under Firewall->NAT/Gaming you should add your "custom service" then go back and add your hosted application.  This is discussed several times in other posts here so won't rehash (plus if you're reading this thread you've probably tried that a bunch of times already).

*Now test again using http://www.canyouseeme.org/, making sure to enter in the right port from the prior step.  Note this website derives your modem's public IP automatically.

This worked for me.  I haven't thought about "why" but it seems like a bug with the firewall and DHCP allocations.

I had also tried both passthrough and default server which failed miserably - again there's no reason for those to fail so badly.  I did not futz with another router fyi.

Hth, good luck folks.

---

@playactn wrote:

First, this Arris device is really obnoxious and I've wasted a lot of time trying to get it working properly with a Tenvis security cam.  That said, I was successful using the NAT/gaming port forwarding.  lapsmith's post helped with some ideas.  I'll try to be concrete with info.

 

My issue was that I could not get the Tenvis webcam accessible from outside the modem (Arris) - I would validate this at http://www.canyouseeme.org/ (port checker).  Here are things I had to do:

 

* In my Tenvis configuration, I set it to a static IP (unchecked DHCP).  Pick a higher IP #, which will become apparent below.

** Also ensure the default gateway and DNS server is correct - for this modem it's 192.168.1.254. Many default devices will have this set to 192.168.1.1 so doublecheck.  W/o this, DDNS will fail (though that doesn't affect f/w accessibility).

* On the modem config, under Home Network->Subnets and DHCP, set the DHCPv4 Start and End range so that your device IP (from bullet 1) is outside/above the end of the range.  e.g. set range from .64 to .100 and have your device set to .115.

* After that, retest that your device is acquiring the static IP by restarting your device (in my case the Tenvis).  Under Device->Device List you can clear the list the scan - your device should appear as "static" next to Allocation.  If not, you didn't set your device properly.

* Now under Firewall->NAT/Gaming you should add your "custom service" then go back and add your hosted application.  This is discussed several times in other posts here so won't rehash (plus if you're reading this thread you've probably tried that a bunch of times already).

*Now test again using http://www.canyouseeme.org/, making sure to enter in the right port from the prior step.  Note this website derives your modem's public IP automatically.

 

This worked for me.  I haven't thought about "why" but it seems like a bug with the firewall and DHCP allocations.

 

I had also tried both passthrough and default server which failed miserably - again there's no reason for those to fail so badly.  I did not futz with another router fyi.

 

Hth, good luck folks.

 

 

---

I don't see anything in here that is unexpected:

• You have to tell the camera where the gateway (router) is.  AT&T has chosen to default to 192.168.1.254, while the camera defaults to expecting 192.168.1.1; either could be changed to make the other happy.  Change the camera is the simplest.
• When you assign the device a static address, you need to put that address outside the range of addresses provided by the gateway via DHCP so that there is no conflict.  
• You have to tell the Gateway that external requests for a given port need to be directed to the camera's IP address.  Otherwise it doesn't know what to do with it.
• I do not know why you had to make the device address static vs DHCP issued, other than it may make the process of setting up the port mapping easier.
• Passthrough is not intended for this situation, though I don't know why it wouldn't work.
• Default server should also work, but since you still need to create rules to pass traffic, so I don't see the point in doing so vs. Port Forwarding the port the camera needs.

---

@JefferMC wrote:

UDP and TCP ports may be opened or closed separately.   There is no such thing as a model 3810 (3800, 3801 maybe).  Would you care to post a screenshot of your FW configuration page?

 

---

Sure. Yeah, it's a 3800HGV-B - sorry! I'm usually not at home when replying to this and didn't have it to look at right away!

Is this enough? Or do you need a screen shot of other settings?