TX-NR709 network initializing issue

I have probs myself with nr 709 on behalf of network. internet radio works fine, but I'm perfectly happy with my 2 FM radiostations ! problem is DLNA. when I stream music, I can't touch the volume (on device, on RC nor on android app), because then it crashes. in zone 2 I can control volume.
I don't know the right names, but this is all when I "pull" music out of NAS or PC, using the receiver with OSD. When I try to "push" music from NAS (by PC, android or Ipad app), it doesn't work at all. My Samsung TV works perfectly in any kind of those situations, so its possible. but not with Onkyo. not with current firmware.

Hi delbarm,

The reason it works with your TV is because it can take pretty much anything that's thrown at it. When you put a receiver in the mix it has to go through handshakes checks and it has to be allowed to get to the net via your router. Also everything in the mix is required by DLNA to be certified or it will not work. So what I'd like for you to try is the following:

1. Make sure that all components are DLNA certified
2. Make you have your router set to allow this function to operate. You may want to contact the router manufacturer and have them walk you through the setup.
3. Make sure your PC is DLNA certified.

thank you for your quick reply.

but :
1. Make sure that all components are DLNA certified CHECK like I said it works on my Samsung TV's software (pulling and pushing, like I call it), not to mention : it even works with a small portable internet radio

2. Make you have your router set to allow this function to operate. You may want to contact the router manufacturer and have them walk you through the setup. CHECK again. I forgot : playing locally stored music with the Onkyo app on my android phone (everything Onkyo) it works, so router is obviously OK. but receiver crashes as soon as I touch the volume on device or any button on app : crash. don't blame it on a perfectly good working device.

3. Make sure your PC is DLNA certified. don't bother. see above 1.

check how smooth Synology soft (+apps) and Samsung (+apps) work. Others face same protocols, so it's possible. handshaking, etc. is for them no problem ? hope you'll fix this soon.
networking is as I see it the next big thing for home audio. don't miss this train.

Mick

Hi Mick,

If this is the case then the unit will need to go to a service center for further evaluation. They can be found on the main page under support on our website. Thank you for choosing Onkyo.

I had similar problems with my receiver when trying to use the internet for music. Worked for a couple of months and then this same problem. But, no help from Linksys re the router and little help from ONKYO. However, for whatever reason, I unplugged the receiver and did not plug it back on until about an hour later. Then turned on the receiver but selected TUNER, then when that played I then went to the NET/USB selection and everything was there to use and listen to. I've used since but do not know whether unplugging helped or my habit now of selecting TUNER first and then going to the NET/USB button but it does work so I'll stick with that. Just do not want to find out if I can skip the routine, yet.

The NET issue happened to me again, so I spent time going trying to find any new information and found on avsforum people were experiencing the same issue all of us are.

Seems the Onkyo has a hard time with some DNS issue which causes it to hang on the NET input. After disabling the Advanced DNS option on my router (which causes it to reset and get a new IP), I also unplugged the network cable from the back of the Onkyo and unplugged the power cord from the Onkyo to fully shut it off. I let it sit for a few minutes, then hooked the network cable back up and plugged the power cord back in. Left it on the BD/DVD input for a minute to give the Onkyo enough time to get an IP address from the router and now I was able to connect to Pandora again.

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.

http://www.avsforum.com/avs-vb/showthread.php?p=21395270#post21395270

or google "avsforum onkyo advanced dns" and it'll be the first result returned.

Hi itsmefd,

Thank you for the research and hopefully this will resolve some of the problems people were having.

My four month old 509 has to be unplugged/plugged at least once per day to reset it. After a random time of use, it simply locks up and simply says: Now Initializing...

I have upgraded to the latest Firmware, changed my switch, placed receiver in DMZ, changed my patch cords, tried connected with the wireless adapter.

NOTHING FIXES THE ISSUE.

It seems to be a firmware issue with the receiver. Any plans to address this?

Hi isturiz,

At this point I would advise a service center to evaluate it. Authorized service centers can be found on our main page under support.

isturiz wrote:My four month old 509 has to be unplugged/plugged at least once per day to reset it. After a random time of use, it simply locks up and simply says: Now Initializing...

I have upgraded to the latest Firmware, changed my switch, placed receiver in DMZ, changed my patch cords, tried connected with the wireless adapter.

NOTHING FIXES THE ISSUE.

It seems to be a firmware issue with the receiver. Any plans to address this?

