Thanks to those who responded to my previous post. I have tried all suggestions and found no change. A quick review: Samba 3.0.11, OpenBSD 3.6, hub connected net, no routers or firewalls involved. An Audiotron music box and a WindowsXP machine in addition to the OpenBSD box. And the issues were the same when Samba 2.x and OBSD 3.4 were installed. Windows media player on the XP box plays music files (.wav) from the Samba share fine, but the Audiotron finds the share, but shows "buffering" for about 2 minutes then doesn't play. It sees the share, finds all the music files, but can load them. But if the Audiotron is directed to find a share and play music from a share on the XP box, it plays the files fine. Can anyone give me some ideas of what would be different about the the way a dedicated network device and the XP box would communicate with the Samba box? I did note that when the Audiotron connects to the Samba box, Samba initially generates a log file smbd.192.168.x.x and then a second smbd.atron (where 192.168.x.x is it's ip address and atron is its name). Is this a clue? Socket options in smb.conf made no apparent changes in the situation. smb.conf: [global] workgroup = MACHOME server string = Parker103 hosts allow = 192.168.x.x 192.168.y.y 127.0.0.1 load printers = yes log file = /var/log/smbd.%m log level = 1 max log size = 50 security = user socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=16384 max xmit = 65536 dns proxy = no encrypt passwords = yes [music] comment = Music storage path = /music read only = no browseable = yes public = yes guest ok = yes veto oplock files = /*.wav/