+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Archive (https://forum.kodi.tv/forumdisplay.php?fid=92)
+--- Forum: First-generation XBOX support (https://forum.kodi.tv/forumdisplay.php?fid=158)
+--- Thread: LanDrive/LanDrive (3.5" HDD NAS enclosure) SMB/SAMBA problems (/showthread.php?tid=18282)
part 3 - brutisb - 2006-10-07
15:44:52 M: 39329792 INFO: smb: [000] 00 44 20 07 01 00 00 00 00 6F 00 74 00 68 00 65 .D ..... .o.t.h.e
15:44:52 M: 39329792 INFO: smb: [010] 00 72 00 00 00 .r...
15:44:52 M: 39329792 INFO: smb: write_socket(-803176440,90)
15:44:52 M: 39329792 INFO: smb: write_socket(-803176440,90) wrote 90
15:44:52 M: 39329792 INFO: smb: got smb length of 123
15:44:52 M: 39329792 INFO: smb: size=123
15:44:52 M: 39329792 INFO: smb: smb_com=0x32
15:44:52 M: 39329792 INFO: smb: smb_rcls=0
15:44:52 M: 39329792 INFO: smb: smb_reh=0
15:44:52 M: 39329792 INFO: smb: smb_err=0
15:44:52 M: 39329792 INFO: smb: smb_flg=136
15:44:52 M: 39329792 INFO: smb: smb_flg2=34817
15:44:52 M: 39329792 INFO: smb: smb_tid=1
15:44:52 M: 39329792 INFO: smb: smb_pid=1
15:44:52 M: 39329792 INFO: smb: smb_uid=0
15:44:52 M: 39329792 INFO: smb: smb_mid=14
15:44:52 M: 39329792 INFO: smb: smt_wct=10
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 0]= 2 (0x2)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 1]= 66 (0x42)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 2]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 3]= 2 (0x2)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 4]= 55 (0x37)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 5]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 6]= 66 (0x42)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 7]= 57 (0x39)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 8]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 9]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_bcc=68
15:44:52 M: 39329792 INFO: smb: [000] 00 00 00 7D C4 42 BA E9 C6 01 00 7D C4 42 BA E9 ...}.B.. ...}.B..
15:44:52 M: 39329792 INFO: smb: [010] C6 01 00 7D C4 42 BA E9 C6 01 00 7D C4 42 BA E9 ...}.B.. ...}.B..
15:44:52 M: 39329792 INFO: smb: [020] C6 01 10 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
15:44:52 M: 39329792 INFO: smb: [030] 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 ........ ........
15:44:52 M: 39329792 INFO: smb: [040] 00 00 00 00 ....
15:44:52 M: 39329792 INFO: smb: size=123
15:44:52 M: 39329792 INFO: smb: smb_com=0x32
15:44:52 M: 39329792 INFO: smb: smb_rcls=0
15:44:52 M: 39329792 INFO: smb: smb_reh=0
15:44:52 M: 39329792 INFO: smb: smb_err=0
15:44:52 M: 39329792 INFO: smb: smb_flg=136
15:44:52 M: 39329792 INFO: smb: smb_flg2=34817
15:44:52 M: 39329792 INFO: smb: smb_tid=1
15:44:52 M: 39329792 INFO: smb: smb_pid=1
15:44:52 M: 39329792 INFO: smb: smb_uid=0
15:44:52 M: 39329792 INFO: smb: smb_mid=14
15:44:52 M: 39329792 INFO: smb: smt_wct=10
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 0]= 2 (0x2)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 1]= 66 (0x42)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 2]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 3]= 2 (0x2)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 4]= 55 (0x37)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 5]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 6]= 66 (0x42)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 7]= 57 (0x39)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 8]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 9]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_bcc=68
15:44:52 M: 39329792 INFO: smb: [000] 00 00 00 7D C4 42 BA E9 C6 01 00 7D C4 42 BA E9 ...}.B.. ...}.B..
15:44:52 M: 39329792 INFO: smb: [010] C6 01 00 7D C4 42 BA E9 C6 01 00 7D C4 42 BA E9 ...}.B.. ...}.B..
15:44:52 M: 39329792 INFO: smb: [020] C6 01 10 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
15:44:52 M: 39329792 INFO: smb: [030] 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 ........ ........
15:44:52 M: 39329792 INFO: smb: [040] 00 00 00 00 ....
15:44:52 M: 39329792 INFO: smb: smbc_stat(smb://192.168.0.10/Net-250G_01/The%20Worlds%20Fastest%20Indian)
15:44:52 M: 39329792 INFO: smb: smbc_getatr: sending qpathinfo
15:44:52 M: 39329792 INFO: smb: size=126
15:44:52 M: 39329792 INFO: smb: smb_com=0x32
15:44:52 M: 39329792 INFO: smb: smb_rcls=0
15:44:52 M: 39329792 INFO: smb: smb_reh=0
15:44:52 M: 39329792 INFO: smb: smb_err=0
15:44:52 M: 39329792 INFO: smb: smb_flg=8
15:44:52 M: 39329792 INFO: smb: smb_flg2=34817
15:44:52 M: 39329792 INFO: smb: smb_tid=1
15:44:52 M: 39329792 INFO: smb: smb_pid=1
15:44:52 M: 39329792 INFO: smb: smb_uid=0
15:44:52 M: 39329792 INFO: smb: smb_mid=15
15:44:52 M: 39329792 INFO: smb: smt_wct=15
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 0]= 58 (0x3A)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 1]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 2]= 10 (0xA)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 3]= 2920 (0xB68)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 4]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 5]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 6]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 7]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 8]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 9]= 58 (0x3A)
15:44:52 M: 39329792 INFO: smb: smb_vwv[10]= 68 (0x44)
15:44:52 M: 39329792 INFO: smb: smb_vwv[11]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[12]= 126 (0x7E)
15:44:52 M: 39329792 INFO: smb: smb_vwv[13]= 1 (0x1)
15:44:52 M: 39329792 INFO: smb: smb_vwv[14]= 5 (0x5)
15:44:52 M: 39329792 INFO: smb: smb_bcc=61
15:44:52 M: 39329792 INFO: smb: [000] 00 44 20 07 01 00 00 00 00 54 00 68 00 65 00 20 .D ..... .T.h.e.
15:44:52 M: 39329792 INFO: smb: [010] 00 57 00 6F 00 72 00 6C 00 64 00 73 00 20 00 46 .W.o.r.l .d.s. .F
15:44:52 M: 39329792 INFO: smb: [020] 00 61 00 73 00 74 00 65 00 73 00 74 00 20 00 49 .a.s.t.e .s.t. .I
15:44:52 M: 39329792 INFO: smb: [030] 00 6E 00 64 00 69 00 61 00 6E 00 00 00 .n.d.i.a .n...
15:44:52 M: 39329792 INFO: smb: write_socket(-803176440,130)
15:44:52 M: 39329792 INFO: smb: write_socket(-803176440,130) wrote 130
15:44:52 M: 39329792 INFO: smb: got smb length of 123
15:44:52 M: 39329792 INFO: smb: size=123
15:44:52 M: 39329792 INFO: smb: smb_com=0x32
15:44:52 M: 39329792 INFO: smb: smb_rcls=0
15:44:52 M: 39329792 INFO: smb: smb_reh=0
15:44:52 M: 39329792 INFO: smb: smb_err=0
15:44:52 M: 39329792 INFO: smb: smb_flg=136
15:44:52 M: 39329792 INFO: smb: smb_flg2=34817
15:44:52 M: 39329792 INFO: smb: smb_tid=1
15:44:52 M: 39329792 INFO: smb: smb_pid=1
15:44:52 M: 39329792 INFO: smb: smb_uid=0
15:44:52 M: 39329792 INFO: smb: smb_mid=15
15:44:52 M: 39329792 INFO: smb: smt_wct=10
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 0]= 2 (0x2)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 1]= 66 (0x42)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 2]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 3]= 2 (0x2)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 4]= 55 (0x37)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 5]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 6]= 66 (0x42)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 7]= 57 (0x39)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 8]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 9]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_bcc=68
15:44:52 M: 39329792 INFO: smb: [000] 00 00 00 E2 B1 95 E5 E6 C6 01 00 E2 B1 95 E5 E6 ........ ........
15:44:52 M: 39329792 INFO: smb: [010] C6 01 00 E2 B1 95 E5 E6 C6 01 00 E2 B1 95 E5 E6 ........ ........
15:44:52 M: 39329792 INFO: smb: [020] C6 01 10 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
15:44:52 M: 39329792 INFO: smb: [030] 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 ........ ........
15:44:52 M: 39329792 INFO: smb: [040] 00 00 00 00 ....
15:44:52 M: 39329792 INFO: smb: size=123
15:44:52 M: 39329792 INFO: smb: smb_com=0x32
15:44:52 M: 39329792 INFO: smb: smb_rcls=0
15:44:52 M: 39329792 INFO: smb: smb_reh=0
15:44:52 M: 39329792 INFO: smb: smb_err=0
15:44:52 M: 39329792 INFO: smb: smb_flg=136
15:44:52 M: 39329792 INFO: smb: smb_flg2=34817
15:44:52 M: 39329792 INFO: smb: smb_tid=1
15:44:52 M: 39329792 INFO: smb: smb_pid=1
15:44:52 M: 39329792 INFO: smb: smb_uid=0
15:44:52 M: 39329792 INFO: smb: smb_mid=15
15:44:52 M: 39329792 INFO: smb: smt_wct=10
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 0]= 2 (0x2)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 1]= 66 (0x42)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 2]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 3]= 2 (0x2)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 4]= 55 (0x37)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 5]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 6]= 66 (0x42)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 7]= 57 (0x39)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 8]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_vwv[ 9]= 0 (0x0)
15:44:52 M: 39329792 INFO: smb: smb_bcc=68
15:44:52 M: 39329792 INFO: smb: [000] 00 00 00 E2 B1 95 E5 E6 C6 01 00 E2 B1 95 E5 E6 ........ ........
15:44:52 M: 39329792 INFO: smb: [010] C6 01 00 E2 B1 95 E5 E6 C6 01 00 E2 B1 95 E5 E6 ........ ........
15:44:52 M: 39329792 INFO: smb: [020] C6 01 10 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
15:44:52 M: 39329792 INFO: smb: [030] 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 ........ ........
15:44:52 M: 39329792 INFO: smb: [040] 00 00 00 00
- Gamester17 - 2006-10-07
I think the NAS box called "LanDisk" and the one called "LanDrive" use the same core hardware and same firmware and thus have the same problems, so checkout these other topic threads with LanDisk and LanDrive SMB issues (which I'm pretty sure has to do with folder and file permissions):
http://forum.xbmc.org/showthread.php?tid=18282&highlight=landrive
http://forum.xbmc.org/showthread.php?tid=21317&highlight=landrive
http://forum.xbmc.org/showthread.php?tid=22444&highlight=landrive
- brutisb - 2006-10-08
Thanks for the update. I've been reading the various articles and there seems to be a number of different problems with the various flavours of NAS boxes.
Luckily I have this build [XBMC.2006-01-08-CLEAN] that works 100% correctly with my LanDisk, so I can test other builds against it.
Quote:I think the NAS box called "LanDisk" and the one called "LanDrive" use the same core hardware and same firmware and thus have the same problems
Comparing the User Manuals of my Vgear LanDisk and the LanDrive it would appear that they are from the same OEM, except mine doesn't have the USB connector.
Small delay getting the Ethereal captures as I only have switches on my network, so I'll have to wait and get a hub from work.
- plugh - 2006-10-08
brutisb Wrote:Hi there,As I recall, the 3-25-06 t3ch build 'worked', the next build didn't. That was when the smbclient core in xbmc was upgraded.
Still hoping someone out there can help.....
I have been able to confirm that builds using CVS up to 07-Jan-06 are working ok and builds using CVS 09-Aug-06 and later are not. Somewhere in between these builds something changed with SMB.
I previously supplied ethereal captures and logs to elupus comparing the 3-25 build to a later one. Unfortunately, the later xbmc build simply hung, precluding useful analysis. (Hence the idea to see what that version smbclient code did on a linux system talking to the nas box.)
Personally, I gave up and switched to a differant solution (Linksys wrtsl54gs) which also required debugging, both on the xbmc side (ethereal captures, and a samba fix that went into the 6-25 t3ch build) and on the linksys side (fat32 filesystem issues in the embedded linux core, with a patch/fix that linksys has released as beta firmware). Sheesh!
At least with the linksys/embedded-linux solution, I've got source code and can (and have) track down problems and build my own firmware image. The lan drives use proprietary code with questionable compatibilty. Hell, it took four firmware releases by the manufacturer before it worked reasonably reliably with windows (nothing like being on the bleeding edge), and then only for W2K/WXP.
Anyway, good luck, and if you look at the changelogs just past 3-25, you'll see the smbclient core update.
- plugh - 2006-10-08
I just checked - I still have a copy of the 3-28 build (not 3-25 as I stated above) if you can't find it anywhere else; and it looks like I deleted the captures from my previous go around...
From the changelog
07-04-2006 updated: libsmb updated to 3.0.22 with enabled libiconv, supports switching dos codepage gui
- brutisb - 2006-10-08
Hi plugh and thanks for the extra info.
I don't know how I missed that cvs when I searched the changelog for smb related changes, would have saved me a lot of time checking different builds
I found torrents of the builds just before the smb update
29.Mar.2006.XBMC.XBOX.MediaCenter.1.1.0.GasGiver
01.Apr.2006.XBMC.XBOX.MediaCenter.1.1.0.GasGiver
and I will try and test them, however there doesn't look to be any seeders out there at the moment
I haven't had any problems with the LanDisk and it satisfied my requirement of having a builtin HDD. Before I purchased it, I tried a couple of other similar units and found various problems, although I must admit I didn't try any wireless units as I have never really liked wireless products and only use them now if there is absolutley no way to hard wire it.
Currently the only problem I have with the LanDisk is with XBMC - so I should consider myself lucky I suppose.
I have a spare computer, so I may well install Lunix and see what happens.
- plugh - 2006-10-08
I guess I shouldn't deride all of the units, there appear to be some types that "work". But the ones based upon the 80186 processor core, sold under various brand names (Tritton, Argosy, Bytecc, Coolmax...), sharing the same basic firmware (to the point that people have experimented with flashing firmware from 'A' on 'B's products) and motherboard (my hd363n has an unpopulated spot where the usb connector would go), have been problematic.
A long and interesting thread here...
http://www.howtofixcomputers.com/bb/ftopic76630-0-asc-0.html
- x_cal1bur - 2006-10-08
I have a Landisk as well and having the same problem for quite some time.
From my limited knowledge on this, I reckon the problem is with the support of multiple codepage of LANDISK. On the other hand, XBMC samba can only support single codepage at a time. XBMC use to support multiple code page til they include the dos codepage gui for samba.
This is just my own deduction and may not be correct.
- elupus - 2006-10-08
very wrong.. we did not support any other codepage than ansi. wich was why many other lan drives didn't work. our support now should be on par with what we had before.. ie directory listing aslong as there isn't too many files/folders in that folder.
codepage has nada todo with this issue. it won't be resolved untill somebody with a landrive and atleast some linux/unix knowledge steps up and helps us out.
- scales82 - 2006-10-12
well i just found something interesting.
i have put the latest basic45 firmware onto my landrive(lanserver,landrive whatever you want)
The previous version (41) had perfect functionality within xbmc in respects to browsing folders etc. i even had a nice music library list built up.
Now, with the latest version it doesnt work..... we all knew that already though.
But what i discovered is if i try to play music thats already listed in my library, the songs play fine!!
so that leads me to think it must have something to do with the way the SMB client within xbmc lists the files within folders.
oh i also discovered that for some reason my landrive does not come up in the workgroup when my computer is off and gives a "workgroup unavailable" message. But that may be my configs problem.
- kabutop - 2006-10-12
Hi all,
I've got the same problem with my nas MAXINPOWER BEMIP35ULI.
I've got a directory A with some files. I can access and browse this directory.
When I add a file B with FTP or SAMBA or with the USB connexion, i can't enter in the directory (Acces Violation in xbmc.log).
If I delete the file B, it's ok again.
If I upload again the file B, no problem...
I try different firmware on my SAN : BASIC41,43 and the latest 45. Same problem.
If I try to access the directory with my linux box : no problem (ubuntu edgy with Samba 3.0.22).
No problem with my MacOSX and my Windows on this directory.
I can upload a tcpdump if you tell me in few word what you need.
Thanks for your great work !
Bye... and sorry for my bad english
- faital - 2006-10-12
do not comminicate with this spammer /admin
- elupus - 2006-10-12
kabutop:
finally someone that might help us nail this trouble
, could you upgrade your ubunto to the 23 release (preferably the b release, but I don't think anything changed in the c release). the do the same directory listing, i'm hoping you'll get a sigfault when doing so. if not, the damn issue will be even harder to nail.
- kabutop - 2006-10-12
OK. I do this tomorrow and I tell you !
Bye
- kabutop - 2006-10-13
elupus Wrote:kabutop:Hi,
finally someone that might help us nail this trouble
The news :
I installed samba-3.0.23b :
- tar xvzf samba-3.0.23b.tar.gz
- cd samba-3.0.23b/source
- ./configure --prefix=/usr --with-smbmount --with-syslog
- make install-everything
So now :
# smbclient --version
Version 3.0.23b
and :
# smbmount
Version 3.0.23b
and :
# strings /usr/lib/libsmbclient.so|grep 3.0.23
3.0.23b
So I tested :
mount //192.168.1.200/PUBLIC /mnt/coin/
No problem if i go in the "bad" directory.
and
smbclient //192.168.1.200/PUBLIC
No problem again
Which method xbmc use to mount SMB share ?
Thanks for your help !
+