NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000 DLNA Enable Option
Hi all,
Perhaps you someone could point me at location of Enable/Disable DLNA server option in latest "V1.0.9.88" revision of firmware of R7000 (AC1900) Nighthals Router. I recall that some of the ...
mkonstantin, I didn't miss the point. I don't have an active R7000 so I can't tell if it is there or not?
It wouldn't surprise me if NG messed it up. Like the screen shot I posted the removed items were on that page. Some probably untrained programmer removed the function and the web page to enable it. Probably was CLUELESS as to what DLNA was so removed the whole page. Code is probably still in the f/w, but no way to enable it.
All I can say complaining here and HOPING NG people report this back and get it fixed is a crap shoot.
DarrenMcan you get this fixed as soon as possible?
Your fix for now, go back to V1.0.9.42 I'd think, .60, .64, and .88 all have serious problems for many user's in varying ways.
I wasn't trying to get to the 'nuts and bolts'. Just high level, 50,000 Ft type of thing.
Usually what happens when one applies a f/w over another, the settings are retained from the old f/w. That is why you don't need to re-enter them. The Flash address is known, but also why sometimes when installing new f/w you need to RESET and reenter setting as the new f/w has moved them to a different address.
That being the case, the GUI information wouldn't be needed as the 'enable bit' was set from the prior version. Just like you did with the .64 I assume. Shouldn't matter if one was using .42 either. The bit was set, and DLNA should run. It IS possible the DLNA database was deleted with the .88, but that wasn't the case.
perhaps i explained it wrong in the first place - everything was working fine after 42->88
Howefer it's knowking issue (a completlly separate one) with the indexer proce that sometimes it corrupts ReadyShare databse perhaps because some unsupport mkv tags, unicode chars in file name/tags and etc. So the one solid solution was - drop that database all together via SMB and then disable/-re-enable media server option (as you're saying RESET that bit in configuration). so when i dopped it and went back to GUI i sa the tab was missing. that's all - so the brian is still in there but had no "mougth" to communicate :-)
Anyway. I think we went over pretty much everyt possible aspect of this issue so i'd say let's see what NG guys do now. Hope they can address it soon enough.
mkonstantin, in the early days, I got my R7000 soon after release, I had tons of problems with the DLNA server. Using it to store ripped DVD's and show on a Smart TV. Some couldn't be played, has DUP's listed, some were missing. It took months of me basically educating them on the FILES.DB structure. I had to simplify it completely using only 2 MOV files I recall. Then dumping the SQLLITE DB and showing them what was going wrong. Got no where fast, until the connected to my PC and I started moving other files with a mix of MP4, WMV, and MOV. Then dumping the database for them to see. Finally they understood. Could a few drops to me but they finally got it working. However, every once in awhile I must rebuild the database by deleting it or unplugging and plugging in the USB drive.
I do have a new USB problem too on the latest R8000 f/w that didn't exist before or on my R7000. Occasionally when I power on the router or reboot it the USB drive is NOT recognized and connected. Just need to pull the cable or power on the USB and connect it again, then it gets picked up. Probably a startup timing issue.
I really hope that NG management gets this all under control. Makes sure Regression testing is done and has made sure the future releases are great. Yes, a router isn't a single function device like a calculator, but it isn't as complex as an OS to test either. Time will tell.
After getting DLNA working after dropping back to .64, I then updated to .88 based on the recommendation in this thread that the database will still be there and DLNA is in the background. But, no DLNA so it’s back to .64 until NG fixes this issue, or a security update is critical, or I’ll go another route. I know NG needs to update, etc but sometimes the maxim of ‘if it ain’t broke, don’t fix it’ springs to mind.