Port Forward a security DVR with new xfinity

[securetech94 0]

I have the Xfinity Arris TG852G 3.0. and I'm having trouble opening ports for my DVRs.

 

When I go to the Admin tool (10.0.0.1) and click to ADD SERVICE and input all the DVR info with the ports needed; when I click SAVE, It wouldn't let me proceed because it doesn't let me Port Forward a device until is listed under connected devices. For some reason it doesn't show on the Connected devises even though is connected with a ethernet cable straight to the modem/router.

 

When I click SAVE it gives me a Alert Code: Server IP addr is not in valid range: 10.0.0.[2~254]

[securetech94 0]

I have the Xfinity Arris TG852G 3.0. and I'm having trouble opening ports for my DVRs.

 

When I go to the Admin tool (10.0.0.1) and click to ADD SERVICE and input all the DVR info with the ports needed; when I click SAVE, It wouldn't let me proceed because it doesn't let me Port Forward a device until is listed under connected devices. For some reason it doesn't show on the Connected devises even though is connected with a ethernet cable straight to the modem/router.

 

When I click SAVE it gives me a Alert Code: Server IP addr is not in valid range: 10.0.0.[2~254]

[Securame 0]

So your router is 10.0.0.1 and you want it to forward a port to IP 192.168.1.122...?

 

If your network is 10.x.x.x you need to change the DVR's IP to something on the same subnet. The router is telling you that the DVR's IP is not on the valid range; it should be something between 10.0.0.2 and 10.0.0.254.

[securetech94 0]

You're totally right. I wish I would think a little better next time.

 

Thanks!!

 

So your router is 10.0.0.1 and you want it to forward a port to IP 192.168.1.122...?

 

If your network is 10.x.x.x you need to change the DVR's IP to something on the same subnet. The router is telling you that the DVR's IP is not on the valid range; it should be something between 10.0.0.2 and 10.0.0.254.

[Numb-nuts 1]

You weren't to know were you? Mistakes are how we learn. The message is kind of assuming you are in the correct subnet so the message (in your case) doesn't really give you enough of a clue where you were going astray.