Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[minigamer]

I'm having the same problem and i only have 2 comps hooked to it right now. this is frustrating and aggravating. Some1 really needs 2 fix this issue or at least give good instructions on how to fix the issue.

[Bizuser]

I am facing the same problem with EBR 2310- with only 1 or 2 ports active. Connections are dropping/timing out on a regular basis - number of times per day. I am on Comcast broadband and connection timeout only when using router, and problems have increased with upgrade to Comcast line couple of months back. It seems that the problem happens when the router gets flooded with high traffic - images, video, or other high intensity traffic. I have tried setting back to default settings, recycling, etc, but nothing seems to help.  Not sure if this can be solved via firmware/setting change or is inherent limitation of EBR-2310?

Appreciate response/pointer from anyone who overcame this or Support team

Thanks!

[Enoch]

Ditto.  This router appears to be a POS!

[jemory802]

I have a similar problem here with my connection via dlink router.   But unlike the others above it is caused by ' fellow apartment dwellers connections ' who hook up to my service.

I have comcast tv and internet and it only happens on the weekend and at night when the staff is off.

I had ( 3 ) Three of my big iron administrators friends , it guys,  take a look over the last 8 months and they said it is the service not the machines, not the router, and not the modem.

My internet will go from 700 all the way down to 33, and stay there until the next morning.  Comcast says the wiring in the building is not theirs so they are not responsible . 

My solution is keep track of outages and  deduct them from my next bill.  Have saved about $250.00 this way.  I am paying them for a certain amount of service and if it is consistently degraded or not there at all i do as i said in the previous sentence.

But for my connection it is the connection not any hardware at all.

Oh by the way, over the last 8 months,  i have used 3 different computers, 2 different OS's, and 3 different routers and got the same results.

[Comicplague]

Dropped packet from 192.168.0.200 to 00.000.000.00 (IP protocol 17) as unable to create new session

^^ Happens repeatedly.....

DHCP Server Parameter 47 was removed from the parameter database
DHCP Server Parameter 46 was removed from the parameter database
DHCP Server Parameter 44 was removed from the parameter database
Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.200 to 66.228.119.250
Blocked outgoing ICMP packet (ICMP type 11) from 00.00.000.000 to 66.228.119.250

Instead of showing my ip address, changed to all 0's

Does anyone know what is causing these?

[mantarny]

is this ever going to be fixed

