Resolving host error

[beecue]

I have had this annoying problem since I upgraded to 80Mbps connection. It only occurs when I am maxing out my connection downloading from usenet. I will get full speed for a few minutes then it seems my router crashes. The connection drops to the server and when I try using my browser it shows "resolving host..." and won't connect to any websites. I have to unplug my router for a few seconds to make things work again.

I'm using a dir-655. Is it time to upgrade or can I fix this?

[zipdoa]

Are you running the latest firmware?

[beecue]

I'm running 1.35. There is 1.37 available but the fixes are for "Fixed WPS-PIN issue" and "Improved compatibility issue with Samsung Galaxy S4". I will update it anyways.

[firebane]

Dlink has never been known for "quality" stuff. I'd say ditch it and invest into a good Asus router and flash with DD or Tomato.

[Alterac]

the DIR-655 was pretty good, it can handle up to about 230mbps WAN<->LAN Throughput.


I would check to see if you can ping 4.2.2.2 while this behavior is happening or not.

If you can, it may be some bad DNS settings (or just your ISP terrible DNS service).

You can use opendns (208.67.222.222 and 208.67.220.220) for free and they are a good service.

[beecue]

I was using opendns. I noticed it was gone after I updated the firmware today. Not sure if it was reset for a while or not so I will have to test if this happens again after I enable it.

[beecue]

Happened while using opendns.

Got this when I pinged.

Pinging 4.2.2.2 with 32 bytes of data:
Request timed out.
Reply from 4.2.2.2: bytes=32 time=275ms TTL=53
Request timed out.
Request timed out.

Ping statistics for 4.2.2.2:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 275ms, Maximum = 275ms, Average = 275ms

[firebane]

May I ask why your using OpenDNS for? Your ISP' DNS should be absolute fine.

[syscal]

Originally posted by firebane
May I ask why your using OpenDNS for? Your ISP' DNS should be absolute fine.

sidetrack, thanks firebane.

OpenDNS is fine, ISP DNS is typically slower. Plus if you have kids you can filter pr0n for free with opendns.

Ping drops - try setting manual speed/duplex on the WAN interface. Unsure what it *should* be set to, but google the model of the shaw modem and you should be able to find it. Let's assume 100MB full.

I know the interweb forum and google is great for troubleshooting, but have you tried calling Shaw yet? techie people typically think of this as a last resort

[firebane]

Originally posted by syscal


sidetrack, thanks firebane.

OpenDNS is fine, ISP DNS is typically slower. Plus if you have kids you can filter pr0n for free with opendns.

Ping drops - try setting manual speed/duplex on the WAN interface. Unsure what it *should* be set to, but google the model of the shaw modem and you should be able to find it. Let's assume 100MB full.

I know the interweb forum and google is great for troubleshooting, but have you tried calling Shaw yet? techie people typically think of this as a last resort

I've found the opposite with OpenDNS compared to Shaws. Its always been slower and less reliable.

[beecue]

I read opendns was good so that's why I was using it. It doesn't matter though since my isp and opendns have the same problem. I don't think it's an isp issue because my modem seems fine and everything works once I reboot my router.

[Alterac]

Looks like you are saturating your upstream with SYN packets, and causing packet loss.

or

Your router may have some advanced features turned on, and is using 100% of its CPU trying to keep up with your throughput.


You have 80mbps down, but what is your upstream?

EDIT- Also, are you wired or wireless?

[beecue]

6mbps upstream. My computer is wired to the router.