July 5th, 2012, 12:01 PM
Boxee won't re-coonect to a restarted SMB server, restarting boxee reconnects
I apologize if I am not posting in the right place, I have tried looking for a solution but could not find people who experienced the same problem.
Here is my setup:
#1 Windows 7 Enterprise SMB Shares (aka: Ivy)
- Left the homegroup
- WORKGROUP (same as boxee)
- In the Network and Sharing Center I am in a Work Group
- Advanced sharing settings:
-- Enabled file sharing for devices that use 40 - or 56- bit encryption
-- Turned on password protected sharing
-- Using user accounts and passwords to connect to other computers
#2 Boxee Box (updated, latest version)
- Connected to Ivy share
Senario of problem #1:
Watching a movie on Ivy share, if Ivy is restarted while the movie is playing, the boxee box freezes, even when Ivy is finished restarting and is back up, Boxee box will continue to be frozen until it is manually restarted, then all is well.
Senario of problem #2:
If the boxee box is always on, and at any point Ivy is restarted, I can no longer connect to Ivy through any route, I cannot access the mapped shares, I canno't readd the share, I cannot re-scan Ivy Share, the only way to fix the problem is to restart boxee.
This problem has been mention before, however on my second computer with nearly identical settings, problem #1 or problem #2 does not occur. I have no clue what it could be because I just reformatted and installed clean Windows 7, re-done all network settings and still the problem persists. I am also going to mention that I am running Norton Antivirus 2012, hoever I did try to disable that dog don't bark.
July 5th, 2012, 02:23 PM
I believe I see the same / similar behavior.
When looking at teh syslog dump from Boxee, it was somethign about unable to mount the CIFS. To be honest, I have just been dealing with it and didn't spend much time looking into it.
July 5th, 2012, 02:35 PM
I have sometimes found that using Logout (instead of Shutdown) has allowed me to access shares which Boxee was not picking up, so it may work for you. This isn't really a solution, but this is a lot quicker than a full reboot of the box.
July 5th, 2012, 04:37 PM
Thank you for your reply, however your solution will only work for scenario #2, because if the boxee freezes during a movie, or while inside of the folder share it becomes unresponsive.
July 6th, 2012, 08:29 AM
Buy a NAS Box or setup a dedicated machine with SMB/NFS shares.
If you were watching a ON Demand movie on your Cable box and you YANKED the cable connection... do you think that when you re-attached the cable the Movie would just keep going? I bet not... I bet you would have to reboot the Cable box.
July 6th, 2012, 01:03 PM
Originally Posted by gonkman
I do have a NAS box it is full to its capacity limits, and its setup as a separate share, as for a dedicated machine, I also have an old computer that I tried using as a dedicated machine. The main reason for my setup is because I have x3 1TB hard drives that are serving little to no purpose, and can only be connected to my main PC via SATA (Ivy).
The other reason is because my old PC is not a gigabit lan, so the transfer speeds cap out at 10mbs, watching high def movies causes latency issues even over wired connection. And getting or building another low end machine for this purpose is not very cost effective.
As for your comment about the TV Cable Box, actually the cable box will be fine, it won't freeze, it will probably even give you some message like "no connection", unlike boxee which will have no responsiveness whatsoever, to top it off, if you do re-connect the cable your tv will resume as normal.
To be honest your post was nothing but bad criticism, I do have my reasons for starting this thread, that is to understand the problem, because I know it's a problem that has a solution, I do not want someone to tell me that my whole method is wrong thx.
July 6th, 2012, 01:29 PM
I am also seeing the same issue on both of my boxes, if the SMB share becomes unavailable for what ever reason, say power outage or service restart. even though the share comes back up and is accessible from other devices i almost always have to reboot the boxes before it can reconnect.
However i think if you wait long enough it will come back because i know I've had drops in the living room, rebooted, and later that day used the box in the dining room without rebooting it. So this seems like its some kind of timeout/reconnect issue/bug. Since i don't seem to be the only one having this issue i think i'll open an issue in jira for the devs to look at and reference this post, unless someone has already done it.