Hi all,
I decided to try Windows out to serve my files to my secondary XBMC instance using a simple file share, with "everyone" having permissions set to Full Control.
The way I added this as a source was to go through the Add Source interface and select "SMB". My problem is that intermittently my server isn't listed, has anyone any ideas as to why a Windows server would sometimes not be present in a SMB search (Which I believe is a Windows protocol!?)
Havent seen this behavior before, did you try to manualy add the source, aka not through discovery? might be better to hard code it if your server has problem showing its shares intermittently.
I've tried that straight after I can't see it in the discovery and XBMC says it can't find the network resource, but would I like to add it anyway. At which point I say no because I figure I can't see it
I don't think my server has problems showing it's shares though, because my Windows 7 computer can see the shares constantly.
Enable debug log and see if you can see something upload log to pastebin and post here.
when enabled you have to fiddle around until you get this error.
Hi, my pastebin of my log from /var/log/messages is here:
http://sprunge.us/PTQN I can't see any errors.
the probably more useful one from the XBMC Debugging is here :
http://sprunge.us/jEOi
I can't make any sense of it , but I think the interesting bit is here?
Code:
18:03:46 T:139999659931392 DEBUG: OpenDir - Using authentication url smb://WORKGROUP
18:04:02 T:140000510138176 DEBUG: CheckDisplayEvents: Received RandR event 121
18:04:02 T:140000510138176 DEBUG: CheckDisplayEvents - notify display reset event
18:04:02 T:140000510138176 NOTICE: CWinSystemX11::RefreshWindow - external or initial xrandr event
18:04:02 T:140000510138176 ERROR: CWinSystemX11::RefreshWindow - could not find resolution
18:04:16 T:140000241432320 DEBUG: Thread Jobworker 140000241432320 terminating (autodelete)
18:04:17 T:139999659931392 DEBUG: Thread Jobworker 139999659931392 terminating (autodelete)
18:05:20 T:140000510138176 NOTICE: Samba is idle. Closing the remaining connections
I can add more detail to my problem.
When the network share is added and I browse the list of videos as "Files", it works flawlessly.
The only problems I get seem to be
1) finding the SMB share in the first place from the SMB menu
2) adding the source as what it actually is e.g. movies or TV Shows, it is really flakey.
I am 90% sure this is not a problem with my particular network, but instead the XBMC netcode perhaps - like I mentioned, it works fine when I browse with Files.
Maybe you can use the IP address of the Windows server instead of relying on WORKGROUP when accessing via Samba? You should be able to go into your router settings and reserve an IP address for your server so that its location remains static.
the server has a static IP address already, but how do you mean I can access it without recursing through the Workgroup?