Print

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

[stphn227]

Hi, this is my first post, I have been reading the topics other people made, trying different settings on the router but nothing can seem to work. I have been experiencing a lot of wireless resets, we have 2 computers and a PS3 running off our router. When I bring up the menu to connect to the router on my computer it shows that there are 7 different routers in the area. Sometimes it shows less, not sure why, but anyways, I have auto-channel scan set off and have the router set to channel 1, since there seems to be only 1 or sometimes 2 other people using that channel. WISH is turned off, dynamic defragmentation off, running mixed 802.11 N and G at 2.4 GHZ, automatic uplink speed is off, and I set it to what was measured, which is 1024 kbps, oh and this is with firmware 1.23. UDP/TCP endpoint filtering is set to endpoint independant, and anti-spoof checking is enabled. Everything else is factory settings.

We have Time Warner Cable, and the computer that is hard wired runs fine all the time, no problems. We seem to get most of the problems under a heavy load, my brother will be playing starcraft 2, and myself on call of duty, and not only are things running laggy, but it drops all the time. If I am surfing the internet and he is playing a game or streaming something, it happens as well, though not as frequently. Signal strength is not a problem, the router is directly below the 2 rooms where the computers/PS3 are located and it is almost always a 100% signal. This is the A2 model of the router as well, what really has me bumming is that I lost the receipt so I would be kinda screwed if I have to replace the router itself. Here is part of the log, not sure if it helps, but here it is anyways.

