Print

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

[P01arBear]

Hello all,

I've been searching all over forums on the web such as dslreports, and even this one. I saw alot of similar problem's but no true answer or at least anything I either haven't tried.

So here's the thing, at first the connexion would just drop very often a day. Since I've been using D-Link for some time, I tweaked a few things to try out, it  still drops at least 2-3 times a day if not more. When this happens, I can't access the router for at least 10-20 secondes, it drops all my computers. D-Link support responded 3x by mail to me after doing what they told me nothing works. Now they're asking me to call a D-Link technicien. So before that, I'm trying out here.

Specs
Firmware Version: 1.21
Hardware Version: A4
Internet provider: Videotron (cable)

LAN PCs
PC1) Laptop with Win XP with wifi "g"
PC2) Desktop with Vista Premium x64 with wifi "n" (DWA-552)

Configs










Logs

Code: [Select]

Priority Time Message
[INFO] Mon Apr 20 21:33:37 2009 Log viewed by IP address 192.168.0.198
[INFO] Mon Apr 20 21:33:30 2009 Allowed configuration authentication by IP address 192.168.0.198
[INFO] Mon Apr 20 21:31:32 2009 Blocked incoming TCP connection request from 59.46.201.60:6000 to (MY_IP):2967
[INFO] Mon Apr 20 21:30:01 2009 Blocked incoming TCP connection request from 221.192.199.36:12200 to (MY_IP):7212
[INFO] Mon Apr 20 21:30:01 2009 Blocked incoming TCP connection request from 221.192.199.36:12200 to (MY_IP):9090
[INFO] Mon Apr 20 21:28:47 2009 Administrator logout
[INFO] Mon Apr 20 21:19:09 2009 Blocked incoming TCP connection request from 221.192.199.36:12200 to (MY_IP):7212
[INFO] Mon Apr 20 21:19:09 2009 Blocked incoming TCP connection request from 221.192.199.36:12200 to (MY_IP):9090
[INFO] Mon Apr 20 21:10:57 2009 Blocked incoming ICMP packet (ICMP type 8) from 202.158.20.20 to (MY_IP)
[INFO] Mon Apr 20 21:10:20 2009 Above message repeated 1 times
[INFO] Mon Apr 20 21:10:13 2009 Wireless link is up
[INFO] Mon Apr 20 21:10:03 2009 Stored configuration to non-volatile memory
[INFO] Mon Apr 20 21:10:01 2009 Wireless link is down
[INFO] Mon Apr 20 21:10:01 2009 Wireless restart
[INFO] Mon Apr 20 21:10:01 2009 Disconnect all stations
[INFO] Mon Apr 20 21:09:46 2009 Stored configuration to non-volatile memory
[INFO] Mon Apr 20 21:04:55 2009 Blocked incoming UDP packet from 202.97.238.236:58996 to (MY_IP):1027
[INFO] Mon Apr 20 21:04:42 2009 Allowed configuration authentication by IP address 192.168.0.198
[INFO] Mon Apr 20 21:03:00 2009 Blocked incoming TCP connection request from 221.192.199.36:12200 to (MY_IP):9090
[INFO] Mon Apr 20 20:51:58 2009 Above message repeated 2 times
[INFO] Mon Apr 20 20:46:36 2009 Blocked incoming TCP connection request from 221.192.199.36:12200 to (MY_IP):7212
[INFO] Mon Apr 20 20:46:36 2009 Blocked incoming TCP connection request from 221.192.199.36:12200 to (MY_IP):9090
[INFO] Mon Apr 20 20:46:11 2009 Blocked incoming TCP connection request from 61.147.107.56:6000 to (MY_IP):2967
[INFO] Mon Apr 20 20:46:10 2009 Above message repeated 1 times
[INFO] Mon Apr 20 20:44:36 2009 Blocked incoming TCP packet from 208.43.231.121:80 to (MY_IP):3072 as SYN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:42:55 2009 Blocked incoming TCP packet from 77.67.91.105:80 to (MY_IP):54826 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:42:53 2009 Above message repeated 2 times
[INFO] Mon Apr 20 20:38:39 2009 Blocked incoming TCP packet from 81.52.130.176:80 to (MY_IP):54878 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:38:38 2009 Above message repeated 2 times
[INFO] Mon Apr 20 20:37:38 2009 Blocked incoming UDP packet from 221.209.110.105:38230 to (MY_IP):1027
[INFO] Mon Apr 20 20:37:11 2009 Blocked incoming TCP packet from 81.52.130.144:80 to (MY_IP):54877 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:37:10 2009 Above message repeated 2 times
[INFO] Mon Apr 20 20:36:23 2009 Blocked incoming TCP packet from 207.46.124.85:1863 to (MY_IP):54423 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Apr 20 20:36:16 2009 Blocked incoming TCP packet from 74.86.200.236:80 to (MY_IP):54891 as RST:ACK received but there is no active connection
[INFO] Mon Apr 20 20:36:10 2009 Blocked incoming TCP packet from 207.46.124.85:1863 to (MY_IP):54423 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Apr 20 20:36:04 2009 Above message repeated 1 times
[INFO] Mon Apr 20 20:36:01 2009 Blocked incoming TCP packet from 74.86.200.236:80 to (MY_IP):54869 as RST:ACK received but there is no active connection
[INFO] Mon Apr 20 20:36:01 2009 Blocked incoming TCP packet from 207.46.124.85:1863 to (MY_IP):54423 as FIN:PSH:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:59 2009 Above message repeated 1 times
[INFO] Mon Apr 20 20:35:58 2009 Blocked incoming TCP packet from 207.46.124.85:1863 to (MY_IP):54423 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:58 2009 Blocked incoming TCP packet from 207.46.124.85:1863 to (MY_IP):54423 as PSH:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:56 2009 Blocked incoming TCP packet from 74.86.200.236:80 to (MY_IP):54867 as RST:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:56 2009 Blocked incoming TCP packet from 74.86.200.236:80 to (MY_IP):54870 as RST:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:56 2009 Blocked incoming TCP packet from 74.86.200.236:80 to (MY_IP):54868 as RST:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:56 2009 Blocked incoming TCP packet from 74.86.200.236:80 to (MY_IP):54871 as RST:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:56 2009 Blocked incoming TCP packet from 74.86.200.236:80 to (MY_IP):54872 as RST:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:52 2009 Blocked incoming TCP connection request from 221.192.199.36:12200 to (MY_IP):9090
[INFO] Mon Apr 20 20:35:46 2009 Blocked incoming TCP packet from 74.125.93.104:80 to (MY_IP):54866 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:34 2009 Blocked outgoing TCP packet from 192.168.0.198:54826 to 77.67.91.105:80 as RST:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:26 2009 Blocked incoming TCP packet from 74.125.93.104:80 to (MY_IP):54866 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:24 2009 Blocked incoming TCP packet from 74.125.91.102:80 to (MY_IP):54880 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:21 2009 Blocked incoming TCP packet from 74.125.93.157:80 to (MY_IP):54876 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:19 2009 Blocked incoming TCP packet from 74.125.93.165:80 to (MY_IP):54873 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:09 2009 Blocked incoming TCP packet from 74.125.93.104:80 to (MY_IP):54866 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:08 2009 Blocked incoming TCP packet from 74.125.91.102:80 to (MY_IP):54880 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:07 2009 Blocked outgoing TCP packet from 192.168.0.198:54866 to 74.125.93.104:80 as RST:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:06 2009 Blocked outgoing TCP packet from 192.168.0.198:54891 to 74.86.200.236:80 as RST:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:04 2009 Blocked incoming TCP packet from 74.125.93.157:80 to (MY_IP):54876 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:02 2009 Blocked incoming TCP packet from 74.125.93.165:80 to (MY_IP):54873 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:00 2009 Blocked incoming TCP packet from 74.125.93.104:80 to (MY_IP):54866 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:35:00 2009 Blocked incoming TCP packet from 74.125.91.102:80 to (MY_IP):54880 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:34:59 2009 Blocked outgoing TCP packet from 192.168.0.198:54439 to 192.221.114.124:80 as RST:ACK received but there is no active connection
[INFO] Mon Apr 20 20:34:59 2009 Blocked outgoing TCP packet from 192.168.0.198:54821 to 24.200.54.24:1859 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:34:59 2009 Blocked outgoing TCP packet from 192.168.0.198:54423 to 207.46.124.85:1863 as PSH:ACK received but there is no active connection
[INFO] Mon Apr 20 20:34:56 2009 Blocked incoming TCP packet from 74.125.93.157:80 to (MY_IP):54876 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:34:56 2009 Blocked incoming TCP packet from 74.125.91.102:80 to (MY_IP):54880 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:34:56 2009 Blocked incoming TCP packet from 74.125.93.104:80 to (MY_IP):54866 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:34:55 2009 Starting DHCP server
[INFO] Mon Apr 20 20:34:54 2009 Blocked incoming TCP packet from 74.125.91.102:80 to (MY_IP):54880 as FIN:ACK received but there is no active connection
[INFO] Mon Apr 20 20:34:54 2009 Blocked incoming TCP packet from 74.125.93.165:80 to (MY_IP):54873 as FIN:ACK received but there is no active connection

