D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: abjurian on July 29, 2009, 08:32:42 AM
-
??? ??? I should have never left v1.21 firmware cause it was working better then this is now. This router just stops responding all together. Lights are flashing and it seems like it is doing something but you can not log into it from a wireless or LAN machine. No internet access or LAN access either. it just stops responding! What a pain in the butt. I have to literally power it off and turn it back on for it to work again. I have tried router defaults and many other settings to no avail. Please DLINK HELP!!!!! ??? ???
-
Whos is your ISP and what type of Internet connection do you have? and What modem brand?
-
Try turning off "Enable NTP Server" and also turn off "DNS realy"
-
I installed the 1.32Nb05 and that worked for 5 days without any issues it seems.
The first light since months.
I have switched over to 1.32 final (mistake) and the last few days are hell again with slow downs and lock ups .
Is there a difference with 1.32b05 and 1.32 final?
First it slows down my clients till the point that internet does not work anymore.
In that case I can not log in to the router anymore.
Reseting the router is the only thing that helps (for a relative short time e.g. upto an hour)
Seeing all issues i had uptill now and it always being the router it must be acting up again.
I am sooooo fed up with the thing that I will replace it with the old one again :(
All this negative energy and frustration is just not worth it anymore.
i'll check back one more time in a few months to see if the problems have gone.
Trying to return the product after a half a year with the webshop will even be more frustration which i really have no energy for anymore.
-
Did you try re-flashing the fw?
This is what I did and it seems to work better
Reset back to defaults by holding a pin in the reset hole. update the fw and reset back to defaults again.
DO NOT load your old configuration. Set it up manually.
Hop this helps.
-
http://forums.dlink.com/index.php?topic=6206.0
disable DNS relay, you might need to renew your network connection on your machines after.
This should work.
This was introduced in 1.22B05. So far dlink has yet to admit their might be a firmware issue.
-
Here's hoping that disabling DNS Relay works (will know tomorrow). As an FYI I called support on this and they are totally oblivious...
Device:
Dlink DIR-655
Problem:
Updated firmware from 1.21 to 1.32na now unit locks up/freezes within 12 hours of operation. It still brodcasts SSID but refuses to communicate either via wireless or wired connection to any device unless hard booted by unplugging power. Performed a hard reset from back of device and reloaded firmware, settings from backup, and lockups persist.
Attempted fix: ('Solution' pending):
Dlink Support: Change MTU value from 1500 to 1492 (me thinks they be off base here) - DONE.
Dlink Forum solution(s): Reload 2x and hand re-configure settings OR disable DNS Relay - DONE.
Results: pending....
EDIT UPDATE: So far the DNS Relay disable seems to have solved the lock-up issue but leaves release 1.32na offically buggy and dysfunctional. Hopefully I'll not need the DNS Relay function anytime soon...
***************************************
On a personal note: I know some of these devices can be buggers to configure, end users can be *****s and liars (those reading this excepted) and therefore support calls could go on forever, but to expect payment for support when a device is out of warranty but gets broken by a firmware update that cannot be rolled back is bad buisness practice. This is twice for me now >:(
-
Well, I have the same problem on 1.31NA and 1.32NA if I set the router ntp server to 0.asia.pool.ntp.org . The router will go into an infinite reboot loop. I set it to my faculty ntp server and it works fine. So if you use ntp server, you might want to change it to a diiferent server or disable it. On that note, 1.21 works fine with that asia server.
-
Well, I have the same problem on 1.31NA and 1.32NA if I set the router ntp server to 0.asia.pool.ntp.org . The router will go into an infinite reboot loop. I set it to my faculty ntp server and it works fine. So if you use ntp server, you might want to change it to a diiferent server or disable it. On that note, 1.21 works fine with that asia server.
There is a thread about that also if you do a search. This is different than what the original poster is talking about.
-
I know but I don't care about this problem much. Just said it so the OP might find out his problem.
-
I am using Armstrong Cable. I tried resetting router. Reloading the firmware. Setting it to factory defaults and manually putting in my info again. I am using a motorola cable modem that the cable company provides. I get 2300 KBps downloads when everything is working! I am not using an NTP server I have no need. I just use the internet for my consoles and email and web. What gets me the maddest is it works fine for everyone for 24-48 hours then just won't respond to anything! Lights are flashing, still broadcasting the SSID but nothing works. Can't connect to the router, internet to computer to computer nothing.
-
As suggested by others, try disabling DNS Relay under Network Settings.
-
I have noticed that when I have a heavy use of torrants and finish downloading the DIr 655 is less responsive and I have to reboot it (power cycle) to get into the settings screen.
-
Maybe time for a RMA.
-
I have hardware v A4 and 1.32NA and the "Enable DNS relay" is greyed out and I can't even uncheck it. My router has the same issue where it will go well for 3-5 days and then it'll just hang even though the lights still go. Can't login to the router and need to unplug it to reset it. Hoping that these tech support folks start getting on top of the QC of their firmwares!
-
I'm having the exact same problem as the OP after upgrading to this firmware. I get a couple of days then have to reboot. I have never had this problem before and it has only started happening with this firmware. The telling point is that even though computers are connected I can no longer reach the routers control panel on 192.168.0.1 I reboot and all is fine for a couple more days. Really snnoying.
-
Did you turn off DNS relay?
I love how more and more people are coming to the board with this problem. Maybe d-link won't be able to keep ignoring it.
-
Hopefully they will fix it then ;) Yes I have now disabled it, only up one day though so waiting to see if that fixes it. Interestingly this is the first time I have had this problem, ONLY on this particular firmware (and I have been updating each new one as they come out).
-
Hopefully they will fix it then ;) Yes I have now disabled it, only up one day though so waiting to see if that fixes it. Interestingly this is the first time I have had this problem, ONLY on this particular firmware (and I have been updating each new one as they come out).
This problem started in 1.22B05 and affects the latest officially release 1.31. The issue is also on the DIR-825 on its newest firmware.
-
Did you turn off DNS relay?
I love how more and more people are coming to the board with this problem. Maybe d-link won't be able to keep ignoring it.
They know it's a problem, Lycan even has a poll on it. Not sure when fw1.21-fw1.22 came out but it's been around since then.
-
They know it's a problem, Lycan even has a poll on it. Not sure when fw1.21-fw1.22 came out but it's been around since then.
Lycan created the poll because I sent him a private message after he locked the freezing thread asking if he could make a sticky post about turning off dns relay if your router is freezing.
-
Lycan created the poll because I sent him a private message after he locked the freezing thread asking if he could make a sticky post about turning off dns relay if your router is freezing.
If Lycan created a poll because you sent him a private message, good for you! But if you search the forum on the subject "DNS Relay", "DNS Relay Problem", etc... you will find has been around since fw1.20-1.21 releases. It's not a new problem!
It's a problem they have not fixed, or don't know how to fix.
-
If Lycan created a poll because you sent him a private message, good for you! But if you search the forum on the subject "DNS Relay", "DNS Relay Problem", etc... you will find has been around since fw1.20-1.21 releases. It's not a new problem!
It's a problem they have not fixed, or don't know how to fix.
I know its not a new problem, I said its been around since 1.22B05.
1.21 had a DNS slowdown issue and 1.22B05 introduced a fix that caused the freezing. Read the long freezing thread, Lycan said that DNS relay shouldn't cause a router to freeze, and if it is freezing to RMA it, I think he even said it wasn't a firmware problem. So far I have not seen any comment by anyone at D-Link saying, "there is a problem with the firmware.".
-
So is it a design flaw with the chipset or something more? The DNS issue is just not with the Dir 655, other Dlink products suffer from the same issue. Explain if you can. MODS are welcome to add their 2 cents!
-
So is it a design flaw with the chipset or something more? Explain if you can. MODS are welcome to add their 2 cents!
I have no idea.
There are a couple things we know:
This seems to happen to every hardware version but not every router
It started in 1.22B05 which "fixed" DNS relay
Its also happening on the DIR-825 only on 1.11+ (I have the original 825 running 1.01 no freezing)
If you read the read the Freezing thread, it sounded like no one at D-link had been able to reproduce this issue or admit that it was a firmware problem. I am fairly confident this isn't a hardware problem. I ran 1.11 on my DIR-655 for months without rebooting it with DNS relay turned on. I upgraded to 1.21 for shareport but didn't end up using it. I then experienced the DNS slowdown problem so I upgraded to 1.22B05 and had freezes that were only fixed by turning off DNS relay. Same issue on 1.32.
-
I will bet the problems has to do with shareport and the programming involved to make it functional.
All in the name of marketing to keep up the competition. Nevermind if it works right just market it and they (us) will buy.
It's sad really because I bought my Dir 655 A2 with FW1.11, it was a router then. Not a NAS device or print server. I upgraded FW because of VOIP problem I had, I like Dlink created my own problem. :-\
-
Its hard to tell because everyone doesn't have the problem, nor are they all running the same configurations. I have had an A2 since 10/2007 that has never had any issues. I have run every beta firmware that has been put out. I have DNS Relay checked and have not experienced any lockups. I do NOT have shareport installed as I use the USB port to power a laptop cooler that I have sitting underneath the router to keep it cool.
-
Its hard to tell because everyone doesn't have the problem, nor are they all running the same configurations. I have had an A2 since 10/2007 that has never had any issues. I have run every beta firmware that has been put out. I have DNS Relay checked and have not experienced any lockups. I do NOT have shareport installed as I use the USB port to power a laptop cooler that I have sitting underneath the router to keep it cool.
maybe heat is the issue. The way it seems now if its partly cloudy and if it's Monday or Friday and if the temp is above 85 degrees and the wind is blowing out of the southwest then this issue will happen. ;D
-
maybe heat is the issue. The way it seems now if its partly cloudy and if it's Monday or Friday and if the temp is above 85 degrees and the wind is blowing out of the southwest then this issue will happen. ;D
I highly doubt its a heat issue, considering I bought my router in July of 08 and I didn't have 1 freeze during the hottest parts of the summer. I also highly doubt that a firmware upgrade could cause the router to "go over the edge" as if the router was teetering on the edge of heat related stability.
Its clearly environment related, network environment and use environment, not physical.
-
I disabled the DNS relay. but now for some reason we have not gotten disconnected but now I am so slow it is unbelievable. what the heck! AHHHHHHHHHHHHHHHHHHHHHHH.
-
I have a A2 and a A3...
The A2 has the lockup problem on 1.32NA....
I will try disabling the DNS relay...
if that doesn't fix it, I'll reconfigure the A3 unit to see if it's any better than the A2...
(the A3 is just another wireless access point in the other side of my house...)
1.21 was rock solid... my wife works from home and I'm her IT support...
WHY DID I UPGRADE!!! ARGH!!!
-
I have a A2 and a A3...
The A2 has the lockup problem on 1.32NA....
I will try disabling the DNS relay...
if that doesn't fix it, I'll reconfigure the A3 unit to see if it's any better than the A2...
(the A3 is just another wireless access point in the other side of my house...)
1.21 was rock solid... my wife works from home and I'm her IT support...
WHY DID I UPGRADE!!! ARGH!!!
+1 here
Definetly not sticking with D-Link in the future. Was going to advice our company to buy D-Link, but after the problems I have been through, I decided to advice our company to stay away from D-Link instead.
-
make sure all of you post in the sticky at the top of the forum.
-
I just installed the new firmware also just a week ago have had 2 lockups in the last week... This is unacceptable because this is for our server machine here in the office.
Should have never upgraded...
-
Brutal!!!!
HW-A3
F/W-11.1 upgraded to 1.32NA
Tech support know very little at this point.
"Changing your wireless Name might help..." Huh? it did not help the random lockups.
Tech support also said.. "There is now way to disable the CAPTCHA at login.."
RTFM tech support. I found the switch myself, nm.
After speaking with a useless tech support person, i was told they were elevating my call by transferring me to a service rep. After 10 minutes on hold, i got disconnected.
I guess i'll call back and try again later today..
I'm having to reboot my router once a day since upgrading.
-
Brutal!!!!
HW-A3
F/W-11.1 upgraded to 1.32NA
Tech support know very little at this point.
"Changing your wireless Name might help..." Huh? it did not help the random lockups.
Tech support also said.. "There is now way to disable the CAPTCHA at login.."
RTFM tech support. I found the switch myself, nm.
After speaking with a useless tech support person, i was told they were elevating my call by transferring me to a service rep. After 10 minutes on hold, i got disconnected.
I guess i'll call back and try again later today..
I'm having to reboot my router once a day since upgrading.
Welcome to everyones problems. Glad to join the group in which everyone is pissed cause theres no fixed yet. All i can say is to disable the DNS relay crap. Im actually thinking of buying a new dir-655 and returning my old dir-655. I still have the box. They should let people do that cause the new firmware just sucks.
-
Welcome to everyones problems. Glad to join the group in which everyone is pissed cause theres no fixed yet. All i can say is to disable the DNS relay ****. Im actually thinking of buying a new dir-655 and returning my old dir-655. I still have the box. They should let people do that cause the new firmware just sucks.
Why buy a new Dir 655? There has to be something else (with functional firmware) that is close. I been looking @ TRENDnet TEW-633GR.
-
Looks like staying on 1.21 for now is a very good idea...
-
Looks like staying on 1.21 for now is a very good idea...
it is an AMAZING IDEA!!! if you ever upgrade the new firmware... look forward into buying a new product.. and MAKE SURE ITS NOT DLINK!
-
it is an AMAZING IDEA!!! if you ever upgrade the new firmware... look forward into buying a new product.. and MAKE SURE ITS NOT DLINK!
Work on your anger management.
Got a perfectly working 655 with 1.32. Perhaps you messed it up yourself?
-
This doesn't exactly match the subject line, but I sure know what DIR-655 lockup is! I am on my third D-Link DIR-655 via the RMA process. This one arrived the middle of July, 2009. It worked fine until August 10th. It locked up and I noticed the Status LED was on solid - not blinking as it is supposed to. A power of and back on got it going. It locked up again this morning - Aug 15, 2009 with the same indications. I called D-Link to report the problem. They were going to send me router #4, but thought better of it. Now I have to call their super duper specialist on Monday to find out what they're going to do. The router arrived with hardware version A4 and firmware version 1.21. I did not change anything, just loaded my saved configuration and let it run. This is supposed to be a great router. I like the features but I am glad I have a Belkin router as a backup!
-
This doesn't exactly match the subject line, but I sure know what DIR-655 lockup is! I am on my third D-Link DIR-655 via the RMA process. This one arrived the middle of July, 2009. It worked fine until August 10th. It locked up and I noticed the Status LED was on solid - not blinking as it is supposed to. A power of and back on got it going. It locked up again this morning - Aug 15, 2009 with the same indications. I called D-Link to report the problem. They were going to send me router #4, but thought better of it. Now I have to call their super duper specialist on Monday to find out what they're going to do. The router arrived with hardware version A4 and firmware version 1.21. I did not change anything, just loaded my saved configuration and let it run. This is supposed to be a great router. I like the features but I am glad I have a Belkin router as a backup!
I know Dlink has it's issues with the last few firmware releases but to be on your 4th router, I'd start thinking about my config or environment that the router is in. I know you said you have your Belkin as a backup but there is a reason it's a backup, it's not as good or dosen't have the features that the Dir 655 has.
Would you entertain me with your config setup including your modem type and connection?
-
I wonder if some of these issues are from people flashing the firmware over wireless. ::)
-
I wonder if some of these issues are from people flashing the firmware over wireless. ::)
That could be, I also believe and many more expirenced people here and in the network field I'm sure could tell us that a lack of knowledge is the problem. The more complex you make a device (like the Dir 655) the more issues your going to have. Simple is good but when you have a complex config along with a complex router your going to have problems.
Thats why you see all the updates in firmware, Dlink is learning also.
-
While turning off DNS relay, also manually enter your DNS numbers individually into the router. My computers connection would show really odd DNS entries and also slow down. Assigning the DNS numbers in the router has fixed that problem.
-
While turning off DNS relay, also manually enter your DNS numbers individually into the router. My computers connection would show really odd DNS entries and also slow down. Assigning the DNS numbers in the router has fixed that problem.
Assigning them where in the router?
Setup-->Network Settings-->DHCP Server Settings ?
Setup-->Wan Manual setup-->Dynamic IP (DHCP) Internet Connection Type?
I have done both and still have DNS Relay enabled and have not had any lockups, life is good.
-
While turning off DNS relay, also manually enter your DNS numbers individually into the router. My computers connection would show really odd DNS entries and also slow down. Assigning the DNS numbers in the router has fixed that problem.
When I had DNS relay turned off (firmware 1.21) I did not do this but the router just used my ISP's defaults so I am not sure why you would need to. What you do need to do is reboot the computer or disable then re-enable the network connection or you will have no connection at all.
-
When I had DNS relay turned off (firmware 1.21) I did not do this but the router just used my ISP's defaults so I am not sure why you would need to. What you do need to do is reboot the computer or disable then re-enable the network connection or you will have no connection at all.
I believe a reboot flushes the DNS cache.
-
Assigning them where in the router?
Setup-->Network Settings-->DHCP Server Settings ?
Setup-->Wan Manual setup-->Dynamic IP (DHCP) Internet Connection Type?
I have done both and still have DNS Relay enabled and have not had any lockups, life is good.
This is where I meant:
Setup-->Internet-->Manual Internet Connection Setup-->Primary DNS Server and Ssecondary DNS Server
Put in your ISP's DNS server information there. If you don't know how to find your ISP's DNS information the easiest way is to disable DNS relay, restart your router, restart your computer (or ipconfig /renew), then on your computer go START->RUN->type in CMD ->then enter ipconfig /all.
There will be two listed DNS servers there under your wireless or LAN connection. (Whichever you are connected to.) Put the first one into the Primary box on the router, and put the second one in the secondary box on the router.
Just disabling DNS relay worked for me, but after a week the connection slowed down quite a bit. After looking around I found I had nearly 20 DNS numbers, nearly all of which were invalid. Doing this little step cleaned that all up and kept it from happening again.
-
This is where I meant:
Setup-->Internet-->Manual Internet Connection Setup-->Primary DNS Server and Ssecondary DNS Server
Put in your ISP's DNS server information there. If you don't know how to find your ISP's DNS information the easiest way is to disable DNS relay, restart your router, restart your computer (or ipconfig /renew), then on your computer go START->RUN->type in CMD ->then enter ipconfig /all.
There will be two listed DNS servers there under your wireless or LAN connection. (Whichever you are connected to.) Put the first one into the Primary box on the router, and put the second one in the secondary box on the router.
Just disabling DNS relay worked for me, but after a week the connection slowed down quite a bit. After looking around I found I had nearly 20 DNS numbers, nearly all of which were invalid. Doing this little step cleaned that all up and kept it from happening again.
I did the very same thing and have had no problems since. :)
If your running DHCP on the Dir 655 you can plug those same DNS numbers into Setup-->Network Settings-->DHCP Server Settings.
-
I know Dlink has it's issues with the last few firmware releases but to be on your 4th router, I'd start thinking about my config or environment that the router is in. I know you said you have your Belkin as a backup but there is a reason it's a backup, it's not as good or doesn't have the features that the Dir 655 has.
Would you entertain me with your config setup including your modem type and connection?
I have ADSL supplied by AT&T plugged into a Motorola 2210 modem. I also have a DNS-323 plugged into the DIR-655. All devices get their 110V from a APC RS-800 Backup Power Supply. All devices are on a shelf quite high in the room to provide good wireless connectivity - and it is good. I have a DSC-3420 wirelessly connected for surveillance. Yes the Belkin is my backup because my wife needs the internet connection for her job. I switch to the Belkin when the D-Link crashes. I have never upgraded the firmware over a wireless connection. In fact, I have never touched the firmware on this router at all. It is still at 1.21, the way it was shipped.
I use a connection type of PPPoE. UPnP enabled. WAN port speed set at 100Mbps. DHCP with a range of 9 to 41 (last octet) NAS and Camera are set outside this range.
-
I have ADSL supplied by AT&T plugged into a Motorola 2210 modem. I also have a DNS-323 plugged into the DIR-655. All devices get their 110V from a APC RS-800 Backup Power Supply. All devices are on a shelf quite high in the room to provide good wireless connectivity - and it is good. I have a DSC-3420 wirelessly connected for surveillance. Yes the Belkin is my backup because my wife needs the internet connection for her job. I switch to the Belkin when the D-Link crashes. I have never upgraded the firmware over a wireless connection. In fact, I have never touched the firmware on this router at all. It is still at 1.21, the way it was shipped.
I use a connection type of PPPoE. UPnP enabled. WAN port speed set at 100Mbps. DHCP with a range of 9 to 41 (last octet) NAS and Camera are set outside this range.
Dose AT&T assign an Static ip and DNS?
Entertain the thought of bypassing the APC to eliminating it as a possible problem.(just for now)
Are you running the Motorola 2210 in "bridge mode"?(disabling DHCP, my guess is prolly not)
Is the Dir 655 running DHCP because if you are and have both the router and modem trying to control the DHCP this will cause double nat and connection problems.
From the Dlink support pages.
DHCP Server Settings
DHCP stands for Dynamic Host Configuration Protocol. The DHCP section is where you configure the built-in DHCP Server to assign IP addresses to the computers and other devices on your local area network (LAN).
Enable DHCP Server
Once your D-Link router is properly configured and this option is enabled, the DHCP Server will manage the IP addresses and other network configuration information for computers and other devices connected to your Local Area Network. There is no need for you to do this yourself.
The computers (and other devices) connected to your LAN also need to have their TCP/IP configuration set to "DHCP" or "Obtain an IP address automatically".
When you set Enable DHCP Server, the following options are displayed.
DHCP IP Address Range
These two IP values (from and to) define a range of IP addresses that the DHCP Server uses when assigning addresses to computers and devices on your Local Area Network. Any addresses that are outside of this range are not managed by the DHCP Server; these could, therefore, be used for manually configured devices or devices that cannot use DHCP to obtain network address details automatically.
It is possible for a computer or device that is manually configured to have an address that does reside within this range. In this case the address should be reserved (see DHCP Reservation below), so that the DHCP Server knows that this specific address can only be used by a specific computer or device.
Your D-Link router, by default, has a static IP address of 192.168.0.1. This means that addresses 192.168.0.2 to 192.168.0.254 can be made available for allocation by the DHCP Server.
Example:
Your D-Link router uses 192.168.0.1 for the IP address. You've assigned a computer that you want to designate as a Web server with a static IP address of 192.168.0.3. You've assigned another computer that you want to designate as an FTP server with a static IP address of 192.168.0.4. Therefore the starting IP address for your DHCP IP address range needs to be 192.168.0.5 or greater.
Example:
Suppose you configure the DHCP Server to manage addresses From 192.168.0.100 To 192.168.0.199. This means that 192.168.0.3 to 192.168.0.99 and 192.168.0.200 to 192.168.0.254 are NOT managed by the DHCP Server. Computers or devices that use addresses from these ranges are to be manually configured. Suppose you have a web server computer that has a manually configured address of 192.168.0.100. Because this falls within the "managed range" be sure to create a reservation for this address and match it to the relevant computer (see Static DHCP Client below).
Being on your 4th router I'd have to guess something is wrong with your config, odds are. Bare with me nobody is perfect and a simple mistake on your end could be the problem. Who knows what the issue is a confict some place may be locking it up, so you have to go though your whole config.
If I were you I would do this go into the 655 setup.
Advance-->Network Filter--> turn on MAC filtering on via the drop-down menu and register all your MAC address and save it.
Setup-->Network Settings-->Add DHCP Reservation assign lan ip's to all your computers and devices and register them but leaving unchecked the static ip's. On that same screen on the section of DHCP Server Settings enter your DNS numbers primary and secondary.
Setup-->Internet--> Manual Internet Connection Options-->Dynamic IP (DHCP) Internet Connection Type enter your Primary and Scondary DNS numbers. Also check to make sure you have the right MAC address of your router there, it's printed on the underside of the router. Save and reboot.
-
I have been having the same problem since the upgrade, I was wondering, if we are having so many issues, cant we just downgrade to 1.21? I mean from what i understand u can download the 1.21 firmware from the dlink support page. THat should work right? unless there is some reason you cant downgrade.
-
Once you flash to the 1.3X firmware there is no going back to the 1.2X.
-
That just seems messed up, why would you build a flash utlity into the router for upgrades but make a firmeware upgrade that would make it work one way after that, this just seems a bit short sighted.
I also have noticed that the lockups only occur when I put heavy traffic thru the netwrok. it happened to me when i was streaming movies and using a bittorrent client that was set to only use limited bandwidth. I did the dns relay disable part, and manually set my dns servers, but I have yet to try it again since i made the change. I really hope that it works as a temp measure because I would hate to think that I've been trying to get this router all this time for nothing.
-
One thing that helped me with movie streaming was to manually set the WAN Speed in advanced networking to 100 Mbs. I also set my system to the same. Now I am able to stream Netflix fairly reliably where as before I was unable to at all. Before 1.32 I had no problems now I am having to reboot the router at least once a day to maintain decent speeds while browsing , gaming. I am still getting drop outs for several minutes after I finish a movie , and just recently my router log has been unable to load due to "insufficient memory". I hope this is fixed soon.
-
D-Link denied my fourth RMA. That's OK. the Belkin router is working just fine configured exactly like the D-Link one was. I reconfigured the DIR-655 as an access point. So far, it is working fine in that role. So much for after the sale product support!