+- Forum (http://forum.xbian.org)
+-- Forum: Software (/forum-6.html)
+--- Forum: Configuration (/forum-17.html)
+--- Thread: [SOLVED] SMB instant timeout in A4 (worked in A3) (/thread-256.html)
SMB instant timeout in A4 (worked in A3) - ilgrank - 13th Jan, 2013 06:52 PM
Hi, and firtst of all let me thank everyone in the forum.. I've been following since some week but registered just now
I've had just one small glitch upgrading from Xbian Alpha 3 to A4. (I did a complete re-install, erasing the SD and putting in it the new image).. now SMB shares aren't working anymore, and I get an instant timeout when trying to access them.
The timeout is so immediate I don't think it is a timeout at all, it seems something else may be wrong. I have the latest, fixed, A4 image.. any idea?
Thanks!
RE: SMB instant timeout in A4 (worked in A3) - namtih - 13th Jan, 2013 07:36 PM
Any helpful message in the xbmc.log, when you get this timeout?
RE: SMB instant timeout in A4 (worked in A3) - ilgrank - 13th Jan, 2013 08:41 PM
Hi, thanks for the quick reply
here's the tail of the xbmc log:
Terminal
05:33:12 T:3042373632 WARNING: CLinuxInputDevice::RelEvent: Unknown rel event code: 8
05:33:31 T:2882602048 ERROR: SMBDirectory->GetDirectory: Unable to open directory : 'smb://WORKGROUP'
unix_err:'6e' error : 'Connection timed out'
05:33:34 T:3042373632 ERROR: GetDirectory - Error getting smb://WORKGROUP
05:33:35 T:3042373632 ERROR: CGUIDialogFileBrowser::GetDirectory(smb://WORKGROUP) failed
05:35:09 T:3042373632 NOTICE: Samba is idle. Closing the remaining connections
as you can see everything happens in 2 seconds (while in A3 browsing the SMB share took more than that)
the first row of the log is for reference only of course, and my other linux machines do browse the SMB shares happily.. (using the same user)..
RE: SMB instant timeout in A4 (worked in A3) - ilgrank - 14th Jan, 2013 03:52 AM
It seems windows doesn't like the client switching (going from A3 to A4) and presenting itself with the same credentials.
I've been able to replicate the issue, and a reboot of the Windows Server solves the problem... weird, but at this point it seems more like a Windows issue..