Main usage
Voice chat over "Xfire" (Port 25999)
MSN (Port 1863, 3389, 6891-6900)
Web Browsing (Port 53, 80,880,443)
Gaming - The 4th Coming (Port 11677)
FTP (Port 20-21)


So 2 questions after this;
1-  How do I fix the constant wifi signal losts/Router booting. I've heard that the firmware 1.22b05 helped alot of people with a similar problem, would it be better for me? And if so, where can I get it

2- Do you suggest anything to optimize these settings?

Need response quickly, my retail warranty ends in 2 weeks must fix before!

Thank you for your time!

[Xinot]

1.22b05

Do not update to 1.30. If u do want 1.30, read threads about it first.

[P01arBear]

No worry's, not thinking about going on a beta that you can roll back wich is why I'd rather 1.22b05.

Any other feebacks, maybe techs that could help out? Or should I just just to 1.22b... 

[EddieZ]

I think the issue is caused by your internet gateway device. Does it have DHCP running also? Dual DHCP is asking for problems. If the internet gateway (modem) is not using DHCP you should change the WAN connection to static (and sill in the static IP from the modem) .

Also set Radio/transmission power to High instead of medium and check Unicasting.

[P01arBear]

Not sure about that...I'm not at home right now, but doesn't static requires login/pass? If so, I don't have it, since it's direct connect (cable).

