Boxee Sucks - Network works then doesnt work

[gmd024]

I believe you said that the BBox worked OK before - was it working before while you were using the powerline adpt'rs --- if possible, can you try connecting the BBox directly to the router with only a hard wire?

The only other suggestion I can think of is jasmeet_9sb's DNS suggestion - it's not really that complicated to try in the BBox's settings

[judgeschambers]

Yes. I have also reset the Boxee and removed all traces of me connecting to it and restarted the setup and still have the same issue.

GMD024,

He also said he's getting a fail on the "update?" I assume when installing the latest Boxee firmware?? We need to back up and make sure that's installing correctly.

Even still, I'm wondering if he should start over and do a factory reset and then let it update to the latest firmware. Of course he'll lose all his settings and will have to re-enter his set up, shares and reindex...but that may be the overall fix for both issues.

I would resort to the router config as the aaaaaablolute last resort as it should not need to be done. Even then....

[gmd024]

GMD024,

He also said he's getting a fail on the "update?" I assume when installing the latest Boxee firmware?? We need to back up and make sure that's installing correctly.

Even still, I'm wondering if he should start over and do a factory reset and then let it update to the latest firmware. Of course he'll lose all his settings and will have to re-enter his set up, shares and reindex...but that may be the overall fix for both issues.

I would resort to the router config as the aaaaaablolute last resort as it should not need to be done. Even then....

Ahh! - I guess I assumed he meant some sort of a 'fail' on connection to shares - If the frmw update has failed, then yes, he should get the frmw installed properly - and a reset/re-install my be required

[judgeschambers]

Ahh! - I guess I assumed he meant some sort of a 'fail' on connection to shares - If the frmw update has failed, then yes, he should get the frmw installed properly - and a reset/re-install my be required

Well, I was not sure either, so I wanted him to clarify and if so....a restore typically sorts out this sort of thing. Lets see what he says.

Then if that does not fix it, then use your suggestion with wired test without the powerline connection to make sure.

[vtxrider]

My money is on the Powerline bridge, those things are finicky. I think boxee should recommend a hard wire connection whenever possible. I know this is not practical in some cases, but I crawled around in the attic pulling cable and am not a bit sorry as my connection to my Dir-655 has been rock solid.
He may want to download the last FW that worked for him, and install from a SD card while blocking the screensaver to prevent to newer update from installing. If it were me I would just snake a cat6 from my router down the hall to the BB to make sure it isn't a communication issue as that is a fast check.

[jf3000]

No, No, No, I updated the BBox and only after the update I have not been able to connect to the computer. I've tried with and without the powerline and still the same process.

Is there a guide for the DNS side of things or if someone can give me some assistance please?

Thank you to all that have replied, much appreciated and also overwhelmed by the general support from the forum as well.

vtxrider I did also try your suggestion with removing the powerline and running the cat6, I originally had the cat6 running and then opted to try the powerline since Dlink gave them to me for free, everything worked fine and was great.

Ran the update and installed, when to access pc and said fail. Wouldnt connect. Have been stumped from there on.

Have done a complete reset as well and still same issues. So completely baffled.

Thank you.

[dadein]

If this is a nameserve problem, I suggest downloading namebench and use the results it offers (after several runs while experiencing problems) rather than guessing which servers would be best.

I have had issues in the past (log-in, connection, buffering, SMB, etc.) which I believe are the result of slower than average name-servers(ie: Boxee not waiting long enough and then not handling the error graciously). By running namebench, I was able to resolve most of it by connecting to the openDNS servers. It's not that the openDNS servers are ALWAYS faster, but they seem to be much more consistent(at least in my case) than my ISP's or other servers.

I don't have the nameservers plugged directly into Boxee, but rather I have configured my router so the whole LAN is using (and protected by) openDNS.