[INFO] Fri Dec 17 16:44:21 2010 Allowed configuration authentication by IP address 192.168.0.197
[INFO] Fri Dec 17 16:43:57 2010 Wireless restart
[INFO] Fri Dec 17 16:43:48 2010 Blocked incoming TCP connection request from 75.118.205.179:1052 to 66.74.131.68:4899
[INFO] Fri Dec 17 16:43:47 2010 Blocked incoming ICMP error message (ICMP type 3) from 98.151.2.220 to 66.74.131.68 as there is no UDP session active between 66.74.131.68:41308 and 192.168.1.100:31264
[INFO] Fri Dec 17 16:43:18 2010 Blocked incoming TCP connection request from 61.147.112.148:6000 to 66.74.131.68:1433
[INFO] Fri Dec 17 16:42:35 2010 Administrator logout
[INFO] Fri Dec 17 16:40:49 2010 Wireless restart
[INFO] Fri Dec 17 16:40:33 2010 Blocked incoming ICMP error message (ICMP type 3) from 173.17.192.124 to 66.74.131.68 as there is no UDP session active between 0.0.0.0:0 and 173.17.192.124:62028
[INFO] Fri Dec 17 16:40:19 2010 Above message repeated 1 times
[INFO] Fri Dec 17 16:37:37 2010 Blocked incoming TCP connection request from 221.1.220.185:12200 to 66.74.131.68:1080
[INFO] Fri Dec 17 16:37:35 2010 Log viewed by IP address 192.168.0.197
[INFO] Fri Dec 17 16:37:31 2010 Allowed configuration authentication by IP address 192.168.0.197
[INFO] Fri Dec 17 16:36:50 2010 Blocked incoming ICMP packet (ICMP type from 129.82.138.38 to 66.74.131.68
[WARN] Fri Dec 17 16:36:30 2010 A network computer (daniel) was assigned the IP address of 192.168.0.195.
[INFO] Fri Dec 17 16:36:29 2010 UPnP expired entry 255.255.255.255 <-> 66.74.131.68:3724 <-> 192.168.0.1953724 TCP 'Blizzard Downloader'
[INFO] Fri Dec 17 16:36:29 2010 The DHCP server address 192.168.0.195 was released by the network device - the network device no longer wants to use it.
[INFO] Fri Dec 17 16:36:26 2010 williams1: Wireless system with MAC address 001C10E4899B secured and linked
[INFO] Fri Dec 17 16:36:26 2010 williams1: Wireless system with MAC address 001C10E4899B associated
[INFO] Fri Dec 17 16:36:26 2010 Above message repeated 1 times
[INFO] Fri Dec 17 16:35:23 2010 williams1: Wireless system with MAC address 001C10E4899B disconnected for reason: Received Deauthentication
[INFO] Fri Dec 17 16:35:23 2010 williams1: Wireless system with MAC address 001C10E4899B associated
[INFO] Fri Dec 17 16:35:23 2010 Above message repeated 1 times
[INFO] Fri Dec 17 16:35:19 2010 Wireless restart
[INFO] Fri Dec 17 16:35:17 2010 Above message repeated 1 times
[INFO] Fri Dec 17 16:34:47 2010 williams1: Wireless system with MAC address 001D0D133A3B disconnected for reason: Received Deauthentication
[INFO] Fri Dec 17 16:34:46 2010 The DHCP server address 192.168.0.194 was released by the network device - the network device no longer wants to use it.
[INFO] Fri Dec 17 16:34:46 2010 UPnP deleted entry 255.255.255.255 <-> 66.74.131.68:3658 UDP
[INFO] Fri Dec 17 16:34:29 2010 Wireless restart
[INFO] Fri Dec 17 16:33:55 2010 Above message repeated 1 times
[INFO] Fri Dec 17 16:33:49 2010 Blocked incoming TCP connection request from 218.29.97.143:3097 to 66.74.131.68:5900
[INFO] Fri Dec 17 16:33:41 2010 Wireless restart
[INFO] Fri Dec 17 16:29:50 2010 Above message repeated 2 times
[INFO] Fri Dec 17 16:29:07 2010 Blocked incoming TCP connection request from 60.173.9.11:6000 to 66.74.131.68:1433
[INFO] Fri Dec 17 16:28:59 2010 Wireless restart
[INFO] Fri Dec 17 16:25:59 2010 Above message repeated 5 times
[INFO] Fri Dec 17 16:25:46 2010 Blocked incoming ICMP packet (ICMP type from 129.82.138.38 to 66.74.131.68
[INFO] Fri Dec 17 16:25:44 2010 Wireless restart
[INFO] Fri Dec 17 16:23:03 2010 Blocked incoming ICMP error message (ICMP type 3) from 90.193.140.28 to 66.74.131.68 as there is no UDP session active between 66.74.131.68:41308 and 192.168.0.5:49654
[INFO] Fri Dec 17 16:22:21 2010 Wireless restart
[INFO] Fri Dec 17 16:18:50 2010 Above message repeated 3 times
[INFO] Fri Dec 17 16:18:24 2010 Blocked incoming TCP connection request from 58.218.204.110:12200 to 66.74.131.68:8090
[INFO] Fri Dec 17 16:18:24 2010 Blocked incoming TCP connection request from 58.218.204.110:12200 to 66.74.131.68:9000
[INFO] Fri Dec 17 16:18:24 2010 Blocked incoming TCP connection request from 58.218.204.110:12200 to 66.74.131.68:9090
[INFO] Fri Dec 17 16:18:24 2010 Blocked incoming TCP connection request from 58.218.204.110:12200 to 66.74.131.68:3246
[INFO] Fri Dec 17 16:18:24 2010 Blocked incoming TCP connection request from 58.218.204.110:12200 to 66.74.131.68:2479








Any help is greatly appreciated, thanks so much.

[FurryNutz]

What are the highest supported wifi mode devices in your house hold? If there isn't any N mode devices, it's recommended using G mode only at 2.4Ghz for most WiFi gaming. 5Ghz will work however if there are obstructions in the way, this will effect the 5Ghz frequency. Also what Security modes are you using? WPA Personal WPA2 TPIK+AES is preferred for general use.

I would try to turn off all wireless devices, any cell phones, Iphones and other Wifi devices. Are there any cordless phones in the house? Shut these off as well.

Use one wired connected PC to configure the router for now.

I would set the routers WiFi for G mode only at 2.4Ghz with no security for testing. If everything else is off, bring up the Williams1 device. By the logs, looks like this was one of the devices that seems to be connecting then getting disconnected. What is this device? See if this device and stream or browse the internet. Look at the logs. See if you notice any disconnections. If nothing, bring up another device. Keep doing this until you see something or anything.

I would start over again with everything off and this time enable security on the router now.
It's possible there could be interference from other routers in the area or cordless phones. Try changing to all different channels to be sure.

Let us know what you find out.

[stphn227]

The computer I use uses a N USB adapter, and my brother's uses a G internal card, then there is the PS3, i'm not sure if that uses G or N. There are no cell phones in the home connected to the router. Williams1 is the name of our wireless network. The security is set to WPA/WPA2. There are 3 cordless phones throughout the house, i'm not sure if it would be an option to turn those off as they get used quite frequently.

[stphn227]

Also, both me and my brother are playing WoW at the same time, and i'm getting a latency of 550MS on a D-link DWA-130 N USB adapter, and he is getting a latency less than 100 on a Linksys G internal card, not sure what the model is on that.

[stphn227]

Update, I downgraded to firmware 1.21 and things have been running much faster and smoother since. I'll keep you posted.

[FurryNutz]

If you have 3 cordless phones thru out the house, need to see what frequency they operate on. They can introduce interference and will produce the wireless disconnects you see in the logs.

[torano]

Update, I downgraded to firmware 1.21 and things have been running much faster and smoother since. I'll keep you posted.

That's odd. I always heard 1.22NA was the better of them. Maybe it's just because of the factory reset that comes with an firmware upgrade and not from the firmware? Or is 1.21NA known to be a better firmware for wireless and wired routing?

[FurryNutz]

You can definately try using v1.21. There were some of us that had bad experiences with it regarding router hangs and wireless restarts on it. I'm curious maybe if v1.21 works better on A2 hardware than A1. Mines A1.

[icemankent]

From your router logs I noticed a whole bunch of "wireless restarts".
Same issue I have been having.

(I RMA'd my 4500 recently specifically because of that issue.  Unfortunately, I did not try downgrading the firmware first, as a test to see if it would resolve the wireless restart issue)

Now that you say you've DOWNgraded to 1.21, can you please tell me if your "wireless restarts" still continue to be an issue, or did they go away permanently ?

[stphn227]

Ok, i'm not getting flat out dropped from anything anymore it seems, but video games seem to run at a total crawl, it was running great when I first put the firmware on, but suddenly it lags like hell. The internet is fine, I can stream stuff without any issue, but I get lag spikes like no other playing games. To answer the question about the cordless phones, 2 of them are 5.8 GHZ, and the third one doesn't say what it is on it anywhere.




Here is another log....


[INFO]   Sat Jan 31 22:52:34 2004   Allowed configuration authentication by IP address 192.168.0.196
[INFO]   Sat Jan 31 22:52:33 2004   Wireless restart
[INFO]   Sat Jan 31 22:52:08 2004   Blocked incoming UDP packet from 148.122.219.76:36272 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:51:19 2004   Blocked incoming UDP packet from 76.188.91.198:10144 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:50:35 2004   Wireless restart
[INFO]   Sat Jan 31 22:50:07 2004   Blocked incoming UDP packet from 173.69.125.39:52226 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:49:53 2004   Blocked incoming UDP packet from 174.117.59.65:52940 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:49:04 2004   Blocked incoming UDP packet from 166.82.215.35:44482 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:48:34 2004   Above message repeated 2 times
[INFO]   Sat Jan 31 22:48:31 2004   Wireless restart
[INFO]   Sat Jan 31 22:48:22 2004   Above message repeated 1 times
[INFO]   Sat Jan 31 22:48:03 2004   Blocked incoming UDP packet from 166.82.215.35:44482 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:47:51 2004   Wireless restart
[INFO]   Sat Jan 31 22:47:16 2004   Blocked incoming UDP packet from 174.117.59.65:52940 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:46:21 2004   Wireless restart
[INFO]   Sat Jan 31 22:45:12 2004   Above message repeated 6 times
[INFO]   Sat Jan 31 22:45:09 2004   Blocked incoming UDP packet from 173.69.125.39:52226 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:45:03 2004   Wireless restart
[INFO]   Sat Jan 31 22:43:05 2004   Above message repeated 1 times
[INFO]   Sat Jan 31 22:42:39 2004   Blocked incoming ICMP packet (ICMP type from 129.82.138.38 to 66.74.131.68
[INFO]   Sat Jan 31 22:42:26 2004   Blocked incoming UDP packet from 173.51.182.220:52207 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:42:11 2004   Wireless restart
[INFO]   Sat Jan 31 22:41:56 2004   Blocked incoming UDP packet from 173.51.182.220:52207 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:41:31 2004   Above message repeated 1 times
[INFO]   Sat Jan 31 22:41:23 2004   Wireless restart
[INFO]   Sat Jan 31 22:40:23 2004   Above message repeated 3 times
[INFO]   Sat Jan 31 22:40:12 2004   Blocked incoming UDP packet from 173.69.125.39:52226 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:39:15 2004   Blocked incoming TCP connection request from 75.182.33.8:2580 to 66.74.131.68:11496
[INFO]   Sat Jan 31 22:39:09 2004   Above message repeated 1 times
[INFO]   Sat Jan 31 22:39:09 2004   Wireless restart
[INFO]   Sat Jan 31 22:39:06 2004   Blocked incoming TCP connection request from 75.182.33.8:2580 to 66.74.131.68:11496
[INFO]   Sat Jan 31 22:39:06 2004   Wireless restart
[INFO]   Sat Jan 31 22:38:14 2004   Above message repeated 1 times
[INFO]   Sat Jan 31 22:36:14 2004   Blocked incoming TCP connection request from 80.48.86.119:60383 to 66.74.131.68:11496
[INFO]   Sat Jan 31 22:36:10 2004   Wireless restart
[INFO]   Sat Jan 31 22:36:08 2004   Blocked incoming TCP connection request from 80.48.86.119:60383 to 66.74.131.68:11496
[INFO]   Sat Jan 31 22:36:05 2004   Above message repeated 1 times
[INFO]   Sat Jan 31 22:36:00 2004   Wireless restart
[INFO]   Sat Jan 31 22:35:26 2004   Above message repeated 3 times
[INFO]   Sat Jan 31 22:35:14 2004   Blocked incoming UDP packet from 71.170.213.13:40236 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:35:11 2004   Blocked incoming UDP packet from 173.69.125.39:52226 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:34:00 2004   Wireless restart
[INFO]   Sat Jan 31 22:33:57 2004   Above message repeated 1 times
[INFO]   Sat Jan 31 22:33:57 2004   Blocked incoming UDP packet from 76.91.73.179:25932 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:33:35 2004   Wireless restart
[INFO]   Sat Jan 31 22:33:14 2004   Blocked incoming UDP packet from 174.117.59.65:52940 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:33:02 2004   Wireless restart
[INFO]   Sat Jan 31 22:32:27 2004   Blocked incoming UDP packet from 76.172.158.6:58043 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:31:41 2004   Wireless restart
[INFO]   Sat Jan 31 22:31:40 2004   Blocked incoming TCP connection request from 221.192.199.49:12200 to 66.74.131.68:9000
[INFO]   Sat Jan 31 22:31:40 2004   Blocked incoming TCP connection request from 221.192.199.49:12200 to 66.74.131.68:9090
[INFO]   Sat Jan 31 22:31:40 2004   Blocked incoming TCP connection request from 221.192.199.49:12200 to 66.74.131.68:3246
[INFO]   Sat Jan 31 22:31:36 2004   Blocked incoming ICMP packet (ICMP type from 129.82.138.38 to 66.74.131.68
[INFO]   Sat Jan 31 22:31:02 2004   Wireless restart
[INFO]   Sat Jan 31 22:30:50 2004   Blocked incoming UDP packet from 66.8.132.33:15373 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:30:41 2004   Blocked incoming UDP packet from 118.92.185.17:21179 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:30:17 2004   Blocked incoming UDP packet from 83.108.60.116:10456 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:30:07 2004   Blocked incoming UDP packet from 173.69.125.39:52226 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:29:45 2004   Wireless restart
[INFO]   Sat Jan 31 22:29:07 2004   Above message repeated 3 times
[INFO]   Sat Jan 31 22:28:30 2004   Blocked incoming TCP packet from 58.64.173.48:80 to 66.74.131.68:61806 as SYN:ACK received but there is no active connection
[INFO]   Sat Jan 31 22:28:29 2004   Blocked incoming UDP packet from 76.114.171.59:17332 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:27:45 2004   Above message repeated 1 times
[INFO]   Sat Jan 31 22:27:27 2004   Wireless restart
[INFO]   Sat Jan 31 22:25:48 2004   Above message repeated 4 times
[INFO]   Sat Jan 31 22:25:42 2004   Blocked incoming UDP packet from 174.54.220.96:28448 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:25:32 2004   Blocked incoming TCP connection request from 80.48.86.119:63219 to 66.74.131.68:11496
[INFO]   Sat Jan 31 22:25:23 2004   Above message repeated 2 times
[INFO]   Sat Jan 31 22:25:15 2004   Blocked incoming UDP packet from 209.121.8.163:63561 to 66.74.131.68:41308
[INFO]   Sat Jan 31 22:25:12 2004   Blocked incoming TCP connection request from 58.218.204.110:12200 to 66.74.131.68:6588
[INFO]   Sat Jan 31 22:25:12 2004   Blocked incoming TCP connection request from 58.218.204.110:12200 to 66.74.131.68:8088
[INFO]   Sat Jan 31 22:25:12 2004   Blocked incoming TCP connection request from 58.218.204.110:12200 to 66.74.131.68:8000
[INFO]   Sat Jan 31 22:25:12 2004   Blocked incoming TCP connection request from 58.218.204.110:12200 to 66.74.131.68:8090
[INFO]   Sat Jan 31 22:25:12 2004   Blocked incoming TCP connection request from 58.218.204.110:12200 to 66.74.131.68:9000
[INFO]   Sat Jan 31 22:25:12 2004   Blocked incoming TCP connection request from 58.218.204.110:12200 to 66.74.131.68:9090
[INFO]   Sat Jan 31 22:25:12 2004   Blocked incoming TCP connection request from 58.218.204.110:12200 to 66.74.131.68:3246
[INFO]   Sat Jan 31 22:25:12 2004   Blocked incoming TCP connection request from 58.218.204.110:12200 to 66.74.131.68:9415
[INFO]   Sat Jan 31 22:25:12 2004   Blocked incoming TCP connection request from 58.218.204.110:12200 to 66.74.131.68:27977
[INFO]   Sat Jan 31 22:25:12 2004   Blocked incoming TCP connection request from 58.218.204.110:12200 to 66.74.131.68:8085

[icemankent]

Holy WIRELESS RESTART, batman !!
It would seem I am/was not alone in getting that problem.

I can only hope the next 4500 I get is not a lemon.
If the new one they send me still has the same issue, I'll send it to DLINK for them to "fix", since they admitted to me via email that a "wireless restart" should only happen when you reboot the router - anything else is a defect in the radio.

[stphn227]

Went back to factory settings, and it seems to have definitely helped for now.

Crossing my fingers...

[FurryNutz]

If your not getting dropped however your seeing a slow down in streaming video. I would review the gaming and gamefuel stick for xbox for additional configuration to see if that will help the with the streaming. Thats what I use here and it work well. I haven't watched any video to my xbox over wireless so I'm not sure how well it works there. Most of my devices are wired accept for my Mac Book and Iphones. Let us know how it goes.

[Locane]

I've been having a similar issue, although I'm not using the wireless.

Mine will just randomly start refusing packets from IP addresses within my network, and it will make websites not load properly and behave extremely slowly.

Restarting the router clears it right up, and it stays good for roughly 3 weeks before it craps out again.

I'm a big fan of D-Link, and it's disappointing to have something I paid $150 for do this kind of thing.

--Locane

[FurryNutz]

what IP addresses are being refused packets? What devices are using these IP addresses?