"Official" Onkyo TX-NR809 Thread - Page 84

So I just unplugged all my HDMIs, plugged them back in, and now it's working again...

Sounds good. Hopefully it was just a temporary issue. I would check to make sure your firmware is up to date, as well. If it happens again, I would start to be concerned about having either a faulty receiver or another one of your devices being faulty.

I am still having no luck with this. Tried different routers. The only thing that worked for a few minutes was when I disconnected everything from my router and rebooted my cable modem and router and plugged the wire into the router after booting up the receiver. It worked for about 3 minutes before everything froze up again.

As far as the USB question, I am hardwiring it. I was just saying that the USB function on the receiver does not work either. When I push USB on the remote it goes to Net after about 3 seconds and freezes. That's what made it difficult to do firmware updates.
That was before I realized that having an ethernet cable in the back freezes up my units USB functionality and NET functionality.
I have not heard from Onkyo on this. Have you had any luck? I am downloading the new firmware right now via USB (after several attempts of getting it to recognize the USB drive). It's updating now. Who knows? Maybe this will do the trick but somehow I doubt it. I think its something really simple with the router settings. I just wish I knew. It did work for about 3 minutes I got Pandora and was able to see my unit on the Ipad software before I got the frozen blue screen error.

UPDATE:
New Firmware did not make a difference but I can get Pandora to work if I do the following in order:
Disconnect Power from Router. Disconnect Power from 809. Turn on 809 and router without ethernet attached. Wait for both to initialize. Connect Ethernet. Now Pandora will work. But if I change to DLNA it will freeze.

I have tried reserving an IP Address/MAC etc on my router and I have tried both DHCP and static. I can't figure this out but I am pretty sure that Onkyo has a problem with the router. I have the firmware updated on the router. It is a Gigabit router. Regardless of whether its something here there is no way the thing should keep freezing.

If you post a step by step of what exactly you are doing to replicate the issue (and exactly what the issue is), I'd try to replicate it on my setup to see if the issue occurs when following that specific series of steps.

I don't have any internet radio subscriptions, so can't test that - but otherwise I'd be willing to see if I can recreate the issue or if you've just been unlucky with the 2 you got.

After using three different routers from two different brands, I was finally able to get a 4th router to try from a third brand (Cisco).
Eureka! I got it to work on the the Cisco and then I started comparing the Cisco (older router) to the newer (2) Dlinks and Linksys. It was a DNS issue with the router.

I was not aware of the new feature called "Advanced DNS" that is available on all of the new Dlink Gigabit routers... well maybe not all but at least the two I had. Furthermore, if you do a quick setup it is automatically enabled and a novice like me won't even notice it's there. I'm not much of a network guy but I saw that the DNS that was on the router status page were bogus when compared to my actual DNS from my ISP. I think its a security feature. Even when I set it up on the Onkyo manually, I would input the DNS server that I saw on the router. And when I allowed it to use DHCP it would just hang up for some reason. Why? I don't know, a computer network guy can probably shed light on that.

Anyway, if you are having trouble with the NET feature, this might work for you.
I went into some advanced settings on my Dlink router. Disabled "Advanced DNS" and its a Christmas miracle! I rebooted everything. It seems to work with Pandora, DLNA, the Ipad App, etc. I don't know what the feature is called on the Linksys but I am suspecting that they have the same thing perhaps under a different name. I'm not 100% sure as I don't have that router handy anymore.

So, if you have a newer router and are having loads of trouble, this may do it for you. I hope it does because I've been frustrated with this for a month now and I really hope I can save someone that frustration. Its my fault that I happen to just try routers with this feature on it but that's all I had available.

Glad I don't have to send it back. I've really started tweaking the sound and really like it now. I told the Onkyo tech support that I'm sure its a router issue and they told me that it wasn't because it should never freeze. I had a feeling it would be something small but annoying like this.

Merry Christmas everybody. I would play around with this thing more just to make sure it doesn't knock out on me later but I'm sleepy and have been working on this for a few hours. I'm just glad it works! Thanks for all of you guys to help me troubleshoot this. Especially you, Bengalih.

