I've been facing a problem where I can't connect to specific websites on my computer, although everything else, like Google, Netflix, and YouTube, works perfectly. It's strange because the same websites load fine on my phone and other devices. My internet speed is decent, about 120 Mbps down and 20 Mbps up, so I doubt it's a speed issue. For example, I used to access limitlessrust.com without any problem just a week ago, but now it's inaccessible. I use a Linksys WUSB6300 USB adapter for Wi-Fi since my motherboard doesn't support it, but I don't think the adapter is the culprit.
Here's what I've tried to fix the issue: flushing DNS, setting manual DNS servers, clearing my browser cache, trying different USB ports for the adapter, connecting directly to the router, running Windows network troubleshooter, switching browsers, disabling IPv6 on the adapter, adjusting firewall settings, and changing my network profile. Nothing seems to work. Any suggestions would be greatly appreciated!
5 Answers
Can you ping limitlessrust.com? Also, switch to the DNS server 1.1.1.1 and see if that helps you access the site.
What’s the Virtualbox host-only connection for? If it’s not in use, try disabling it and see if that improves the situation.
I disabled that connection, but it didn't change anything.
You might want to run an 'ipconfig /all' and share the results. It can give us more insight into your network settings.
Here's my output: [link to image]. What do you think?
Have you tried visiting the IP address for limitlessrust.com directly? It's 104.21.48.1. Sometimes that helps isolate connection issues.
I tried that, but it said refused to connect again.
Can you access other websites without issues? Also, ensure that no VPN is active and double-check any web protection services like Malwarebytes that might be interfering.
I can ping other sites just fine. I don't have a VPN on right now. I did disable web protection on Malwarebytes since it was blocking too much, and my browser settings are minimal.
Pinging didn't work, and switching DNS didn't help either. [link to image].