It doesn't work here at all. It leaves 2 smbd instances that can't be quit or break'd and that use 100% cpu every time something tries to connect to it. I can connect locally to non-passworded shares. But remote, and passworded accounts don't work, so it's not much use. The logs are full of weird stuff like...

[2004/06/27 17:25:08, 0] smbd/sec_ctx.c:push_sec_ctx(264)
Out of memory in push_sec_ctx()
[2004/06/27 17:25:08, 0] smbd/sec_ctx.c:push_sec_ctx(264)
Out of memory in push_sec_ctx()

And nmbd can't be run using -D, so that's another problem.

So has anyone really got this version of Samba to work at all? If so, were you using Miami/MiamiDX and how did you manage it?

First read the News again.
There is an update to remove the 'weird' part.

Second MiamiDX connected to a wlan-router
connects fine to and from a winxp laptop.

amitcp:Samba/lib/smb.conf

[global]
workgroup = MYGROUP
netbios name = pegasos
server string = Tester
security = SHARE
log file = /Samba/log/log.%m
max log size = 500
load printers = No
local master = No
guest account = pcguest
guest only = Yes
guest ok = Yes

[All]
comment = All volumes in the system
path = /Test
public = yes
only guest = yes
writable = yes
printable = no
map archive = no
map hidden = no
map system = no

I'm already using the update. All it does is removes debug stuff in the output for speed. It doesn't stop fatal debug output, which is needed. So that's not the problem.

My conf file (although I've tried MANY others):

[global]
workgroup = HOUSE
netbios name = PEGASOS
server string = Pegasos / MOS
encrypt passwords = Yes
update encrypted = Yes
map to guest = Bad User
null passwords = Yes
debug level = 0
syslog = 0
log file = /samba/log/log.%m
max log size = 50
debug timestamp = No
dns proxy = No
guest account = pcguest

[MorphOS]
comment = MorphOS System
path = /sys/
valid users = kennyr
write list = kennyr

[Storage]
comment = Storage Archive
path = /storage/
valid users = kennyr
writeable = Yes

[All]
path = /
valid users = kennyr
writeable = Yes


It's not a conf file issue. All configuration files do the exact same.

Robin, do a status in cli. How many smbd instances has it launched in your system? And are you using Miami?

My full status using MiamiDX:

Test:> status
Process 1: Loaded as command: Samba:sbin/nmbd
Process 2: Loaded as command: mossys:ambient/Ambient
Process 3: Loaded as command:
Process 4: Loaded as command: dnetc
Process 5: Loaded as command: rx
Process 6: Loaded as command: IRCd:ircd
Process 7: Loaded as command: Samba:sbin/smbd
Process 10: Loaded as command: smbfs '//PC/Ordner'
Process 11: Loaded as command: RX
Process 13: Loaded as command: status

Have you perhaps tried Snoopdos ? Or removing the
valid users for at least one share ?

Played a little with your config.
It does not connect until I remove the '/' from
your server string ... hope this helps

Process 10: Loaded as command: Samba:sbin/nmbd
Process 11: Loaded as command: Samba:sbin/smbd
Process 12: Loaded as command: Samba:sbin/smbd
Process 13: Loaded as command: Samba:sbin/smbd
Process 14: Loaded as command: Samba:sbin/smbd
Process 15: Loaded as command: Samba:sbin/smbd
Process 16: Loaded as command: Samba:sbin/smbd
Process 17: Loaded as command: Samba:sbin/smbd
Process 18: Loaded as command: Samba:sbin/smbd
Process 19: Loaded as command: Samba:sbin/smbd
Process 20: Loaded as command: Samba:sbin/smbd
Process 21: Loaded as command: Samba:sbin/smbd
Process 22: Loaded as command: Samba:sbin/smbd
Process 23: Loaded as command: Samba:sbin/smbd
Process 24: Loaded as command: Samba:sbin/smbd
Process 25: Loaded as command: Samba:sbin/smbd
Process 26: Loaded as command: Samba:sbin/smbd

That's what I get, every time. And thats just a few connections. Seems smbd at least is still broken.

A kingdom for more high quality ports.