Hi,

I am having limited success with accessing my iTunes library through the NET feature on my 809, and I was wondering if my experience was better than, worse than, or on par with what should be expected. Here are some specifics.

I have a Mac and I am running a DLNA server. The 809 sees the server and I can navigate to the iTunes directory in my Music directory. The good news is that I can see all my individual songs (and play them). The bad news is that I do not know how to easily navigate through the thousands of songs.

On my Mac, the layout does not match what I see from the 809, which strikes me as odd. My iTunes directory contains several subdirectories rather than thousands of individual songs. Specifically, it contains a subdirectory called iTunes Music, which in turn contains a separate subdirectory for each ARTIST, each of which contains a separate subdirectory for each ALBUM, each of which contains individual SONGS from that album.

I was hoping to see this same layout through my 809, so that I could navigate to a given song (or album) more easily. What are others doing to play iTunes songs (or albums) through the 809 via a DLNA server and the NET option? Is there a simple way to "fix" this problem?

Thanks,

Gregg

Which DLNA server are your running? Most I use let you navigate by Tags like Artist etc, or Folders. Maybe your DLNA server can build it's own index instead of using iTunes Library, which maybe presenting what you are seeing.

I am new to this, and I would be willing to use whatever DLNA server works best (and hopefully is free or inexpensive). For this test, I used iSedora, which can be used for free (and with full features) for 60 minutes at a time (otherwise I think it's $25 or $30). I also tried (briefly) TVMOBiLi, but I could not get the 809 to see it, though that may be due to an error on my part.

Is there a DLNA server that you recommend for the Mac? Thanks,

Gregg

I don't use 809 for Net or DLNA. Nor have I got much Mac experience.

http://en.wikipedia.org/wiki/List_of...ients#Software

is a useful resource in this area.

If you really struggle, you could look at Logitech Media Server from mysqueezebox.com

I know that has a Mac version which the 809 can see, but this server is designed and great at serving to it's own squeezeboxes. Not sure it is the best solution.

How big is the music library you are hoping to serve? Most people would look at running a NAS for this job, which would have a built in DLNA server, and would save you having the Mac switched on.

Thanks for the input. I have several thousand songs, probably less than 5000, so not a very big collection compared to most people. Maybe I will look into the NAS route, but I just figured that the route I tried would be simpler, since my computer is always on.

To be honest, I don't know how often I would play music through NET. I was just curious about whether it would work with iTunes and the DLNA server I already had on the computer. Partly I wrote to the list because I thought it was odd (and oddly interesting) that the directory layout showed by the 809 is different than what is on the computer.

Thanks,

Gregg

I got my new 809 on Friday. Thanks to some helpful advice from some off the forum members things are going pretty well. The manual has been my best friend the past couple of days. I am still having some problems with audessey. Sometimes it is grayed out and sometimes not. I can't find anything pertinent in the manual so I thought I would ask you guys. We watched a movie on Netflix today after running the auto quick set up instead of the 8 position full set up. The dialogue was very hard to hear no matter which listening mode I tried. Any ideas on that one ?

Joe

Hi!

Does Audyssey support the subwoofer? In that case, can you configure Audyssey to only adjust the other channels (not the subwoofer)?

Well Yes and Yes

If you dont want audyssey to manage the sub, just unplug while configuring.

Not sure why you DON'T though, you can always turn the sub up later if you want more.

Is anyone using oy remote?? I downloaded it but when i try to runt it, it tells me it is not a valid win32 application. I'm running windows 7/64. Is this the reason.

Thank you!

I have a separate calibrator for the sub (anti-mode).

Not sure if your other calibrator for the sub is better/worse than what Audyssey can deliver, but you will need to deal with the crossover between the two systems.

Option 1
Leave your existing system doing it's job, and then run Audyssey as normal, including sub

Option 2
Disable your existing sub calibration feature, and let Audyssey do it's thing.

Anything else is likely to cause cross over problems and not be what either.system was trying to do.

Ok, well like others have posted, not sure it will do any better. Try it both ways, you have nothing to loose.

I run Win7 /64 too and have no problems. What version of oyremote exactly are you running?

Also, you might want to try XP compatibility mode when running the application. Again, though, I don't need to run it in compatibility mode for it to work for me.

Ghostnotes,

I thought of one more thing. It is possible that your downloaded file is corrupted. Try downloading it again, making sure that you actually save the file to your computer. Here is the direct link to the newest version: http://www.krautsourced.com/files/so...mote.0.17a.exe

You also need to have .NET 3.5 installed for the application to run. You can get this download from Microsoft here: http://download.microsoft.com/downlo...dotnetfx35.exe

Any gamers in here have a preferred listening mode for 7.1 and call of duty. I know onkyo has the game modes, just curious if there is a better mode for typical 7.1 and an Xbox 360.

Thanks
Jake

I guess most like direct, but I like the THX mode for games, but that is for my PS3 since I don't have a 360.

Thanks! I'll try that out!

Well glad that things worked out. I researched a couple minutes on the dlink "Advanced DNS". Honestly I'm not 100% sure why that would cause the issue (and probably can't be unless I got a packet dump of the network to analyze), but here are the basics:

