I read another post from three months ago where someone had a similar issue, although it was closed, so there weren't that many comments. The last comment said most of this community would be able to solve the issue if OP would have posted their site.

So here's mine: www.localclientsnow.com

Situation: it seems to only open on certain phones or when you're on a VPN.

- I can open it on my phone with no VPN.
- But I can't open it on my computer unless I have the VPN on.

I've never had this issue where it says it can't connect. Claude keeps telling me my ISP has my site blocked. It wasn't blocked like an hour and a half ago, though.

----------------------------
What I did leading up to this:
1. A little context of what happened prior to this. I was working with Claude like I always do, except I'm at 99% of my weekly limit, so I switched over to Codex in the terminal.
2. I thought Codex was about to make some simple changes and push and merge it live.
3. I went to load my site, and ever since then, it's had a connection error.

* Although I don't really relate it to Codex at all because my friend could not open it earlier today from the same error. We thought that his VPN or security system was blocking our site.

I just bought this domain from Porkbun in the last 48 hours, so I'm thinking maybe it's because of that. Although I own over 50 domains and I've built over a hundred client websites and never had this happen once.

ANY HELP IS APPRECIATED!

Hi all. I'm new to DOCSIS, working under this, and I was wondering if anyone could tell me what are some of the main things/topics that I have to know definitely in order to start. Anything that would actually help me understand the HFC/DOCSIS work? Thank you

Mummy ml m

I don't know a lot about networks so some things may be weirdly/inaccurately described.

Some time ago issues started for ethernet connection for all my roommates except one (Brad, good with computer stuff). Connection is really slow for us sometimes and we aren't sure why. I've tried logging to modem admin page and all looks good however Brads computer does not show up in device list despite him using the ethernet cable. I've checked the modem and his cable was the only one that had green light on while the rest had yellow ones (i've read that light color indicates quality of the connection?). There are no priority settings on modem settings page, and it's not in bridge mode (Residential Gateway Enabled). Is it possible that Brad is hogging all the internet somehow?

(we are suspicius because he did something before cause firewall changed to maximum from typical)

how can i fix this ? it’s supposed to be a option to pick what connection to share to but hasn’t shown since the first time i did it

Why is the internet not free,the community internet is need if you have a server you install a program then you have a private connection.

Hi All,

