Print

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

[RoomTenONine]

Loaded this up yesterday.  Phones seemed fine, unlike the 1.10 version. Although they had a disconnect here and there it was crazy like before. Unfortunately, I'm back on 1.09.  The Roku 4 was doing the same thing as 1.10. Constant disconnects.

[FurryNutz]

Who was the wireless configured when you had v1.11 loaded?
What modes where you using and are you using now?

How is the Roku 4 configured to connect to the router? 2.4Ghz or 5Ghz?
How far way is the Roku from the router?

Loaded this up yesterday.  Phones seemed fine, unlike the 1.10 version. Although they had a disconnect here and there it was crazy like before. Unfortunately, I'm back on 1.09.  The Roku 4 was doing the same thing as 1.10. Constant disconnects.

[RoomTenONine]

When I loaded 1.11, I used the same settings as I always have.  Very little beyond default.  Password protected wifi, smart connect, my u/d speeds entered into QoS and IPV6 set to Auto Config SLAAC/dhcpv6 and SLAAC+stateless dhcp for Comcast cable Blast Plus.  These settings have been flawless since I bought the router at release and through every firmware except 1.10 and 1.11.

The Roku 4 is basically one floor in the room below the router.  With all firmware the signal strength is stated as good to excellent in the basic menu.  Entering the secret wifi menu for Roku 4, signal strength, antenna 1 and 2 are all in the green.  Glitch/sec sits in the green to yellow boundary.  SNR is good.  Roku 4 has dual band AC capability.   Even with these solid connection stats, the 1.10 and 1.11 just constantly disconnect.  The router just breaks connection.  It was the same with our iPhone and Nexus 6 phones with 1.10.  This time we aren't using either of those phones and have 2 new Google Pixels, which are much more stable, but still got booted with 1.11.

I didn't go back and check my Chromecast this time.  Went right back to 1.09.

I've quoted at the very end here, my original post in the 1.10 thread that is now locked.

Who was the wireless configured when you had v1.11 loaded?
What modes where you using and are you using now?

How is the Roku 4 configured to connect to the router? 2.4Ghz or 5Ghz?
How far way is the Roku from the router?

Loaded this up yesterday.  Phones seemed fine, unlike the 1.10 version. Although they had a disconnect here and there it was crazy like before. Unfortunately, I'm back on 1.09.  The Roku 4 was doing the same thing as 1.10. Constant disconnects.

Installed the 1.10 today using the standard procedure.  Major issues with wifi disconnects.  My Roku 4, which has been 100% rock solid with this router on all other firmware, can't hold a connection at all.  My Chromecast Audio also bugged out on the hi-fi.  This was all the case with SC enabled (and which was never an issue before).

Reverting back to previous 1.09 solved it all.  Like others said, it is a shame since the new features looked and sounded great.

[FurryNutz]

Is the Roku up to date on its FW?

Did you try the router with SC disabled?

Seems that the Roku is the only device that seems to have problems and may not be totally a FW issue on the 890L..There maybe some drivers with in the FW on the 890L that maybe not working well with the FW thats on the Roku...

[RoomTenONine]

Is the Roku up to date on its FW?

Did you try the router with SC disabled?

Seems that the Roku is the only device that seems to have problems and may not be totally a FW issue on the 890L..There maybe some drivers with in the FW on the 890L that maybe not working well with the FW thats on the Roku...

It's all up to date.  I didn't try without SC because I need to use SC.  It's a major reason I purchased the router and I expect that feature to work.  The Roku works flawlessly on all other versions with this router and other routers I own.  With the known issues with the post-1.09 firmware here I'm pointing the finger at the 890 firmware.  The bugs were worse with 1.10 for sure, but that doesn't mean it is all squashed in 1.11. 

That said, I'll give 1.11 another run over the holiday break and see what I come up with.

[FurryNutz]

Something may have changed in recent FW version that may be incompatible with the Roku and causing problems. This maybe something that you should get on the phone with D-Link about and have them review this. This only seems to be effecting the Roku and the 890L.

Let us know how it goes over the holidays.

[tmlfan007]

Hi All,

The disconnect issues affect more than just Roku boxes. Like the previous poster said, the disconnects are far less frequent than on 1.10, and the reconnect happens quicker, however they are still happening. I am having the issue with my iPhones as well as my laptops. I know the point of 1.11 was a security release, but they have clearly tried to tweak other aspects to fix the problems in 1.10, and it is better - however still not completely corrected.

I have reverted back to 1.09 as well until this is fixed. You would think a problem as serious as what occurred in 1.10 would have been corrected by now.

Thanks

[FurryNutz]

What region are you located?

I've been running v1.11 on my 890L since it came out with SC enabled and all of my iPhones, an iPad, MacBook Pro 2008 and iMac are all working well. I haven't noticed any issues with it. Both of my NEST controllers are connected to it and no disconnections on them as with my DCS-933L. I will be testing my XB1 on wireless and setting up my DISH Joeys for wireless and testing as well...I also have a DIR-857 and DIR-615 working as 2ndary APs in other locations in the house so there is some interferences for my configuration.

We'd need more information on your issues your seeing. Thus you haven't specified what exactly your devices are seeing when they disconnect, what they are doing. You haven't given any details...
How the router is configured?
How many devices do you have connected at once?
What OS versions are loaded on each device?
Have you tried SC enabled and disabled?
When you loaded v1.11 did you factory reset and set up from scratch or just load a saved configuration file. I factory reset and set up from scratch each time I update FW.

So at this time we can only speculate that this maybe a mis-configuration or interferences maybe of yor router rather than a FW issue.

[FurryNutz]

Ok, just added 2 5Ghz bridges to the 890L. A DIR-868L and DIR-880L in bridge mode. A DISH Joey is connected to each. Currently up and running and video is streaming. SC enabled.

[b17gsr]

Furry, how far are your devices from the router? As soon as I have a floor or more than 20' between me and the router, the wifi drops for 10 devices.  Even the room really guy above the router!

[FurryNutz]

My farthest devices is a NEST and DIR-880L(wireless bridge mode) in the master bedroom, one floor down and about 25-30ft away thru one floor and opposite from where 890L is and SC enabled.

When I'm in the room with my iPhone 6sP and Mac Book Pro 2008, I'm connected well and don't see any disconnections...

Furry, how far are your devices from the router? As soon as I have a floor or more than 20' between me and the router, the wifi drops for 10 devices.  Even the room really guy above the router!

[b17gsr]

I reverted back to V1.09 and the family is happy.

[FurryNutz]

 

[stomasak]

I also had to roll back to the 1.09 firmware version.  My Roku TV works again after having the same disconnect problem.  Another issue is that the router admin page does not work in the latest Chrome or Edge browser after the 1.10 or 1.11 update.  The QA department needs to do a better job of finding these escape defects before a release.  This is really is unacceptable for a company of this stature to release two flawed updates without proper testing.

[FurryNutz]

Thanks for your posting your concerns. Hope next update will fix issues.

v1.11 works for me.

I also had to roll back to the 1.09 firmware version.  My Roku TV works again after having the same disconnect problem.  Another issue is that the router admin page does not work in the latest Chrome or Edge browser after the 1.10 or 1.11 update.  The QA department needs to do a better job of finding these escape defects before a release.  This is really is unacceptable for a company of this stature to release two flawed updates without proper testing.