Print

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

[k3rmit]

Hello.

Well, I have no idea what's going on but... I've had Linksys BEFSR41 (which is about 7 years old BTW), and Dlink DI-604). I finally decided to buy gigabit router and here we are.

Everything is fine, wireless works perfect (actually I turned it off, because I don't need WiFi at this moment), I have cable modem and it's getting all the data (IP, DNSes etc) automatically (Dynamic IP >DHCP<).

But after a while I noticed that router drops connection between itself and my modem. CABLE led beams, everything is OK, router works, I'm able to login, and the best joke is it even shows "Network Status :
Established" and proper Connection Up Time! So, modem works, router works but I have no internet for a short period of time every few minutes. I'm using "ping www.site.com -n 10000" sometimes and I'm getting timeouts when it happens.

I've got latest firmware, I've even turned WiFi, all firewall options, DHCP and QoS off. Nothing has changed. And when I use my old Linksys instead of DIR-655 - everything's fine.

What should I do? Provider won't help me with this, because as You can see everything is fine, excepting this router ;]

Part of my log:

[INFO] Thu Dec 04 12:39:33 2008 Blocked incoming TCP packet from 83.5.86.84:20313 to xx.xxx.xx.xxx:2951 as RST:ACK received but there is no active connection
[INFO] Thu Dec 04 12:39:29 2008 Log viewed by IP address 192.168.1.2
[INFO] Thu Dec 04 12:39:27 2008 Allowed configuration authentication by IP address 192.168.1.2
[INFO] Thu Dec 04 12:37:37 2008 Blocked incoming TCP packet from 24.57.139.103:52261 to xx.xxx.xx.xxx:25077 as RST received but there is no active connection
[INFO] Thu Dec 04 12:36:53 2008 Blocked incoming ICMP error message (ICMP type 3) from 79.116.249.171 to xx.xxx.xx.xxx as there is no UDP session active between xx.xxx.xx.xxx:25077 and 192.168.1.100:23855
[INFO] Thu Dec 04 12:36:19 2008 Allowed configuration authentication by IP address 192.168.1.2
[INFO] Thu Dec 04 12:35:48 2008 Blocked incoming TCP packet from 83.100.151.184:11677 to xx.xxx.xx.xxx:2849 as RST:ACK received but there is no active connection
[INFO] Thu Dec 04 12:35:43 2008 Blocked incoming TCP packet from 83.100.151.184:11642 to xx.xxx.xx.xxx:2849 as RST:ACK received but there is no active connection
[INFO] Thu Dec 04 12:35:42 2008 Blocked incoming TCP packet from 24.57.139.103:52169 to xx.xxx.xx.xxx:25077 as RST received but there is no active connection
[INFO] Thu Dec 04 12:35:40 2008 Blocked incoming TCP packet from 83.100.151.184:11629 to xx.xxx.xx.xxx:2849 as RST:ACK received but there is no active connection
[INFO] Thu Dec 04 12:34:31 2008 Blocked incoming UDP packet from 125.194.119.10:57257 to xx.xxx.xx.xxx:61810
[INFO] Thu Dec 04 12:34:20 2008 UPnP added entry 255.255.255.255 <-> xx.xxx.xx.xxx:25077 <-> 192.168.1.4:25077 UDP timeout:-1 'uTorrent (UDP)'
[INFO] Thu Dec 04 12:34:20 2008 UPnP added entry 255.255.255.255 <-> xx.xxx.xx.xxx:25077 <-> 192.168.1.4:25077 TCP timeout:-1 'uTorrent (TCP)'
[INFO] Thu Dec 04 12:34:19 2008 Blocked incoming TCP connection request from 209.66.117.54:57485 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:19 2008 Blocked incoming TCP connection request from 209.133.121.253:39551 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:19 2008 Blocked incoming TCP connection request from 88.106.73.136:61897 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:19 2008 Blocked incoming TCP connection request from 209.133.121.172:57571 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:19 2008 Blocked incoming TCP connection request from 83.100.151.184:11297 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:18 2008 Blocked incoming UDP packet from 116.26.237.57:8983 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:18 2008 Blocked incoming TCP connection request from 209.133.121.136:46377 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:17 2008 Blocked incoming TCP connection request from 209.133.122.173:37609 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:17 2008 Blocked incoming UDP packet from 212.3.144.163:5515 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:17 2008 Blocked incoming UDP packet from 71.2.126.122:10124 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:16 2008 Blocked incoming UDP packet from 80.236.124.103:12262 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:16 2008 Blocked incoming UDP packet from 86.12.249.70:7642 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:16 2008 Blocked incoming UDP packet from 87.120.0.85:26765 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:15 2008 Blocked incoming UDP packet from 201.253.83.2:25985 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:15 2008 Blocked incoming TCP connection request from 209.133.121.162:54169 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:15 2008 Blocked incoming UDP packet from 213.25.18.104:26680 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:15 2008 Blocked incoming UDP packet from 220.225.73.140:41221 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:15 2008 Blocked incoming TCP connection request from 190.138.136.73:46809 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:14 2008 Blocked incoming TCP connection request from 209.133.122.200:33381 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:14 2008 Blocked incoming UDP packet from 125.93.120.185:16001 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:14 2008 Above message repeated 1 times
[INFO] Thu Dec 04 12:34:13 2008 Blocked incoming UDP packet from 189.15.130.71:10282 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:13 2008 Blocked incoming UDP packet from 89.133.146.27:1048 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:13 2008 Blocked incoming TCP connection request from 88.106.73.136:61897 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:12 2008 Blocked incoming UDP packet from 58.20.233.66:49398 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:12 2008 Blocked incoming TCP connection request from 190.138.136.73:46809 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:12 2008 Blocked incoming TCP connection request from 209.66.117.18:37829 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:12 2008 Blocked incoming UDP packet from 121.96.161.70:59317 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:12 2008 Blocked incoming TCP connection request from 209.133.122.161:39799 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:11 2008 Blocked incoming UDP packet from 94.98.25.209:10976 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:10 2008 Blocked incoming TCP connection request from 88.106.73.136:61897 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:10 2008 Blocked incoming TCP connection request from 122.116.15.25:61905 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:10 2008 Blocked incoming TCP connection request from 91.150.223.8:61059 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:09 2008 Blocked incoming TCP connection request from 209.133.121.162:54169 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:09 2008 Blocked incoming TCP connection request from 209.249.45.36:52486 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:09 2008 Blocked incoming TCP connection request from 209.133.121.173:54512 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:08 2008 Blocked incoming UDP packet from 116.206.174.47:22636 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:08 2008 Blocked incoming TCP connection request from 88.168.249.126:1210 to xx.xxx.xx.xxx:135
[INFO] Thu Dec 04 12:34:07 2008 Blocked incoming TCP connection request from 209.133.121.172:57571 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:06 2008 Blocked incoming UDP packet from 83.238.228.68:26643 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:06 2008 Blocked incoming TCP connection request from 209.133.121.162:54169 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:06 2008 Blocked incoming TCP connection request from 209.133.121.136:46377 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:06 2008 Blocked incoming TCP connection request from 209.66.117.18:37829 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:06 2008 Blocked incoming TCP connection request from 209.133.122.161:39799 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:05 2008 Blocked incoming TCP connection request from 209.133.121.153:58315 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:05 2008 Blocked incoming UDP packet from 125.73.87.205:7697 to xx.xxx.xx.xxx:25077
[INFO] Thu Dec 04 12:34:05 2008 Blocked incoming TCP connection request from 88.168.249.126:1210 to xx.xxx.xx.xxx:135
[INFO] Thu Dec 04 12:34:05 2008 Blocked incoming TCP connection request from 24.57.139.103:52710 to xx.xxx.xx.xxx:25077

I've had no internet for example between 12:37 and 12:38.

Or here between 12:44 and 45:

[INFO]   Thu Dec 04 12:45:01 2008   Log viewed by IP address 192.168.1.2
[INFO]   Thu Dec 04 12:44:04 2008   Blocked incoming TCP packet from 83.5.86.84:20690 to xx.xxx.xx.xxx:3089 as RST:ACK received but there is no active connection
[INFO]   Thu Dec 04 12:43:58 2008   Blocked incoming TCP packet from 83.5.86.84:20675 to xx.xxx.xx.xxx:3089 as RST:ACK received but there is no active connection
[INFO]   Thu Dec 04 12:43:56 2008   Blocked incoming TCP packet from 83.5.86.84:20673 to xx.xxx.xx.xxx:3089 as RST:ACK received but there is no active connection
[INFO]   Thu Dec 04 12:43:49 2008   Blocked incoming UDP packet from 80.72.153.67:60205 to xx.xxx.xx.xxx:19637
[INFO]   Thu Dec 04 12:41:22 2008   Blocked incoming TCP packet from 83.5.86.84:20473 to xx.xxx.xx.xxx:3006 as RST:ACK received but there is no active connection
[INFO]   Thu Dec 04 12:41:16 2008   Blocked incoming TCP packet from 83.5.86.84:20456 to xx.xxx.xx.xxx:3006 as RST:ACK received but there is no active connection
[INFO]   Thu Dec 04 12:41:13 2008   Blocked incoming TCP packet from 83.5.86.84:20453 to xx.xxx.xx.xxx:3006 as RST:ACK received but there is no active connection

Why it's blocking connections almost every second with firewall turned OFF? :O

Thanks for help!

HINT: it looks like it's blocking tcps from my providers modems like 83.100.151.184, 83.5.86.84. What the? BUT not always, sometimes it just blocks other ips.

[Lycan]

It's blocking traffic that didn't originate on your LAN.
Also you can't turn the firewall off. It's a NAT router.

[k3rmit]

OK, understood.

So what should I do when everything works fine on different (Dlinks also) routers, but DIR-655 probably randomly loses connection for 3 to even 90 seconds every few minutes? I guess it's all about configuration since everything else works fine...

Thanks.

[funchords]

Check your "Event Viewer" in Windows for events coinciding with these lost times.  Since the modem/router log isn't really giving any WAN-port clues, the problem may lie on your machine itself or its connection to the router.

Does this only happen when uTorrent or another P2P client is running?  If so, try setting uTorrents upload speed limit to 15 kB/s and see if that helps.  If it does, you possibly were overrunning your broadband modem's buffer with traffic, and in that state everything waits for the queued traffic to clear, including pings.   Are you having any problems getting the green light in uTorrent?  When you are "disconnected," does all uTorrent traffic stop coming in -- or are you only unable to surf web pages (in other words, does the disconnection affect connected sessions or just prevent new ones)?

On your ping www.somesite.com, I'd like you to try that with the first outside hop to www.somesite.com -- for example, do a tracert www.somesite.com and note the first IP address that is not your own router (it's either the first or second one that answers).  Then do your mega-ping to that address.  This will help determine if it's your connection to your ISP or your ISPs connection further upstream. 

