PDA

View Full Version : Windows can't access Samba server

eliufoo
5th October 2007, 03:41 PM
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
40esp
6th October 2007, 02:17 AM
[global]
workgroup = MYGROUP
netbios name = HELEN
server string = Samba Server
log file = /var/log/samba/%m.log
max log size = 50
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
browseable = Yes
read only = no





see if that works for you.

also. remember if you have a firewall up when you connect to the workgroup it will not work.



good luck. =]
scottro
6th October 2007, 03:51 AM

Hrrm, samba usually uses 137-139. One is for it to give out its NETBIOS name. Out of curiosity, with your current configuation, what happens if MS clients try to connect using IP address rather than NETBIOS name?

As was already said, check firewalls too (possibly the MS firewalls as well.)


Also, the update between 3.25x and 3.26 had several changes. Looking through FreeBSD's ports/UPDATING, I see a brief summary.

This is a cumulative update of net/samba3 from version 3.0.25a to
3.0.26a. Detailed list of all the changes can be found:

http://www.samba.org/samba/history/samba-3.0.26a.html

or in the WHATSNEW.txt file in the port's document directory.

Short summary is:
o Memory leaks in Winbind's IDMap manager.
o CVE-2007-4138 - Incorrect primary group assignment for domain
users using the RFC 2307 or sfu winbind nss info plugin.
o File sharing with Widows 9x clients.
o Winbind running out of file descriptors due to stalled child
processes.
o MS-DFS inter-operability issues.
o Offline caching of files with Windows XP/Vista clients.
o Improper cleanup of expired or invalid byte range locks on files.
o Crashes is idmap_ldap and idmap_rid.

Bug #4715 (https://bugzilla.samba.org/show_bug.cgi?id=4715) is NOT
fixed yet, although it won't core dump smbd process any more. Still,
access to the shares other than UFS is not guaranteed.

* USE SUCH SHARES AT YOUR OWN RISK *

(Note that UFS is for FreeBSD and probably irrelevant in your situation.)
eliufoo
6th October 2007, 07:20 PM
Thanks for the configuration but, it didn't work :-( and I have completely disable my firewall (both IP tables and SELinux).

I'm not sure if this will help but, apple machines can access my server. It only windows machine that has an issue.
40esp
7th October 2007, 04:54 PM
Thanks for the configuration but, it didn't work :-( and I have completely disable my firewall (both IP tables and SELinux).

I'm not sure if this will help but, apple machines can access my server. It only windows machine that has an issue.


if you have a windows firewall you need to disable that.

it blocks the port. I've been through this problem =]
eliufoo
8th October 2007, 06:18 AM
if you have a windows firewall you need to disable that.

it blocks the port. I've been through this problem =]


Which windows firewall? and how do I disable it?
marcrblevins
13th October 2007, 03:30 AM
Try:

su -
chkconfig --list | grep mb

Should see similiar to:
[root@kiriyamablevins ~]# chkconfig --list | grep mb
nmb 0:off 1:off 2:on 3:on 4:on 5:on 6:off
smb 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@kiriyamablevins ~]#

If not then:

chkconfig smb on
chkconfig nmb on
service nmb restart
service smb restart


You may also need in /etc/samba/smb.conf
wins support = yes
name resolve order = wins lmhosts hosts bcast
scottro
13th October 2007, 03:54 AM
The Windows firewall can be reached by Control Panel Security. It's on the bottom, I think. I don't have an XP box at home. so can't help too much. Or, if you go to the Windows help and put in firewall, it will probably enable you to open the configuration dialog from there.
eliufoo
17th October 2007, 03:58 PM
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.