D-Link Forums

The Graveyard - Products No Longer Supported => Routers / COVR => DIR-615 => Topic started by: motravo on January 10, 2010, 10:34:01 AM

Title: Some HTTP requests time out with DIR-615, but only those made from OS X
Post by: motravo on January 10, 2010, 10:34:01 AM
I'm upgrading a Linksys wireless router to a D-Link DIR-615. I didn't change anything else about my configuration, but some HTTP requests are now failing from my Macs. Here are the devices on my network:

- DSL Modem (AT&T)
- D-Link router: DIR-615, H/W Rev C1, F/W 3.11NA (it came with 3.10NA; I upgraded to 3.11NA)
  - connects to WAN with PPPoE
  - mixed 802.11 mode (I've also tried with g-only and b-only, with the same result)
- Acer desktop running Vista connected through ethernet
- iMac running Leopard connected through ethernet
- PowerBook running Leopard connected through wifi


The problem is that no response is received from many HTTP requests made from the Macs. Which requests fail seems to depend on the browser and computer. I've seen *no* problems from the Windows computer. I'm guessing this is because D-Link only tested their product with Windows (amazingly, their setup software is windows-only).

So, for example, from Safari on the PowerBook, when I try to view a youtube video, the page loads, but the video does not play. This behavior is very repeatable. When I set up a proxy to look at the requests, there is no response to the request for the video data, which comes from a different server than the rest of the page data. However, switching to Firefox does make the video play. However, many other URLs fail to load in firefox, usually eventually showing this message:

<HTML><HEAD>
<TITLE>Request Timeout</TITLE>
</HEAD><BODY>
<H1>Request Timeout</H1>
The server timed out while waiting for the browser's request.<P>
Reference&#38;#38;#38;#38;#32;&#38;#38;#38;#38;#35;2&#38;#38;#38;#38;#46;ae7a81d8&#38;#38;#38;#38;#46;1263143797&#38;#38;#38;#38;#46;0
</BODY></HTML>

I see failures in all browsers on both Macs, but none on any browser in windows. Software firewalls are turned off in OS X.

Nothing shows up in the logs I can find through the router's web interface, so I don't know where else to go from here other than to just get a non-D-Link router. I tried calling D-Link but they had a bad/fuzzy connection to India and the rep just hung up on me.

Any idea would be appreciated. thanks!

-- Ugh, submitting this post didn't go through from Safari or Firefox on the mac. I have to do it from windows
Title: Re: Some HTTP requests time out with DIR-615, but only those made from OS X
Post by: rwagner76 on March 04, 2011, 05:27:58 AM
I actually am having the same problem - except I am having problems on Windows using Chrome.  I don't appear to have the issue using Internet Explorer (though I don't use IE very much)...
Title: Re: Some HTTP requests time out with DIR-615, but only those made from OS X
Post by: FurryNutz on March 04, 2011, 07:04:14 AM
Have you tried another broswer besides Chrome and IE? How about Opera and FireFox or Flock?
I presume that if you don't see it in IE and only Chrome, that might be an issue.
Title: Re: Some HTTP requests time out with DIR-615, but only those made from OS X
Post by: billy_kidd on March 04, 2011, 09:17:45 AM
I thought MACs were easy to use... sooo much better than a PC <snick>
Title: Re: Some HTTP requests time out with DIR-615, but only those made from OS X
Post by: FurryNutz on March 04, 2011, 09:54:11 AM
 ;)
Title: Re: Some HTTP requests time out with DIR-615, but only those made from OS X
Post by: stonetownmike on March 04, 2011, 03:58:23 PM
I've experienced no problems with my Rev. C1 router and two Macs -- one wired, one wireless -- regardless of what browser I use (Safari, Camino, Opera, Chrome, Firefox, iCab etc.) If you're not having problems with your Windows computer, I wouldn't blame the router. Do you have DNS servers configured in each of your Macs as well as your router? OpenDNS is fast and free, if you're not using it already. Also, IPV6 is enabled by default on OS X. Best to disable it in your network prefs. If you're using an HTTP proxy, such as GlimmerBlocker, see if turning it off makes a difference. Those are pretty basic suggestions. My apologies if you've already tried them.