Boxee

regression: SMB Shares no longer accessable from Windows Domain files server.

Details

  • Product:
    Boxee Client
  • Severity:
    Critical
  • Version:
    1.2.0.20310
  • Operating System:
    Boxee Box
  • Number of attachments:
    4

Description

I am unable to get into my network shares on my windows domain machines.
This can be a windows 7 desktop 64bit or a windows 2008r2 server.
This environment has been working since the initial release of boxee. I noticed it was broken the release before the DVI fix, the current beta built still has the result.

I have reset my domain account to ensure password is correct.
I am unable to play any existing movies or music. I attempted to create a new share but can't access though I can browse the server share list.

Reference previous case. BOXEE-10721

Suggested workaround:
Please try to change the compatibility level of NTLM security at your server.
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"

  1. boxee.1312940906.2139.tar.bz2
    09/Aug/11 9:54 PM
    54 kB
    mike maltar
  2. boxee.1312943253.2527.tar.bz2
    09/Aug/11 10:28 PM
    105 kB
    mike maltar
  3. boxee.1313234626.2101.tar.bz2
    13/Aug/11 8:11 AM
    40 kB
    mike maltar
  4. smb 1..0 capture.pcap
    13/Aug/11 8:23 AM
    120 kB
    mike maltar

Issue Links

Activity

Hide
mike maltar added a comment -
A bit more infomation. I am connecting via hardwired ethernet cable. No issues connecting to internet. I am unable to access any of my previous content that has been indexed. Or create any new content links. I can get the SMB server list, there are no DNS problems and it is a flat ethernet network. This used to work fine until 1.2 release. I am using VMWARE ESXI to host windows envirnoment, of which none of my workstations have problems accessing share. As I stated in my first post. This worked flawlessly since I first bought the boxee box on release day.. The latest release today aug 9, still has the problem. I cleared the boxee logs and put in debug mode and have submitted the logs for review.

I just confirmed it is not just a domain issue. I took a windows 7 professional 64bit machine and created a workgroup called TMP which is the same name as my domain. I created a local user on the machine which is the same as the domain user that has the problem in my domain. This is called pass though security., I tested my ability to use the local user from another machine and it worked with no issue. Came back to the boxee, browesed network shares, under SMB. I could see the share and machine called MCP9 I was unable to access that share as well. So it might not be limited to domain account as I thought. Here is that log as well

Show
mike maltar added a comment - A bit more infomation. I am connecting via hardwired ethernet cable. No issues connecting to internet. I am unable to access any of my previous content that has been indexed. Or create any new content links. I can get the SMB server list, there are no DNS problems and it is a flat ethernet network. This used to work fine until 1.2 release. I am using VMWARE ESXI to host windows envirnoment, of which none of my workstations have problems accessing share. As I stated in my first post. This worked flawlessly since I first bought the boxee box on release day.. The latest release today aug 9, still has the problem. I cleared the boxee logs and put in debug mode and have submitted the logs for review. I just confirmed it is not just a domain issue. I took a windows 7 professional 64bit machine and created a workgroup called TMP which is the same name as my domain. I created a local user on the machine which is the same as the domain user that has the problem in my domain. This is called pass though security., I tested my ability to use the local user from another machine and it worked with no issue. Came back to the boxee, browesed network shares, under SMB. I could see the share and machine called MCP9 I was unable to access that share as well. So it might not be limited to domain account as I thought. Here is that log as well
Hide
mike maltar added a comment -
Log from boxee connecting attempting to test from non domain windows 7 machine.
Show
mike maltar added a comment - Log from boxee connecting attempting to test from non domain windows 7 machine.
Hide
mike maltar added a comment -
Still not working in 1.2.0.20310
Show
mike maltar added a comment - Still not working in 1.2.0.20310
Hide
Rafael Mizrahi [Boxee] added a comment -
mike, I can see in your log that the CIFS SMB mount fails with permission denied

