Network (SMB) issues with latest public beta build?

**jbgeezus** · July 16th, 2010, 05:49 PM

All that is checked, except what do you mean by "make sure boxee has the smb workgroup set to this same workgroup name"? I see where you'd set the default SMB login/password for boxee, but not a place to give boxee an SMB workgroup name.

There's a log attached to the jira ticket. Do you want me to set the debug level to more detail? What would you like me to do in boxee while it's logging?

**dconti** · July 16th, 2010, 05:55 PM

Originally Posted by jbgeezus

All that is checked, except what do you mean by "make sure boxee has the smb workgroup set to this same workgroup name"? I see where you'd set the default SMB login/password for boxee, but not a place to give boxee an SMB workgroup name.

There's a log attached to the jira ticket. Do you want me to set the debug level to more detail? What would you like me to do in boxee while it's logging?

sorry, the first part was a brain fart, forgot that we don't expose that on windows.

yes, can you set the log level to debug? it should be available through the settings menu

**darcilicious** · July 16th, 2010, 05:57 PM

Originally Posted by dconti

if your shares or servers are disappearing after 10-20 minutes, i will need a log. this shouldn't happen if both machines are still online.
-dan

I sent a log previous to the public release of this version; should I resend another?

This was not an issue with the previously released public version (which I'm still running on Vista x86 and Windows 7 x86) but is very apparent with the latest release running on Windows x64.

**dconti** · July 16th, 2010, 06:00 PM

Originally Posted by darcilicious

I sent a log previous to the public release of this version; should I resend another?

This was not an issue with the previously released public version (which I'm still running on Vista x86 and Windows 7 x86) but is very apparent with the latest release running on Windows x64.

Check your PM. I'm guessing there isn't a bug for that part yet

**jbgeezus** · July 16th, 2010, 06:27 PM

Originally Posted by dconti

sorry, the first part was a brain fart, forgot that we don't expose that on windows.

yes, can you set the log level to debug? it should be available through the settings menu

Debug level log attached to JIRA. Includes:
Startup
navigating to files>>network>>(one of the bad shares)
Shutdown

**dconti** · July 16th, 2010, 06:44 PM

Originally Posted by jbgeezus

Debug level log attached to JIRA. Includes:
Startup
navigating to files>>network>>(one of the bad shares)
Shutdown

ok, this is a simple bug where we get the workgroup name mixed up with the machine name when we get a response from your machine. i'm sorry we broke this for you.

in the short term, you can map these shares as local drives and use them that way from boxee without issue, so at least you're not up a creek while we work on a fix.

thanks,
-dan

**jbgeezus** · July 16th, 2010, 07:20 PM

Thanks Dan. Glad I was able to notice it and provide the info you needed. Now I feel like a moderately useful beta tester.

**dconti** · July 17th, 2010, 10:15 PM

For the other issue mentioned in this thread (SMB mapped sources are going offline after 15-20 minutes) i've created:

http://jira.boxee.tv/browse/BOXEE-5159

Feel free to watch/comment if you are experiencing that specific issue on that bug.

Thanks,
-Dan

**darcilicious** · July 17th, 2010, 10:29 PM

Thanks Dan, for taking the time to track this puppy down!

**ruitsbarbosa** · July 18th, 2010, 08:52 AM

Hi

This issue is also happening to me on a Mac. Just two days ago everything worked perfectly, and now the access to my shared folders returns the message "Failed to retrieve data". Even when I try to add those folders as sources again it fails "Operation timed out". Have you found a fix for Mac too?

Thanks!