It is an issue with the networking portion of the firmware which Onkyo does not acknowledge as an issue. They'll tell you first to update the firmware, then to reset the receiver to the factory default settings and then if that doesn't work then to send it to the service center which cannot reproduce the issue that many of us have reported. Or they will say it's your router, cables, ISP, etc that is the cause. My receiver gets an IP address without any issues and I can get to the receiver's web page just fine. It just can't connect to any streaming music via Internet or local network. Personally, I have just given up using any of the network functions on the receiver. I check from time to time to see if there are any updates to this, but since these are 2011 models, I doubt there will be any new firmware updates to fix this issue.

isturiz wrote:My four month old 509 has to be unplugged/plugged at least once per day to reset it. After a random time of use, it simply locks up and simply says: Now Initializing...

I have upgraded to the latest Firmware, changed my switch, placed receiver in DMZ, changed my patch cords, tried connected with the wireless adapter.

NOTHING FIXES THE ISSUE.

It seems to be a firmware issue with the receiver. Any plans to address this?

isturiz,

I had similar issues with my 509, among many other things. I had to send mine in to a service center because it was almost not usable. When I got it back 2 weeks later the work order said it had to repair multiple cold and open solders on the USB, HDMI and Sub Preout boards. Needless to say this was Onkyo's poor quality control and lazy construction and the service center(not affiliated but works with Onkyo) fixed all my issues and now it works better than it did 3 MONTHS NEW. I'm guessing this is probably your issue as well. However, get Onkyo to pay for shipping because this is their fault.

I have had all of these same network issues since day one with my 808. It randomly just drops itself off the network and to get it to connect again takes a miracle. Yesterday I thought I'd attempt to install the firmware update that was released in March. As soon as I hit the button, it gives me "version error" messages and locks up. After cycling the power off and back on, it had dropped off the network. An hour later, after unplugs, resets, modem/router resets, ethernet cable unplugs and more power cycles I got it to once again connect to the network and was able to use Pandora. Once attempting to try and do the firmware update again, the same thing happens. When trying just to get the net radio functions to work again, I get other errors and it won't connect.
I've contacted Onkyo about my machine before through their customer service email and last week spoke with their support people. All they suggest is to send it to United Radio Service in Syracuse, NY. I worked for United Radio and want nothing to do with bringing my receiver there, not to mention it will be a three week turnaround at best. I'm so sick of the network issues with this machine. No other piece of network connected gear gives me hassle like this. Even trying to use the iPhone app, the machine will just randomly drop itself off the network and I won't be able to use the app. The unit is still under warranty but I just don't want to deal with the wasted time and money of a "return for service". I want it replaced.

Hi dtsdig,

If you've done all that and you say you used to work for United Radio then you understand our warranty policy. If our customer support reps determined your unit needs service and it has not been serviced already then you have to take or send it to a service center whether that be United or some other authorized service center. If you'd like to discuss this more in depth you may contact our parts and service department at 201-785-2600 option #4

OnkyoUSA wrote:Hi dtsdig,

If you've done all that and you say you used to work for United Radio then you understand our warranty policy. If our customer support reps determined your unit needs service and it has not been serviced already then you have to take or send it to a service center whether that be United or some other authorized service center. If you'd like to discuss this more in depth you may contact our parts and service department at 201-785-2600 option #4

dtsdig,

I would suggest the service center I used to fix your issue........ http://www.ablserv.com

The turn around time from shipment to receiving it back was just under 2 weeks and they were in contact with me the whole time. Shipped it back extremely well-packaged and they were very competent(describing what solders were fixed on what boards). I say if you've lost all hope and have to have warranty work done, ship it to these guys.

All,

It seems we are all having the same problems with NRx09 network functions on Onkyo equipment.

My story is nothing new. I can ping the two units I own, I can browse to their web pages but accessing the NET functions gives me either a blue screen or the dreaded "Initializing...."

Shortly after the upgrade I was able to use the DLNA functionality on both AVR's using the remote2 app on my ipad. Happy days. Two weeks later the app couldn't detect the AVR's.

As an experienced and senior software engineer, network engineer and Telco general manager I know a firmware problem when I see one.

I am fortunate enough to have network traces from the boxes both BEFORE the problems started and AFTER:

Simply put, both AVR's where sending UDP Muliticast packets to the correct mulitcast address for upnp:

Looks like this:

10:12:35.219382 IP pch.mypond.net.32905 > 239.255.255.250.1900: UDP, length 371

This is a upnp advertisement packet which tells a DLNA control point (remote2 app for example) how to talk to the Onkyo. This is correct behaviour.

