• May 24, 2025, 12:55:50 PM
  • 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: Router disconnect issue -- log included  (Read 19329 times)

newtoncd

  • Level 1 Member
  • *
  • Posts: 19
Router disconnect issue -- log included
« on: August 31, 2009, 09:00:56 PM »
I use Qwest DSL (IP address 10.0.0.1) with my DLink DIR-655 router with 1.32NA firmware.

Every so often, the router will disconnect for about 25-40 seconds.  My laptop will automagically reconnect and all is well.  My wife's desktop is also affected as she loses her connection during this period.  If you are on the phone, it will also cut the call off.

Do you guys see anything in the log that would be the issue/problem?  I use DHCP, have ntp enabled (but the problem exists with and without ntp enabled).

I have the following running off the DLink DIR-655:  magicJack phone service with HP thin client via ethernet, HP C6180 wireless printer and laptop using WPA encryption and desktop via ethernet.

I would appreciate any help..... thanks.


[INFO] Mon Aug 31 21:53:00 2009 Log viewed by IP address 192.168.0.198
[INFO] Mon Aug 31 21:50:20 2009 Above message repeated 1 times
[INFO] Mon Aug 31 21:50:16 2009 Allowed configuration authentication by IP address 192.168.0.198
[INFO] Mon Aug 31 21:44:39 2009 UPnP added entry 255.255.255.255 <-> 10.0.0.3:34683 <-> 192.168.0.198:34683 UDP timeout:0 'DNA (UDP)'
[INFO] Mon Aug 31 21:44:39 2009 UPnP added entry 255.255.255.255 <-> 10.0.0.3:34683 <-> 192.168.0.198:34683 TCP timeout:0 'DNA (TCP)'
[INFO] Mon Aug 31 21:36:44 2009 Blocked outgoing TCP packet from 192.168.0.198:56330 to 74.208.5.69:110 as FIN:ACK received but there is no active connection
[INFO] Mon Aug 31 21:34:52 2009 NewtonNet: Wireless system with MAC address 001F3C508358 secured and linked
[INFO] Mon Aug 31 21:34:52 2009 NewtonNet: Wireless system with MAC address 001F3C508358 associated
[INFO] Mon Aug 31 21:34:52 2009 Above message repeated 1 times
[INFO] Mon Aug 31 21:34:52 2009 Wireless restart
[INFO] Mon Aug 31 21:34:50 2009 NewtonNet: Wireless system with MAC address 001F3C508358 secured and linked
[INFO] Mon Aug 31 21:34:50 2009 NewtonNet: Wireless system with MAC address 001F3C508358 associated
[INFO] Mon Aug 31 21:34:50 2009 Above message repeated 1 times
[INFO] Mon Aug 31 21:34:49 2009 Wireless restart
[INFO] Mon Aug 31 21:30:46 2009 Blocked incoming TCP packet from 72.199.88.206:5938 to 10.0.0.3:3447 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Aug 31 21:30:04 2009 Above message repeated 4 times
[INFO] Mon Aug 31 21:30:03 2009 Blocked incoming TCP packet from 72.199.88.206:5938 to 10.0.0.3:3447 as FIN:ACK received but there is no active connection
[INFO] Mon Aug 31 21:30:03 2009 Blocked incoming TCP packet from 72.199.88.206:5938 to 10.0.0.3:3447 as PSH:ACK received but there is no active connection
[INFO] Mon Aug 31 21:29:55 2009 Blocked incoming TCP packet from 72.199.88.206:5938 to 10.0.0.3:56371 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Aug 31 21:29:43 2009 Blocked incoming TCP packet from 74.222.4.66:5938 to 10.0.0.3:1305 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Aug 31 21:29:39 2009 Blocked outgoing TCP packet from 192.168.0.198:56364 to 63.111.69.126:80 as RST:ACK received but there is no active connection
[INFO] Mon Aug 31 21:29:33 2009 Blocked incoming TCP packet from 72.199.88.206:5938 to 10.0.0.3:56371 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Aug 31 21:29:24 2009 Blocked incoming TCP packet from 74.222.4.66:5938 to 10.0.0.3:1305 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Aug 31 21:29:21 2009 Blocked incoming TCP packet from 72.199.88.206:5938 to 10.0.0.3:56371 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Aug 31 21:29:16 2009 Above message repeated 1 times
[INFO] Mon Aug 31 21:29:15 2009 Blocked incoming TCP packet from 74.222.4.66:5938 to 10.0.0.3:1305 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Aug 31 21:29:13 2009 Blocked incoming TCP packet from 72.199.88.206:5938 to 10.0.0.3:56371 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Aug 31 21:29:12 2009 Blocked incoming TCP packet from 72.199.88.206:5938 to 10.0.0.3:56371 as FIN:ACK received but there is no active connection
[INFO] Mon Aug 31 21:29:12 2009 Blocked incoming TCP packet from 72.199.88.206:5938 to 10.0.0.3:56371 as PSH:ACK received but there is no active connection
[INFO] Mon Aug 31 21:29:10 2009 Blocked incoming TCP packet from 74.222.4.66:5938 to 10.0.0.3:1305 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Aug 31 21:28:58 2009 Above message repeated 3 times
[INFO] Mon Aug 31 21:28:57 2009 Blocked incoming TCP packet from 74.222.4.66:5938 to 10.0.0.3:1305 as FIN:ACK received but there is no active connection
[INFO] Mon Aug 31 21:28:57 2009 Blocked incoming TCP packet from 74.222.4.66:5938 to 10.0.0.3:1305 as PSH:ACK received but there is no active connection
[INFO] Mon Aug 31 21:28:56 2009 Blocked outgoing TCP packet from 192.168.0.199:1305 to 74.222.4.66:5938 as PSH:ACK received but there is no active connection
[INFO] Mon Aug 31 21:28:47 2009 NewtonNet: Wireless system with MAC address 001F3C508358 secured and linked
[INFO] Mon Aug 31 21:28:47 2009 NewtonNet: Wireless system with MAC address 001F3C508358 associated
[INFO] Mon Aug 31 21:28:47 2009 Above message repeated 1 times
[INFO] Mon Aug 31 21:28:46 2009 Wireless restart
[INFO] Mon Aug 31 21:28:46 2009 Blocked outgoing TCP packet from 192.168.0.196:3447 to 72.199.88.206:5938 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Aug 31 21:28:46 2009 Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
[INFO] Mon Aug 31 21:28:42 2009 Above message repeated 1 times
[INFO] Mon Aug 31 21:28:42 2009 Establishing connection w/ auth server: 165.193.79.40:443.
[INFO] Mon Aug 31 21:28:42 2009 Time synchronized
[INFO] Mon Aug 31 21:28:41 2009 Requesting time from 207.232.83.70
[INFO] Mon Aug 31 21:28:41 2009 Time server ntp1.dlink.com is at IP address 207.232.83.70
[INFO] Mon Aug 31 21:28:41 2009 Spam Server(s):  DLS.BSECURE.COM(443),
[INFO] Mon Aug 31 21:28:41 2009 Auth Server(s):  DLA.BSECURE.COM(443),
[INFO] Mon Aug 31 21:28:41 2009 Filter Servers(s):  DLF.BSECURE.COM(443), DLF2.BSECURE.COM(443),
[INFO] Mon Aug 31 21:28:40 2009 NewtonNet: Wireless system with MAC address 001F3C508358 secured and linked
[INFO] Mon Aug 31 21:28:40 2009 NewtonNet: Wireless system with MAC address 001F3C508358 associated
[INFO] Mon Aug 31 21:28:40 2009 Above message repeated 1 times
[INFO] Mon Aug 31 21:28:39 2009 Blocked incoming TCP packet from 63.111.69.126:80 to 10.0.0.3:56364 as RST received but there is no active connection
[INFO] Mon Aug 31 21:28:37 2009 Initiating securespot services.
[INFO] Mon Aug 31 21:28:37 2009 Allocating securespot services.
[WARN] Mon Aug 31 21:28:37 2009 Bsecure remote access enabled on port 8098.
[INFO] Mon Aug 31 21:28:37 2009 WAN interface speed measurement completed.  Upstream speed is 811 kbps
[INFO] Mon Aug 31 21:28:23 2009 NewtonNet: Wireless system with MAC address 001F3C508358 secured and linked
[INFO] Mon Aug 31 21:28:23 2009 NewtonNet: Wireless system with MAC address 001F3C508358 associated
[INFO] Mon Aug 31 21:28:23 2009 Above message repeated 1 times
[INFO] Mon Aug 31 21:28:22 2009 NewtonNet: Wireless system with MAC address 001CC449D9EE secured and linked
[INFO] Mon Aug 31 21:28:22 2009 NewtonNet: Wireless system with MAC address 001CC449D9EE associated
[INFO] Mon Aug 31 21:28:22 2009 Above message repeated 1 times
[INFO] Mon Aug 31 21:28:21 2009 Wireless link is up
[INFO] Mon Aug 31 21:28:18 2009 Starting DHCP server
[INFO] Mon Aug 31 21:28:12 2009 Estimating speed of WAN interface
[INFO] Mon Aug 31 21:28:11 2009 Obtained IP Address using DHCP. IP address is 10.0.0.3
[INFO] Mon Aug 31 21:28:11 2009 Bringing up WAN using DHCP
[INFO] Mon Aug 31 21:28:11 2009 WAN interface cable has been connected
[INFO] Mon Aug 31 21:28:11 2009 LAN interface is up
[INFO] Mon Aug 31 21:28:11 2009 LAN Ethernet Carrier Detected
[INFO] Mon Aug 31 21:28:10 2009 Device initialized
[WARN] Mon Aug 31 21:28:09 2009 Wireless schedule init
[INFO] Mon Aug 31 21:28:09 2009 guest: Unlock AP setup
[INFO] Mon Aug 31 21:28:09 2009 primary: Unlock AP setup
[INFO] Mon Aug 31 21:28:09 2009 No Internet access policy is in effect. Unrestricted Internet access allowed to everyone
« Last Edit: September 01, 2009, 08:10:00 PM by newtoncd »
Logged