[INFO] Sun Feb 22 19:39:32 2004 Log viewed by IP address 192.168.0.101
[INFO] Sun Feb 22 19:39:08 2004 Dropped packet from 192.168.0.101 to 174.129.254.129 (IP protocol 6) as unable to create new session
[INFO] Sun Feb 22 19:39:07 2004 Blocked incoming TCP connection request from 60.173.11.20:6000 to 67.252.154.156:1433
[INFO] Sun Feb 22 19:35:03 2004 Dropped packet from 192.168.0.103 to 209.18.42.163 (IP protocol 6) as unable to create new session
[INFO] Sun Feb 22 19:35:02 2004 Dropped packet from 192.168.0.101 to 195.122.131.15 (IP protocol 6) as unable to create new session
[INFO] Sun Feb 22 19:35:02 2004 Dropped packet from 192.168.0.101 to 38.126.130.201 (IP protocol 6) as unable to create new session
[INFO] Sun Feb 22 19:35:01 2004 Dropped packet from 192.168.0.101 to 216.223.0.208 (IP protocol 6) as unable to create new session
[INFO] Sun Feb 22 19:35:00 2004 Dropped packet from 192.168.0.103 to 209.18.42.163 (IP protocol 6) as unable to create new session
[INFO] Sun Feb 22 19:34:59 2004 Dropped packet from 192.168.0.103 to 209.18.47.61 (IP protocol 17) as unable to create new session
[INFO] Sun Feb 22 19:34:58 2004 Dropped packet from 192.168.0.103 to 209.18.47.62 (IP protocol 17) as unable to create new session
[INFO] Sun Feb 22 19:34:58 2004 Dropped packet from 192.168.0.101 to 216.223.0.208 (IP protocol 6) as unable to create new session
[INFO] Sun Feb 22 19:34:57 2004 Dropped packet from 192.168.0.101 to 209.18.47.62 (IP protocol 17) as unable to create new session
[INFO] Sun Feb 22 19:34:56 2004 Dropped packet from 192.168.0.101 to 38.126.130.201 (IP protocol 6) as unable to create new session
[INFO] Sun Feb 22 19:34:55 2004 Dropped packet from 192.168.0.101 to 76.13.217.253 (IP protocol 6) as unable to create new session
[INFO] Sun Feb 22 19:34:55 2004 Dropped packet from 192.168.0.101 to 174.129.254.129 (IP protocol 6) as unable to create new session
[INFO] Sun Feb 22 19:34:54 2004 Dropped packet from 192.168.0.101 to 209.18.47.61 (IP protocol 17) as unable to create new session
[INFO] Sun Feb 22 19:34:53 2004 Dropped packet from 192.168.0.101 to 209.18.47.62 (IP protocol 17) as unable to create new session
[INFO] Sun Feb 22 19:34:53 2004 Dropped packet from 192.168.0.101 to 38.126.130.201 (IP protocol 6) as unable to create new session
[INFO] Sun Feb 22 19:34:52 2004 Dropped packet from 192.168.0.101 to 209.18.47.62 (IP protocol 17) as unable to create new session
[INFO] Sun Feb 22 19:34:52 2004 Dropped packet from 192.168.0.101 to 174.129.254.129 (IP protocol 6) as unable to create new session
[INFO] Sun Feb 22 19:34:52 2004 Dropped packet from 192.168.0.101 to 76.13.217.253 (IP protocol 6) as unable to create new session
[INFO] Sun Feb 22 19:34:49 2004 Dropped packet from 192.168.0.101 to 174.129.225.52 (IP protocol 6) as unable to create new session
[INFO] Sun Feb 22 19:34:44 2004 Blocked incoming UDP packet from 10.10.7.158:5300 to 67.252.154.156:59243
[INFO] Sun Feb 22 19:28:16 2004 Dropped packet from 192.168.0.101 to 209.18.47.62 (IP protocol 17) as unable to create new session
[INFO] Sun Feb 22 19:28:12 2004 Blocked incoming UDP packet from 10.10.7.157:5300 to 67.252.154.156:59837
[INFO] Sun Feb 22 19:09:17 2004 Blocked incoming UDP packet from 10.10.7.150:5300 to 67.252.154.156:63471
[INFO] Sun Feb 22 19:09:16 2004 Blocked incoming UDP packet from 10.10.7.152:5300 to 67.252.154.156:63471
[INFO] Sun Feb 22 19:09:16 2004 Previous message repeated 1 time
[INFO] Sun Feb 22 19:06:52 2004 Blocked incoming TCP connection request from 66.63.194.155:2076 to 67.252.154.156:3724
[INFO] Sun Feb 22 19:06:46 2004 Previous message repeated 1 time
[INFO] Sun Feb 22 19:06:45 2004 Blocked incoming UDP packet from 10.10.7.157:5300 to 67.252.154.156:53730
[INFO] Sun Feb 22 19:06:43 2004 Blocked incoming TCP connection request from 66.63.194.155:2076 to 67.252.154.156:3724

[cyric_74]

I'm having this problem as well.

I thought DLink was a quality brand, didn't expect the router to be a problem so I've since bought a 2nd one for another connection.

I think I'm going to return that one though and look at replacing the first one as well.

I'll definitely think hard about buying any more dlink products if this is the quality level and support I can expect.

[gas]

Having the same problem as everyone else. This is very frustrating!!!!!!!!!!! My roommate hates me cause her internet is so f*ing bad. Does D-Link have a solution? This is the 2nd d-link router I've purchased. I don't have a lot of extra cash to buy another one but I'm ready to flush this down the toilet and get a different brand.

I've done everything, had comcast reset the signal so many times and just had them come to the house a few days ago. What gives D-Stink?

[Mackerel]