Now, I am seeing this:

20:15:37.126654 IP dh-129.mypond.net.40418 > 239.255.250.250.9131: UDP, length 109

This is very odd. Both my 509 and 609 send out these packets. They are not recognized by anything on my network (I would not expect it too). These packets are advertising an H232 function (nothing to do with DLNA).

This is a bug Onkyo. Lets get it fixed.

(Yes I have tried the hard reset, firmware upgrade, etc, etc).

Regards,
Barrie

More help for Onkyo Support:

21:18:18.000192 IP iggle.mypond.net.bootps > dh-185.mypond.net.bootpc: BOOTP/DHCP, Reply, length 300
21:18:18.010755 IP iggle.mypond.net.bootps > dh-185.mypond.net.bootpc: BOOTP/DHCP, Reply, length 300

21:18:18.886079 ARP, Request who-has dh-185.mypond.net tell iggle.mypond.net, length 28
21:18:18.886667 ARP, Reply dh-185.mypond.net is-at 00:09:b0:c6:38:ec (oui Unknown), length 46
21:18:18.886680 IP iggle.mypond.net > dh-185.mypond.net: ICMP echo request, id 8334, seq 0, length 28
21:18:18.887198 IP dh-185.mypond.net > iggle.mypond.net: ICMP echo reply, id 8334, seq 0, length 28
21:18:23.877918 ARP, Request who-has iggle.mypond.net tell dh-185.mypond.net, length 46
21:18:23.877931 ARP, Reply iggle.mypond.net is-at 00:1c:c0:f3:63:2b (oui Unknown), length 28
21:18:35.642965 IP dh-185.mypond.net.48639 > 239.255.255.250.1900: UDP, length 101
21:18:35.768583 IP dh-185.mypond.net.1900 > 239.255.255.250.1900: UDP, length 162
21:18:35.775957 IP dh-185.mypond.net.48639 > 239.255.255.250.1900: UDP, length 101
21:18:35.790281 IP dh-185.mypond.net.1900 > 239.255.255.250.1900: UDP, length 209
21:18:35.811919 IP dh-185.mypond.net.1900 > 239.255.255.250.1900: UDP, length 153
21:18:35.833422 IP dh-185.mypond.net.1900 > 239.255.255.250.1900: UDP, length 217
21:18:35.854923 IP dh-185.mypond.net.1900 > 239.255.255.250.1900: UDP, length 219
21:18:35.876469 IP dh-185.mypond.net.1900 > 239.255.255.250.1900: UDP, length 207
21:18:35.877984 IP dh-185.mypond.net.48639 > 239.255.255.250.1900: UDP, length 101
21:18:35.898093 IP dh-185.mypond.net.1900 > 239.255.255.250.1900: UDP, length 303
21:18:35.902559 ARP, Request who-has dh-185.mypond.net tell dh-169.mypond.net, length 46
21:18:35.912605 ARP, Request who-has dh-185.mypond.net tell dh-186.mypond.net, length 46
21:18:35.915624 ARP, Request who-has dh-185.mypond.net tell dh-166.mypond.net, length 46
21:18:35.924021 IP dh-185.mypond.net.1900 > 239.255.255.250.1900: UDP, length 350
21:18:35.945523 IP dh-185.mypond.net.1900 > 239.255.255.250.1900: UDP, length 294
21:18:35.965102 ARP, Request who-has dh-185.mypond.net tell dh-181.mypond.net, length 46
21:18:35.968214 IP dh-185.mypond.net.1900 > 239.255.255.250.1900: UDP, length 358
21:18:35.978537 IP dh-185.mypond.net.48639 > 239.255.255.250.1900: UDP, length 101
21:18:35.990537 IP dh-185.mypond.net.1900 > 239.255.255.250.1900: UDP, length 360
21:18:36.001020 ARP, Request who-has dh-185.mypond.net tell pch.mypond.net, length 46
21:18:36.002648 IP iggle.mypond.net.41810 > dh-185.mypond.net.48639: UDP, length 428
21:18:36.013759 IP dh-185.mypond.net.1900 > 239.255.255.250.1900: UDP, length 348
21:18:36.038090 IP dh-185.mypond.net.1900 > 239.255.255.250.1900: UDP, length 303
21:18:36.048534 IP dh-185.mypond.net.55588 > iggle.mypond.net.49152: Flags [S], seq 449948286, win 5840, options [mss 1460,sackOK,TS val 4294940131 ecr 0,nop,wscale 1], length 0
21:18:36.048558 IP iggle.mypond.net.49152 > dh-185.mypond.net.55588: Flags [S.], seq 1036548512, ack 449948287, win 5792, options [mss 1460,sackOK,TS val 430115313 ecr 4294940131,nop,wscale 6], length 0
21:18:36.049270 IP dh-185.mypond.net.55588 > iggle.mypond.net.49152: Flags [.], ack 1, win 2920, options [nop,nop,TS val 4294940131 ecr 430115313], length 0
21:18:36.062790 IP dh-185.mypond.net.55588 > iggle.mypond.net.49152: Flags [F.], seq 1, ack 1, win 2920, options [nop,nop,TS val 4294940132 ecr 430115313], length 0
21:18:36.062844 IP iggle.mypond.net.49152 > dh-185.mypond.net.55588: Flags [P.], seq 1:336, ack 2, win 91, options [nop,nop,TS val 430115317 ecr 4294940132], length 335
21:18:36.062855 IP iggle.mypond.net.49152 > dh-185.mypond.net.55588: Flags [F.], seq 336, ack 2, win 91, options [nop,nop,TS val 430115317 ecr 4294940132], length 0
21:18:36.063400 IP dh-185.mypond.net.55588 > iggle.mypond.net.49152: Flags [R], seq 449948288, win 0, length 0
21:18:36.063406 IP dh-185.mypond.net.55588 > iggle.mypond.net.49152: Flags [R], seq 449948288, win 0, length 0
21:19:08.112688 IP dh-185.mypond.net.60652 > 239.255.250.250.9131: UDP, length 109
21:19:54.113569 IP dh-185.mypond.net.41378 > 239.255.250.250.9131: UDP, length 109
21:20:51.114276 IP dh-185.mypond.net.47769 > 239.255.250.250.9131: UDP, length 109
21:21:46.114953 IP dh-185.mypond.net.41499 > 239.255.250.250.9131: UDP, length 109
21:22:39.116215 IP dh-185.mypond.net.59972 > 239.255.250.250.9131: UDP, length 109
21:23:34.116893 IP dh-185.mypond.net.41413 > 239.255.250.250.9131: UDP, length 109
21:24:20.117698 IP dh-185.mypond.net.60011 > 239.255.250.250.9131: UDP, length 109
21:25:02.118610 IP dh-185.mypond.net.38925 > 239.255.250.250.9131: UDP, length 109
21:25:41.119403 IP dh-185.mypond.net.34785 > 239.255.250.250.9131: UDP, length 109