ERROR: CCifsDirectory::GetResource - failed to mount CIFS share, status[13][Permission denied], share[//192.168.1.10/Music]

have you added the smb source manually ?
did you try writing the user name with a prefix of teh domain name ? for example Domain/Username ?
Show
Rafael Mizrahi [Boxee] added a comment - mike, I can see in your log that the CIFS SMB mount fails with permission denied ERROR: CCifsDirectory::GetResource - failed to mount CIFS share, status[13][Permission denied], share[//192.168.1.10/Music] have you added the smb source manually ? did you try writing the user name with a prefix of teh domain name ? for example Domain/Username ?
Hide
Jeff Bindon added a comment -
I get the same issue using my D-link DNS-323 NAS. All my SMB shares via my NAS worked fine until the update this morning. I tried resharing the folders - but the Boxee box wont access them. If I try to add the share via network sources - i can see the shares, it just wont go into the folder - it just goes back to the nas root folder.
Show
Jeff Bindon added a comment - I get the same issue using my D-link DNS-323 NAS. All my SMB shares via my NAS worked fine until the update this morning. I tried resharing the folders - but the Boxee box wont access them. If I try to add the share via network sources - i can see the shares, it just wont go into the folder - it just goes back to the nas root folder.
Hide
Rafael Mizrahi [Boxee] added a comment -
Jeff,
are you using a windows Domain file server?
please attach a log file.
Show
Rafael Mizrahi [Boxee] added a comment - Jeff, are you using a windows Domain file server? please attach a log file.
Hide
Rafael Mizrahi [Boxee] added a comment -
Mike, Jeff,
are you trying to connect to a password protected windows directory?
try to add the source and wrote DOMAIN\User as the user name.
Show
Rafael Mizrahi [Boxee] added a comment - Mike, Jeff, are you trying to connect to a password protected windows directory? try to add the source and wrote DOMAIN\User as the user name.
Hide
K.bart added a comment -
I have the same symptoms as you since preforming the latest update to my Boxee Box. My set-up is slightly different - Media is kept on a Netgear ReadyNas NV+
Since the update I can see the root share folders(not files) on my NAS but it always prompts for creds (there are none as it is set to everyone for access) and then it doesn't connect. The NAS is accessible from other systems/devices on the network without any creds, and works flawlessly.

I've had to revert to the 0.9 firmware to get the Boxee Box working at all, and now I am stuck on this old FW until this get's resolved.

Common Boxee guys - this is a wide spread issue and impacts everyone accessing network shares via the BB. Please get this sorted out asap
Show
K.bart added a comment - I have the same symptoms as you since preforming the latest update to my Boxee Box. My set-up is slightly different - Media is kept on a Netgear ReadyNas NV+ Since the update I can see the root share folders(not files) on my NAS but it always prompts for creds (there are none as it is set to everyone for access) and then it doesn't connect. The NAS is accessible from other systems/devices on the network without any creds, and works flawlessly. I've had to revert to the 0.9 firmware to get the Boxee Box working at all, and now I am stuck on this old FW until this get's resolved. Common Boxee guys - this is a wide spread issue and impacts everyone accessing network shares via the BB. Please get this sorted out asap
Hide
mike maltar added a comment -
I am confident I am typing the correct password.. I changed it to a one character password.. I earased all my existing shares that used to work and will atempt to recreate. Yes I have two domain controller, and a fileserver running under esxi 4.1. I do use the prefix for the domain with is actullly domain\username and not domain/username as you have listed.
Show
mike maltar added a comment - I am confident I am typing the correct password.. I changed it to a one character password.. I earased all my existing shares that used to work and will atempt to recreate. Yes I have two domain controller, and a fileserver running under esxi 4.1. I do use the prefix for the domain with is actullly domain\username and not domain/username as you have listed.
Hide
Bill Beauvais added a comment - - edited
Simply, my by Boxee worked yesterday, updated last night, now does not let me access anything from my shared folders!!!! Is there a solution that I can apply without having to be an IT master? I love my Boxee, I don't love my useless square thing that's looking at me right now.
Show
Bill Beauvais added a comment - - edited Simply, my by Boxee worked yesterday, updated last night, now does not let me access anything from my shared folders!!!! Is there a solution that I can apply without having to be an IT master? I love my Boxee, I don't love my useless square thing that's looking at me right now.
Hide
Bill Beauvais added a comment -
ps....on an iMac, worked perfectly out of the box and has survived firmware updates before...
Show
Bill Beauvais added a comment - ps....on an iMac, worked perfectly out of the box and has survived firmware updates before...
Hide
mike maltar added a comment -
I deleted all my shares I can browse all the way to the share listing but as soon as I atempt to log in I get the error. I created a share with everyone full control and I still can't get though it. I understand where Bill is comming from. I am an IT Expert (MSCE) and I can't get it to work. As I pointed out in my last ticket, I think you need to look at the unexpected SMB signature message . I agree that it is retuning logon failure that might be generic retrun code, but look at the Send error in session setup?



CIFS VFS: Unexpected SMB signature
Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
 CIFS VFS: Send error in SessSetup = -13
 CIFS VFS: cifs_mount failed w/return code = -13
 CIFS VFS: Unexpected SMB signature

I would be big dollars, that you eneabled SMB2 in samba, and there is a bug in your code. SAMB has lots of know issues wtih SMB2. While SMB2 is the way to go. Try disabling SMB2 (client side) and rebuld.

Show
mike maltar added a comment - I deleted all my shares I can browse all the way to the share listing but as soon as I atempt to log in I get the error. I created a share with everyone full control and I still can't get though it. I understand where Bill is comming from. I am an IT Expert (MSCE) and I can't get it to work. As I pointed out in my last ticket, I think you need to look at the unexpected SMB signature message . I agree that it is retuning logon failure that might be generic retrun code, but look at the Send error in session setup? CIFS VFS: Unexpected SMB signature Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE  CIFS VFS: Send error in SessSetup = -13  CIFS VFS: cifs_mount failed w/return code = -13  CIFS VFS: Unexpected SMB signature I would be big dollars, that you eneabled SMB2 in samba, and there is a bug in your code. SAMB has lots of know issues wtih SMB2. While SMB2 is the way to go. Try disabling SMB2 (client side) and rebuld.
Hide
mike maltar added a comment -
OK my SMB2 theory might not be valid, I disabled SMB2 one of my servers and I stil have the same issue. Ran another debug trace only performing a minimal number of steps. Powered on unit, went to files, SMB , saw my listing of SMB shares, selected my SMB1 server with SMB2 disabled, and then selected my SMB2 server. Same issue can't even get into the shares

. I did notice and error in the djmount

djmount[1709]: segfault at fffffffb ip b7dd8919 sp bfcf1a24 error 4 in libc-2.7.so[b7d70000+12d000]
then whole bunch of input input0: event field not found
ramzswap: Invalid ioctl 21297
Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
 CIFS VFS: Send error in SessSetup = -13
 CIFS VFS: cifs_mount failed w/return code = -13
Status code returned 0xc0000072 NT_STATUS_ACCOUNT_DISABLED
 CIFS VFS: Send error in SessSetup = -127
 CIFS VFS: cifs_mount failed w/return code = -127
Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
 CIFS VFS: Send error in SessSetup = -13
 CIFS VFS: cifs_mount failed w/return code = -13
Status code returned 0xc0000072 NT_STATUS_ACCOUNT_DISABLED
 CIFS VFS: Send error in SessSetup = -127
 CIFS VFS: cifs_mount failed w/return code = -127
Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
 CIFS VFS: Send error in SessSetup = -13
 CIFS VFS: cifs_mount failed w/return code = -13
Status code returned 0xc0000072 NT_STATUS_ACCOUNT_DISABLED
 CIFS VFS: Send error in SessSetup = -127
 CIFS VFS: cifs_mount failed w/return code = -127


My account is not Disabled..

So I created a second share tmp2 and set the share to allow the everyone permission and then enabled the guest account and it works. That is not an acceptable solution as nobody would enable the guest account.. It has to be something in the authentication. I did a wire shark dump have enclosed it along with another debug dump
Show
mike maltar added a comment - OK my SMB2 theory might not be valid, I disabled SMB2 one of my servers and I stil have the same issue. Ran another debug trace only performing a minimal number of steps. Powered on unit, went to files, SMB , saw my listing of SMB shares, selected my SMB1 server with SMB2 disabled, and then selected my SMB2 server. Same issue can't even get into the shares . I did notice and error in the djmount djmount[1709]: segfault at fffffffb ip b7dd8919 sp bfcf1a24 error 4 in libc-2.7.so[b7d70000+12d000] then whole bunch of input input0: event field not found ramzswap: Invalid ioctl 21297 Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE  CIFS VFS: Send error in SessSetup = -13  CIFS VFS: cifs_mount failed w/return code = -13 Status code returned 0xc0000072 NT_STATUS_ACCOUNT_DISABLED  CIFS VFS: Send error in SessSetup = -127  CIFS VFS: cifs_mount failed w/return code = -127 Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE  CIFS VFS: Send error in SessSetup = -13  CIFS VFS: cifs_mount failed w/return code = -13 Status code returned 0xc0000072 NT_STATUS_ACCOUNT_DISABLED  CIFS VFS: Send error in SessSetup = -127  CIFS VFS: cifs_mount failed w/return code = -127 Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE  CIFS VFS: Send error in SessSetup = -13  CIFS VFS: cifs_mount failed w/return code = -13 Status code returned 0xc0000072 NT_STATUS_ACCOUNT_DISABLED  CIFS VFS: Send error in SessSetup = -127  CIFS VFS: cifs_mount failed w/return code = -127 My account is not Disabled.. So I created a second share tmp2 and set the share to allow the everyone permission and then enabled the guest account and it works. That is not an acceptable solution as nobody would enable the guest account.. It has to be something in the authentication. I did a wire shark dump have enclosed it along with another debug dump
Hide
No thanks added a comment -
This should be marked as Critical. Boxee cannot play video files from network sources.

I'm running Windows Home Server and Boxee Box now constantly asks for my login/password.
Show
No thanks added a comment - This should be marked as Critical. Boxee cannot play video files from network sources. I'm running Windows Home Server and Boxee Box now constantly asks for my login/password.
Hide
Royce Rezendes added a comment -
I cannot access my network shares or browse to them manually using SMB after the 1.2 update. I'm going to try and remove and re-add them and I will post back the results.
Show
Royce Rezendes added a comment - I cannot access my network shares or browse to them manually using SMB after the 1.2 update. I'm going to try and remove and re-add them and I will post back the results.
Hide
Royce Rezendes added a comment -
when I go to add the sources after deleting them, I choose SMB, then (because my server doesn't appear) I choose Manually. Then I type my HOSTNAME and it allows me to view the shares and I choose a folder and it backs out to the first menu after choosing Add Source and No new sources are added.
Show
Royce Rezendes added a comment - when I go to add the sources after deleting them, I choose SMB, then (because my server doesn't appear) I choose Manually. Then I type my HOSTNAME and it allows me to view the shares and I choose a folder and it backs out to the first menu after choosing Add Source and No new sources are added.
Hide
Adam Kelley added a comment -
Same thing here. SMB shares are now asking for credentials. This has completely ruined the weekend, as no access to our media library!
Show
Adam Kelley added a comment - Same thing here. SMB shares are now asking for credentials. This has completely ruined the weekend, as no access to our media library!
Hide
Royce Rezendes added a comment -
OK, all is working now... I think maybe a windows update or something coincidental was my problem because all I did was restart my server and now all is well.
Show
Royce Rezendes added a comment - OK, all is working now... I think maybe a windows update or something coincidental was my problem because all I did was restart my server and now all is well.
Hide
greg galanos added a comment -
SMB code definitely broken. Was forced to update to new version. Rebooted. BB can no longer find public shares on Windows 7. Gets to the /machine/Users then cannot show /public folder and gives error message 'Loading Error. Could not access file, directory or device.'

is there a workaround here? Or at least 'REVERT YOUR FORCED UPDATE' with another forced update.
Show
greg galanos added a comment - SMB code definitely broken. Was forced to update to new version. Rebooted. BB can no longer find public shares on Windows 7. Gets to the /machine/Users then cannot show /public folder and gives error message 'Loading Error. Could not access file, directory or device.' is there a workaround here? Or at least 'REVERT YOUR FORCED UPDATE' with another forced update.
Hide
Rafael Mizrahi [Boxee] added a comment -
please try the following on your windows server:

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"
Show
Rafael Mizrahi [Boxee] added a comment - please try the following on your windows server: 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"
Hide
greg galanos added a comment -
On NON-SERVER Windows 7, I have confirmed the following (AND IT WORKS!!!):

Open "Administrative Tools" > "Security Configuration Management"

Browse to "Security Settings > Local Policies > Security Options"

Change the value of "Network security: LAN Manager authentication leve from "None Set" to
"Send LM & NTLM - use NTLMv2 session security if negotiated"

All good again.
Show
greg galanos added a comment - On NON-SERVER Windows 7, I have confirmed the following (AND IT WORKS!!!): Open "Administrative Tools" > "Security Configuration Management" Browse to "Security Settings > Local Policies > Security Options" Change the value of "Network security: LAN Manager authentication leve from "None Set" to "Send LM & NTLM - use NTLMv2 session security if negotiated" All good again.
Hide
mike maltar added a comment -
 I will give that a try and get back to you. Though I am not sure that reducing the security level is the soltuion. It worked with NTLM2 in past versions, why can't you just derermined what chanaged in the code and fix it.?
Show
mike maltar added a comment -  I will give that a try and get back to you. Though I am not sure that reducing the security level is the soltuion. It worked with NTLM2 in past versions, why can't you just derermined what chanaged in the code and fix it.?
Hide
Rafael Mizrahi [Boxee] added a comment -
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" ?
Show
Rafael Mizrahi [Boxee] added a comment - 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" ?
Hide
Rafael Mizrahi [Boxee] added a comment -
* Suggested Workaround 3:
see if removing special characters (non alphanumeric, for example @#$%,&) from the password workaround this issue

* Suggested Workaround 4:
Add the workgroup or domain name to the username value. for example WorkgroupName\UserName

since this issue became mixed with various reasons for SMB to stop working,
please, everyone, move to use the more general issue BOXEE-11038 and I am closing this one.

Add your votes and comments at BOXEE-11038
Show
Rafael Mizrahi [Boxee] added a comment - * Suggested Workaround 3: see if removing special characters (non alphanumeric, for example @#$%,&) from the password workaround this issue * Suggested Workaround 4: Add the workgroup or domain name to the username value. for example WorkgroupName\UserName since this issue became mixed with various reasons for SMB to stop working, please, everyone, move to use the more general issue BOXEE-11038 and I am closing this one. Add your votes and comments at BOXEE-11038
Hide
Rafael Mizrahi [Boxee] added a comment -
closed as duplicate of BOXEE-11038
please add your votes and comments at issue BOXEE-11038
Show
Rafael Mizrahi [Boxee] added a comment - closed as duplicate of BOXEE-11038 please add your votes and comments at issue BOXEE-11038
Hide
Rafael Mizrahi [Boxee] added a comment -
NTLMv2 fixed . verified using 1.2.2.20482
Show
Rafael Mizrahi [Boxee] added a comment - NTLMv2 fixed . verified using 1.2.2.20482

People

Vote (12)
Watch (7)

Dates

  • Created:
    Updated:
    Resolved: