Solved One specific website not opening - connection times out

[AliceE]

Hi all,
I've been trying to solve this problem for a few hours now and I think I'm going crazy.

I'm trying to log into the following website: MyProgrammingLab | Pearson
It says it's connecting for a bit, and then the connection times out (the URL changes to MyProgrammingLab | Pearson).

What I've tried doing so far:
1. Trying on different browsers (firefox and IE) - same problem.
2. Tried on other devices (cellphone via WiFi connection + other computer on network) - it worked there, so I'm thinking this isn't a network issue.
3. Flushed DNS
4. netsh winsock reset catalog, netsh int ipv4 reset reset.log, netsh int ipv6 reset reset.log
5. Windows update, clearing all possible cache and temporary files, disabling antivirus and all of that popular stuff.
6. Restarted the computer (several times, fun)
7. Ping and tracert both work for pearson.turingscraft.com; trying to enter the IP that shows up for tracert also time outs.
8. Checked if NIC drivers are up to date (they are).
9. Updated Java.
10. Checked the hosts file.
11. Connected to a cellphone hotspot and tried logging into the website - still nothing (does work on the phone itself).

It drives me crazy that I can't figure this out, and I can't seem to find anything new in my google searches. Help.

 

[Callender]

There's a redirect on that site. Where to and the URL redirected to might depend upon where you live. It's using akamai server which is a content distribution network.

Basically try using a browser with Geolocation enabled. Don't use a proxy. Swith off any script blocker or other types of content blocker. See if you get the same results.

​

 

[AliceE]

Oh, it redirects me to this URL:

https://pearson.turingscraft.com/codelab/jsp/pearson/auth.jsp

It changed in the original post to the title text, my bad. My chrome's location option is enabled - the site didn't ask for my location at no point, though. My phone and the other computer I tried on didn't have any different location settings, either.

 

[AliceE]

If anyone's interested, the issue did turn out to be a DNS one. I didn't even think it's possible for only one computer on the network to have problems with the ISP DNS (while all other devices work fine), but I guess we learn something new everyday lol. Changing the DNS to Google's DNS fixed the issue.