Every computer on a TCP/IP network (which is basically every networked computer) has an IP address. However, since IP addresses are difficult to remember, we assign them friendly hostnames. For instance 72.9.159.100 is better known as www.avsforum.com. When we want to visit that address we type "www.avsforum.com" in our browser - but the computer needs to know the actual IP address of the server in order to connect us.

The process that is used in most practical implementation to find this is DNS - Domain Name System/Domain Name Server. In essence (dumbed down for explanation here) DNS provides a giant yellow pages that allows us to ask for the number based on the name. The service itself is actually distributed, but most home users have their routers configured to provide a DNS server at their ISP as their first query. While anyone can host a DNS server, all ISPs maintain their own for customers and because of network latency (among other things) it is often best to configure your router with your ISP's DNS address.

In many cases, you don't need to configure anything, because your router (if it is a different box than your ISP gave you) will automatically detect the right information (through the DHCP/Automatic addressing process). Additionally, most routers will then do one of two things for all the clients on the home network:

1) Give the same IP address they got for their DNS to the clients: So, for instance if my router got 34.121.299.110 for its DNS server it would hand that off to clients as well.

2) Give clients its own IP address for their DNS: So, for instance if the router's IP is 192.168.1.1 that will be what it tells clients to use for DNS.

In the former, this means a client will go and contact their ISP DNS directly for name resolution. In the latter it means that a client will talk to their own router and that router will then query/proxy the ISP for them and introduce a level of caching. I suppose you can debate pros/cons of each - but I would prefer option #1.

DNS is incredibly important to the way the internet operates. If we can't connect to a DNS server and we don't know the exact IP of a server we are trying to connect to - we will never be able to connect to it. Some devices may be hardcoded to look for a particular name (like www.widgets.com) instead of the IP so you might not even have a choice to use the IP directly.

Because of the way DNS works, there are ways to fool around with it to get some additional benefits. Let's say that your ISP doesn't want you visiting the site illegalsoftwaredownloads.com. They can remove that entry from their DNS server, or add a fake entry that actually directs you elsewhere. Or, lets say that they discover that a bunch of websites are malicious to you - they might remove/change all those entries in their servers as well.

ISPs don't usually do this (at least in USA) - it may be considered a violation of "free speech" or some other law. But, there are companies out there that offer DNS servers for use that DO block these harmful sites. Arguably the most well known is OpenDns.org. Now that I have explained this you can go look at http://www.opendns.com/technology/ to help solidify what they do.

The "Advanced DNS" found in your D-Link router apparently tells the router to use the OpenDNS servers for your network. To be honest - I like OpenDNS - as long as you understand how it works. Sometimes sites may be classified certain ways and OpenDNS may prevent you from getting to them. But, like all security related things, it is always a compromise between ease of use and security.

All that being said - I don't really know why using the OpenDNS server instead of your ISP's servers should have caused the issues you describe.