macodin

  • Level 1 Member
  • *
  • Posts: 1
Re: Router disconnect issue -- log included
« Reply #1 on: September 01, 2009, 01:32:05 PM »
I'm not super great at this stuff so maybe someone better will come along, but if the phone also goes out wouldn't that make it a line issue or do you have a VOIP running through your router?

From what you said, I'd be calling Quest and asking what's up.  The router sits behind the modem so for the router to do what you're describing it'd have to mess up your modem in a way that not only knocks the modem off the network but freezes the line and I just don't see that happening.

Ahh, ignore me you have magicjack, I didn't catch that, so it very well could be the router.  Oh wells, sorry I didn't offer anything useful.
« Last Edit: September 01, 2009, 01:34:43 PM by macodin »
Logged

jpm67

  • Level 1 Member
  • *
  • Posts: 24
Here are some settings I have found to make the router most Compatible
« Reply #2 on: September 01, 2009, 03:50:04 PM »
Go to www.windowsupdate.com and download and install all available updates. Reboot and do it again until no more updates are available. In particular, look for available network card drivers and check those in the hardware section so they will be installed.

Make these settings on the router:

Under Advanced --> QOS engine --> QOS engine setup:
Uncheck Dynamic Fragmentation

Under Advanced --> Advanced Wireless -->Advanced Wireless Settings:
Uncheck Short GI

