• October 24, 2020, 10:24:58 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: D-Link - Frequent disconnections  (Read 7442 times)

The-Link

  • Level 1 Member
  • *
  • Posts: 3
D-Link - Frequent disconnections
« on: February 05, 2011, 05:22:09 AM »

I've had a long-time trouble with my router (D-Link Dir-855), getting disconnections every now and then. I usually lose connection for 2-3 minutes every time the router disonnects.

I tried to fix it myself by restoring it to factory default, but it didn't work. I am using the firmware 1.23WW right now, but the issue persisted even with the older ones.
However, I am using a customized setting right now.
One of the things I have changed are the DNS servers (no idea what it does, but someone told me to try it). Before, when I got disconnected and tried to find the problem, it said that the DNS server wasn't responding. So I changed it to 8.8.8.8, 8.8.4.4.
Other things is changed is turning off the DNS relay and QoS. But I believe that none of these settings are responsible for my frequent disonnections, as the factory default settings didn't fix it.

Also, I checked the logs some weeks ago, and I got this
Quote
UPnP renew entry AN.IP.ADRESS <-> AN.IP.ADRESS <-> AN.IP.ADRESS UDP timeout:0 'Teredo'

So I turned the UPnP off, and now I get this:
(I have no idea why it's restarting. But as you can see, I got the "Blocked incoming TCP packet from <blablabla> as FIN:ACK received but there is no active connection" even before it restarted.

Quote
[INFO] Fri Feb 04 14:17:40 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:17:33 2011 Blocked incoming TCP connection request from 111.72.38.178:4692 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:17:32 2011 2.4GHz Band: Wireless link is up
[INFO] Fri Feb 04 14:17:28 2011 Blocked incoming TCP connection request from 77.228.234.254:52107 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:17:27 2011 Blocked incoming TCP connection request from 111.72.38.178:4692 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:17:22 2011 Blocked incoming TCP connection request from 77.228.234.254:52107 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:17:19 2011 Above message repeated 1 times
[INFO] Fri Feb 04 14:17:07 2011 5GHz Band: Wireless link is down
[INFO] Fri Feb 04 14:17:07 2011 5GHz Band: Wireless restart
[INFO] Fri Feb 04 14:17:07 2011 5GHz Band: Disconnect all stations
[INFO] Fri Feb 04 14:17:07 2011 2.4GHz Band: Wireless link is down
[INFO] Fri Feb 04 14:17:07 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:17:07 2011 2.4GHz Band: Disconnect all stations
[INFO] Fri Feb 04 14:17:07 2011 All Wireless shut down
[INFO] Fri Feb 04 14:17:05 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:17:02 2011 Above message repeated 1 times
[INFO] Fri Feb 04 14:17:00 2011 Blocked incoming TCP connection request from 111.72.38.178:4580 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:16:58 2011 Blocked outgoing TCP packet from 192.168.0.199:52111 to 87.248.217.254:80 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:16:57 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:16:55 2011 Blocked incoming TCP connection request from 61.15.176.246:50398 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:16:54 2011 Blocked incoming TCP connection request from 111.72.38.178:4580 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:16:51 2011 Above message repeated 1 times
[INFO] Fri Feb 04 14:16:49 2011 Blocked incoming TCP connection request from 61.15.176.246:50398 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:16:48 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:16:46 2011 Blocked incoming TCP connection request from 61.15.176.246:50398 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:16:45 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:16:40 2011 Above message repeated 2 times
[INFO] Fri Feb 04 14:16:39 2011 Blocked incoming TCP packet from 216.52.241.140:2099 to 213.66.190.58:51666 as ACK received but there is no active connection
[INFO] Fri Feb 04 14:16:39 2011 Blocked incoming TCP packet from 216.52.241.140:2099 to 213.66.190.58:51665 as ACK received but there is no active connection
[INFO] Fri Feb 04 14:16:37 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:16:35 2011 Above message repeated 1 times
[INFO] Fri Feb 04 14:16:33 2011 Blocked incoming TCP connection request from 77.228.234.254:51969 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:16:28 2011 Blocked incoming TCP connection request from 111.72.38.178:4488 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:16:27 2011 Blocked incoming TCP connection request from 77.228.234.254:51969 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:16:24 2011 Above message repeated 1 times
[INFO] Fri Feb 04 14:16:24 2011 2.4GHz Band: Wireless link is up
[INFO] Fri Feb 04 14:16:22 2011 Blocked incoming TCP connection request from 111.72.38.178:4488 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:16:19 2011 Above message repeated 1 times
[INFO] Fri Feb 04 14:15:58 2011 5GHz Band: Wireless link is down
[INFO] Fri Feb 04 14:15:58 2011 5GHz Band: Wireless restart
[INFO] Fri Feb 04 14:15:58 2011 5GHz Band: Disconnect all stations
[INFO] Fri Feb 04 14:15:58 2011 2.4GHz Band: Wireless link is down
[INFO] Fri Feb 04 14:15:58 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:15:58 2011 2.4GHz Band: Disconnect all stations
[INFO] Fri Feb 04 14:15:58 2011 All Wireless shut down
[INFO] Fri Feb 04 14:15:56 2011 Blocked incoming TCP connection request from 111.72.38.178:4372 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:15:56 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:15:50 2011 Above message repeated 2 times
[INFO] Fri Feb 04 14:15:50 2011 Blocked incoming TCP connection request from 111.72.38.178:4372 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:15:41 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:15:38 2011 Blocked incoming TCP connection request from 77.228.234.254:51821 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:15:37 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:15:32 2011 Blocked incoming TCP connection request from 77.228.234.254:51821 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:15:29 2011 Above message repeated 1 times
[INFO] Fri Feb 04 14:15:29 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:15:28 2011 Blocked incoming TCP connection request from 111.72.38.178:4277 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:15:26 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:15:25 2011 Blocked incoming TCP packet from 72.21.214.39:80 to 213.66.190.58:51802 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:23 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:15:22 2011 Blocked incoming TCP connection request from 111.72.38.178:4277 to 213.66.190.58:16868
[INFO] Fri Feb 04 14:15:21 2011 Blocked incoming TCP packet from 72.21.214.39:80 to 213.66.190.58:51804 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:20 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:15:20 2011 Blocked incoming TCP packet from 72.21.214.39:80 to 213.66.190.58:51805 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:18 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:15:17 2011 Blocked incoming TCP packet from 72.21.203.146:80 to 213.66.190.58:51800 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:17 2011 Blocked incoming TCP packet from 72.21.214.39:80 to 213.66.190.58:51802 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:16 2011 2.4GHz Band: Wireless restart
[INFO] Fri Feb 04 14:15:14 2011 2.4GHz Band: Wireless link is up
[INFO] Fri Feb 04 14:15:13 2011 Blocked outgoing TCP packet from 192.168.0.199:51998 to 216.115.111.49:80 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:13 2011 Blocked outgoing TCP packet from 192.168.0.199:51995 to 216.115.111.49:80 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:13 2011 Blocked outgoing TCP packet from 192.168.0.199:51997 to 216.115.111.49:80 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:13 2011 Blocked outgoing TCP packet from 192.168.0.199:51996 to 216.115.111.49:80 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:13 2011 Blocked outgoing TCP packet from 192.168.0.199:51992 to 216.115.111.49:80 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:13 2011 Blocked outgoing TCP packet from 192.168.0.199:51991 to 216.115.111.49:80 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:13 2011 Blocked outgoing TCP packet from 192.168.0.199:52018 to 216.115.111.49:80 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:13 2011 Blocked incoming TCP packet from 72.21.214.39:80 to 213.66.190.58:51802 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:12 2011 Blocked incoming TCP packet from 72.21.214.39:80 to 213.66.190.58:51804 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:12 2011 Blocked incoming TCP packet from 72.21.214.39:80 to 213.66.190.58:51805 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:11 2011 Blocked incoming UDP packet from 78.84.86.242:19539 to 213.66.190.58:27545
[INFO] Fri Feb 04 14:15:11 2011 Blocked incoming TCP packet from 72.21.214.39:80 to 213.66.190.58:51802 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:10 2011 Blocked incoming TCP packet from 72.21.203.146:80 to 213.66.190.58:51798 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:10 2011 Blocked incoming TCP packet from 72.21.214.39:80 to 213.66.190.58:51802 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:09 2011 Blocked incoming TCP packet from 72.21.203.146:80 to 213.66.190.58:51800 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:08 2011 Blocked incoming TCP packet from 72.21.214.39:80 to 213.66.190.58:51804 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:08 2011 Blocked incoming TCP packet from 72.21.214.39:80 to 213.66.190.58:51805 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:06 2011 Blocked incoming TCP packet from 72.21.214.39:80 to 213.66.190.58:51804 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:06 2011 Blocked incoming TCP packet from 72.21.214.39:80 to 213.66.190.58:51805 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:05 2011 Blocked incoming TCP packet from 72.21.214.39:80 to 213.66.190.58:51804 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:05 2011 Blocked incoming TCP packet from 72.21.214.39:80 to 213.66.190.58:51805 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:05 2011 Blocked incoming TCP packet from 72.21.203.146:80 to 213.66.190.58:51800 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:03 2011 Above message repeated 1 times
[INFO] Fri Feb 04 14:15:02 2011 Blocked incoming TCP packet from 72.21.203.146:80 to 213.66.190.58:51798 as FIN:ACK received but there is no active connection
[INFO] Fri Feb 04 14:15:02 2011 Blocked incoming TCP packet from 72.21.203.146:80 to 213.66.190.58:51800 as FIN:ACK received but there is no active connection

« Last Edit: February 05, 2011, 05:28:07 AM by The-Link »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49277
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: D-Link - Frequent disconnections
« Reply #1 on: February 05, 2011, 10:23:02 AM »

DNS Relay and uPNP are recommended to be ON.

What devices are you using over wireless?

What wireless modes are you using. Try single mode G at 2.4Ghz with out any security to test. Just testing. Then apply security.

If you have Advanced DNS Service, turn this off and then make sure your Primary and 2ndary DNS IP addresses are being filled in under Setup/Internet/Manual. You can get these DNS IP addresses from Status/Device Info/Wan section.
Are you using auto DHCP IP addresses? Can you set up a static reserved IP address?

What ISP Service do you have? DSL or Cable?
DO you know if your ISP Modem is a stand alone modem or does it have a built in router?
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

The-Link

  • Level 1 Member
  • *
  • Posts: 3
Re: D-Link - Frequent disconnections
« Reply #2 on: February 05, 2011, 11:00:57 AM »

Right now I'm using the mode: mixed n, g and b. I have turned the Advanced DNS Service off already and changed the DNS to 8.8.8.8 (primary) and 8.8.4.4 (secondary) which is identical to the the ones found in Status/Device info/Wan section. However the DNS (8.8.8.8 and 8.8.4.4) are not the default ones. I've changed it to Google.

I'm not sure about the DHCP and Static stuff, as I'm not experienced with these kind of things. But under Setup/Internet, the router says that I'm using Dynamic IP. I don't think my ISP has provided me with a static IP adress.

I'm not sure about the DSL/cable stuff either. But on the modem there's a light that says DSL, so I guess that's what I'm using. I don't think the modem has an in-built router no.
_

Thanks for the reply, I'll try the settings.

Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49277
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: D-Link - Frequent disconnections
« Reply #3 on: February 05, 2011, 11:08:54 AM »

I would change the DNS IP addresses to the ones that your ISP provides for trouble shooting.

What I mean for static IP addresses is that under Setup/Network settings, there is a section called Number of DHCP Clients, It's recommended to select the Reserve option on each row and reserve the assigned IP address for each of your devices you have connected, wired and wireless.

OK, I think you have DSL. You can see if you have a built in router by looking at the Status/Device Info/Wan section. If the WAN IP address started with a 2 digit number, ##.##.###.###, then your DSL modem is either stand alone or is in a bridged mode. If your seeing a 192.168 address by chance then your DSL modem has a built in router and is not in a bridge mode.

What devices are you using over wired and wireless? PC or any phones?

Are there any cordless house phones that run 2.4Ghz or 5Ghz?

What wireless modes are you using. Try single mode G at 2.4Ghz with out any security to test. Just testing. Then apply security.
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

The-Link

  • Level 1 Member
  • *
  • Posts: 3
Re: D-Link - Frequent disconnections
« Reply #4 on: February 06, 2011, 07:51:53 AM »

We have 3 PC in our house. 2 of them are laptops, but both of them are connected through wires. And yes, then we have phones too. But they are not cordless.

And yeah, still getting disconnections.
Quote
[INFO]   Sun Feb 06 17:39:31 2011   Blocked incoming TCP packet from 74.125.43.154:80 to 81.235.251.128:53297 as FIN:ACK received but there is no active connection
[INFO]   Sun Feb 06 17:39:30 2011   Blocked incoming TCP packet from 74.125.43.138:80 to 81.235.251.128:53451 as FIN:ACK received but there is no active connection
[INFO]   Sun Feb 06 17:39:28 2011   Blocked incoming TCP connection request from 61.15.176.246:64970 to 81.235.251.128:16868
[INFO]   Sun Feb 06 17:39:28 2011   Blocked incoming TCP packet from 74.125.43.138:80 to 81.235.251.128:53451 as FIN:ACK received but there is no active connection
[INFO]   Sun Feb 06 17:39:26 2011   Above message repeated 2 times
[INFO]   Sun Feb 06 17:39:22 2011   Blocked incoming TCP connection request from 61.15.176.246:64970 to 81.235.251.128:16868
[INFO]   Sun Feb 06 17:39:21 2011   Blocked incoming TCP packet from 74.125.43.154:80 to 81.235.251.128:53297 as FIN:ACK received but there is no active connection
Here are two pictures of my current settings. In the last picture in the 'Lan Computers' section, you can see the name of the computers.
The xxxxNight is the name of my computer. But in the last picture, you can see two of them. Why am I assigned with 2 IP adresses?

(Also, one thing I've noticed is that I rarely get disonnected at night. It usually happens in the middle of the day. I'm not sure about this though)






« Last Edit: February 06, 2011, 10:33:22 AM by The-Link »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49277
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: D-Link - Frequent disconnections
« Reply #5 on: February 06, 2011, 11:00:32 AM »

Looks like this is comming from the ISP modem and the router is doing his job. I would contact your ISP and ask them if they see any thing as they can tell if the ISP modem is dropping for any reason. Tell them of these log entries.

What are your firewall settings at? I recommend using EndPoint Independent for both TCP and UDP.

Looks like your PC is getting 2 IP addresses as it sees a Wired connection and a wireless connection. Is your wireless ON while your wired?

If your getting disconnected during the day, might mean that it's when it's the busiest part of the time frame and I would make mention of this with your ISP.

You are getting correct WAN information in the WAN section of the router. Make sure your Setup/Internet/Manual section reflects the same for Primary and 2ndary DNS IP addresses. It looks like the ISP modem is in bridged mode and your Router is in PPPoE mode for DSL and is working correctly.

The router is doing its job and just because the router seems to be disconnecting doesn't mean there is a problem with the router. Lets look at the DSL line and the ISP. Ask them specifically if they can see if the DSL modem has been down or disconnected for any reason during the timeframes you said. Let us know.
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!