Some Sites Unavailable Through Airport Extreme

Question

Level 1

101 points

Some Sites Unavailable Through Airport Extreme

I am unable to access some pages when using the latest Airport Extreme (v 7.7.3).

One example is: https://ajax.googleapis.com/ajax/libs/angularjs/1.3.16/angular.js

When connected through Airport Extreme, it tries to load the page, then it times out. It happens on all my Macs, as well as on a PC running W7. All browsers, with cleaned cache and cookies. It started a couple of days ago, without any (known to me) changes made to the configuration. It happens to maybe 10% to 20% of the pages I've tried.

Bypassing the Airport Extreme and connecting directly to the cable modem (TWC) loads the pages fine, both with wired and wireless connections.

I was just getting happier with the Airport Extreme, as the frequent connection drops were fixed a couple of months ago. And now this 😟

Anyone with any ideas?

Posted on Jun 25, 2015 9:45 PM

Reply

Answer 1

MadisonP

Level 5

4,844 points

Jun 25, 2015 10:50 PM in response to Jon Blank

Hi, Jon.

My first thought would be a corrupt routing table/DNS entry in the Airport's memory. Have you tried restoring it to factory defaults? https://support.apple.com/en-us/HT201945

-- By default, Airport will use the DNS provided by your modem. As your modem allows you access to these pages, do not modify the DNS settings on your Airport during the setup process.

If the issue persists I see two possibilities:

-- Some kind of incompatibility between your modem and the Airport. Ideally, take your Airport to another location with a different modem/connection type and see if the same websites load / don't load. If they work fine, then we know the issue is with your modem.

-- Something is wrong with the Airport. Seems very unlikely as you say other sites work fine. Contact Apple for their thoughts: Contact Apple for support and service - Apple Support

Best of luck to you,

Madison

Reply

Answer 2

Jon Blank Author

Level 1

101 points

Jun 26, 2015 2:29 AM in response to MadisonP

Thanks, Madison!

The hard reset did it.

Thanks a million!

Reply