But anyway, a problem with my web provider would bring down the wireless? I don't understand...I should just lose internet access, not acces to my router??!! 

And about transmit power, I've read else where on this forum phew times that low transmit would offert more stability. So that would be wrong or...

I'm at work, keep the advices coming in I'll try it all out tonight.

[Arvald]

I had a similar issue which weirdly enough was resolved though assigning a DHCP reservation to each machine.

It was a suggestion I found on this board but did not make much sense to me.

[P01arBear]

That I've already done. Didn't help.

[tipstir]

That I've already done. Didn't help.

In the location of the router what's near it that can give off EMI/EMF?

Digital Cable Box
HDTV
Stereo Surround Amp
Speakers
Cordless Phone
Computers
AC Power Outlet

Try placing the router near open space here and open doorway.. See what happen.. That firmware 1.21 has it given prior issues?

[P01arBear]

It's near a TV, but has normal cable. Still, if all other suggestions fail I'll try moving it see what gives. And if someone asks, all the phones are on 5ghz band...

Should I bring up firmware to 1.22b05? (I can roll back if I doesn't work right?)

[EddieZ]

Upgrade to 1.22 beta. No problem downgrading. Stay away from 1.30 though.

[P01arBear]

Alright, so when I get back:

Bring in firmware 1.22b05
Try to set WAN on static IP
Set Radio/transmission power to High
Check Unicasting
Set channel width to 20 (supposed to be more stable?)
Moving the router itself

Might just configure the QoS engine also, my passage on the forum as shown me alot about it, now I simply find it awesome!

If someone as something else to add, go ahead I'll try it all...

Oh yeah, does this version of firmware have the "securespot" thing!?

[tipstir]

Alright, so when I get back:

Bring in firmware 1.22b05
Try to set WAN on static IP
Set Radio/transmission power to High
Check Unicasting
Set channel width to 20 (supposed to be more stable?)
Moving the router itself

Might just configure the QoS engine also, my passage on the forum as shown me alot about it, now I simply find it awesome!

If someone as something else to add, go ahead I'll try it all...

Oh yeah, does this version of firmware have the "securespot" thing!?

Yep it does.. I am on 1.30NA but 1.22B05 was okay also... 1.30NA doesn't allow you to downgrade the firmware though.  I would leave the Qos and Wish settings by default unless you're really into gaming, downloading and media streaming.

[P01arBear]

Thanks for the quick response, very appreciated. Should already be setting this up in an hour (god...working days are long).

I really hope that this bug will be killed with these changes, I've always used D-Link, never had any trouble. It's the first time I invest so much in an router/wifi card, I trusted D-Link again. Just hope it won't let me down.

Could someone explain the meaning of this;

Code: [Select]

TCP packet from 74.125.93.157:80 to (MY_IP):54876 as FIN:ACK received but there is no active connectionI understand the fact I received some packet...Just don't understand first what the heck is on that port, second what does FIN:ACK and last when it says "no active connection" that refers to my modem or connected clients?

[EddieZ]

This was my first dlink product and I am very content with it. After having used Asus, Linksys and Tornado routers.

[tipstir]

This was my first dlink product and I am very content with it. After having used Asus, Linksys and Tornado routers.

First router ahh.. I've used wired routers using the DLINK for years they never had issues. Is just this wireless features is the issue. 1.11 okay for 6 months, tried 1.21 nope, then tried 1.22B05 okay working great for 1.5 months then same issue appeared. Now with 1.30NA wireless is stronger but the same issue is present using wireless but not through wireless. I don't have drops anymore but 404 error and hangs on certain sites is the issue for me.