Re: Problem with Samba on Squeeze [SOLVED]
> From: Roger Morgan > To: Camaleón ; debian-user@lists.debian.org > Sent: Mon, May 2, 2011 11:32:16 AM > Subject: Re: Problem with Samba on Squeeze > > > From: Camaleón > > > To: debian-user@lists.debian.org > > Sent: Sun, May 1, 2011 8:15:10 PM > > Subject: Re: Problem with Samba on Squeeze > > > > On Sun, 01 May 2011 10:58:01 -0700, Roger Morgan wrote: > > > > >> From: Camaleón > > > > > >> It looks something related to authentication. > > >> > > >> Is there anything interesting at samba logs? I know samba logs are > > >> pretty hard to understand :-) but maybe there is something in there > > >> that give you any clue. > > >> > > > Here are the logs for the relevant time. > > > > (...) I eventually solved this as follows. 1. Uninstall samba completely including configs: the following packages: samba samba-doc samba-common samba-common-bin libwbclient0 swat smbclient libsmbclient webmin and their dependencies. 2. Check samba directories /var/lib/samba and /etc/samba don't exist any more. 3. Reboot 4. Install packages: samba samba-common samba-common-bin libwbclient0 smbclient 5. List users with pdbedit. (the installation, trying to be smart, had added 4 users). Tried: smbclient -L lyra and responding with my password, still didn't work, but produced an error message instead of timing out. I googled for it and found somebody else had had the same problem and fixed it by deleting the users which installation had added with pdbedit, and re-creating them with smbpasswd -a. 6. Delete the users found in step 5 with pdbedit, and add the users needed with smbpasswd. Then everything works. This is an old installation of Samba, going back to lenny, and I conclude that the upgrades didn't do exactly what they should have. The clean install should not be different from an upgraded install but it clearly was. Thanks to Camaleón for helping with this. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/174583.98101...@web65515.mail.ac4.yahoo.com
Re: Problem with Samba on Squeeze
On Tue, 03 May 2011 16:45:57 -0400, Tom H wrote: > On Tue, May 3, 2011 at 9:41 AM, Camaleón wrote: >> El 2011-05-03 a las 02:50 -0700, Roger Morgan escribió: > > >> (resending to the list, no sensible data on it) > > I think that you mean "sensitive." :) (...) Ooops! I did it again :-P Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.05.04.11.57...@gmail.com
Re: Problem with Samba on Squeeze
On Tue, May 3, 2011 at 9:41 AM, Camaleón wrote: > El 2011-05-03 a las 02:50 -0700, Roger Morgan escribió: > (resending to the list, no sensible data on it) I think that you mean "sensitive." :) >> > From: Camaleón >> > Make a quick test. Try "smbclient -L servername" but when asked for the >> > user's password just press [enter] to log anonymously and check if you >> > get any output differenet than the first one. >> > >> Yes, it is different: >> >> ~$ smbclient -L lyra >> Enter roger's password: >> Anonymous login successful > > Wow. It logs just fine. So in the end there must be something with > authentication which does not like samba but dunno "what" nor "why" :-? > > Sorry, I'm out of ideas :-( and the full logs you sent was not showing > any specific error or warning on the authentication side. Let's see if > someone here can suggest another thing to test... > >> Domain=[GALAXY] OS=[Unix] Server=[Samba 3.5.6] >> >> Sharename Type Comment >> - --- >> print$ Disk Printer Drivers >> Samsung1510 Printer lyra smbshare >> common Disk lyra smbshare >> IPC$ IPC IPC Service (lyra server) >> Samsung_ML-1510_700 Printer Samsung ML-1510_700 >> Anonymous login successful >> Domain=[GALAXY] OS=[Unix] Server=[Samba 3.5.6] >> Server Comment >> - --- >> LYRA lyra server >> Workgroup Master >> - --- >> GALAXY LYRA 0. (Unrelated to your problem) If this is your only samba server, you might want to have preferred master = yes local master = yes domain master = yes os level = 65 in smb.conf to prevent master browser election 1. Does running "smblient -L 127.0.1.1" make a difference? 2. Does restricting the smb ports to either 139 or 445 with "smb ports = ..."in smb.conf make a difference? 3. Does "testparm -s" flag any problems? 4. Does "pdbedit -Lv" out output the users that you want to have in samba? Are the samba users' passwords the same in the system and for samba? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktinioco0seeqd7f3thi6akwd3_v...@mail.gmail.com
Re: Problem with Samba on Squeeze
On Sun, May 1, 2011 at 6:51 AM, Roger Morgan wrote:
> Samba is running but I can't connect to it, and when I do the following
> test
> (from the Samba server):
> smbclient -L servername
>
> the response (after entering correct password) is:
> cut here---
> Receiving SMB: Server stopped responding
> session setup failed: Call timed out: server did not respond after 2
> milliseconds
> ---end of response--
>
> the Samba programs are running, here's the relevant part of the output of
> ps -ef
> | grep mb
> root 1969 1 0 18:13 ?00:00:00 /usr/sbin/smbd -D
> root 1983 1969 0 18:13 ?00:00:00 /usr/sbin/smbd -D
> root 2308 1 0 18:13 ?00:00:00 /usr/sbin/nmbd -D
>
> And here's my smb.conf file:
> #=== Global Settings ===
>
> [global]
>log file = /var/log/samba/log.%m
>load printers = yes
>guest account = leong
>
add:
map to guest = Bad User
printer = ML-1510_700
>passwd chat = *Enter\snew\s*\spassword:* %n\n
> *Retype\snew\s*\spassword:*
> %n\n *password\supdated\ssuccessfully* .
>obey pam restrictions = yes
>write list = leong
>
Delete write list
encrypt passwords = true
>public = yes
>
Delete public
>passwd program = /usr/bin/passwd %u
>passdb backend = tdbsam
>dns proxy = no
>writeable = yes
>
Delete writeable
>server string = %h server
>path = /var/common
>
Delete path
>unix password sync = yes
>workgroup = galaxy
>comment = lyra smbshare
> #valid users = leong (no valid users list means anyone can login)
>syslog = 0
>panic action = /usr/share/samba/panic-action %d
>max log size = 1000
>directory mode = 766
>
Delete directory mode
>pam password change = yes
>
> ## Browsing/Identification ###
>
> # Change this to the workgroup/NT-domain name your Samba server will part
> of
>
> # server string is the equivalent of the NT Description field
>
> # Windows Internet Name Serving Support Section:
> # WINS Support - Tells the NMBD component of Samba to enable its WINS
> Server
> # wins support = no
>
> # WINS Server - Tells the NMBD components of Samba to be a WINS Client
> # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
> ; wins server = w.x.y.z
>
> # This will prevent nmbd to search for NetBIOS names through DNS.
>
> # What naming service and in what order should we use to resolve host names
> # to IP addresses
> ; name resolve order = lmhosts host wins bcast
>
> Networking
>
> # The specific set of interfaces / networks to bind to
> # This can be either the interface name or an IP address/netmask;
> # interface names are normally preferred
> ; interfaces = 127.0.0.0/8 eth0
>
> # Only bind to the named interfaces and/or networks; you must use the
> # 'interfaces' option above to use this.
> # It is recommended that you enable this feature if your Samba machine is
> # not protected by a firewall or is a firewall itself. However, this
> # option cannot handle dynamic or non-broadcast interfaces correctly.
> ; bind interfaces only = yes
>
>
>
> Debugging/Accounting
>
> # This tells Samba to use a separate log file for each machine
> # that connects
>
> # Cap the size of the individual log files (in KiB).
>
> # If you want Samba to only log through syslog then set the following
> # parameter to 'yes'.
> # syslog only = no
>
> # We want Samba to log a minimum amount of information to syslog.
> Everything
> # should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
> # through syslog you should set the following parameter to something
> higher.
>
> # Do something sensible when Samba crashes: mail the admin a backtrace
>
>
> ### Authentication ###
>
> # "security = user" is always a good idea. This will require a Unix account
> # in this server for every user accessing the server. See
> # /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
> # in the samba-doc package for details.
> security = user
>
> # You may wish to use password encryption. See the section on
> # 'encrypt passwords' in the smb.conf(5) manpage before enabling.
>
> # If you are using encrypted passwords, Samba will need to know what
> # password database type you are using.
>
>
> # This boolean parameter controls whether Samba attempts to sync the Unix
> # password with the SMB password when the encrypted SMB password in the
> # passdb is changed.
>
> # For Unix password sync to work on a Debian GNU/Linux system, the
> following
> # parameters must be set (thanks to Ian Kahan <<
> ka...@informatik.tu-muenchen.de>
> for
> # sending the correct chat script for the passwd program in Debian Sarge).
>
> # This boolean controls whether PAM will be used for password changes
> # when requested by an SMB client instead of the program listed in
> # 'passwd program'. The default is 'no'.
>
> ## Domains ###
>
> # Is this machine able to authent
Re: Problem with Samba on Squeeze
El 2011-05-03 a las 02:50 -0700, Roger Morgan escribió: (resending to the list, no sensible data on it) > > From: Camaleón > > > > > Make a quick test. Try "smbclient -L servername" but when asked for the > > user's password just press [enter] to log anonymously and check if you > > get any output differenet than the first one. > > > Yes, it is different: > > ~$ smbclient -L lyra > Enter roger's password: > Anonymous login successful Wow. It logs just fine. So in the end there must be something with authentication which does not like samba but dunno "what" nor "why" :-? Sorry, I'm out of ideas :-( and the full logs you sent was not showing any specific error or warning on the authentication side. Let's see if someone here can suggest another thing to test... > Domain=[GALAXY] OS=[Unix] Server=[Samba 3.5.6] > > Sharename Type Comment > - --- > print$ Disk Printer Drivers > Samsung1510 Printer lyra smbshare > common Disk lyra smbshare > IPC$IPC IPC Service (lyra server) > Samsung_ML-1510_700 Printer Samsung ML-1510_700 > Anonymous login successful > Domain=[GALAXY] OS=[Unix] Server=[Samba 3.5.6] > > Server Comment > ---- > LYRA lyra server > > WorkgroupMaster > ---- > GALAXY LYRA Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110503134138.ga5...@stt008.linux.site
Re: Problem with Samba on Squeeze
On Mon, 02 May 2011 02:32:16 -0700, Roger Morgan wrote:
>> From: Camaleón
>> Sadly those are pretty generic errors and don't tell much about the
>> cause of the failure. Try by increasing samba log level¹ ("log level =
>> 3"), restart samba daemons, run smbclient again and review again the
>> logs.
(...)
> After setting log level = 3, rebooting, and running smbclient again,
> there are 4 logfiles. The extra 2 are log.lyra and log.__fff_127.0.0.1
> All four are copied below
> start log.nmbd-
(...)
I think the relevant ones here are the smbd logs. Anyway, I didn't see
any noticeable error or nmbd, it seems to be operating fine :-?
> -start log.smbd--
(...)
I keep the messages I think can be relevant (or at least the ones that
are "human readable").
> [2011/05/02 11:03:54.662286, 3] lib/privileges.c:63(get_privileges)
> get_privileges: No privileges assigned to SID
> [S-1-5-21-38502757-452903869-1500568620-1000]
> [2011/05/02 11:03:54.662339, 3] lib/privileges.c:63(get_privileges)
> get_privileges: No privileges assigned to SID [S-1-5-2]
> [2011/05/02 11:03:54.662374, 3] lib/privileges.c:63(get_privileges)
> get_privileges: No privileges assigned to SID [S-1-5-11]
(...)
> [2011/05/02 11:03:54.731748, 3] auth/token_util.c:467
> (create_local_nt_token) Failed to fetch domain sid for GALAXY
This bunch of messages seems to be all related but I can't understand
their meaning nor know if they can lead to the error you are seeing :-?
> printing/printing.c:1412(start_background_queue)
> start_background_queue: Starting background LPQ thread
> [2011/05/02 11:03:54.744550, 3]
> ../lib/util/util_net.c:68(interpret_string_addr_internal)
> interpret_string_addr_internal: getaddrinfo failed for name 0.0.0.0
> [Address family for hostname not supported]
> [2011/05/02 11:03:54.744630, 3]
> ../lib/util/util_net.c:68(interpret_string_addr_internal)
> interpret_string_addr_internal: getaddrinfo failed for name 0.0.0.0
> [Address family for hostname not supported]
> [2011/05/02 11:03:54.745308, 2] smbd/server.c:721(smbd_parent_loop)
> waiting for connections
(...)
These ones seem coming from the printing spooler.
> start log.lyra -
> [2011/05/02 11:05:52.748104, 3] auth/auth.c:216(check_ntlm_password)
> check_ntlm_password: Checking password for unmapped user
> [GALAXY]\[roger]@[LYRA] with the new password interface
> [2011/05/02 11:05:52.748160, 3] auth/auth.c:219(check_ntlm_password)
> check_ntlm_password: mapped user is: [LYRA]\[roger]@[LYRA]
This record seems to indicate that the user has been logged successfully.
> start log.___127.0.0.1
(...)
> [2011/05/02 11:05:52.696039, 3] smbd/negprot.c:691(reply_negprot)
> Selected protocol NT LANMAN 1.0
Here it selects the protocol...
> [2011/05/02 11:05:52.747966, 3]
> smbd/sesssetup.c:1232(reply_sesssetup_and_X_spnego)
> NativeOS=[Unix] NativeLanMan=[Samba] PrimaryDomain=[]
> [2011/05/02 11:05:52.748014, 3]
> libsmb/ntlmssp.c:747(ntlmssp_server_auth)
> Got user=[roger] domain=[GALAXY] workstation=[LYRA] len1=24 len2=24
> end log.___127.0.0.1
And the user is logged (just the same we see in the "log.lyra" file
record of above).
> I hope you can see something useful here! Roger
I wish I can understand samba logs (they look like gibberish to me) but
at least we can see the user gets authenticated okay so the problem with
the first of the messages you sent can have another source and not an
auth issue per se but a samba timeout problem... :-?
Make a quick test. Try "smbclient -L servername" but when asked for the
user's password just press [enter] to log anonymously and check if you
get any output differenet than the first one.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.05.02.13.20...@gmail.com
Re: Problem with Samba on Squeeze
> From: Camaleón
> To: debian-user@lists.debian.org
> Sent: Sun, May 1, 2011 8:15:10 PM
> Subject: Re: Problem with Samba on Squeeze
>
> On Sun, 01 May 2011 10:58:01 -0700, Roger Morgan wrote:
>
> >> From: Camaleón
> >
> >> It looks something related to authentication.
> >>
> >> Is there anything interesting at samba logs? I know samba logs are
> >> pretty hard to understand :-) but maybe there is something in there
> >> that give you any clue.
> >>
> > Here are the logs for the relevant time.
>
> (...)
>
> Sadly those are pretty generic errors and don't tell much about the cause
> of the failure. Try by increasing samba log level¹ ("log level = 3"),
> restart samba daemons, run smbclient again and review again the logs.
>
> P.S. 1 - Don't forget to restore to the previous samba log level or your
> disk will be quickly flooded :-)
>
> P.S. 2 - Before sending the logs, review the content to avoid sending
> sensible data (replace/delete anything you don't want to be viewed by
After setting log level = 3, rebooting, and running smbclient again,
there are 4 logfiles. The extra 2 are log.lyra and log.__fff_127.0.0.1
All four are copied below
start log.nmbd-
[2011/05/02 11:03:53, 0] nmbd/nmbd.c:857(main)
nmbd version 3.5.6 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2011/05/02 11:03:53.585807, 2] lib/tallocmsg.c:106(register_msg_pool_usage)
Registered MSG_REQ_POOL_USAGE
[2011/05/02 11:03:53.585855, 2] lib/dmallocmsg.c:77(register_dmalloc_msgs)
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
[2011/05/02 11:03:53.585904, 3] param/loadparm.c:9158(lp_load_ex)
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
[2011/05/02 11:03:53.586029, 3] ../lib/util/params.c:550(pm_process)
params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
[2011/05/02 11:03:53.586067, 3] param/loadparm.c:7842(do_section)
Processing section "[global]"
[2011/05/02 11:03:53.586524, 3] nmbd/nmbd.c:383(reload_nmbd_services)
services not loaded
[2011/05/02 11:03:53.596088, 2] nmbd/nmbd.c:890(main)
Becoming a daemon.
[2011/05/02 11:03:53.599547, 3] nmbd/nmbd.c:951(main)
Opening sockets 137
[2011/05/02 11:03:53.599695, 3]
../lib/util/util_net.c:68(interpret_string_addr_internal)
interpret_string_addr_internal: getaddrinfo failed for name 0.0.0.0 [Address
family for hostname not supported]
[2011/05/02 11:03:53.599750, 0] nmbd/nmbd.c:696(open_sockets)
[2011/05/02 11:04:04, 0] nmbd/nmbd.c:857(main)
nmbd version 3.5.6 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2011/05/02 11:04:04.655530, 2] lib/tallocmsg.c:106(register_msg_pool_usage)
Registered MSG_REQ_POOL_USAGE
[2011/05/02 11:04:04.655571, 2] lib/dmallocmsg.c:77(register_dmalloc_msgs)
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
[2011/05/02 11:04:04.655620, 3] param/loadparm.c:9158(lp_load_ex)
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
[2011/05/02 11:04:04.655740, 3] ../lib/util/params.c:550(pm_process)
params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
[2011/05/02 11:04:04.655777, 3] param/loadparm.c:7842(do_section)
Processing section "[global]"
[2011/05/02 11:04:04.656233, 3] nmbd/nmbd.c:383(reload_nmbd_services)
services not loaded
[2011/05/02 11:04:04.656294, 2] nmbd/nmbd.c:890(main)
Becoming a daemon.
[2011/05/02 11:04:04.659356, 3] nmbd/nmbd.c:951(main)
Opening sockets 137
[2011/05/02 11:04:04.659551, 3] nmbd/nmbd.c:739(open_sockets)
open_sockets: Broadcast sockets opened.
[2011/05/02 11:04:04.659675, 2] lib/interface.c:340(add_interface)
added interface eth1 ip=fe80::211:43ff:fea5:5e0e%eth1
bcast=fe80:::::%eth1 netmask=:::::
[2011/05/02 11:04:04.659792, 2] lib/interface.c:340(add_interface)
added interface eth1 ip=192.168.1.3 bcast=192.168.1.255 netmask=255.255.255.0
[2011/05/02 11:04:04.659896, 2] nmbd/nmbd_subnetdb.c:171(make_subnet)
making subnet name:192.168.1.3 Broadcast address:192.168.1.255 Subnet
mask:255.255.255.0
[2011/05/02 11:04:04.659931, 2] nmbd/nmbd_subnetdb.c:288(create_subnets)
create_subnets: ignoring non IPv4 interface.
[2011/05/02 11:04:04.659958, 2] nmbd/nmbd_subnetdb.c:171(make_subnet)
making subnet name:UNICAST_SUBNET Broadcast address:0.0.0.0 Subnet
mask:0.0.0.0
[2011/05/02 11:04:04.659988, 2] nmbd/nmbd_subnetdb.c:171(make_subnet)
making subnet name:REMOTE_BROADCAST_SUBNET Broadcast address:0.0.0.0 Subnet
mask:0.0.0.0
[2011/05/02 11:04:04.744805, 2] nmbd/nmbd_lmhosts.c:41(load_lmhosts_file)
load_lmhosts_file: Can't open
Re: Problem with Samba on Squeeze
On Sun, 01 May 2011 10:58:01 -0700, Roger Morgan wrote:
>> From: Camaleón
>
>> It looks something related to authentication.
>>
>> Is there anything interesting at samba logs? I know samba logs are
>> pretty hard to understand :-) but maybe there is something in there
>> that give you any clue.
>>
> Here are the logs for the relevant time.
(...)
Sadly those are pretty generic errors and don't tell much about the cause
of the failure. Try by increasing samba log level¹ ("log level = 3"),
restart samba daemons, run smbclient again and review again the logs.
P.S. 1 - Don't forget to restore to the previous samba log level or your
disk will be quickly flooded :-)
P.S. 2 - Before sending the logs, review the content to avoid sending
sensible data (replace/delete anything you don't want to be viewed by
everyone).
¹http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html#LOGLEVEL
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.05.01.18.15...@gmail.com
Re: Problem with Samba on Squeeze
> From: Camaleón > To: debian-user@lists.debian.org > Sent: Sun, May 1, 2011 5:15:50 PM > Subject: Re: Problem with Samba on Squeeze > > On Sat, 30 Apr 2011 13:51:51 -0700, Roger Morgan wrote: > > > Samba is running but I can't connect to it, and when I do the following > > test (from the Samba server): > > smbclient -L servername > > > > the response (after entering correct password) is: > > cut here--- > > Receiving SMB: Server stopped responding session setup failed: Call > > timed out: server did not respond after 2 milliseconds > > ---end of response-- > > (...) > > It looks something related to authentication. > > Is there anything interesting at samba logs? I know samba logs are pretty > hard to understand :-) but maybe there is something in there that give > you any clue. > Here are the logs for the relevant time. First log.nmbd : ---cut here--- [2011/04/30 18:13:03, 0] nmbd/nmbd.c:857(main) nmbd version 3.5.6 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 [2011/04/30 18:13:03.057129, 0] nmbd/nmbd.c:696(open_sockets) [2011/04/30 18:13:13, 0] nmbd/nmbd.c:857(main) nmbd version 3.5.6 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 [2011/04/30 18:13:44.242349, 0] nmbd/nmbd_become_lmb.c:395(become_local_master_stage2) * Samba name server LYRA is now a local master browser for workgroup GALAXY on subnet 192.168.1.3 * [2011/04/30 22:55:38.467321, 0] nmbd/nmbd.c:71(terminate) Got SIGTERM: going down... [2011/05/01 06:50:24, 0] nmbd/nmbd.c:857(main) nmbd version 3.5.6 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 --end of log.nmbd extract --- Then log.smbd: cut here--start of log.smbd extract--- [2011/04/30 06:23:08, 0] smbd/server.c:1123(main) smbd version 3.5.6 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 [2011/04/30 07:53:45.799147, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected [2011/04/30 08:25:45.948255, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected [2011/04/30 11:05:46.656557, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected [2011/04/30 11:37:46.807467, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected [2011/04/30 13:13:47.238251, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected [2011/04/30 14:17:47.532892, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected [2011/04/30 14:49:47.677722, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected [2011/04/30 15:21:47.821676, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected [2011/04/30 18:01:50.789490, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected [2011/04/30 18:13:03, 0] smbd/server.c:1123(main) smbd version 3.5.6 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 [2011/04/30 20:41:49.436355, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected [2011/05/01 06:50:24, 0] smbd/server.c:1123(main) smbd version 3.5.6 started. ---end of log.smbd extract--- I don't understand the getpeername error message. Roger -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/861007.84510...@web65502.mail.ac4.yahoo.com
Re: Problem with Samba on Squeeze
On Sat, 30 Apr 2011 13:51:51 -0700, Roger Morgan wrote: > Samba is running but I can't connect to it, and when I do the following > test (from the Samba server): > smbclient -L servername > > the response (after entering correct password) is: > cut here--- > Receiving SMB: Server stopped responding session setup failed: Call > timed out: server did not respond after 2 milliseconds > ---end of response-- (...) It looks something related to authentication. Is there anything interesting at samba logs? I know samba logs are pretty hard to understand :-) but maybe there is something in there that give you any clue. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.05.01.15.15...@gmail.com
Problem with Samba on Squeeze
Samba is running but I can't connect to it, and when I do the following test
(from the Samba server):
smbclient -L servername
the response (after entering correct password) is:
cut here---
Receiving SMB: Server stopped responding
session setup failed: Call timed out: server did not respond after 2
milliseconds
---end of response--
the Samba programs are running, here's the relevant part of the output of ps
-ef
| grep mb
root 1969 1 0 18:13 ?00:00:00 /usr/sbin/smbd -D
root 1983 1969 0 18:13 ?00:00:00 /usr/sbin/smbd -D
root 2308 1 0 18:13 ?00:00:00 /usr/sbin/nmbd -D
And here's my smb.conf file:
#=== Global Settings ===
[global]
log file = /var/log/samba/log.%m
load printers = yes
guest account = leong
printer = ML-1510_700
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:*
%n\n *password\supdated\ssuccessfully* .
obey pam restrictions = yes
write list = leong
encrypt passwords = true
public = yes
passwd program = /usr/bin/passwd %u
passdb backend = tdbsam
dns proxy = no
writeable = yes
server string = %h server
path = /var/common
unix password sync = yes
workgroup = galaxy
comment = lyra smbshare
#valid users = leong (no valid users list means anyone can login)
syslog = 0
panic action = /usr/share/samba/panic-action %d
max log size = 1000
directory mode = 766
pam password change = yes
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
# server string is the equivalent of the NT Description field
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# This will prevent nmbd to search for NetBIOS names through DNS.
# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast
Networking
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes
Debugging/Accounting
# This tells Samba to use a separate log file for each machine
# that connects
# Cap the size of the individual log files (in KiB).
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
# Do something sensible when Samba crashes: mail the admin a backtrace
### Authentication ###
# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
security = user
# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan
<
for
# sending the correct chat script for the passwd program in Debian Sarge).
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
## Domains ###
# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