I have the same problem with my EBR-2310, but it only started about 4 months ago (have had the router for quite a while). I see no special indications inside the log, so at my side it seems to be purely the provider (who has a name for bad connections) or their ADSL setup at my PABX. This Canadian company, whose short name rhymes with 'Give-us' tends to rummage around on the ADSL boards. But symptoms are about the same.
On a good day I get 6 Mbps for a few hours, then about 3-5 mins of zilch, and all is well again.

I suspected the router first, but as I see no special entries in the Router-log I see no way of putting the blame on the router. Also it happens infrequently. It is also a B1 with 2.01...

EDIT: I do not use torrents of any kind...

[fribie]

I have the same problem with my EBR-2310, but it only started about 4 months ago (have had the router for quite a while). I see no special indications inside the log, so at my side it seems to be purely the provider (who has a name for bad connections) or their ADSL setup at my PABX. This Canadian company, whose short name rhymes with 'Give-us' tends to rummage around on the ADSL boards. But symptoms are about the same.
On a good day I get 6 Mbps for a few hours, then about 3-5 mins of zilch, and all is well again.

I suspected the router first, but as I see no special entries in the Router-log I see no way of putting the blame on the router. Also it happens infrequently. It is also a B1 with 2.01...

I don't use torrent or something similar. I had seven years D604 and I had never a problem. It was on day and night. The new one going in trash soon. My friend borrow me Linksys and it works without problem.

[BlueToast]

Hello, I am also having the same problem. My problem started only a couple weeks ago out of the blue; no changes have occurred in my network within this time period. Our last firmware update was 2 years ago, currently using v2.01. We also have our router to use OpenDNS (208.67.222.222 and 208.67.220.220), and have had it set to this since having bought this router in 2008.

[INFO] Tue Apr 13 17:37:26 2010 Dropped packet from 192.168.2.3 to 208.67.220.220 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 17:37:26 2010 Blocked incoming TCP connection request from 221.195.73.86:3313 to 72.173.2.187:1080
[INFO] Tue Apr 13 17:37:26 2010 Blocked incoming TCP connection request from 221.195.73.86:3352 to 72.173.2.187:8000
[INFO] Tue Apr 13 17:37:26 2010 Dropped packet from 192.168.2.3 to 208.67.222.222 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 17:37:26 2010 Dropped packet from 192.168.2.3 to 208.67.220.220 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 17:37:25 2010 Dropped packet from 192.168.2.3 to 208.67.222.222 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 17:37:25 2010 Dropped packet from 192.168.2.3 to 208.67.220.220 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 17:37:25 2010 Dropped packet from 192.168.2.3 to 208.67.222.222 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 17:37:25 2010 Dropped packet from 192.168.2.3 to 208.67.220.220 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 17:37:25 2010 Dropped packet from 192.168.2.3 to 208.67.222.222 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 17:37:24 2010 Dropped packet from 192.168.2.204 to 96.30.35.120 (IP protocol 6) as unable to create new session
[INFO] Tue Apr 13 17:37:24 2010 Previous message repeated 1 time
[INFO] Tue Apr 13 17:37:24 2010 Dropped packet from 192.168.2.3 to 208.67.220.220 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 17:37:24 2010 Dropped packet from 192.168.2.3 to 72.21.206.70 (IP protocol 6) as unable to create new session
[INFO] Tue Apr 13 17:37:24 2010 Dropped packet from 192.168.2.184 to 72.249.66.26 (IP protocol 6) as unable to create new session
[INFO] Tue Apr 13 17:37:24 2010 Previous message repeated 2 times
[INFO] Tue Apr 13 17:37:24 2010 Dropped packet from 192.168.2.3 to 208.67.222.222 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 17:37:24 2010 Dropped packet from 192.168.2.3 to 208.67.220.220 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 17:37:24 2010 Dropped packet from 192.168.2.3 to 72.21.210.125 (IP protocol 6) as unable to create new session
[INFO] Tue Apr 13 17:37:24 2010 Dropped packet from 192.168.2.3 to 208.67.222.222 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 17:37:24 2010 Dropped packet from 192.168.2.3 to 208.67.220.220 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 17:37:24 2010 Dropped packet from 192.168.2.3 to 204.2.177.33 (IP protocol 6) as unable to create new session
[INFO] Tue Apr 13 17:37:24 2010 Previous message repeated 5 times
[INFO] Tue Apr 13 17:37:20 2010 Blocked incoming TCP connection request from 221.195.73.86:3313 to 72.173.2.187:1080
[INFO] Tue Apr 13 17:37:20 2010 Blocked incoming TCP connection request from 221.195.73.86:3352 to 72.173.2.187:8000
[INFO] Tue Apr 13 17:37:17 2010 Previous message repeated 1 time