Under Advanced --> Wi-Fi Protected Setup:
Uncheck enable

Under Advanced --> Secure Spot:
Uncheck Enable Securespot services

Under Setup --> Internet --> Manual Internet Connection Setup:
Uncheck Enable Advanced DNS Service

Under Setup --> Network Settings --> Router Settings:
Uncheck Enable DNS Relay

Under Setup --> Network Settings --> DHCP Server Settings:
Check Always Broadcast

Under Setup --> Wireless Settings --> Manual Wireless Network Setup:
Set 802.11 Mode to Mixed n,g,b
Check Enable Auto Channel Scan
Set Transmission rate to Best (automatic)
Set channel width to Auto 20/40
security mode to WPA personal
Set Visibility Status to visible

Under Wireless Security Mode set:
Set Security mode WPA-Personal
Set WPA Mode to WPA2 Only
Cipher type AES
Pre-Shared Key is required





Logged

newtoncd

  • Level 1 Member
  • *
  • Posts: 19
Re: Router disconnect issue -- log included
« Reply #3 on: September 01, 2009, 04:00:50 PM »
Thanks for the thorough reply.  I am using DHCP, is there any issue with disabling 'Uncheck Enable DNS Relay' .... I think when I tried that before (after reading it on the forum), I was no longer able to access the Internet.

