This discussion is archived
258 Views 4 Replies Latest reply: Oct 3, 2005 11:35 AM by Dan Ramsey
Currently Being ModeratedOct 1, 2005 10:22 AM (in response to Seb J)This is a DNS problem. Trying to figure out where the problem lies, and how to fix it if possible, is beyond most of us. You might try manually adding in the IP addresses of your ISP's DNS in System Preferences->Network->Show Airport->TCP/IP tab.
Currently Being ModeratedOct 1, 2005 10:43 AM (in response to Henry B.)Nope, tried the DNS route. Put the DNS servers into both the AE and System Preferences.
And the DNS idea does not work when you consider the fact that I CAN get to a website like the .Mac webmail, and from what I can tell it gets stuck on loading the .woa.
It's gotta be something else. There must be some kind of issue with the DLink and the AE.
Currently Being ModeratedOct 1, 2005 11:01 AM (in response to Seb J)Well... it might still be a DNS problem, but not one easily fixable by manually configuring the Airport Express and Mac with the IP addresses of your ISP's DNS. I do agree - the bottom line cause of this problem is some sort of "issue" between your ISP, the D-Link modem, and the Airport Express. Unfortunately, there are not many options for solving this problem without trying to replace either the D-Link or the Airport Express with another make/model of device.
Currently Being ModeratedOct 3, 2005 11:35 AM (in response to Seb J)Hi
I've had exactly the same problem with my D-Link modem. I swore it was an issue with my ISP, Pipex.
But, having dug my old D-Link wireless router out of the cupboard and set it up in place of the Airport Express, the problem goes away.
Let me know if you get any answers!! mailto:firstname.lastname@example.org