In a second window, run another mega-ping, this time just to your own router.

[k4rmit]

(I couldn't login to my last acc so this one that's my new one)

There's nothing in Event Viewer. My PC works perfect with a few different routers so I don't thnik so there is something wrong with my connection between router and PC by the way.

It disconnects me all the time, even where there is no traffic in my LAN/WAN network. It just happens randomly.

When I ping somesite.com I'm getting timeouts from time to time. When it occurs I have perfect pings to my router all the time (<1 ms) so connection with my router is OK.

Tracert doesn't help, because I'm not able to ping anything outisde my network when this %$%##$ DIR-655 blocks the traffic.

What to do now? I wrote to Dlink Support. One week ago. No reply. And they promise on their website "response time less than 24hrs".

  Ech.

[funchords]

Don't worry about email -- you're better off here.  More eyes on the crisis, and everyone with an idea can pitch in. 

(I couldn't login to my last acc so this one that's my new one)

k4rmit after k3rmit -- that's too cool!

There's nothing in Event Viewer. My PC works perfect with a few different routers so I don't thnik so there is something wrong with my connection between router and PC by the way.

It disconnects me all the time, even where there is no traffic in my LAN/WAN network. It just happens randomly.

When I ping somesite.com I'm getting timeouts from time to time. When it occurs I have perfect pings to my router all the time (<1 ms) so connection with my router is OK.

