Blu-ray and DVD Players/Recorders

[Chipmaster]

I attempted to download the latest firmware update to allow Netflix streaming on my newly purchased NS-BRDVD3 player and had a number of problems.  In every case I received an error message that the update failed.  Turns out it ended up being my modem which was rendered inoperable because Cox Cable had updated their network hardware.

I purchased a Motorola SB5101U modem which solved ALL of my network problems and let me easily download and installed the latest firmware up.

My Insignia NS-BRDVD3 player now works flawlessly.  I purchased it at Best Buy 10/28/2009. 

[doctorj]

I have the same issue with the wired ethernet connection, but have worked around it - but now that you mention not getting a lot of reports I want to report it.  I am using a "straight" CAT5 ethernet cable (i.e. not a crossover).

I have an older Belkin F5D7230-4.  When the NS-BRDVD3 is connected to a port on that, it is hit-and-miss whether or not the ethernet connection will be working when I power on the Insignia.  I would estimate 8/10 times it shows up as not connected.  But when it does connect, it works fine until power down.  Unplugging and re-plugging either end of the ethernet cable multiple times until it connects is a lot faster than powering it off/on... but either method will work to "eventually" establish a connection - albeit a royal pain.

I also have a D-Link DIR-655.  The Insignia works consistently when connected to the D-Link.  It just wastes a gigabit port... that I have very few of.  This is how I use it now.

The Belkin is connected to the D-Link and this connection functions flawlessly, through power-downs and resets of the D-Link.  In fact, no other device has EVER had an issue connecting to the Belkin... until this Insignia NS-BRDVD3 player.  I would not make the leap to place the blame on the routers.  There is something "unique" about the Insignia.

The only difference that I can think of is that the D-Link has Auto-MDIX and the Belkin does not.  I am speculating that the Insignia has Auto-MDIX and the negotiation intermittently fails when connected to the Belkin, resulting in the "no connection" problem.  The DD-WRT is in the same class, so I expect whatever the cause, it is the same issue.  Could the Insignia be determining that a crossover cable is in use, when in fact it is not?

BTW: I think most people today when people have intermittent trouble with a device like this just return it and get something else; especially when it's out-of-the-box trouble.  Also, I am speculating that newer network devices all support Auto-MDIX and therefore work.  I believe this could explain the few reports.

Another answer could be to note a cheap ethernet hub/switch that does work well with the Insignia.  Then this could be connected to the Insignia before the troublesome routers and effectively used to insulate the problem.

[doctorj]

I made an unfortunate observation today.  With a DVD in the player at power-on, connected to the D-Link DIR-655 router, it fails to connect 100% of the time!  I tried this repeatedly.  Remove the DVD, power off and back on and it connects.

This is easily repeatable.  It was the 2009 Star Trek DVD if that makes any difference (not Blu-Ray).

When it fails to connect, I see a "Connected" with a green checkmark.  Then the DVD disc detected icon and whatnot.  Followed by the network problem, press the "red" button.  Checking the settings it says "aquiring address" forever.

You guys should be able to repeat these issues.  I personally have experienced EVERY single issue that I have seen documented about this player that matches my setup.  I am pretty sure that I can reproduce any of them, but the only issue of concern for me is the network connectivity.

Again, I have a work-around.  Don't leave a disc in the player.  Hopefully this will help to come up with a resolution.  Admitting that you have a problem is the first step to recovery.

[Two99Point80]

---

doctorj wrote: When it fails to connect, I see a "Connected" with a green checkmark.  Then the DVD disc detected icon and whatnot.  Followed by the network problem...

Again, I have a work-around... Hopefully this will help to come up with a resolution.  Admitting that you have a problem is the first step to recovery.

---

Sounds like there's a flag in the software which indicates a good network connection, but that flag is being overwritten in some circumstances by a routine which shouldn't be writing to that address.

[Pardon me for that - I programmed microcontrollers a number of years ago and my code didn't always do what I expected ]

Between all of us, maybe we'll be able to restore our players to sanity...

Message Edited by Two99Point80 on 11-22-2009 07:27 AM

[doctorj]

---

Two99Point80 wrote:

[Pardon me for that - I programmed microcontrollers a number of years ago and my code didn't always do what I expected ]

Between all of us, maybe we'll be able to restore our players to sanity...

Message Edited by Two99Point80 on 11-22-2009 07:27 AM

---

The frustrating part for me is that I am a Senior Software Engineer, working for the past 20 years in embedded software and the last 15 for the automotive industry.  Operational glitches are simply not something we could let go to production.  With drive by wire technology... it must always work under all conditions.  I can fix it - I am expected to solve the impossible every day.

It's a bit of a different story in consumer electronics.  I try to play my role as customer and see how goes.  I am pleased to see that Insignia does appear to take a genuine interest in fixing the issues.  With most products the bugs are never repaired, and the only way to a fully functional device is reverse-engineering the firmware after it has been abandonded by the company and making the corrections - albeit this is getting progessively more difficult (impossible just takes longer).

I'm keeping my fingers crossed.

[Two99Point80]

---

doctorj wrote:

The frustrating part for me is that I am a Senior Software Engineer, working for the past 20 years in embedded software and the last 15 for the automotive industry.  Operational glitches are simply not something we could let go to production.

---

Ah.  My experience was in handheld electronic games, where we'd sometimes tell the boss IFNAB ("It's A Feature, Not A Bug.")  Totally different requirements.  Know what you mean about consumer-product incompleteness - I at one time owned three Amigas :-)

[millard]

I also, out of nowhere had, the internet connection failure. Tried different cables, pinged IP addres of player, was fine. I aslo removed disc from player and it worked. I know in the past I've left a disc in the player and then stopped the disc that was playing and went into the Netflix option and it worked. I have the option to auto play the disc checked. The disc was a Blu-ray of Planet Earth.

[Killiondude]

Like somebody else on here did, I couldn't get the first DVD player to connect to my network, so after talking to a customer service agent (yes, useless), I exchanged the item only to find out that the second one didn't work either! I'm completely dismayed with this, especially the fact that the Insignia techs can't replicte a problem that seems to have affected many.

To explain my set up, I have the system plugged into a WRT45-something router (Linksys), which is plugged into my cable modem. I've tried multiple network cables, in various ports on the router, and I've even plugged it directly into my cable modem to no avail. It would be nice to have a firmware upgrade to fix this problem. 

[fhall1]

I don't know what's going on with mine...I put up one of the biggest stinks in this thread about this problem and now my player hasn't dropped its connection in a couple weeks.  Sad thing is I didn't change a thing.  Not complaining, but not thinking it's fixed either.

[fhall1]

---

Roger-INSG wrote:

All,

      Please try the following to help us isolate the cause.  When the player is showing as disconnected go to Settings - Network - Network Test and report back what you see.

---

OK....finally lost the network connection tonight.  Network test says "Connection 0.0.0.0  timeout"