Problems with getting Samba working properly

[cgc5483]

Recently updated to the 632 build of Vix 3.0. Since this I've had trouble seeing my Vu Duo on the network. I've enabled Samba in the Network but in any of my computers I can't see the VuDuo any more. OpenWebif, FTP and telnet is working fine. In windows explorer I can type the ip address and it will let me connect. However, I connect to the VuDuo using XBMC on another computer and using SMB I can't find the VuDuo so really need this working.

My log shows the following:

[1970/01/01 01:00:14, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 1 (min password length), returning 0
[1970/01/01 01:00:14, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 2 (password history), returning 0
[1970/01/01 01:00:14, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 3 (user must logon to change password), returning 0
[1970/01/01 01:00:14, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 4 (maximum password age), returning 0
[1970/01/01 01:00:14, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 5 (minimum password age), returning 0
[1970/01/01 01:00:14, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 6 (lockout duration), returning 0
[1970/01/01 01:00:14, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 7 (reset count minutes), returning 0
[1970/01/01 01:00:14, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 8 (bad lockout attempt), returning 0
[1970/01/01 01:00:14, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 9 (disconnect time), returning 0
[1970/01/01 01:00:14, 1] lib/account_pol.c:account_policy_get(286)
account_policy_get: tdb_fetch_uint32 failed for field 10 (refuse machine password change), returning 0
[1970/01/01 01:00:16, 0] /home/vix/oe-alliance/builds/openvix/gb800solo/tmp/work/mips32el-oe-linux/samba-3.0.37-r5/samba-3.0.37/source/lib/pidfile.c:pidfile_create(112)
ERROR: smbd is already running. File /var/run/smbd.pid exists and process id 307 is running.
[2013/03/24 22:39:13, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 192.168.0.16. Error = Connection reset by peer
[2013/03/24 22:41:12, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2013/03/24 22:41:12, 0] printing/pcap.c:pcap_cache_reload(159)


Config file:
[global]
load printers = no
guest account = root
log file = /tmp/smb.log
log level = 1
security = share
server string = Dreambox %h network services
workgroup = CAOIMHZENBOOK netbios name = %h
case sensitive=yes
preserve case=yes
short preserve case=yes
socket options = TCP_NODELAY
preferred master = no
local master = no
oplocks = yes

[Root]
comment = Everything - take care!
path = /
read only = no
public = yes
guest ok = yes

[Harddisk]
comment = The harddisk
path = /media/hdd
read only = no
public = yes
guest ok = yes

Any help much appreciated.

[JoshuaGrey]

Im having a similar problem, with not being able to see my Vu+Duo in Windows 7 'Networks', i too have Samba installed, and i can see my other computers in this location.

Any help on these networking issues appreciated,

[bigbaz]

I'm having the exact same issue. Using VIX 3.0 build 6.32 on VU+Duo, samba is enabled on both boxes but they refuse to appear on my network.They ping fine and again they connect via OpenWebif, FTP and telnet. Any ideas on how to rectify this please?

[BubbleBalls]

Had a similar issue a month ago. Duo and Quad not recognised. Powered down both boxes, reset router, waited a few minutes and powered up the boxes, all fine since.


Tapatalker

[bigbaz]

Thanks BB for the reply. I'm going to give that a try, thanks.

[bigbaz]

Had a similar issue a month ago. Duo and Quad not recognised. Powered down both boxes, reset router, waited a few minutes and powered up the boxes, all fine since.


Tapatalker


Tried that, didn't work for me unfortunately. I will keep at it until I do :confused:

[twol]

Have this problem as well, systems can see the box but get error on trying to display folders... Same on both my boxes

...... Updated to 643 and now it works