Okay, agreed, the connection between you and the DIR655 is cool. It's beyond the DIR655 that's iffy.

Tracert doesn't help, because I'm not able to ping anything outisde my network when this %$%##$ DIR-655 blocks the traffic.

No, that's definitely not the case, otherwise it would show up in the log (if it does, show me). 

What I'd like you to try now, however, is to bypass the router.  Connect your computer directly to your broadband modem and repeat the ping test to www.somesite.com.  If you get the same drops here as you did when you were going through the router, then the problem doesn't involve the router. 

While you're in this state, you can try that traceroute thing again (ping the first hop).  This will help you figure out if the problem is between your house and the first hop, or is it something deeper in your ISP.

[shagnorth]

What I'd like you to try now, however, is to bypass the router.  Connect your computer directly to your broadband modem and repeat the ping test to www.somesite.com.  If you get the same drops here as you did when you were going through the router, then the problem doesn't involve the router.

If the issue was with his modem or ISP, the other routers he has would have the same issue.

[funchords]

If the issue was with his modem or ISP, the other routers he has would have the same issue.

Ah, he did say that. 

I'm kinda stumped, then.  If I were having this problem, I think I would probably try a hard-reset, run at factory defaults for a while, and on the first sign of failure I'd be on the phone for an RMA. 

