> The Port Forwarding service, is not working, [...]
Which you determined how, exactly?
> [...] recently i changed to this device, [...]
"changed" from what? Same ISP, or different? Same public IP address
or different?
> [...] i have my service hosted in 192.168.0.2 and work perfectly,
> [...]
What is your "my service"? "work" how, exactly? In your
(unspecified) client, were you specifying the LAN IP address of the
server? What happens if you specify the WAN/Internet IP address of the
CG3000Dv2?
> img3.png
I can't see the server IP address in that picture. Is it
"192.168.0.2"? Is that a static or reserved dynamic address, or are you
trusting in luck to keep the server LAN IP address fixed?
> [...] i can see my website in my phone that is conected in the same
> network. [...]
Is your "my website" related to your "my service"?
> [...] But using my public address, i got connection timeout error
> after waiting some seconds.
"using" how, exactly? What is your "my public address"? ("a.b" out
of "a.b.c.d" would be enough.)
Does your "my public address" match the WAN/Internet IP address of
the CG3000Dv2? (ADVANCED > ADVANCED Home : Internet Port : Internet IP
Address)
The usual problems with this stuff are:
1. Wrong external IP address (different from the port-forwarding
router's WAN/Internet IP address). (An intermediate NAT router, for
example, could cause this. Or an ISP using carrier-grade NAT to
conserve IPv4 addresses.)
2. Bad port-forwarding rule (wrong port(s), wrong target address --
including a wandering target).
3. Server not listening on the port-forwarding target system.
4. External influences: ISP blocking, other firewalls, ...
Item 3 might be covered, but not enough information to decide on the
others.