We lose access to the internet occasionally, and I have traced the problem down to either (1) the router or (2) the ISP. I am so far unable to determine whether it is the router's fault or ISPs fault.

I have also found myself unable to access http://192.168.2.1/ sometimes, giving me a connection not found/timed out/reset error (I cannot remember what it was now), and this would only occur while having lost connectivity to the internet. We can still ping 192.168.2.1 and get a response back.

EDIT: I will be trying a Firebox sometime soon to see if the problem lies in the router or not.

EDIT2: Internet went out again -- so I immediately went to check the logs in the control panel.

[INFO] Tue Apr 13 19:31:07 2010 Blocked incoming TCP connection request from 72.173.3.189:54981 to 72.173.2.187:5900
[INFO] Tue Apr 13 19:31:00 2010 Blocked incoming TCP packet from 72.173.3.189:54977 to 72.173.2.187:80 as FIN:ACK received but there is no active connection
[INFO] Tue Apr 13 19:30:58 2010 Blocked incoming TCP connection request from 72.173.3.189:54981 to 72.173.2.187:5900
[INFO] Tue Apr 13 19:30:46 2010 Log viewed by IP address 192.168.2.204
[INFO] Tue Apr 13 19:30:40 2010 Dropped packet from 192.168.2.3 to 208.67.220.220 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 19:30:39 2010 Dropped packet from 192.168.2.3 to 208.67.222.222 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 19:30:39 2010 Dropped packet from 192.168.2.3 to 208.67.220.220 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 19:30:39 2010 Blocked incoming TCP connection request from 72.173.3.189:54981 to 72.173.2.187:3389
[INFO] Tue Apr 13 19:30:31 2010 Dropped packet from 192.168.2.3 to 208.67.222.222 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 19:30:31 2010 Dropped packet from 192.168.2.184 to 216.246.75.98 (IP protocol 6) as unable to create new session
[INFO] Tue Apr 13 19:30:28 2010 Dropped packet from 192.168.2.3 to 208.67.222.222 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 19:30:25 2010 Blocked incoming TCP packet from 72.173.3.189:54977 to 72.173.2.187:80 as FIN:ACK received but there is no active connection
[INFO] Tue Apr 13 19:30:25 2010 Dropped packet from 192.168.2.3 to 208.67.220.220 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 19:30:25 2010 Dropped packet from 192.168.2.3 to 208.67.222.222 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 19:30:25 2010 Dropped packet from 192.168.2.3 to 208.67.220.220 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 19:30:25 2010 Dropped packet from 192.168.2.3 to 208.67.222.222 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 19:30:24 2010 Dropped packet from 192.168.2.3 to 208.67.220.220 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 19:30:23 2010 Dropped packet from 192.168.2.3 to 208.67.222.222 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 19:30:23 2010 Dropped packet from 192.168.2.3 to 208.67.220.220 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 19:30:23 2010 Dropped packet from 192.168.2.3 to 208.67.222.222 (IP protocol 17) as unable to create new session
[INFO] Tue Apr 13 19:30:16 2010 Blocked incoming UDP packet from 70.164.248.196:4917 to 72.173.2.187:10178
[INFO] Tue Apr 13 19:30:14 2010 Blocked incoming TCP packet from 72.173.3.189:54980 to 72.173.2.187:8080 as RST:ACK received but there is no active connection
[INFO] Tue Apr 13 19:30:08 2010 Blocked incoming TCP packet from 72.173.3.189:54977 to 72.173.2.187:80 as FIN:ACK received but there is no active connection
[INFO] Tue Apr 13 19:30:03 2010 Blocked incoming TCP packet from 72.173.3.189:54980 to 72.173.2.187:8080 as FIN:ACK received but there is no active connection
[INFO] Tue Apr 13 19:29:45 2010 FTP ALG rejected packet from 192.168.2.204:3634 to 216.40.209.34:21
[INFO] Tue Apr 13 19:29:40 2010 Dropped packet from 192.168.2.184 to 69.63.176.181 (IP protocol 6) as unable to create new session
[INFO] Tue Apr 13 19:29:05 2010 Dropped packet from 192.168.2.3 to 208.67.220.220 (IP protocol 17) as unable to create new session