Update:  I made all of the changes, but when I select 'uncheck enable DNS relay', I am no longer able to access the Internet.  I was having an issue with the HP C6180 wireless printer losing its ability to connect to the network, so I had to set all of the devices with "assigned IPs".  Would that be the cause of me losing the Internet with unchecking the DNS relay?? 

Thanks!
« Last Edit: September 01, 2009, 04:29:21 PM by newtoncd »
Logged

jpm67

  • Level 1 Member
  • *
  • Posts: 24
Re: Router disconnect issue -- log included
« Reply #4 on: September 01, 2009, 05:29:02 PM »
With DNS relay checked each device is assigned 192.168.0.1 as the DNS server. When you uncheck it, the DNS servers from your Internet Service provider (ISP) are used. If you are using DHCP, they are assigned automatically. You have to enter them manually if you are using static IP addresses.

I recommend you "uncheck enable DNS relay" and reboot your router. Then, enable DCHP on your clients and EITHER reboot them OR go to the DOS command prompt and type "ipconfig /release" then type "ipconfig /renew". This forces a renewal of your DHCP "lease" which includes the new DNS settings. Your computers will still be trying to use the old DNS settings until you do this. That is why it quit working.

If you need to know what DNS servers your Windows clients are using, you should be able to go to the DOS command prompt and type "ipconfig /all".  You will see the IP addresses of the DNS servers you are using.
Logged

newtoncd

  • Level 1 Member
  • *
  • Posts: 19
Re: Router disconnect issue -- log included
« Reply #5 on: September 01, 2009, 05:42:27 PM »
Thanks, after a reboot, all of the devices are working with that option unchecked.  I feel pretty stupid that I didn't realize I need to reboot or release the old address.  Anyway, thanks, I hope your fixes work.

I cleared out the log, I guess time will tell.

Again, thanks.
« Last Edit: September 01, 2009, 05:46:23 PM by newtoncd »
Logged

jpm67

  • Level 1 Member
  • *
  • Posts: 24
Re: Router disconnect issue -- log included
« Reply #6 on: September 01, 2009, 06:18:00 PM »
Hope it works out. If it still gives you trouble, consider these settings:

Most desirable. Fastest speeds. Sometimes has compaibility issues:

Set WPA Mode to "Auto WPA or WPA2"
Cipher type "TKIP and AES"

Less desirable. Sometimes helps with devices that have trouble negotiating wether to use AES or TKIP. Devices must support AES. Older stuff often does not:

Set WPA Mode to "Auto WPA or WPA2"
Cipher type "AES"

Least desirable, but most compatibile. Slower speeds:

Set WPA Mode to WPA Only
Set Cipher type TKIP

Keep in mind, each time you make these changes you should reboot the router and reconfigure your wireless clients to match.
Logged

davevt31

  • Level 9 Member
  • ****
  • Posts: 1601
Re: Router disconnect issue -- log included
« Reply #7 on: September 01, 2009, 08:46:37 PM »
Looks like you are using the SecureSpot Services, I think this is why when you uncheck DNS Relay that you no longer get access.
Logged

newtoncd

  • Level 1 Member
  • *
  • Posts: 19
Re: Router disconnect issue -- log included
« Reply #8 on: September 02, 2009, 04:35:46 PM »
The router has been up for a record 23 hours and 41 minutes; not a single disconnect ... thank you so much!!!!
Logged

newtoncd

  • Level 1 Member
  • *
  • Posts: 19
Re: Router disconnect issue -- log included
« Reply #9 on: September 03, 2009, 04:35:24 PM »
48 hours ... no disconnects ... problem solved.  Thanks jpm67!!!!
Logged