1.0.4.6 2a: "The specified network name is no longer available" ??

[AverySimonsen]

After "downgrading" 1.0.7.8 stock firmware to kfurge's 1.0.4.6 2a (which works wonderfully btw), I have had one problem which I can't seem to get rid of. I can't access the smb shares any longer. Not from windows and not from my ubuntu box either. In samba's log I get a lot of the following:

[los@(none) ~]$ tail -f -n20 /var/log/samba.log
[2007/08/26 17:38:30, 0] lib/util.c:smb_panic(1400)
PANIC: internal error
[2007/08/26 17:39:17, 0] lib/fault.c:fault_report(36)
================================================== =============
[2007/08/26 17:39:17, 0] lib/fault.c:fault_report(37)
INTERNAL ERROR: Signal 11 in pid 10005 (3.0.2)
Please read the appendix Bugs of the Samba HOWTO collection
[2007/08/26 17:39:17, 0] lib/fault.c:fault_report(39)
================================================== =============
[2007/08/26 17:39:17, 0] lib/util.c:smb_panic(1400)
PANIC: internal error
[2007/08/26 18:05:20, 0] lib/fault.c:fault_report(36)
================================================== =============
[2007/08/26 18:05:20, 0] lib/fault.c:fault_report(37)
INTERNAL ERROR: Signal 11 in pid 10019 (3.0.2)
Please read the appendix Bugs of the Samba HOWTO collection
[2007/08/26 18:05:20, 0] lib/fault.c:fault_report(39)
================================================== =============
[2007/08/26 18:05:20, 0] lib/util.c:smb_panic(1400)
PANIC: internal error

Does anybody have any idea as to the reasons behind the apparent PANIC?

Thanks in advance
/LO

[AverySimonsen]

Does nobody have any clues on this? AFAIK, I have followed the kfurge tutorial to the letter, so I would have thought maybe others had seen the same problem of samba seasing to work.

[AverySimonsen]

Yay .. got back smb access!

Running
sudo /usr/local/samba/bin/smbpasswd -a my_user my_pass

seemed to do the trick.

/shares/MYVOLUME1/__pdc/smbpasswd is still empty, but /shares/MYVOLUME1/__pdc/passdb.tdb appears to contain the added user data.

Don't know whether this will survive a reboot, but if it doesn't it should be a simple matter of adding the above line to rc.local.