The main page (not logs page) loaded with a popup saying that 'not all components loaded', and it was kind of slow at loading the logs page. Wasn't as instantaneous as usual. I was also trying to connect to an FTP at the time, which is how I detected that the internet went out. I wasn't doing anything online before. I can still print to my network printer, which is hooked up to a DD-WRT router (acting as a switch) somewhere else in the house.

Internet connectivty came back after a couple or few minutes from realizing there was no connectivity.

EDIT3: After the connectivity came back up (from the statement directly above), I immediately tried to connect to FTP, and after successful logon and directory listing, I quickly refreshed the logs page in the control panel. Here's what comes after:

[INFO] Tue Apr 13 19:36:03 2010 Log viewed by IP address 192.168.2.204
[INFO] Tue Apr 13 19:35:36 2010 Blocked incoming ICMP error message (ICMP type 3) from 89.133.100.1 to 72.173.2.187 as there is no UDP session active between 72.173.2.187:37402 and 192.168.10.5:9939
[INFO] Tue Apr 13 19:35:30 2010 Previous message repeated 2 times
[INFO] Tue Apr 13 19:32:02 2010 Blocked incoming TCP packet from 72.173.3.189:54977 to 72.173.2.187:80 as FIN:ACK received but there is no active connection

[BlueToast]

I'm pretty sure this is my ISP's fault. Problem seems to have disappeared. Would anyone disagree with the idea that if the router were dying or going faulty, the symptoms should be consistent?

[leec]

EBR-2310 HW Ver. B1, Firmware 2.01

We have been getting CONSTANT timeouts with this router connected to our cable modem. We have a small home network (3-4 PCs) doing web surfing a little music streaming. I suspect the problem is with DNS Relay(?) because streaming never is interrupted, but web browsing seems to get a never ending series of timeouts when doing DNS look-ups. I've had a ping session at times when this is happening and that will occasionally timeout.

I finally got tired of hearing "the Internet is down!" from the kids and hooked a laptop directly into the cable modem. No problem, very very fast speeds with no timeouts. Plugged back into the 2310 and the same behavior started. This product should have never been released. Too bad, I bought D-Link specifically because they have been rock solid in the past. I've given up and swapped in our (ancient) Linksys BEFSR41 and no problems so far.

BTW - seems D-Link is not interested in responding to this problem on the Support forum. I will be posting on the Amazon comments section for this product. I'd suggest you do the same where you bought - Amazon, Google Products, Newegg, CNET, etc. Good that people know what they are getting BEFORE they purchase.

[Mackerel]

I suspect the problem is with DNS Relay(?) because streaming never is interrupted, but web browsing seems to get a never ending series of timeouts when doing DNS look-ups.

Streaming is a single continuous session, whereas browsing creates quite a few sessions during the span of browsing to a single page...

I have switched off UPnP, DNS Relay and QoS. Problem stays. Mostly happens when a few computers in the network are browsing simultaneously. Indeed it could be 'hanging' (i.e. non-clearing) sessions. Must be the firmware as connecting directly to my provider does not show the symptoms...

[Mackerel]

Finally 'dropped' the EBR-2310 in favour of a Linksys E1000. Have not had any dropped connections since.
Shame, for the rest the router is a fine thing, but this issue never was solved, whatever combination of settings I used.

Alas, but I am still using quite a bit of other D-Link hardware... And they all perform well.