One possibility (though I find this unlikely) is that at some point during the Onkyo network initialization it is hardcoded to attempt contact with a site (e.g. connectme.onkyo.com). If for some reason this was blocked by OpenDNS, a webpage would be returned, but not what the Onkyo expects. Perhaps if the engineers were silly enough to have enabled something like this in the first place, they were also silly enough not to ensure that some garbage data returned didn't interfere with the initialization process.

A better possibility may be that the AdvancedDNS feature does some other unadvertised function on the network. In any event, I find it hard to believe that whatever it is doing to mess with DNS would lock up the Onkyo in the way that you describe. Although AdvancedDNS may have issues - those issues shouldn't interfere. I would say that the Onkyo is more to blame since any garbage or lack of information provided over the network shouldn't cause a lock up.

Another example of this may be that AdvancedDNS also changes how local names on your network are resolved and the lock-ups were the result of trying to find local network names by querying the OpenDNS servers. If something like this was happening I would expect some delays perhaps and then timeouts, but not full system lockups.

If I have the time I may try to do a packet capture of the Onkyo network init process and see if I can detect anything strange. Again, since I don't know the exact steps you were performing, I won't be able to truly replicate your experience (e.g. were you trying to access a network resource, or did you already configure any resources like a home server, etc). It's always best to use IP addresses when configuring connectivity to eliminate DNS as a possible issue. Of course, when it comes to an appliance we don't always know what it is doing under the hood.

Looking over the Advanced DNS information on the Dlink site and it is supposed to provide help when incorrect website addresses are entered, in other words if you make a typo, instead of just giving you a "page not found" it supposedly gives you some suggestions on what may have been entered incorrectly.

However, for it to be causing problems with the receiver, where the addresses are almost certainly in the firmware, that service may be doing something else.

It may also be the case that there is an address in the firmware which is generating a redirect page and the Advanced DNS is trying to offer a "suggestion" rather than simply letting the redirect do it's job :-) This is just speculation of course, the bottom line is that turning it off fixes things for you :-)

I am running 2 Sony TVs off of my 809. One is in a room where I have 7.1 set up. The other is in our bedroom and runs off the tv's speakers. With my old 805, I used a HDMI splitter to feed each TV. I had hoped to use the dual HDMI out to do the same.

I find I can't get sound over HDMI and out of the reciever's speaker outs at the same time....................Am I missing something?
Thanks,
Mike

I re downloaded it and ran windows update but for some reason i do not see .NET3.5 installed in my programs and features.....strange. I tried to run it in compatability mode anyway but it is still giving me the same error. Another strange thing is that it is not trying to install it on my C: drive. Instead it is trying to install it on one of it's partitions.... The bootstrap version that is.

The other version does not give me any indication that it is installing. either the one you pointed to or the one on Microsoft's webpage.

Yeah that is some really odd behavior. A virus or malware on your PC, perhaps? Do you have admin rights for the user account you are logged into with Win7?

I disabled auto protect and the firewall on Norton in the beginning of this cause it did not recognize it so it would flag it,cashe is cleaned and i also ran a registry cleaner as well. What confuses me is why it's trying to run the install on my I: partition.

On another note, I just put the 809 through it's paces (music).I only had the nerve to run it to about 60% in fear of blowing my dad's polk surround speakers. At that level it seems that either the amp is running out of headroom(which i doubt) or my acoustic research AR-9's are, i suspect it's the AR-9's(high res series).The mids still sound good but the lows and highs get confused or muddled.I'm still trying to set the eq levels and placement(which is limited) so that may be the case as well. The sub is a velodyne and it seems to be able to keep up.

Are you on Windows 7? .Net Framework 3.5 is part of Windows 7 install already - so it won't show up under "Programs and Features." You need to click on "Turn Windows features on or off" and ensure the framework is checked. It should be installed by default.

If you need to verify that framework is properly installed you can look here:
http://blogs.msdn.com/b/astebner/arc...3/8999004.aspx

Strange....

I see .net version 2.0.5027 for 64 and 32 bit but no .Net3.5