Boxee

Deklin added a comment - 12/Aug/11 11:03 AM - edited My environment is a WORKING environment, here are my specs for reference 1. Wired network 2. SMB Shared on a protected public share called \\mediaserver\videos 3. Server is Windows Home Server V1 (2003) 4. The user/password I use is ascii characters with a ! in the password. e.g. user, password! 5. No issue since 1.1, 1.2 RC1, 1.2 RC2 1.2 Release 6. I only use MP4/M4V files and never had any stream issues unless they are super high bit rate however that could be my WHS box as I am also running it inside ESXi 4.1. 7. My router is a Linksys E3000 running DDWRT and is also my DHCP server. Nothing special. Again my environment has been working in all releases listed in #5 above, even 1.2 release. Hope this helps

James Colligan added a comment - 12/Aug/11 11:08 AM Did you update from 1.1.2 to 1.2? YES Are you wired or wireless? WIRELESS Where are your shares located? Windows 7 x64 machine Is UpnP working ?? NFS working?? Everything was working great with 1.1.2, now that I've updated I get the loading error. Everytime I tried the RC releases I've had the same results. If I revert back to 1.1.2(Which I've done) my SMB shares work again.

Vince added a comment - 12/Aug/11 11:29 AM - edited Did you update from 1.1.2 to 1.2? YES Are you wired or wireless? WIRELESS Where are your shares located? On a custom PC (Openfiler). With password protected shares it's not working. With public (guest) shares, it's working. I tried with and without "DOMAIN\" with no result. Never tried RC releases. edit : I attached my debug files

SFS added a comment - 12/Aug/11 11:38 AM Did you update from 1.1.2 to 1.2? Yes - previous FWR worked great. Downgrading from new to previous works great. Are you wired or wireless? No - wired entire network. Where are your shares located? Win7 x64 machine. It's just a simple SMB share of an USB HDD with 3 folders in it - TV, Movies, Concerts. With the new FWR when I try to open a SMB share it asks for user/pass which I give it (although it should already know) - it then says no files etc. If I browse from network -> SMB -> myPC I can see the share, but trying to access says no files. Downgrading to previous FWR works great. Wish updates were not mandatory. I'd recommend pulling this update as a mandatory update until this issue is understood.

Aaron Thompson added a comment - 12/Aug/11 12:10 PM - edited Interesting. Using my unRAID and WHS v1 with RC1 and RC2 I did not really have buffering issues but alot of audio dropouts. With this release the audio is back to normal and I have yet to see an buffering from my BD ISOs. I've watched around 7 hours of content from BD ISO since it was released and have not seen any buffering yet. I wonder why Dekin is having issues from his WHS but I have not noticed anything with mine so far. Edit: I see Dekin is using MP4/M4V files while I've only used BD ISOs so far. I have not played around with any of my MKVs or TS or MPEG2 files. But those four types are the only ones I use for my local HD content. I don't have any passwords on my WHS shares so I don't know if that makes a difference.

Faffman added a comment - 12/Aug/11 12:58 PM - edited Did you update from 1.1.2 to 1.2? YES Are you wired or wireless? WIRED (via a Netgear WNHD3004 wireless bridge 78% signal) Where are your shares located? ReadyNAS Pro Pioneer Is UpnP working ?NFS working? YES (lots of buffering) / NO Files are m2ts. Buffering every few seconds/minutes. No problems streaming on the previous firmware. (Logs sent via the 'Boxee Support Tool')

darcilicious added a comment - 12/Aug/11 12:59 PM - edited Folks, don't forget to attach your debug logs, it will go a long way to helping Boxee narrow down the point of failure!

Marcel Hass [Boxee] added a comment - 12/Aug/11 1:32 PM Please please attach your boxee logs

Stefan Koplik added a comment - 12/Aug/11 2:04 PM Did you update from 1.1.2 to 1.2? Yes Are you wired or wireless? Wired Where are your shares located? I've shared C: and D: Is UpnP working ?NFS working? Dunno, no problems before the update though

Jason M Page added a comment - 12/Aug/11 5:16 PM Did you update from 1.1.2 to 1.2? -Not sure, was running one of the RCs prior.   Are you wired or wireless? -Wired.   Where are your shares located? -Synology DS1511+ NAS.   Is UpnP working?NFS working? -I don't use either UpnP or NFS.

Corey Flood added a comment - 12/Aug/11 7:56 PM - edited Did you update from 1.1.2 to 1.2? Yes Are you wired or wireless? Wireless Where are your shares located? Netgear ReadyNas NV+ Is UpnP working ?NFS working? Unsure as these are not enabled. Was working fine before the update, now it either won't play, or it asks for authentication where none was needed before, and will not authenticate even when presented with valid credentials. Log attached and linked here. http://jira.boxee.tv/secure/attachment/14902/boxee.1313192107.1959.tar.bz2 edit: I turned UPNP on for my my roommate so he could play with his Revue, and I can browse and watch files via UPNP. I am using this a temporary workaround, but I would prefer smb shares to be functional again. Also, might I recommend turning off enforced updating?

Tim Jenkins added a comment - 12/Aug/11 8:58 PM - edited Did you update from 1.1.2 to 1.2?YES Are you wired or wireless? Wired to router - wireless to share Where are your shares located? Win 7 laptop I have an attached hard drive to the boxee box. This works fine and I can see the files from the win laptop. The problem is in accessing files from the win 7 share. As others have stated: I can see the computer but can not access any of the shared folders. It worked fine in the previous releases.

Alan Brazendale added a comment - 12/Aug/11 9:34 PM - edited Please add your debug logs and as much info such as: Did you update from 1.1.2 to 1.2? YES Are you wired or wireless? Wired Where are your shares located? On Buffalo NAS Device (SMB) Is UpnP working ?NFS working? no such devices Symptoms: In previous revision all worked as expected. None of the shares on the NAS device have user or password authentication, they are all open. From a PC I can browse to the shares and load content. When browsing 'Shows' or 'Movies' I can see my content (from before the update) but when I select a file, it will say that its not available. If I head over to the 'Files' menu and manually select the full UNC path for the particular shared folder, it presents me with a username/password box. (I tried typing in the admin account for the NAS box and it worked, but the shares aren't password protected and once the Boxee is power cycled the username/password is lost). Boxee is DHCPing from my Linksys router and NAS has a static.. both are wired to the same linksys router.

Pieter Viljoen added a comment - 12/Aug/11 11:06 PM After 1.2 I can no longer play files from my server. Wired gigabit. Server is Windows Server 2008 R2 Logon credentials are for domain user, entered as domain/user_name (it was impossible to enter them as domain\user_name when I set it up) I have two boxes, both forced a 1.2 update, both are now broken both worked fine before. Debug log added.

Robin Fernandes added a comment - 13/Aug/11 9:23 AM - edited Just want to chime in as another user who is unable to access files over SMB since the upgrade to 1.2. I can access the top level of the shared system, but I get the following error message when trying to access subdirectories: "Loading Error. Could not access file, directory or device" > Did you update from 1.1.2 to 1.2? Yes, that's when the issue started. > Are you wired or wireless? Wired. > Where are your shares located? Windows 7 system at smb://qseye/shared2 > Is UPNP working? Yes. > NFS working? I don't have infrastructure to test this. Attached logs (boxee.1313242252.2141-rf.tar.bz2). Please let me know if there's anything else I can do to help progress this issue.

Michael Orr added a comment - 13/Aug/11 11:21 AM I am also now having issues accessing my shares and files over SMB. - Yes, I upgraded to 1.2 (it was previously working) - Wired - Shares are located on a Windows 7 (64-bit) machine, just in a workgroup I attached my log files. Don't care that it shows the user/pass in some places and in other's it's ***'d out :) A quick scan show some errors when trying to access the merlin (my computername)\Videos share: ERROR: CCifsDirectory::GetResource - failed to found host address [merlin] ERROR: CCifsDirectory::GetDirectory - failed to get resource for path [smb://******@merlin/Videos/] DEBUG: GetDirectory - Error getting smb://******@merlin/Videos The 'failed to find host address' error is interesting, since it was obviously able to find the computer in the first place, as when I attempted to browse from the Files menu, it did in fact connect to my machine and list the 2 shares. But when I try to go in the 'Videos' share, it fails.

Joseph Hill added a comment - 14/Aug/11 6:45 AM Did you update from 1.1.2 to 1.2? - YES Are the shares password protected? - YES, ASCII Are you wired or wireless? - WIRED On which operating system or machine your shares located? - Win2k8 & Win2k3 domain shares Is UpnP or AFP or NFS working - UpnP & AFP Pretty much same story as previous posts. Upgraded now get prompt for password and no matter what type of share I make I cannot access. Is there a way to reset to factory defaults with out a remote. I lost mine and been using phone instead, but no network at repair screen. :(

Rafael Mizrahi [Boxee] added a comment - 14/Aug/11 6:49 AM please try the following Open "Administrative Tools" > "Local Security Policy" Browse to "Security Settings > Local Policies > Security Options" Change the value of "Network security: LAN Manager authentication level" from "Send NTLMv2 response only" to "Send LM & NTLM - use NTLMv2 session security if negotiated"

Michael Orr added a comment - 14/Aug/11 8:01 AM Thanks Rafael, Workaround #1 (change to local security policy setting) worked for me.

Rafael Mizrahi [Boxee] added a comment - 14/Aug/11 8:23 AM Corey and Pieter, your logs does not include boxee log. probably because your log level is set to NONE or INFO please change the log level to DEBUG and attach a log file which created during reproduction of the problem.

Robin Fernandes added a comment - 14/Aug/11 10:09 AM Unfortunately, neither workaround appears to have done the trick for me: - "LAN Manager authentication level" was set to "Not defined". Changing it to "Send LM & NTLM - use NTLMv2 session security if negotiated" has had no visible impact on Boxee's behaviour. - "Everyone" has read access to the shared folder, but the Boxee Box still fails to connect.

Michael Orr added a comment - 14/Aug/11 10:33 AM Robin, did you reboot your PC after making the Security policy setting change? I'm not 100% sure, but I believe you may have to reboot for the setting to become in effect (I rebooted and it worked for me).

Robin Fernandes added a comment - 14/Aug/11 10:52 AM Michael, I can confirm the problem persists after a reboot of both the Boxee and the Windows 7 file server. I have attached a new set of logs with debug level tracing with these workarounds in place (boxee.1313333261.2240-rf.tar.bz2).

Pete Brubaker added a comment - 14/Aug/11 4:36 PM - edited Did you update from 1.1.2 to 1.2? Yes Are the shares password protected? Yes Are you wired or wireless? Wired On which operating system or machine your shares located? Fedora Core 14, Samba, version below Is UpnP or AFP or NFS working? Dont know. Attached my logs - boxee.1313355981.4611.tar.bz2 Name : samba Relocations: (not relocatable) Version : 3.5.8 Vendor: Fedora Project Release : 76.fc14 Build Date: Fri 01 Apr 2011 09:16:42 AM PDT Install Date: Sat 21 May 2011 01:08:29 PM PDT Build Host: x86-03.phx2.fedoraproject.org Group : System Environment/Daemons Source RPM: samba-3.5.8-76.fc14.src.rpm Size : 18219148 License: GPLv3+ and LGPLv3+ Signature : RSA/SHA256, Sat 02 Apr 2011 05:44:04 AM PDT, Key ID 421caddb97a1071f Packager : Fedora Project URL : http://www.samba.org/ Summary : Server and Client software to interoperate with Windows machines Can't do the first workaround. Second work around failed. Allowed guest access on the share with the user account 'nobody.' Boxee sees the share, but when going to connect it asks for a user/pass which I leave blank or put in "nobody" and it still wont connect. Also, just wanted to also chime in that perhaps making updates mandatory ISN'T a good idea. Especially with no way to roll back to a previous version.

Tim Jenkins added a comment - 14/Aug/11 5:10 PM - edited Debug Log for Tim Jenkins attached. I tried both of the workarounds with no success.

Rafael Mizrahi [Boxee] added a comment - 15/Aug/11 3:12 AM to those who experience this issue using a NAS. Does your NAS using a static or dynamic IP address? Does your NAS using "User or Domain Security" or "Share Security" ?

Rafael Mizrahi [Boxee] added a comment - 15/Aug/11 4:09 AM Pete and Robin, You cannot connect to the shares because boxee cannot find your smb host error "failed to found host address" 1. On what kind of host your SMB shares are located ? on a NAS ? on a Windows machine? 2. does this host using static or dynamic IP address ? try configuring it using a static ip address.

Robin Fernandes added a comment - 15/Aug/11 6:52 AM Rafael - thanks for looking into this. To answer your questions: 1. The SMB share is on a Windows 7 64bit system. 2. It uses a static IP address (which has not changed recently). Other systems on the network resolve the host correctly and can access the shared data. Also, I would like to suggest that Boxee does in fact resolve the host at first (the error message in the logs may be misleading): as mentioned above, I am able to connect to the share, but I get the error message "Could not access file, directory or device" when I attempt to access subdirectories. I believe this may be visible in the log: Here I access the top level of the share - this is successful:    00:46:38.0571 T:2932095888 M:514170880 DEBUG: thread start, auto delete: 0    00:46:38.0572 T:2932095888 M:514170880 DEBUG: OpenDir - Using authentication url smb://qseye    00:46:41.0191 T:2932095888 M:512294912 DEBUG: Thread 2932095888 terminating A few seconds later I attempt to navigate into the /shared directory - this fails:    00:46:43.0059 T:2932095888 M:512167936 DEBUG: thread start, auto delete: 0    00:46:43.0060 T:2932095888 M:512167936 ERROR: CCifsDirectory::GetResource - failed to found host address [qseye]    00:46:43.0060 T:2932095888 M:512167936 ERROR: CCifsDirectory::GetDirectory - failed to get resource for path [smb://qseye/shared/]    00:46:43.0061 T:2932095888 M:512167936 DEBUG: GetDirectory - Error getting smb://qseye/shared/    00:46:43.0061 T:2932095888 M:512167936 DEBUG: Thread 2932095888 terminating

Rafael Mizrahi [Boxee] added a comment - 15/Aug/11 7:01 AM - edited Robin, thank you for the information. the reason for boxee "failed to found host address" is because the sources are attempted to auto mount before boxee is "Scanning interfaces for shares" I see no "Scanning interfaces for shares" in your log and it is because the network interface is not initialized yet. 1. When Boxee "failed to found host address ", can you browse to Files > Network and see this host (qseye) in the list ? 2. have you added this source manually by typing its IP address ? 3. please attach a longer log file.

Robin Fernandes added a comment - 15/Aug/11 7:26 AM Rafael, 1. My host qseye does not appear under Files > Network. IIRC, this was true before the problem started: it didn't appear automatically - I had to manually add the source. 2. I cannot add the source manually by typing in the IP address. Attempting to do so just returns me to the "Manually enter IP / Name..." screen with no visible error message. You can see that happening in the log I supplied. Not sure whether that unwanted URL encoding (%2e instead of .) is superficial or significant.    00:47:07.0967 T:2941414288 M:512086016 DEBUG: thread start, auto delete: 0    00:47:07.0968 T:2941414288 M:512086016 DEBUG: OpenDir - Using authentication url smb://192%2e168%2e1%2e119    00:47:12.0048 T:2941414288 M:512094208 DEBUG: SMBDirectory->GetDirectory: Unable to open directory : 'smb://192%2e168%2e1%2e119'                                             unix_err:'6e' error : 'Connection timed out'    00:47:12.0049 T:2941414288 M:512094208 DEBUG: GetDirectory - Error getting smb://192.168.1.119/    00:47:12.0049 T:2941414288 M:512094208 DEBUG: Thread 2941414288 terminating I can add the source manually by typing in the host name: I can add the top level directory this way, but when I try to access subdirectories in the Files view, I get the error. I also get the failure if I try to directly add the subdirectory as a source. Thanks again for your persistence with this, and don't hesitate to ask for more info (note however that I'm in an Australian timezone so will become unresponsive shortly).

Rafael Mizrahi [Boxee] added a comment - 15/Aug/11 7:55 AM Robin, 1. does your smb password has any non alpha numeric characters? for example @#?$%^&* 2. please attach a longer log file. I wish to see if boxee starts "Scanning interfaces for shares" in your log.

Robin Fernandes added a comment - 15/Aug/11 8:26 AM Rafael, 1. No. In fact, to attempt to workaround this issue, I have given "Everyone" read access to the share, and turned off password protected sharing under "Control Panel / Network and Internet / Network and Sharing Center / Advanced sharing settings". 2. See boxee.1313410218.6505-rf.tar.bz2. You'll see that "Scanning interfaces for shares" does kick in, but qseye is not found. Another system ("LAPTOP") is found - this is my flatmate's system, and its shares are intentionally protected and unavailable to Boxee. Just to be clear, the problematic behaviour when connecting to qseye is identical whether or not this "LAPTOP" machine is on the network.

Rafael Mizrahi [Boxee] added a comment - 15/Aug/11 8:33 AM Robin, so in your case and in other users who experience an internal error of "failed to found host address" it is clear that boxee fails to auto mount and connect to SMB shares which are not found by boxee network discovery. in other words, if going to Files > Network does not show your host , the source will fail to mount on start. I have reported an internal issue BOXEE-11078 on this.

Rafael Mizrahi [Boxee] added a comment - 15/Aug/11 10:29 AM - edited to those who experience this issue using a NAS. (faffman, jason, corey, Alan) please response to the following questions: 1. please attach a debug log which contain your tests. You have not posted a log file. 2. when the source is not accessible, can you see the host name (of the NAS) by going into Files > Network (could be a duplicate of issue BOXEE-11078 ) 3. are you using a Domain or Workgroup Authentication. see if changing the username into DOMAIN_Name/username solves the mount problem.

Corey Flood added a comment - 15/Aug/11 7:14 PM @Rafael 1. I posted a log, I can post another one though 2. The source is visible via host name as noted in my earlier log. 3. I use a NAS, it should be set to workgroup authentication, with no password required.

Faffman added a comment - 15/Aug/11 7:42 PM @Rafael My issue is with BUFFERING, not share access. Darci suggest I log it here. It appears that this issue has been swamped under the mass of people having share problems. I don't want the buffering problems that I and others are having to be forgotten so if you know of a more suitable ticket I'll log it there instead. Thanks

J H added a comment - 15/Aug/11 10:44 PM Did you update from 1.1.2 to 1.2? YES Are the shares password protected? NO Does your NAS using a static or dynamic IP address? No idea Does your NAS using "User or Domain Security" or "Share Security" ? Are you wired or wireless? Wired On which operating system or machine your shares located? 7 64 my pc doesn't even show up anymore to browse for SMB shares, library is still there under movies but none will play, no idea what to do, was working fine before update

Rafael Mizrahi [Boxee] added a comment - 16/Aug/11 5:08 AM - edited @Corey, as mentioned, your log archive was missing boxee log. please change the log level to DEBUG and attach a new log. try entering the username as WorkgroupName/Username @Faffman, this issue is not about buffering, so please post a different issue. @J H, @Robin Fernandes, your conenction sharing problem is because of issue BOXEE-11078 BOXEE-11078 regression: SMB shares are only mounted to hosts which are found by boxee network discovery. This issue is scheduled to be fixed asap.

Rafael Mizrahi [Boxee] added a comment - 16/Aug/11 5:30 AM tim, see if removing special characters (non alphanumeric, for example @#$%,&) from the password workaround this issue.

Tim Jenkins added a comment - 16/Aug/11 9:36 AM Thank you changing the password has solved the issue.

Chris LaFave added a comment - 16/Aug/11 8:21 PM - edited Did you update from 1.1.2 to 1.2? Yes. Are the shares password protected? Yes. Does your NAS using a static or dynamic IP address? Dynamic; have shares mapped via hostname. Does your NAS using "User or Domain Security" or "Share Security" ? Share security. Are you wired or wireless? Wired. On which operating system or machine your shares located? Linux/Synology DS209+ Attached my debug file (boxee.1313637178.1934.tar.bz2.tar.bz2.tar.bz2)

mike maltar added a comment - 16/Aug/11 11:14 PM Workaround 1 = terrible not going to compromis security to fix something that used to work, but I did a test and it works Workaround 2 = just as bad ..allowing LM .12 and ntlm v1 didn't help me in my domain at home, even set as a domain policy Workaound 3 = does not apply. Workaround 4 = is wrong it is domain\username and not domain/username but just for grins and jollys tried it doesn't work either..

Nick added a comment - 17/Aug/11 4:46 AM Using the previous firmware I didn't experience any problems streaming media through SMB. >Did you update from 1.1.2 to 1.2? Yes >Are the shares password protected? No, guest account enabled. >Does your NAS using a static or dynamic IP address? Through DHCP, but it's always assigned to the same IP address. >Are you wired or wireless? Boxee - wired NAS (Windows 7 machine) - wireless >On which operating system or machine your shares located? Windows 7

Rafael Mizrahi [Boxee] added a comment - 17/Aug/11 4:49 AM Chris, Nick and mike maltar, please attach a DEBUG log created while you reproduces the issue on Boxee.

Adam Rowe added a comment - 17/Aug/11 3:49 PM Attach a debug log created during reproducing the problem. Done. boxee.1313608378.1896.tar.bz2 Are the shares password protected? No. Does your SMB host using a static or dynamic IP address? Static. Does your SMB host user is part of a workgroup or a domain ? Workgroup. Are you wired or wireless? Wired. On which operating system or NAS your shares located? Netgear ReadyNAS 600 Other devices in the same workgroup can access the share without problems. Can you see the share host (the computer or NAS) when going to Files > Network ?

Nick added a comment - 17/Aug/11 6:14 PM @Rafael Mizrahi: Added debug-log, filename boxee.1313618982.2424.tar.bz2

Chris LaFave added a comment - 17/Aug/11 11:16 PM Debug file

Rafael Mizrahi [Boxee] added a comment - 18/Aug/11 4:09 AM chris, your log archive does not contain a DEBUG log. change the log level to DEBUG, reproduce the issue and attach a new log archive. Nick, I see at your log ERROR: CCifsDirectory::GetResource - failed to found host address [NICK2] you are experiencing issue BOXEE-11078 regression: SMB shares are only mounted to hosts which are found by boxee network discovery. your only workaround is to have the SMB host computer or NAS being found at the network by boxee. This issue already fixed internally and will be released ASAP.

Jacob Borsting added a comment - 18/Aug/11 6:05 PM - edited I can browse all my folder with no problems and my nas shows up under network discovery. But I get an error if I try to play any file. I didn't have any problems with the last firmware. The log gives me the following error: ERROR: Open - error reading from input stream log: boxee.1313704620.6497.tar.bz2

Chris LaFave added a comment - 18/Aug/11 10:43 PM This time I made sure that a debug log was in the file. I had Debug enabled, but for some reason it wasn't creating a .log file.

Simon K added a comment - 19/Aug/11 6:20 AM - edited Same issue here. It's actually been fine for about a week, but just stopped working after I rebooted the boxee just now. Are the shares password protected? No. Does your SMB host using a static or dynamic IP address? Static. Does your SMB host user is part of a workgroup or a domain ? Workgroup. Are you wired or wireless? Wired. On which operating system or NAS your shares located? Win 7 x64

Brett Kelly added a comment - 20/Aug/11 7:33 AM Great, go to watch movie tonight anf cant as shares are now stuffed fully.

Wuench added a comment - 20/Aug/11 1:09 PM Did you update from 1.1.2 to 1.2? YES Are you wired or wireless? Wired Where are your shares located? ReadyNAS Files are located on ReadyNAS box accessed as SMB shares. Security on ReadyNAS is set to Share (no authentication username/password required). Boxee Box is unusable to me at this point. I am not willing to add security to those shares as I would have to go through all my other machines and fix their access if I do that. Also ReadyNAS give a warning that file permissions may become corrupted on existing files if security mode is changed. I am reverting until this is fixed.

gmd added a comment - 20/Aug/11 6:13 PM I did not have the SMB issue(s) with this release v. - but anyone that did might want to try the new beta release (v120.20339) that Marcel posted on the Boxee forum earlier today... http://forums.boxee.tv/showthread.php?t=40629

Wuench added a comment - 20/Aug/11 6:29 PM Posting a patch that needs to be loaded via USB is not an acceptable answer for me. I am currently between USB keys. 1.) This needs to be made available as a beta update using the System Update option, 2.) Updates need to be made optional in the future, and 3.) A mechanism needs to be created to revert to the last version without the need for USB keys, etc.

Corey Flood added a comment - 20/Aug/11 6:59 PM Tried 1.2.020339 (info here http://forums.boxee.tv/showthread.php?t=41566) No change. Log uploaded.

Robin Fernandes added a comment - 20/Aug/11 9:51 PM Sorry to report that the latest beta (1.2.1.20339-6101b41) does not improve the symptoms at all. Situation is unchanged: I can access the top level of my share, but not subdirectories. The messages in the log appear to be a bit different, perhaps more informative. Here's a part the looks relevant (see also attached full log boxee.1313890823.2294-rf.tar.bz2): 11:37:50.0215 T:3071424288 M:522215424 DEBUG: CGUIWindowBoxeeBrowse::OnClick, item clicked, path = smb://qseye/shared/ (browse) 11:37:50.0215 T:3071424288 M:522215424 DEBUG: ============================FileItem Dump Start=================================== 11:37:50.0216 T:3071424288 M:522215424 DEBUG: Is Folder: true 11:37:50.0216 T:3071424288 M:522215424 DEBUG: Is Playable Folder: false 11:37:50.0216 T:3071424288 M:522215424 DEBUG: Is Parent Folder: false 11:37:50.0217 T:3071424288 M:522215424 DEBUG: Label: shared 11:37:50.0217 T:3071424288 M:522215424 DEBUG: Label2: 11:37:50.0217 T:3071424288 M:522215424 DEBUG: path: smb://qseye/shared/ 11:37:50.0217 T:3071424288 M:522215424 DEBUG: Label preformatted: false 11:37:50.0218 T:3071424288 M:522215424 DEBUG: Thumb: 11:37:50.0218 T:3071424288 M:522215424 DEBUG: Icon: DefaultFolder.png 11:37:50.0218 T:3071424288 M:522215424 DEBUG: Title: 11:37:50.0219 T:3071424288 M:522215424 DEBUG: m_contenttype: 11:37:50.0219 T:3071424288 M:522215424 DEBUG: m_extrainfo: 11:37:50.0219 T:3071424288 M:522215424 DEBUG: Selected: false 11:37:50.0219 T:3071424288 M:522215424 DEBUG: Size: 0 11:37:50.0220 T:3071424288 M:522215424 DEBUG: m_iprogramCount: 0 11:37:50.0220 T:3071424288 M:522215424 DEBUG: m_idepth: 1 11:37:50.0220 T:3071424288 M:522215424 DEBUG: m_lStartOffset: 0 11:37:50.0220 T:3071424288 M:522215424 DEBUG: m_lEndOffset: 0 11:37:50.0221 T:3071424288 M:522215424 DEBUG: DVD Label: 11:37:50.0221 T:3071424288 M:522215424 DEBUG: OverlayIcon: 0 11:37:50.0221 T:3071424288 M:522215424 DEBUG: m_iDriveType: 0 11:37:50.0221 T:3071424288 M:522215424 DEBUG: m_bCanQueue: true 11:37:50.0222 T:3071424288 M:522215424 DEBUG: m_bIsShareOrDrive: false 11:37:50.0222 T:3071424288 M:522215424 DEBUG: m_dateTime: 1926-11-12 11:37:50.0222 T:3071424288 M:522215424 DEBUG: m_iLockMode: 0 11:37:50.0222 T:3071424288 M:522215424 DEBUG: m_strLockCode: 11:37:50.0223 T:3071424288 M:522215424 DEBUG: m_iBadPwdCount: 0 11:37:50.0223 T:3071424288 M:522215424 DEBUG: ** No video info tag 11:37:50.0223 T:3071424288 M:522215424 DEBUG: ** No music info tag 11:37:50.0223 T:3071424288 M:522215424 DEBUG: Properties (11): 11:37:50.0224 T:3071424288 M:522215424 DEBUG: [controlId] -> [0] 11:37:50.0224 T:3071424288 M:522215424 DEBUG: [directoryPath] -> [smb://qseye/] 11:37:50.0224 T:3071424288 M:522215424 DEBUG: [DisplayPath] -> [smb://qseye/shared/] 11:37:50.0224 T:3071424288 M:522215424 DEBUG: [index] -> [2] 11:37:50.0225 T:3071424288 M:522215424 DEBUG: [is-first-in-container] -> [1] 11:37:50.0225 T:3071424288 M:522215424 DEBUG: [is-last-in-container] -> [0] 11:37:50.0225 T:3071424288 M:522215424 DEBUG: [IsFolder] -> [1] 11:37:50.0226 T:3071424288 M:522215424 DEBUG: [isloaded] -> [1] 11:37:50.0226 T:3071424288 M:522215424 DEBUG: [itemid] -> [24865-0] 11:37:50.0226 T:3071424288 M:522215424 DEBUG: [parentPath] -> [smb://qseye/] 11:37:50.0227 T:3071424288 M:522215424 DEBUG: [windowId] -> [10479] 11:37:50.0227 T:3071424288 M:522215424 DEBUG: ** No external file item 11:37:50.0227 T:3071424288 M:522215424 DEBUG: ** No additional links 11:37:50.0228 T:3071424288 M:522215424 DEBUG: ============================FileItem Dump End=================================== 11:37:50.0228 T:3071424288 M:522215424 DEBUG: CBoxeeItemLauncher::ExecutePlayableFolder - checking for [path=smb://qseye/shared/] (epf) 11:37:50.0229 T:3071424288 M:522215424 DEBUG: ------ Window Init (DialogProgress.xml) ------ 11:37:50.0229 T:3071424288 M:522215424 DEBUG: Loading skin file: DialogProgress.xml 11:37:50.0234 T:3071424288 M:522215424 DEBUG: Load DialogProgress.xml: 5.44ms 11:37:50.0236 T:3071424288 M:522215424 DEBUG: Alloc resources: 6.92ms (5.99 ms skin load) 11:37:50.0236 T:3071424288 M:522215424 WARNING: CGUIWindow::OnMessage - GUI_MSG_SETFOCUS - FAILED to get the control to focus for [id=10]. [WinId=10101] 11:37:50.0814 T:2933689232 M:522207232 DEBUG: thread start, auto delete: 0 11:37:50.0816 T:2933689232 M:522211328 DEBUG: CCifsDirectory::GetResource - mounting CIFS share [//qseye/shared] ==> [/tmp/mnt/smb%5fqseye%5fshared/] 11:37:50.0817 T:2933689232 M:522211328 ERROR: CCifsDirectory::GetResource - failed to mount CIFS share, status[22][Invalid argument], share[//qseye/shared] 11:37:50.0818 T:2933689232 M:522211328 ERROR: CCifsDirectory::GetDirectory - failed to get resource for path [smb://qseye/shared/] 11:37:50.0818 T:2933689232 M:522211328 DEBUG: GetDirectory - Error getting smb://qseye/shared/ 11:37:50.0819 T:2933689232 M:522211328 DEBUG: CCifsDirectory::GetResource - mounting CIFS share [//qseye/shared] ==> [/tmp/mnt/smb%5fqseye%5fshared/] 11:37:50.0820 T:2933689232 M:522211328 ERROR: CCifsDirectory::GetResource - failed to mount CIFS share, status[22][Invalid argument], share[//qseye/shared] 11:37:50.0820 T:2933689232 M:522211328 ERROR: CCifsDirectory::GetDirectory - failed to get resource for path [smb://qseye/shared/] 11:37:50.0820 T:2933689232 M:522211328 DEBUG: GetDirectory - Error getting smb://qseye/shared/ 11:37:50.0821 T:2933689232 M:522211328 DEBUG: Thread 2933689232 terminating Let me know if there's anything I can do to help.

Jacob Borsting added a comment - 23/Aug/11 2:39 AM My box is still bricked with fw 1.2.0.20339 (20th August). 11 days without a working box.. this is worse than when you messed up the audio in 1.1. log: boxee.1313704620.6497.tar.bz2

Marcel Hass [Boxee] added a comment - 23/Aug/11 4:07 AM @Jacob You can see your NAS and add it as a source however when you play any file you get an error?

Jacob Borsting added a comment - 23/Aug/11 4:39 AM - edited @Marcel Yes, I can browse my network shares fine, but I get an error when trying to play any file. Something about the file being currupt or something. I didn't have any problems with the previous stable fw. I have to explain to my girlfriend that she can't host her weekly Desperate Housewifes event because the people who made the box forced an update that broke it.. lucky me :(

Marcel Hass [Boxee] added a comment - 23/Aug/11 6:20 AM @Jacob Completely understand...what NAS are you using? Have you tried UPNP? NFS? as workaround till we solve this issue?

Jacob Borsting added a comment - 23/Aug/11 5:04 PM @Marcel I'm using a Thecus N2100 NAS. I just tried setting up NFS and it seems to work fine.

Wuench added a comment - 24/Aug/11 7:02 PM PLEEEEEASE How do we roll back to a working version???? (My forum account won't let me post).

darcilicious added a comment - 24/Aug/11 7:08 PM @jacob and @eric see this post on how to download/install previous versions, and how to block updates: http://forums.boxee.tv/showthread.php?t=40772

Pieter Viljoen added a comment - 27/Aug/11 12:16 AM Beta firmware 1.2.0.20339 does NOT solve the problem, still unable to access shares on W2K8 R2 using domain account.

Hans Schulze added a comment - 27/Aug/11 7:47 PM I had problems accessing SMB movies on DLink DNS323 after watching a Youtube video that didn't end "nicely" - long pause on a black screen. I got some message about not being able to access the file. After an hour of messing with trying to add/re-add/scan a directory (which seems to work), I finally rebooted Boxee Box and the problem went away. Sounds like something got corrupted. Did you update from 1.1.2 to 1.2? YES Are you wired or wireless? Wired Where are your shares located? On DNS323 (SMB) Is UpnP working ?NFS working? yes, don't know.

Rafael Mizrahi [Boxee] added a comment - 28/Aug/11 7:37 AM - edited @Jacob Borsting I have reviewd your log. you are experiencing a playback error which seems not related to this issue. please report your playback error in a different new issue. @Chris LaFave Please upgrade to 1.2.1.20339 which include a fix for BOXEE-11078 http://forums.boxee.tv/showthread.php?t=41566 @Simon K please attach a DEBUG log so I can investigate the problem you are experiencing. I also recommend that you upgrade to 1.2.1.20339 http://forums.boxee.tv/showthread.php?t=41566 @Corey Flood your log archive is still missing boxee log file. please set your log level to DEBUG, reproduce the problem, get a latest log and attach it to this issue. @Robin Fernandes, issue BOXEE-11178 reproduced and assigned to R&D @Pieter Viljoen W2K8 R2 using domain account getting error 127 Key has Expired error issue BOXEE-10848 reproduced and assigned to R&D Netgear ReadyNas users Which ReadyNAS firmware are you using? Are you using Security Mode "user" or "share" try changing the NAS Security Mode to "user" http://support.netgear.com/app/answers/detail/a_id/14291/~/how-to-set-readynas-share-access

Corey Flood added a comment - 28/Aug/11 2:41 PM @Rafael I am not sure what I am doing wrong, because I am putting it in debug mode, rebooting, testing, and then going and grabbing the log file from my PC. Regardless though, my ReadyNAS NV+ is running 4.1.7, I am not really willing to load beta software on my NAS. The most current version is 4.1.8-T9. More info can be found here. http://www.readynas.com/forum/viewtopic.php?f=17&t=55155 Also, I was using Security Mode "share". I set it to "user", and added a user named "guest". Booted my BB up and it worked! As a reminder I am using BB firmware 1.2.0.20339.

Chris LaFave added a comment - 28/Aug/11 3:27 PM @Rafael I tried the beta firmware you suggested, with the same results. It acts like it can't see my SMB share. My NAS doesn't show up in the list of SMB devices when it scans, but I can manually enter the hostname, user & pass, and then it shows up. Once I go one directory deep into the share though, that's when it disappears. So I can't add any media sources from this share, as it goes back to the device discovery screen after I click to enter my videos share. Conversely, I did enable UpnP and was able to browse this share and add it as a source. I don't know if it is my imagination or not, but when using UpnP it seems that my videos stutter a bit. Plus I'd rather not leave this turned on, as I want some level of security for my NAS shares.

Rafael Mizrahi [Boxee] added a comment - 29/Aug/11 5:33 AM @Corey Flood thanks for the update that switching ReadyNas to security mode "user" workaround the problem. for those with Netgear ReadyNAS using Security Mode "share" 1. Switch from Security Mode "Share" into "User" or 2. If you still insist on using Security Mode "Share", Try to set the user the same as the share name. @Chris LaFave Please attach a new log using 1.2.1.20339

Pieter Viljoen added a comment - 31/Aug/11 11:18 AM A forum user suggested I use the user@domain format. I discovered the following while testing: 1.2.0 and 1.2.1 (Beta): You have to remove all sources and start again. Even if you change the SMB credentials, the already added media uses the old credentials and keeps failing. 1.2.0: user@domain works, for newly added sources. 1.2.1 (Beta): user@domain does not work, just user does work, for newly added sources. 1.2.0 and 1.2.1 (Beta): SMB network playback continually re-buffers.

Robin Fernandes added a comment - 09/Sep/11 11:07 PM - edited Sounds like one of the root causes is fixed in 1.2.1.20361 (via BOXEE-11178). Any chance of making that build publicly available, so I can confirm it resolves the issue? I'm amongst those who have been unable to access their media since the 1.2.0 update over a month ago and have had no luck with the various workarounds... so any steps forward would be greatly appreciated. I'm still happy to work with you and provide any info you need.

Pete Brubaker added a comment - 10/Sep/11 2:19 PM Pretty sweet customer service guys. I've had a brick in my house for a month. What makes this even more awesome is that I cant block outgoing connections on my u-verse router so I can't roll back. You should have had this fixed and a new version released in a couple days.

Robin Fernandes added a comment - 17/Sep/11 10:36 PM Just another bump to ask for a quick update on this. Any chance of making a build with the fix to BOXEE-11178 available, so I can confirm it resolves the issue? Any other news on the SMB problems in general? Any kind of update would be greatly appreciated. My Boxee Box has been unusable for so long now, I'm at risk of forgetting it exists. :)

Robin Fernandes added a comment - 26/Sep/11 4:53 AM Just another request for an update from the devs. I'm still happy to act as your re-create environment and test any pre-release builds.

Rafael Mizrahi [Boxee] added a comment - 26/Sep/11 5:04 AM - edited Robin and Pete, this issue was opened to collect miscellaneous SMB reports from users and distribute them to the correct jira issues. we are aware of the status of password protected SMB share and working on fixing this asap in v1.2.1

Robin Fernandes added a comment - 02/Oct/11 9:52 AM - edited It seems Beta Firmware 1.2.1.20392 (http://forums.boxee.tv/showthread.php?t=43692) resolves the issue for me. Thanks!

Rafael Mizrahi [Boxee] added a comment - 04/Oct/11 4:36 AM All issues appears to be fixed in version 1.2.1.20426 If this same issue happens again, please open a new issue.

Rafael Mizrahi [Boxee] added a comment - 25/Oct/11 10:21 AM NTLMv2 fixed . verified using 1.2.2.20482