Yesterday we ran into a packet loss and jitter issue between NTT and Arelion. NTT NOC confirmed it was congestion between them and Arelion and gave a boiler tempalte response about them wanting to work on increasing capacity etc. and if anyone is a client of Arelion to reach out directly. NTT has always been good for us. I came across [https://www.reddit.com/r/networking/comments/1i90gy4/arelion\\_have\\_depeered\\_ntt\\_in\\_europe/\](https://www.reddit.com/r/networking/comments/1i90gy4/arelion_have_depeered_ntt_in_europe/) and that post makes it seem like NTT isn't the one playing nice.

We all know about Cogent not playing nice with HE (and I think at one point Google as well) which is why I wont ever use their service unless they are the only option. Whenever their sales reach out my response is the same "have you worked out your issues with HE yet?". My question/frustration/issue is with an ISP telling you that they are connecting you to the internet when they are not. If I want to use Cogent for v6 then I MUST get another ISP that can get to HE or I don't have full internet routing. In such cases do you just "eat it" and get multiple uplinks or do you put pressure on your upstreams? My clients don't care who is at fault they simply want their internet to work. I am very much against regulation but it's 2026. There should be a standard as to whom is in the Tier1 club and the big boys should be forced to work out their differences.

When I try to Telnet into my Mr1100 the screens pop-up and I try to enter AT command it gives me timeout error.

How do i fix this ? was working the first time then when i turn pc back on my adapter wasn’t working no more . The pc itself is getting internet but i’m tryna internet share to something else and it’s not working.

Disclosure: I'm on the marketing team at No-IP. We put together a guide for anyone stuck on this problem, and I'd like to hear how others here handle it. Our solution is No-IP Public Tunnels. Cloudflare Tunnel, Tailscale, ngrok and others use the same outbound model.

One of the most common questions we see: "I forwarded the port, the rule is correct, and it still doesn't work." Usually it comes down to one of these:

• CGNAT. Your ISP shares one public IP across many customers. No router setting fixes it. It's common on cellular, satellite and a lot of residential fiber.
• A locked router. ISP combo units that hide or remove the port forwarding page.
• Double NAT. An ISP gateway sitting in front of your own router.
• You shouldn't open a port anyway. A client's security baseline or change process rules out inbound rules, or nobody wants to own that rule long term.

Quick CGNAT check: compare the WAN IP on your router's status page with what any "what's my IP" site shows. If they don't match, you're behind carrier NAT. A WAN address in 100.64.0.0/10 gives it away.

The workaround is to flip the direction. Instead of waiting for inbound connections, a client on the device opens an encrypted outbound connection to a tunnel service and keeps it open. Requests come back over that connection. No open port, no router access, no call to the ISP. Outbound traffic is almost always allowed, so this works where inbound doesn't.

Port forwarding is still fine if all three are true: you have a real public IP, you control the router, and someone will maintain the rule. If any of those is a no, a reverse tunnel is the better fit.

A tunnel doesn't replace the basics: put authentication on whatever you expose, keep it patched, and don't post the access URL publicly.

Curious what others are doing:

1. Has your ISP moved you to CGNAT? What did you switch to?
2. If you're still port forwarding, how do you keep track of those rules over time?

If you're trying to fix this right now, the full guide walks through how to diagnose which problem you have, how to pick between port forwarding and a tunnel, and where Dynamic DNS fits in: https://blog.noip.com/how-to-get-remote-access-when-your-network-has-no-way-in

Hi good afternoon all and hope you are doing well.

Currently I am facing one issue when I ping the ip address of other devices in my terminal it's coming the destination host is unreachable. even with my biometric device (give a static ip) same result. please give any solution, i beginner so i don't have much knowledge. iam using Tp link router.

I've been building NetPulse, a lightweight Android app for checking your network quality. It has a Material 3 interface with light and dark themes.

What works in v0.1.0-beta:

- Live ICMP ping monitor with Start / Stop

- Latency, min / average / max, jitter and packet loss over the last 300 samples

- Only two permissions (INTERNET and ACCESS_NETWORK_STATE), no ads, no analytics, nothing uploaded

What's coming next: a DNS benchmark (Cloudflare, Google, Quad9, Control D) measured separately from ping, latency charts, test history and CSV export.

The app uses the system ping tool, so some phones may block it. That's the main thing I want to find out: does it work on your device? Please tell me your phone brand and Android version, and any bugs or features you'd like to see.

Beta APK: https://github.com/Mireli5656/NetPulse/releases/tag/v0.1.0-beta

Source code: https://github.com/Mireli5656/NetPulse

The beta is signed with a debug key, so uninstall any earlier NetPulse build before installing it.

Thanks for trying it!

A simple 20-second modem power cycle improves performance and may resolve other problems with all devices regardless their platforms, operating systems, network complexity and regardless how they connected to the network either via Ethernet cable, or wirelessly.

I would recommend to perform a modem power cycle periodically depending on the network volume usage (for example, once a month, or weekly). This way would prevent many problems to occur including completely unexpected ones.

A simple 20-second modem power cycle flushes out hidden memory leaks, speeds up performance, and resolves a wide variety of underlying network problems. This applies to all devices regardless of their platform, operating system, or network complexity—and it works equally well whether your machines are hardwired via an Ethernet cable or connected wirelessly over Wi-Fi.

Instead of waiting for an internet crash or a strange website login error to happen, it is highly effective to treat your gateway like any other computer and maintain it proactively.

Why a Full Power Cycle Works Universally:

• Shared Core Engine: All data packets (wired and wireless) land in the exact same internal processor. Power-cycling clears memory leaks at the source.
• NAT Table Optimization: It completely wipes out thousands of stale, dead connection tags accumulated from weeks of browsing, reducing latency.
• Zero-Latency DNS: It forces the modem to request a fresh, uncorrupted directory map from your internet provider, instantly fixing unexpected connection blocks.
• Wireless Channel Clean up: Upon reboot, the modem automatically scans the airwaves to select the cleanest, less-congested broadcast channel available.

Recommended Proactive Maintenance Schedule:

• Weekly Reset: Highly recommended if your household runs heavy daily data volume, multiple computers, or intensive virtual applications like Android emulators.
• Monthly Reset: A perfect baseline for standard households focused primarily on everyday web browsing, checking weekly accounts, and casual streaming.

Making this quick reset a regular habit based on your network volume completely prevents a massive amount of unexpected network problems from ever forming in the first place.