Hi guys,

I would like to start by thanking all those who'll participate in solving my problem and good luck. It has been eating me up for two days now.

I was running Samba Version 3.0.23c-2 and it was working perfeclty with below configuration. I decided to yum and get the latest version Version 3.0.24*. That was the starting point of all my erros and problems. Since the upgrade, windows users have been able to access my samba server. I rollback to 3.0.23c-2, but no luck. Still facing the same issues.

See logs files below.

[global]
workgroup = MYGROUP
netbios name = HELEN
server string = Samba Server
log file = /var/log/samba/%m.log
max log size = 50
smb ports = 139
dns proxy = No
cups options = raw

[homes]
comment = Home Directories
read only = No
browseable = No

[archive]
comment = Old guds
path = /mnt/archive/Shared
valid users = elly, guest
create mask = 0222


I get the following logs when a window client tries to access the server.

Partial log out
[2007/10/05 17:22:23, 0] lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 192.168.1.48. Error Broken pipe
[2007/10/05 17:22:23, 0] lib/util_sock.c:send_smb(769)
Error writing 53 bytes to client. -1. (Broken pipe)
[2007/10/05 17:22:23, 0] smbd/server.c:exit_server_common(657)
===============================================================
[2007/10/05 17:22:23, 0] smbd/server.c:exit_server_common(659)
Abnormal server exit: reply_echo: send_smb failed.
[2007/10/05 17:22:23, 0] smbd/server.c:exit_server_common(660)
===============================================================
[2007/10/05 17:22:23, 0] lib/util.c:log_stack_trace(1721)
BACKTRACE: 9 stack frames:
#0 smbd(log_stack_trace+0x2d) [0x67725d]
#1 smbd [0x723a65]
#2 smbd [0x723c43]
#3 smbd(reply_echo+0x235) [0x4cec85]
#4 smbd [0x50aa70]
#5 smbd(smbd_process+0x7ab) [0x50bb9b]
#6 smbd(main+0xbd0) [0x7258e0]
#7 /lib/libc.so.6(__libc_start_main+0xdc) [0xd8ef2c]
#8 smbd [0x495fb1]
[2007/10/05 17:22:23, 0] smbd/server.c:exit_server_common(664)
Last message was SMBecho
[2007/10/05 17:22:23, 5] lib/util.c:show_msg(500)
[2007/10/05 17:22:23, 5] lib/util.c:show_msg(510)
size=49
smb_com=0x2b
smb_rcls=0
smb_reh=0
smb_err=0
smb_flg=24
smb_flg2=49219
smb_tid=65535
smb_pid=65279
smb_uid=0
smb_mid=65534
smt_wct=1
smb_vwv[ 0]= 1 (0x1)
smb_bcc=12
[2007/10/05 17:22:23, 10] lib/util.c:dump_data(2237)
[000] 4A 6C 4A 6D 49 68 43 6C 42 73 72 00 JlJmIhCl Bsr.
[2007/10/05 17:22:23, 0] lib/fault.c:dump_core(173)
dumping core in /var/log/samba/cores/smbd

I've tried the following:
1. Flushed my iptables
2. Disable SELinux
3. Create, restart samba deamons

Please, assist me on this.

Regards,
Elly

Can you see the share on the linux box using either smbclient or smbtree?

Yes, I can see the share. Even Mac machine can access the samba server. I'm only getting this problem with windows machine.

I too faced the same problem. It seems, if we restart the Windows machine,
then it's able to access the Samba server.

Dear

Do u made any backup of smb.conf file before updating the package ?

Thanking You
Subrun

thanks for all the help guys. after restarting the machine, smb just came back to service.

I'm going through logs to check what has changed to make it work again. If i discover the problem, will post it.

Thanks again.