This shows the following:

The AVR gets a valid DHCP address.

The AVR start telling the world about it being a DLNA renderder. (Good)

The AVR has a chat with my DLNA server (all good and expected)

AT 21:09:18, things fall apart. The NR609 starts sending packets to an H323 Multicast address (and stops telling the world about it's DLNA capabilities)

Screen wise, I just see the "Now Initializing" repeated again and again.

I have taken my NR509 off the network in case the two were interfering (unlikely).

The mystery continues. I suspect that the AVR is hung up looking for a Spotify server or something.

Barrie

In regards to your issue- it would possibly be more effective to contact our Product Support Dept for further assistance with this specific issue via our phone number and hours of operation below. We would like to speak with you and work to troubleshoot and resolve your issue, with you having access to your unit, as prompt as possible. We would like to speak with you and provide a thorough answer to your inquiry and assist you with any further questions you may have.

Cordially;

Forum Moderator

I recently got a new router modem, wired & wireless, now I cant connect to my last fm subscription. When I look at the device list in my router, my Onkyo TX NR709's mac address is not on it. Im using the Onkyo's wireless adaptor in the front USB which used to work fine with my last router combo. I now have a ZyXel PK5001Z from centurylink. I dont want to reset my receiver if I dont have to, can someone help? Also there is no support phone number listed (below) Thank's, Don..

Working with Onkyo support in Australia, Onkyo in Japan and Netgem (a popular STB maker), we have found the problem.

The Onkyo network stack is sensitive to (slightly) malformed UPnP multicast frames. If it sees frames which are a bit odd, it locks up in the fashion we are all very familiar with.

I am not happy with the solution presented to me (Netgem have released a fix to their STB firmware such that it no longer causes an Onkyo to crash) but my problems are solved.

The right solution here is for Onkyo to fix their firmware so it doesn't go silly when it sees odd UPnP frames.

Meanwhile, turn UPnP off on your router and restart everything. Should solve the problem. If you need UPnP, put some pressure on Onkyo to lift their game. They know what the problem is.