Problem with opening ports resolved.
Problem with opening ports resolved.
Hello everyone, I'm sorry for the English issues. I tried changing my ISP modem to see if it would help, but nothing worked. The port forwarding rule is enabled in the DMZ, and I've talked to several ISP reps. Now I'm getting the same public IP address as before. Thanks in advance!
Two things: 1. Don't turn on DMZ unless you have a very specific reason to do so. It's dangerous if you don't know what you're doing. 2. The ports are forwarded, but do you actually have a running server listening on those ports? If not, incoming requests are rejected and will appear as if they're closed.
Internet access in your house comes from various sources such as fiber, coaxial, DSL, LTE, or through a combination of these. Your setup involves checking if a router is connected to the modem and whether it's a single device or a combo unit. Be aware of potential issues like double NAT configurations.
I usually configure the ISP router as a bridge, which connects to my private router: Synology RT2600AC. For troubleshooting this issue, I’m using my ISP router as the router and my Synology as an access point. When I switch to my Synology router with ISP set to bridging, the ISP modem gets a non-private IP address: 100.X.X.X/20 (carrier-grade NAT). My DG for the Synology router is the ISP modem. I’ve enabled port forwarding and set up the firewall role for the desired access port, but nothing happens. Even with my ISP router active, I can’t open the ports. Do you think my ISP is using two NATs for this? Thanks for your reply. 1. I’d suggest adding a DMZ in my troubleshooting steps. 2. Yes, your monitor shows an app listening on the same port I’m trying to reach. Thanks for your response.
If your ISP puts you behind NAT64-CGN then Port Forwarding is basically a non-option but I've not heard of this with a Coax based WAN. It's most common with LTE connections. If you can't Port Forward when directly connected to the main modem/router with Bridged Mode disabled then you'll have to call your ISP and ask if it's even an option. Most of the time when it's something that's easily fixable it's either because of a Double NAT or user mis-configuration. You've eliminated Double NAT as even being a possibility. I assume you've configured Port Forwarding correctly (it's not complicated). May need to talk to them. If they have you behind their own Router then you're basically SOL. Have to get a different ISP.
I noticed I spoke with four different people, but none provided useful answers or guidance. It seems switching ISPs might be necessary. Thank you for your support—I really value it. Have a great day. This port range is what I was told should be open: 135-1124.
I'm just a bit slow, but I need three ports open—SSL VPN for Synology, web login VPN, and RDP from anywhere. All within a specific range.
Take the necessary steps seriously. Setting ports open on your network is similar to leaving your front door unattended. Whatever comes through, you must ensure someone is ready to welcome them. Opening a wide range of ports is akin to leaving every door, window, and vent in your home exposed. The server these ports connect to becomes exposed to potential attacks across all 990 ports. If a vulnerable protocol exists on any of those ports, the server could be compromised without cause. Port Forwarding acts as an exception list within your router’s firewall. Trying to bypass all 990 entries is risky. Only keep the ones you truly need.