Port forwarding - Device stuck with 10.0.0.2 ip

[findanish]

Hey there,

Really need some assistance here, Shaw tech support is dead end because they dont support port forwarding services but they still decided to move the port forwarding features over a webpage.

I'm trying to set up port forward for a device that has 10.0.0.52 IP in the connected device area within the Bluecurve modem but when I'm trying to open a port from internet.shaw.ca, it binds it with 10.0.0.2 ip and shows No associated device. It does show the right ip (10.0.0.52) everywhere. I'm out of ideas, I've reset the modem 5 times to no avail, these port forwards just come back even after a reset. 

[mdk]

@findanish -- [Shaw] donut support port-forwarding services, but they still decided to move the port-forwarding features over a webpage.

That was a decision forced onto Shaw by Comcast, who do all the software development for the BlueCurve.

> I've reset the modem 5 times to no avail, these port forwards just come back even after a reset. 

How did you do the "reset"? Power-off/power-on the modem? Used the "pin-hole reset" method? Used that web-site?

[CanEHdianboi]

Im having the same issue, did you end up figuring it out? 

[electric]

Same deal here, I asked support, they don't help.  If you look up the "no associated device" term you will see Xfinity customers with the same problem trying to setup port forwards via the web interface with the same issue.  One of their suggestions was to try in the app, i did, didn't work.  If I get get this to work I'll have to change ISP as I need this to work. lame they won't trouble shoot their own software.

[mdk]

@electric -- if you switch the cable-modem to "bridged" mode, and you get Shaw to provision the cable-modem with one additional "public" IP-address, then one "public" IP-address can be allocated to the computer that you want as the target of your port-forwarding. The other "public" IP-address can be assigned to the WAN port on a WiFi-capable router that you can own and that you can fully manage -- it will act as a DHCP-server for your wired/wireless devices. What you lose by "bridging" is the hidden WiFi networks that the Shaw cable-modem has been broadcasting to your other Shaw devices (repeater, remote TV box).

Or, since "10.0.0.2" seems to work, can you change the IP-address of the "target" computer from 10.0.0.25 to 10.0.0.2 ?