[madmax1]

On the back of your router cheek FRIMWARE VER its under code bare its like that
H W ver: !!! then see F.W ver : !! then go to
www.dlink.ca download the lastest Frimware ver  please cheek carefully Hw ver its very important
once you saved it in your desktop open then    192.168.0.1  wierd PC to router go to tools then browse the file then open  then SAVE SETTING
YOUR ROUTER WILL need to setup again . It will fix the dropped connection
Madmax1

[thecreator]

Hello.

Well, I have no idea what's going on but... I've had Linksys BEFSR41 (which is about 7 years old BTW), and Dlink DI-604). I finally decided to buy gigabit router and here we are.

Everything is fine, wireless works perfect (actually I turned it off, because I don't need WiFi at this moment), I have cable modem and it's getting all the data (IP, DNSes etc) automatically (Dynamic IP >DHCP<).

But after a while I noticed that router drops connection between itself and my modem. CABLE led beams, everything is OK, router works, I'm able to login, and the best joke is it even shows "Network Status :
Established" and proper Connection Up Time! So, modem works, router works but I have no internet for a short period of time every few minutes. I'm using "ping www.site.com -n 10000" sometimes and I'm getting timeouts when it happens.

I've got latest firmware, I've even turned WiFi, all firewall options, DHCP and QoS off. Nothing has changed. And when I use my old Linksys instead of DIR-655 - everything's fine.

What should I do? Provider won't help me with this, because as You can see everything is fine, excepting this router ;]

Part of my log:
I've had no internet for example between 12:37 and 12:38.

Or here between 12:44 and 45:

Why it's blocking connections almost every second with firewall turned OFF? :O

Thanks for help!

HINT: it looks like it's blocking tcps from my providers modems like 83.100.151.184, 83.5.86.84. What the? BUT not always, sometimes it just blocks other ips.

Hi k4rmit,

Please reply and post exactly how you install your D-Link Router. If necessary redo the installation, to refresh your memory, because you may have overlooked something that is necessary to do, but you never did.