Re: [Samba] Error was Transport endpoint is not connected
Just read the mentioned article but I think this does not describe my problem. The error described there is more like a warning message to me. Moreover even if I define smb ports 139 the message still appears which it should not according to the article. Also, as mentioned, the backup fails. Here again the entries from the logfile. [2010/10/18 22:06:14.464881, 0] lib/util_sock.c:474(read_fd_with_timeout) [2010/10/18 22:06:14.499439, 0] lib/util_sock.c:1432(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. Copying the file manually from windows works. Took the windows Box 14 minutes. Thing is that it sometimes works and sometimes not. Using the other (older version) samba server it always works. I pretty much rule out any hardware issues NIC, etc. because the ReadyNAS also exports NFS shares and rsync's a good deal of data every night without any trouble at all. Best regards Rob On Tue, 2010-10-19 at 15:39 +0200, Gaiseric Vandal wrote: The following may help explain the error: http://wiki.samba.org/index.php/Samba_Myths So if you copy the file it is OK, but if the backup job runs an integrity check first it fails? What is involved in the integrity check? Is it somehow opening a connection to the server before starting the integrity check? On 10/19/2010 03:05 AM, robert.gehr wrote: I tried it with smb ports 139 to no avail. Same problem. The backup job takes that long because the windows box first runs an integrity check. If I just copy the file manually it takes a couple of minutes. As already mentioned the other samba server 3.4.7 works without any problems. What does that error message actually mean? Does it mean a network error has occurred, the server has run into a timeout, the server can no longer resolve the name of the client or what? Ideas are welcome. Rob On Fri, 2010-10-15 at 14:57 +0200, Gaiseric Vandal wrote: Did you try changing smb.conf on the NAS to be port 139 only? Also, it seems that 55 GB should not take one hour to copy (55 GBytes is 440 Gbit, and at 1 Gbit/sec and 60 secs / min, the transfer sohuld take about minutes- at least in theory.) I am guessing it is dropping because it tries to reestablish a connection part way through the transfer. On 10/15/2010 07:12 AM, robert.gehr wrote: Nice try. The backup fails exactly the moment the message appears in the log. So I would say it is something to worry about. Has really no one any ideas why this all of a sudden comes up. Thanks for any hints Rob On Tue, 2010-10-12 at 08:41 +0200, Daniel Müller wrote: This message only says: I established to one of the ports 139 or 445 and dropped the other. It is nothing to trouble about. --- EDV Daniel Mller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tbingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im Auftrag von Gaiseric Vandal Gesendet: Montag, 11. Oktober 2010 16:48 An: samba@lists.samba.org Betreff: Re: [Samba] Error was Transport endpoint is not connected By default samba listens on two TCP ports- 445 and 139. You can specify this in smb.conf smb ports = 445 139 445 is the newer smb over tcp.139 is the older smb over netbios over tcp/ip. 445 was for Windows 2000 and newer clients.. I am not sure why samba enables 445 by default since as far as I know it does not support smb-over-tcp (without the NBT/netbios over tcp stuff.)If you set smb ports = 139 in your smb.conf you should see endpoint messages disappear. I think what happens is Win 2000 (and newer) clients will initially try to connect on port 445, find it isn't really compatible, and then dump down to NBT on port 139. So your NAS may be occasionally connecting on port 139 without problems and occasionally connecting on port 445, and which point it fails. OR- the endpoint errors may be completely unrelated, but you just don't look for when when the NAS is working. Is the NAS part of the domain? Is it a windows or linux/samba based device? My samba server is a PDC. XP clients in the domain connect with no problems regardless of if smb ports is 139 only or 139 + 445. XP/Win7 clients NOT in the domain can't connect to shares if 445 is disabled, which indicates they are connecting to 445 1st. On 10/11/2010 08:57 AM, robert.gehr wrote: Hello All I used to back up a Mssql database (about 55GB) to a samba share without any
Re: [Samba] Error was Transport endpoint is not connected
I tried it with smb ports 139 to no avail. Same problem. The backup job takes that long because the windows box first runs an integrity check. If I just copy the file manually it takes a couple of minutes. As already mentioned the other samba server 3.4.7 works without any problems. What does that error message actually mean? Does it mean a network error has occurred, the server has run into a timeout, the server can no longer resolve the name of the client or what? Ideas are welcome. Rob On Fri, 2010-10-15 at 14:57 +0200, Gaiseric Vandal wrote: Did you try changing smb.conf on the NAS to be port 139 only? Also, it seems that 55 GB should not take one hour to copy (55 GBytes is 440 Gbit, and at 1 Gbit/sec and 60 secs / min, the transfer sohuld take about minutes- at least in theory.) I am guessing it is dropping because it tries to reestablish a connection part way through the transfer. On 10/15/2010 07:12 AM, robert.gehr wrote: Nice try. The backup fails exactly the moment the message appears in the log. So I would say it is something to worry about. Has really no one any ideas why this all of a sudden comes up. Thanks for any hints Rob On Tue, 2010-10-12 at 08:41 +0200, Daniel Müller wrote: This message only says: I established to one of the ports 139 or 445 and dropped the other. It is nothing to trouble about. --- EDV Daniel Mller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tbingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im Auftrag von Gaiseric Vandal Gesendet: Montag, 11. Oktober 2010 16:48 An: samba@lists.samba.org Betreff: Re: [Samba] Error was Transport endpoint is not connected By default samba listens on two TCP ports- 445 and 139. You can specify this in smb.conf smb ports = 445 139 445 is the newer smb over tcp.139 is the older smb over netbios over tcp/ip. 445 was for Windows 2000 and newer clients.. I am not sure why samba enables 445 by default since as far as I know it does not support smb-over-tcp (without the NBT/netbios over tcp stuff.)If you set smb ports = 139 in your smb.conf you should see endpoint messages disappear. I think what happens is Win 2000 (and newer) clients will initially try to connect on port 445, find it isn't really compatible, and then dump down to NBT on port 139. So your NAS may be occasionally connecting on port 139 without problems and occasionally connecting on port 445, and which point it fails. OR- the endpoint errors may be completely unrelated, but you just don't look for when when the NAS is working. Is the NAS part of the domain? Is it a windows or linux/samba based device? My samba server is a PDC. XP clients in the domain connect with no problems regardless of if smb ports is 139 only or 139 + 445. XP/Win7 clients NOT in the domain can't connect to shares if 445 is disabled, which indicates they are connecting to 445 1st. On 10/11/2010 08:57 AM, robert.gehr wrote: Hello All I used to back up a Mssql database (about 55GB) to a samba share without any problems. The samba server Server-A was running version 3.4.7 We just got one of those Netgear ReadyNas3200 things and I tried to backup up to a share there which sometimes works and sometimes not in wich case I get the following error: snip--- [2010/10/08 21:32:26.937834, 0] lib/util_sock.c:474(read_fd_with_timeout) [2010/10/08 21:32:26.966404, 0] lib/util_sock.c:1432(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. ---snap- The samba version on the ReadyNas is 3.5.4 On the windows side nothing has changed apart form the destination to the new share. The ReadyNas performs pretty well and I do not get any network errors or otherwise. To rule out some network problem I exported a nfs share on the ReadyNas which I mounted on Server-A, created a share on Server-A that points to the nfs-mount and ran a backup. No problems and no errors. Any ideas which buttons to push in order to get a reliable backup going again? From what I read this usually points to a problem on the client side but nothing has changed there. I could of course use the Server-A:smb-nfs-mount:ReadyNas solution but this is not what I want. Thanks Rob -- -- To unsubscribe from this list go to the following URL and read the instructions:
Re: [Samba] Error was Transport endpoint is not connected
Nice try. The backup fails exactly the moment the message appears in the log. So I would say it is something to worry about. Has really no one any ideas why this all of a sudden comes up. Thanks for any hints Rob On Tue, 2010-10-12 at 08:41 +0200, Daniel Müller wrote: This message only says: I established to one of the ports 139 or 445 and dropped the other. It is nothing to trouble about. --- EDV Daniel Mller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tbingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im Auftrag von Gaiseric Vandal Gesendet: Montag, 11. Oktober 2010 16:48 An: samba@lists.samba.org Betreff: Re: [Samba] Error was Transport endpoint is not connected By default samba listens on two TCP ports- 445 and 139. You can specify this in smb.conf smb ports = 445 139 445 is the newer smb over tcp.139 is the older smb over netbios over tcp/ip. 445 was for Windows 2000 and newer clients.. I am not sure why samba enables 445 by default since as far as I know it does not support smb-over-tcp (without the NBT/netbios over tcp stuff.)If you set smb ports = 139 in your smb.conf you should see endpoint messages disappear. I think what happens is Win 2000 (and newer) clients will initially try to connect on port 445, find it isn't really compatible, and then dump down to NBT on port 139. So your NAS may be occasionally connecting on port 139 without problems and occasionally connecting on port 445, and which point it fails. OR- the endpoint errors may be completely unrelated, but you just don't look for when when the NAS is working. Is the NAS part of the domain? Is it a windows or linux/samba based device? My samba server is a PDC. XP clients in the domain connect with no problems regardless of if smb ports is 139 only or 139 + 445. XP/Win7 clients NOT in the domain can't connect to shares if 445 is disabled, which indicates they are connecting to 445 1st. On 10/11/2010 08:57 AM, robert.gehr wrote: Hello All I used to back up a Mssql database (about 55GB) to a samba share without any problems. The samba server Server-A was running version 3.4.7 We just got one of those Netgear ReadyNas3200 things and I tried to backup up to a share there which sometimes works and sometimes not in wich case I get the following error: snip--- [2010/10/08 21:32:26.937834, 0] lib/util_sock.c:474(read_fd_with_timeout) [2010/10/08 21:32:26.966404, 0] lib/util_sock.c:1432(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. ---snap- The samba version on the ReadyNas is 3.5.4 On the windows side nothing has changed apart form the destination to the new share. The ReadyNas performs pretty well and I do not get any network errors or otherwise. To rule out some network problem I exported a nfs share on the ReadyNas which I mounted on Server-A, created a share on Server-A that points to the nfs-mount and ran a backup. No problems and no errors. Any ideas which buttons to push in order to get a reliable backup going again? From what I read this usually points to a problem on the client side but nothing has changed there. I could of course use the Server-A:smb-nfs-mount:ReadyNas solution but this is not what I want. Thanks Rob -- Everything should be made as simple as possible, but not simpler. ~ Albert Einstein -- baumann GmbH Oskar-von-Miller-Str. 7 92224 Amberg - Deutschland / Germany GF / CEO: Dr. Georg Baumann, Rudi Neumann, Josef Konrad HR: Amberg HRB 1067 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Error was Transport endpoint is not connected
I don't think this is my problem. Samba on the ReadyNas works all right, it is fast, I can mount shares etc. No worries at all. Only if I copy that huge file which takes abaut an hour (depending on the network load) or so the error pops up and the backup fails. The ReadNas is a Debian based Linux. The windows machine a Server 2008 R2 system. As already mentioned backing up to the old samba server never caused any troubles. Both the old samba server and the ReadyNas have the default smb ports = 445 139 settings. Both machines run as member servers of an AD Domain. Thanks again for any hints. Rob On Mon, 2010-10-11 at 16:47 +0200, Gaiseric Vandal wrote: By default samba listens on two TCP ports- 445 and 139. You can specify this in smb.conf smb ports = 445 139 445 is the newer smb over tcp.139 is the older smb over netbios over tcp/ip. 445 was for Windows 2000 and newer clients.. I am not sure why samba enables 445 by default since as far as I know it does not support smb-over-tcp (without the NBT/netbios over tcp stuff.)If you set smb ports = 139 in your smb.conf you should see endpoint messages disappear. I think what happens is Win 2000 (and newer) clients will initially try to connect on port 445, find it isn't really compatible, and then dump down to NBT on port 139. So your NAS may be occasionally connecting on port 139 without problems and occasionally connecting on port 445, and which point it fails. OR- the endpoint errors may be completely unrelated, but you just don't look for when when the NAS is working. Is the NAS part of the domain? Is it a windows or linux/samba based device? My samba server is a PDC. XP clients in the domain connect with no problems regardless of if smb ports is 139 only or 139 + 445. XP/Win7 clients NOT in the domain can't connect to shares if 445 is disabled, which indicates they are connecting to 445 1st. On 10/11/2010 08:57 AM, robert.gehr wrote: Hello All I used to back up a Mssql database (about 55GB) to a samba share without any problems. The samba server Server-A was running version 3.4.7 We just got one of those Netgear ReadyNas3200 things and I tried to backup up to a share there which sometimes works and sometimes not in wich case I get the following error: snip--- [2010/10/08 21:32:26.937834, 0] lib/util_sock.c:474(read_fd_with_timeout) [2010/10/08 21:32:26.966404, 0] lib/util_sock.c:1432(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. ---snap- The samba version on the ReadyNas is 3.5.4 On the windows side nothing has changed apart form the destination to the new share. The ReadyNas performs pretty well and I do not get any network errors or otherwise. To rule out some network problem I exported a nfs share on the ReadyNas which I mounted on Server-A, created a share on Server-A that points to the nfs-mount and ran a backup. No problems and no errors. Any ideas which buttons to push in order to get a reliable backup going again? From what I read this usually points to a problem on the client side but nothing has changed there. I could of course use the Server-A:smb-nfs-mount:ReadyNas solution but this is not what I want. Thanks Rob -- Everything should be made as simple as possible, but not simpler. ~ Albert Einstein -- baumann GmbH Oskar-von-Miller-Str. 7 92224 Amberg - Deutschland / Germany GF / CEO: Dr. Georg Baumann, Rudi Neumann, Josef Konrad HR: Amberg HRB 1067 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Error was Transport endpoint is not connected
Hello All I used to back up a Mssql database (about 55GB) to a samba share without any problems. The samba server Server-A was running version 3.4.7 We just got one of those Netgear ReadyNas3200 things and I tried to backup up to a share there which sometimes works and sometimes not in wich case I get the following error: snip--- [2010/10/08 21:32:26.937834, 0] lib/util_sock.c:474(read_fd_with_timeout) [2010/10/08 21:32:26.966404, 0] lib/util_sock.c:1432(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. ---snap- The samba version on the ReadyNas is 3.5.4 On the windows side nothing has changed apart form the destination to the new share. The ReadyNas performs pretty well and I do not get any network errors or otherwise. To rule out some network problem I exported a nfs share on the ReadyNas which I mounted on Server-A, created a share on Server-A that points to the nfs-mount and ran a backup. No problems and no errors. Any ideas which buttons to push in order to get a reliable backup going again? From what I read this usually points to a problem on the client side but nothing has changed there. I could of course use the Server-A:smb-nfs-mount:ReadyNas solution but this is not what I want. Thanks Rob -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba-3.5.2 - getent group not returning any info
Hello there
I just installed 3.5.2 and encountered the following. Compile worked all
right but getent group would not give back any results, though getent
passwd did list those AD users. The server runs as AD member and
winbind seems to work normally. wbinfo -u and wbinfo -g return the
desired info just getent group sucks.
It works using the previous 3.3.8 version as well as with 3.4.7 using an
unchanged smb.conf.
I can live with 3.4.7 but thought it might be of interest.
Thanks for all the efforts.
Rob
Here the relevant smb.conf:
winbind trusted domains only = No
winbind use default domain = Yes
winbind nested groups = Yes
winbind separator = /
winbind enum users = yes
winbind enum groups = yes
winbind expand groups = 3
idmap uid = 1-2
idmap gid = 1-2
and strace for getent group
poll([{fd=4, events=POLLIN|POLLPRI|POLLERR|POLLHUP, revents=POLLIN}], 1,
-1) = 1
read(4, \27\3\1\0 , 5)= 5
read(4, \v\225\310\17\375\t\324\334\02240\275F\213\'^\275Bt\37..., 32)
= 32
read(4, \27\3\1\0P, 5)= 5
read(4, \246\250\266\251]+)\301[\272?O\226\242\21BOs\n\373\30..., 80)
= 80
rt_sigaction(SIGPIPE, {SIG_DFL}, NULL, 8) = 0
open(/etc/ld.so.cache, O_RDONLY) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=90174, ...}) = 0
mmap(NULL, 90174, PROT_READ, MAP_PRIVATE, 5, 0) = 0x7f74914cf000
close(5)= 0
open(/lib64/libnss_winbind.so.2, O_RDONLY) = 5
read(5, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\200\33\0...,
832) = 832
fstat(5, {st_mode=S_IFREG|0755, st_size=35642, ...}) = 0
mmap(NULL, 2145744, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 5,
0) = 0x7f748e928000
fadvise64(5, 0, 2145744, POSIX_FADV_WILLNEED) = 0
mprotect(0x7f748e92d000, 2097152, PROT_NONE) = 0
mmap(0x7f748eb2d000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_DENYWRITE, 5, 0x5000) = 0x7f748eb2d000
mmap(0x7f748eb2f000, 19920, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_ANONYMOUS, -1, 0) = 0x7f748eb2f000
close(5)= 0
mprotect(0x7f748eb2d000, 4096, PROT_READ) = 0
munmap(0x7f74914cf000, 90174) = 0
lstat(/tmp/.winbindd, {st_mode=S_IFDIR|0755, st_size=17, ...}) = 0
lstat(/tmp/.winbindd/pipe, {st_mode=S_IFSOCK|0777, st_size=0, ...}) =
0
socket(PF_FILE, SOCK_STREAM, 0) = 5
fcntl(5, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(5, F_SETFL, O_RDWR|O_NONBLOCK)= 0
fcntl(5, F_GETFD) = 0
fcntl(5, F_SETFD, FD_CLOEXEC) = 0
connect(5, {sa_family=AF_FILE, path=/tmp/.winbindd/pipe}, 110) = 0
select(6, [5], NULL, NULL, {0, 0}) = 0 (Timeout)
write(5, 0\10\0\0\0\0\0\0\0\0\0\0\204;\0\0\0\10\0\0\0\0\0\0\0\0...,
2096) = 2096
select(6, [5], NULL, NULL, {5, 0}) = 1 (in [5], left {5, 0})
read(5, \250\r\0\0\2\0\0\0\27\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0...,
3496) = 3496
select(6, [5], NULL, NULL, {0, 0}) = 0 (Timeout)
write(5, 0\10\0\\0\0\0\0\0\0\0\204;\0\0\0\10\0\0\0\0\0\0\0\0...,
2096) = 2096
select(6, [5], NULL, NULL, {5, 0}) = 1 (in [5], left {5, 0})
read(5, \341\r\0\0\2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0...,
3496) = 3496
select(6, [5], NULL, NULL, {5, 0}) = 1 (in [5], left {5, 0})
read(5, /usr/local/samba-3.5.2-run/var/l..., 57) = 57
lstat(/usr/local/samba-3.5.2-run/var/locks/winbindd_privileged,
{st_mode=S_IFDIR|0750, st_size=17, ...}) = 0
lstat(/usr/local/samba-3.5.2-run/var/locks/winbindd_privileged/pipe,
{st_mode=S_IFSOCK|0777, st_size=0, ...}) = 0
socket(PF_FILE, SOCK_STREAM, 0) = 6
fcntl(6, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(6, F_SETFL, O_RDWR|O_NONBLOCK)= 0
fcntl(6, F_GETFD) = 0
fcntl(6, F_SETFD, FD_CLOEXEC) = 0
connect(6, {sa_family=AF_FILE,
path=/usr/local/samba-3.5.2-run/var/locks/winbindd_privileged/pipe},
110) = 0
close(5)= 0
select(7, [6], NULL, NULL, {0, 0}) = 0 (Timeout)
write(6, 0\10\0\0\n\0\0\0\0\0\0\0\204;\0\0\0\0\0\0\0\0\0\0\0\0\0...,
2096) = 2096
select(7, [6], NULL, NULL, {5, 0}) = 1 (in [6], left {5, 0})
read(6, \250\r\0\0\2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0...,
3496) = 3496
select(7, [6], NULL, NULL, {0, 0}) = 0 (Timeout)
write(6, 0\10\0\0\f\0\0\0\0\0\0\0\204;\0\0\0\0\0\0\0\0\0\0\0\0\0...,
2096) = 2096
select(7, [6], NULL, NULL, {5, 0}) = 1 (in [6], left {5, 0})
read(6, \250\r\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0...,
3496) = 3496
close(3)= 0
munmap(0x7f74914e7000, 4096)= 0
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL}, NULL, 8) = 0
select(7, [6], NULL, NULL, {0, 0}) = 0 (Timeout)
write(6, 0\10\0\0\v\0\0\0\0\0\0\0\204;\0\0\0\0\0\0\0\0\0\0\0\0\0...,
2096) = 2096
select(7, [6], NULL, NULL, {5, 0}) = 1 (in [6], left {5, 0})
read(6, \250\r\0\0\2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0...,
3496) = 3496
exit_group(0) = ?
--
To
[Samba] AD and winbindd madness
Hello all I tried for a couple of days now to get our samba domain hooked up with an AD controller. I followed these instructions: http://www.msadfaq.de/wiki/ActiveDirectory/trust_relationship_samba_ad I've solved a couple of problems over the years but this is a hard nut to crack. The setup is as follows AD runs the domain BAUMANN (realm: baumann.local) samba runs the domain BAUMANN-GMBH The trust relationship has been esatblished, at least so it seems. What I can do when I fire up winbind on the samba PDC (baadm1) wbinfo -u: works wbinfo -g: works wbinfo -m: works wbind -t: never returns but spits out no errors getent passwd/group show the users/groups of the AD BAUMANN domain I can assign file/group ownership to users/groups from the BAUMANN domain. If I don't have winbindd running I can connect to a share located on the PDC of the samba controlled BAUMANN-GMBH domain, but can not write to it. If I run winbindd I can't connect to the share anymore. Same user, same password. The error winbindd comes up with: SCHANNEL: schannel_decode seq_num=13 data_len=32 SCHANNEL: schannel_decode seq_num=13 data_len=32 cli_pipe_validate_current_pdu: got pdu len 96, data_len 20, ss_len 12 rpc_api_pipe: got PDU len of 96 at offset 0 rpc_api_pipe: host baad1.baumann.local, pipe \NETLOGON, fnum 0x8006 returned 40 bytes. netr_LogonSamLogonEx: struct netr_LogonSamLogonEx out: struct netr_LogonSamLogonEx validation : * validation : union netr_Validation(case 3) sam3 : NULL authoritative: * authoritative: 0x01 (1) flags: * flags: 0x (0) result : NT_STATUS_LOGON_FAILURE NTLM CRAP authentication for user [BAUMANN]\[gehr] returned NT_STATUS_LOGON_FAILURE (PAM: 4) Here the relevant entries of smb.conf on the samba PDC [global] dos charset = 850 unix charset = ISO8859-1 display charset = ISO8859-1 workgroup = BAUMANN-GMBH server string = %h passdb backend = ldapsam:ldap://baadm1.baumann-gmbh.de, ldap://bafs2.baumann-gmbh.de; username map = /usr/local/samba/lib/user.map lanman auth = No socket options = TCP_NODELAY SO_RCVBUF=16384 SO_SNDBUF=16384 add user script = /usr/local/sbin/smbldap-useradd -m %u add group script = /usr/local/sbin/smbldap-groupadd -a -p %g add user to group script = /usr/local/sbin/smbldap-groupmod -m %u %g delete user from group script = /usr/local/sbin/smbldap-groupmod -x %u %g set primary group script = /usr/local/sbin/smbldap-usermod -g %g % u add machine script = /usr/local/sbin/smbldap-useradd -w %u logon path = domain logons = Yes os level = 65 domain master = Yes wins support = Yes kernel oplocks = No ldap admin dn = cn=ldap-admin,dc=baumann-gmbh,dc=de ldap group suffix = ou=groups ldap idmap suffix = ou=idmap ldap machine suffix = ou=computers ldap passwd sync = Yes ldap suffix = dc=baumann-gmbh,dc=de ldap ssl = start tls ldap user suffix = ou=people #idmap backend = ldap:ldap://baadm1.baumann-gmbh.de #idmap domains = BAUMANN-GMBH idmap uid = 1-2 idmap gid = 1-2 ldapsam:trusted = yes idmap config BAUMANN-GMBH:ldap_url = ldap://baadm1.baumann-gmbh.de idmap config BAUMANN-GMBH:ldap_base_dn = ou=idmap,dc=baumann-gmbh,dc=de idmap config BAUMANN-GMBH:backend = ldap idmap config BAUMANN-GMBH:default = yes Here the conf winbindd gets started with: [global] workgroup = baumann netbios name = baadm1 idmap uid = 3-4 idmap gid = 3-4 winbind enum users = yes winbind enum groups = yes #winbind separator = + realm = BAUMANN.LOCAL #winbind use default domain = Yes security = ADS domain master = No encrypt passwords = yes password server = baad1.baumann.local client use spnego = yes winbind trusted domains only = No Help is greatly appreciated, for it is must that we get this thing going. Thanks and regards Rob Success is going from failure to failure without loss of enthusiasm. ~ Winston Churchill -- baumann GmbH Oskar-von-Miller-Str. 7 92224 Amberg - Deutschland / Germany GF / CEO: Dr. Georg Baumann, Rudi Neumann, Josef Konrad HR: Amberg HRB 1067 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] NetApp unable to join samba PDC
Hello there I've just been trying to get a NetApp FAS2020, DataOnTap 7.2.5.1 to join our domain. No luck so far . The PDC is samba 3.2.4 with ldap backend. I created the account manually and when I try to join the NetApp I get these in the samba logs. [2008/11/14 08:32:48, 0] rpc_server/srv_netlog_nt.c:_netr_ServerAuthenticate2(520) _netr_ServerAuthenticate2: netlogon_creds_server_check failed. Rejecting auth request from client BAFS4 machine account BAFS4$ NetApp spits that out: Once you have created and/or reset the 'BAFS4' machine account, press ENTER. [continue]: *** CIFS Setup could not establish a connection with the Primary Domain *** Controller (PDC). Usually this happens when the 'BAFS4' account does *** not exist in the domain or must have it's password reset. I googled like a maniac and found one post that Volker Lendecke got it working but no description of how it was done. Another post talked about it only worked using tdbsam and not ldapsam but also no solution. Joining windows XP, NT4, etc. machines to the domain works, so the setup can't be all that wrong I suppose. Does anyone have a clue of what's going on here. NetApp states it does not support Samba PDC's but that doesn't necessarily mean it won't work so I hope at least. Help is more than greatly appreciated. Regards Rob -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Robert Gehr is NOT in the house
Ich werde ab 12.05.2008 nicht im Büro sein. Ich kehre zurück am 23.05.2008. In dringenden Fällen Elmar Pöpperl o. Michael Feige kontaktieren -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] samba + cups
Hello everyone I hope this is not off topic. The samba + cups thing is driving me nuts. Samba runs as PDC and print server. Everything is fine, printing works, automatic driver download works etc. Now I want only certain people to be able to stop a printer under windows. After digging around a bit I set my cupsd.conf file up like so: Policy default Limit Send-Document Resume-Printer Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job Allow from @LOCAL Order deny,allow /Limit Limit Pause-Printer Resume-Printer Set-Printer-Attributes Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class CUPS-Delete-Class CUPS-Accept-Jobs CUPS-Reject-Jobs CUPS-Set-Default AuthType BasicDigest Require user @Admin-Group Order deny,allow /Limit Limit CUPS-Authenticate-Job Require user @OWNER @SYSTEM Require user @Admin-Group Satisfy any Order deny,allow /Limit This has no effect at all. The strange thing is that cups logs the following when I pause and unpause a printer under Windows. E [11/Mar/2008:13:29:43 +0100] Pause-Printer: Unauthorized I [11/Mar/2008:13:29:43 +0100] Saving printers.conf... I [11/Mar/2008:13:29:43 +0100] Printer IT-Laser1 stopped by root. I [11/Mar/2008:13:29:47 +0100] Saving printers.conf... I [11/Mar/2008:13:29:47 +0100] Printer IT-Laser1 started by rob. Why is the thing being stopped by root and started by me (rob)?? Do the settings in cupsd.conf make any sense at all in combination with samba because samba runs as root and whatever a user does is seen by cups as being done by root?? Maybe I'm on the wrong track altogether. Help is greatly appreciated. Regards Rob -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 3.0.28 continuously dumping core
Hello all Compiled 3.0.28 from source and get continuous core dumps. The machine running as PDC continous to work though. Core dumps are reproduceable and happen when, for example, I am trying to connect to a share that does not exist as well as when I install a new printer driver using the Microsoft wizard thing. We are running two other machines with 3.0.28 without any core dumps at all. Here the dump and following what smbd is linked against. Compiler used is: gcc-4.1.2 2008/02/23 21:05:13, 0] lib/fault.c:fault_report(41) === [2008/02/23 21:05:13, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 3040 (3.0.28) Please read the Trouble-Shooting section of the Samba3-HOWTO [2008/02/23 21:05:13, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2008/02/23 21:05:13, 0] lib/fault.c:fault_report(45) === [2008/02/23 21:05:13, 0] lib/util.c:smb_panic(1633) PANIC (pid 3040): internal error [2008/02/23 21:05:13, 0] lib/util.c:log_stack_trace(1737) BACKTRACE: 24 stack frames: #0 /usr/local/samba/sbin/smbd(log_stack_trace+0x2d) [0x80218b36] #1 /usr/local/samba/sbin/smbd(smb_panic+0x74) [0x80218c5e] #2 /usr/local/samba/sbin/smbd [0x80205179] #3 [0xe420] #4 /usr/local/samba/sbin/smbd(winbindd_send_request+0x66) [0x8022831d] #5 /lib/libnss_winbind.so.2(winbindd_request+0x1e) [0x408a2b4a] #6 /lib/libnss_winbind.so.2(_nss_winbind_getpwnam_r+0x7b) [0x408a341f] #7 /lib/tls/libc.so.6(getpwnam_r+0xcc) [0x4033ab9c] #8 /lib/tls/libc.so.6(getpwnam+0x91) [0x4033a5e1] #9 /usr/local/samba/sbin/smbd(sys_getpwnam+0x1d) [0x802079b7] #10 /usr/local/samba/sbin/smbd(getpwnam_alloc+0xcc) [0x8020ab9a] #11 /usr/local/samba/sbin/smbd(Get_Pwnam_alloc+0x29c) [0x8020a75a] #12 /usr/local/samba/sbin/smbd(Get_Pwnam+0x2a) [0x8020a8d7] #13 /usr/local/samba/sbin/smbd(get_user_home_dir+0x1d) [0x8020a924] #14 /usr/local/samba/sbin/smbd(find_service+0x5e) [0x800bc445] #15 /usr/local/samba/sbin/smbd(get_referred_path+0x183) [0x800c7751] #16 /usr/local/samba/sbin/smbd(setup_dfs_referral+0x14a) [0x800c7d8f] #17 /usr/local/samba/sbin/smbd(handle_trans2+0x5bff) [0x8009f064] #18 /usr/local/samba/sbin/smbd(reply_trans2+0x6c0) [0x8009ff40] #19 /usr/local/samba/sbin/smbd [0x800ba237] #20 /usr/local/samba/sbin/smbd(smbd_process+0x8bf) [0x800bb4ca] #21 /usr/local/samba/sbin/smbd(main+0xb97) [0x802d5564] #22 /lib/tls/libc.so.6(__libc_start_main+0xe0) [0x402c9500] #23 /usr/local/samba/sbin/smbd [0x800475e2] [2008/02/23 21:05:13, 0] lib/fault.c:dump_core(181) ldd output: linux-gate.so.1 = (0xe000) libldap-2.3.so.0 = /usr/local/lib/libldap-2.3.so.0 (0x4002) liblber-2.3.so.0 = /usr/local/lib/liblber-2.3.so.0 (0x40055000) libcups.so.2 = /usr/lib/libcups.so.2 (0x40061000) libssl.so.0.9.8 = /usr/local/lib/libssl.so.0.9.8 (0x4008d000) libcrypto.so.0.9.8 = /usr/local/lib/libcrypto.so.0.9.8 (0x400cd000) libz.so.1 = /lib/libz.so.1 (0x4020f000) libpthread.so.0 = /lib/tls/libpthread.so.0 (0x4022) libm.so.6 = /lib/tls/libm.so.6 (0x4023) libcrypt.so.1 = /lib/libcrypt.so.1 (0x40252000) libacl.so.1 = /lib/libacl.so.1 (0x40284000) libresolv.so.2 = /lib/libresolv.so.2 (0x4028a000) libnsl.so.1 = /lib/libnsl.so.1 (0x4029c000) libdl.so.2 = /lib/libdl.so.2 (0x402b1000) libc.so.6 = /lib/tls/libc.so.6 (0x402b4000) libsasl2.so.2 = /usr/lib/libsasl2.so.2 (0x403c9000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000) libattr.so.1 = /lib/libattr.so.1 (0x403df000) Help is always appreciated. Regards Rob -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] inotify trouble
Hello there This morning our main Samba server was pretty unresponsive running at a 30+ load average. After digging a bit what I found in the logs was the following. No data on inotify fd?! [2008/01/21 07:02:59, 0] smbd/notify_inotify.c:inotify_handler(234) That entry appears a billion zillion times in the log file until the file system is filled up leaving no space on the device and sending samba into oblivion. Anyone knows what is causing this? I never had that before having run a lot of different samba versions. I also found a couple of entries in the logs like this. [2008/01/18 15:50:46, 1] smbd/notify_inotify.c:watch_destructor(342) inotify_rm_watch returned Invalid argument This doesn't seem to cause any trouble though. Samba: 3.0.28 Kernel: 2.6.20.3 Help is greatly appreciated Regards Rob -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] cups page_log strangeness
Hi there I just upgraded from 3.0.23d to 3.0.25b. The server acts as PDC and print server. The setup is that Win clients automtically download the printers from samba. Worked all right so far. Here is what I did. Compiled the new version and installed it. Stopped smbd and nmbd and copied everything under /old-samba/var/ to /new-samba/var/ smb.conf stayed the same. Fired up the new version. The printing system ist cups-1.2.11 Before the upgrade the cups page_log alwas showed entries in the form: PrinterA userX 879018 [28/Jun/2007:09:37:38 +0200] 1 1 - 10.230.10.175 PrinterB userY 879019 [28/Jun/2007:09:37:40 +0200] 1 1 - 10.230.10.205 PrinterC userZ 879020 [28/Jun/2007:09:44:18 +0200] 1 1 - 10.230.1.7 Now the page_log looks like this: PrinterA userX 879264 [28/Jun/2007:11:12:37 +0200] 1 1 - 10.230.10.37 PrinterC userZ 879265 [28/Jun/2007:11:13:49 +0200] 1 1 - localhost PrinterC userY 879266 [28/Jun/2007:11:14:09 +0200] 1 1 - localhost PrinterA userH 879270 [28/Jun/2007:11:20:03 +0200] 1 1 - 10.230.11.33 What's the localhost entry mean? It definetely is a job handed down from some Win client and did not originate on the server. Did I miss something? Also a couple of minutes after bringing up the new version, a few people called that they could not print any more. A few minutes later it worked again without me touching a thing. Any ideas? Thanks Rob -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] winbindd issues on member server
Hi there After having posted a while ago about the trouble I had with 3.0.23 I gave it another try with 3.0.23d I installed the current version on our samba PDC and BDC while the member server was still running 3.0.22. This setup has worked for a couple of weeks with no issues. I then upgraded the member server two days ago to 3.0.23d and after serveral hours I could not connect via ssh to the member server anymore. I got no login shell. I could also not log in on the console. Fortunately I still had an open session so I killed winbindd and immediately I could log in again. Errors in my winbindd log are as follows. winbindd Exceeding 200 client connections, no idle connection found and heaps of: nsswitch/winbindd.c:request_main_recv(556) malloc failed The malloc failed entries I also get under 3.0.22 which works OK Another thing that happened was that all of a sudden users had no write permissions on shares anymore they could write to a couple of minutes before. After logging in anew to the domain they could write again to the shares. So I am back on 3.0.22 The system is not the most up to date because it's the our main fileserver and we don't want to play too many tricks. smb.conf of the member server: unix charset = ISO8859-1 display charset = ISO8859-1 workgroup = MYDOM server string = %h (Samba %v) interfaces = 10.230.1.1/255.255.0.0 security = DOMAIN password server = pdc, bdc deadtime = 10 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 wins server = baadm1 kernel oplocks = No ldap admin dn = cn=root,dc=mydom,dc=de ldap group suffix = ou=groups ldap idmap suffix = ou=idmap ldap machine suffix = ou=computers ldap passwd sync = Yes ldap suffix = dc=mydom,dc=de ldap ssl = start tls ldap user suffix = ou=people idmap backend = ldap:ldap://pdc.mydom.de idmap uid = 1-2 idmap gid = 1-2 winbind trusted domains only = Yes acl group control = Yes create mask = 00 force create mode = 0775 directory mask = 00 force directory mode = 0775 map acl inherit = Yes veto oplock files = /*.sql/*.SQL/*.idx/*.IDX/*.fxp/*.FXP/*.xls/*.doc/*.mdb/*.DBF/*.dbf/*.CDX/*.cdx/*.mdx/*.MDX/*.mmo/*.MMO/*.prg/*.PRG/*.dbt/*.DBT/ level2 oplocks = No strict locking = No log level = 1 Some other info that might help. Host type: i486-suse-linux-gnu System: Linux bafs1 2.6.8.1 #2 Thu Sep 9 16:57:23 CEST 2004 i686 i686 i386 GNU/Linux Architecture: i686 Addons: db db2 linuxthreads noversion Build CFLAGS: -O2 -mcpu=i486 -march=i486 -g Build CC: gcc Compiler version: 2.95.3 20010315 (SuSE) Kernel headers: UTS_RELEASE Symbol versioning: yes Build static: yes Build shared: yes Build pic-default: no Build profile: yes Build omitfp: no Build bounded: no Build static-nss: no Stdio: libio Thanks for your help -- Best Regards Rob -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] member server 3.0.23c drives me nuts
Hello everybody First of all thanks to the developer team in providing the samba suite. I have been running samba servers for serveral years now but 3.0.23c just drives me nuts. I have a PDC and BDC running samba 3.0.23c with openldap as backend and also a samba member server trying to run 2.0.23c. The member server is the primary file server so I can't play with it all that much. The member server was running 3.0.22 before without any problems. Last night I upgraded to 3.0.23c and the fun began. Things I observed: 1) Random people just could not mount any shares on the member server anymore or the mount process took very very long. All of a sudden, they could connect to the shares again at normal speed without me changing anything. 2) I could not log in to the member server anymore via ssh and also not on the console. The server just didn't give me a shell. This led me to resetting the server who had an uptime of almost 600 days. This is actually what grieves me most ;-) After poking around a bit I found in log.winbindd [2006/10/09 14:41:41, 0] nsswitch/winbindd.c:process_loop(832) winbindd: Exceeding 200 client connections, no idle connection found [2006/10/09 14:41:41, 0] nsswitch/winbindd.c:request_main_recv(556) malloc failed googling I found someone describing the same problem and also not being able to log into his box anymore. If I kill winbindd and fire it up again it works for about an hour or two before the message appears again. wbinfo -u then produces an error like Cannot connect to DOMAIN or something like that. 3) When trying to assign acls in windows to files joe suddenly appears as joe (Unix User\joe) instead of joe (MYDOMAIN\joe) Here goes the global part of smb.conf on the member server. [global] unix charset = ISO8859-1 display charset = ISO8859-1 workgroup = MYDOM server string = %h (Samba %v) interfaces = 10.230.1.1/255.255.0.0 security = DOMAIN password server = pdc, bdc deadtime = 10 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 wins server = pdc kernel oplocks = No ldap admin dn = cn=admin,dc=mydom,dc=de ldap group suffix = ou=groups ldap idmap suffix = ou=idmap ldap machine suffix = ou=computers ldap suffix = dc=mydom,dc=de ldap ssl = start tls ldap user suffix = ou=people idmap backend = ldap:ldap://pdc.mydom.de idmap uid = 1-2 idmap gid = 1-2 winbind trusted domains only = Yes acl group control = Yes create mask = 00 force create mode = 0775 directory mask = 00 force directory mode = 0775 map acl inherit = Yes veto oplock files = /*.xls/*.doc/*.mdb level2 oplocks = No strict locking = No log level = 1 What am I missing or am I getting too old for the job?? Help is greatly appreciated. -- Best Regards Robert Gehr Technological progress has merely provided us with more efficient means for going backwards ~ Aldous Huxley o /\ /_ o__ o* ~(_) ,/'_ o__ Robert Gehr (_)\(_) ,/'_ o__ o__ Baumann GmbH, 92224 Amberg (_)\(_) ,/'_ ,/'_ visit: http://www.baumann-gmbh.de (_)\(_) (_)\(_) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] fully qualified usernames ??
Hi there Just a couple of questions to help me understand. When I upgrade from 3.0.22 to 3.0.23c the access restrictions on my shares on the member server no longer work. I read in the Changes file Since Samba 3.0.8, it has been recommended that all domain accounts listed in smb.conf on a member server be fully qualified with the So far so good I know what I have to do still I don't quite understand why the member server is no longer able to identify the user connecting. When, on the member server, I do a wbinfo -U ID I get the correct SID When I do wbinfo -a joe%passwd it succeeds as well as a wbinfo -a DOMAIN\\joe%passwd So winbindd identifies joe all right even without the DOMAIN prefix. Why does this no longer work for shares on the member server that have valid users = joe defined?? The member server gets its local users and groups via ldap. I also have in my smb.conf: winbind trusted domains only = Yes What am I missing?? Thanks -- Best Regards Robert Gehr Technological progress has merely provided us with more efficient means for going backwards ~ Aldous Huxley -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 3.0.23: assigning users to printers
Hello I just upgraded our PDC from 3.0.22 to 3.0.23 with all the bells and whistles. I am running OpenLdap as a backend and did what's been written in the Changelog regarding indexing. The new version started up fine and worked all right. Netlogons, shares, printing etc. I could also assign ACLs to my files as before. The PDC also works as a printserver running cups with the drivers stored in samba. The strange thing is that when in windows I want to assign a user to a printer it does not work any longer. A message comes up, telling me it could not be established that the printserver belongs to the domain. Funny thing is, that the printserver is the PDC. This problem only appears in 3.0.23. With 3.0.22 it works all right. Did I miss something?? Thanks for helping Rob -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] strange BDC Behaviour
Hello everybody I am running two Domaincontrollers PDC and BDC both with an LDAP Backend (Master and Slave) and another samba fileserver FS1 who is a Domain Member. We have about 180 win clients (W2k and XP) on the network. We are also running a w2k terminalserver (TS) with about ten clients hooking up to it. We are running a login script assigning shares automatically to the clients. The strange thing is, that ever so often people connecting to the terminalserver can not get their shares assigned from the Domain Member Server FS1. When trying to map the shares manually on the TS by entering \\FS1\share the login box comes up asking for username and password. When I enter the IP address of FS1 e.g. \\10.10.10.10\share I can connect, also when I enter the FQDN e.g. \\FS1.mydomain.de\share the connection works. The clients also map a share, using the netbios name, from the BDC which always works. What we noticed is, that clients on the TS usually use the BDC for loging on to the network which shouldn't be I suppose. As far as I understand it, the client should sign on to the network via the PDC and only use the BDC if the former fails. Right Most of the time it helps to send a HUP signal to the nmbd and the smbd on the BDC but sometimes not. This is pretty strange and causes quite a bit of discomfort on the users as well as on our side. Ordinary clients do not show this type of behaviour at all, only acounts on the TS Anyone any ideas??? Here the smb.conf files global section from PDC,BDC and FS1 who can't be all that wrong, otherwise things would not work at all. Help is greatly appreciated. Best regards Rob - PDC config file [global] dos charset = 850 unix charset = ISO8859-1 display charset = ISO8859-1 workgroup = MYDOMAIN passdb backend = ldapsam:ldap://pdc.mydomain.de, ldap://bdc.mydomain.de; username map = /usr/local/samba/lib/user.map lanman auth = No socket options = TCP_NODELAY SO_RCVBUF=16384 SO_SNDBUF=16384 add user script = /usr/local/sbin/smbldap-useradd -m %u add group script = /usr/local/sbin/smbldap-groupadd -a -p %g add user to group script = /usr/local/sbin/smbldap-groupmod -m %u %g delete user from group script = /usr/local/sbin/smbldap-groupmod -x %u %g set primary group script = /usr/local/sbin/smbldap-usermod -g %g %u add machine script = /usr/local/sbin/smbldap-useradd -t 0 -w %u logon path = domain logons = Yes os level = 65 domain master = Yes wins support = Yes kernel oplocks = No ldap admin dn = cn=root,dc=mydomain,dc=de ldap group suffix = ou=groups ldap idmap suffix = ou=idmap ldap machine suffix = ou=computers ldap passwd sync = Yes ldap suffix = dc=mydomain,dc=de ldap ssl = start tls ldap user suffix = ou=people idmap backend = ldap:ldap://pdc.mydomain.de idmap uid = 1-2 idmap gid = 1-2 ldapsam:trusted = yes printer admin = @Domain_Admins, @Print_Operators, Administrator map acl inherit = Yes lprm command = /usr/bin/cancel '%p-%j' lppause command = lp -i '%p-%j' -H hold lpresume command = lp -i '%p-%j' -H resume queuepause command = /usr/bin/disable '%p' queueresume command = /usr/bin/enable '%p' level2 oplocks = No strict locking = No --- Here the file for the BDC [global] unix charset = ISO8859-1 display charset = ISO8859-1 workgroup = MYDOMAIN server string = %h (Samba %v) passdb backend = ldapsam:ldap://bdc.mydomain.de, ldap://pdc.mydomain.de; username map = /usr/local/samba/lib/user.map socket options = TCP_NODELAY SO_RCVBUF=16384 SO_SNDBUF=16384 logon path = domain logons = Yes domain master = No kernel oplocks = No ldap admin dn = cn=root,dc=mydomain,dc=de ldap group suffix = ou=groups ldap idmap suffix = ou=idmap ldap machine suffix = ou=computers ldap passwd sync = Yes ldap suffix = dc=mydomain,dc=de ldap ssl = start tls ldap user suffix = ou=people idmap backend = ldap:ldap://pdc.mydomain.de idmap uid = 1-2 idmap gid = 1-2 ldapsam:trusted = yes oplocks = No level2 oplocks = No And here the file from the DOMAIN MEMBER FS1 [global] unix charset = ISO8859-1 display charset = ISO8859-1 workgroup = MYDOMAIN server string = %h (Samba %v) interfaces = 10.230.1.1/255.255.0.0 security = DOMAIN password server = pdc, bdc deadtime = 10 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 wins server = pdc kernel oplocks = No ldap admin dn = cn=root,dc=mydomain,dc=de ldap group suffix = ou=groups ldap idmap suffix = ou=idmap ldap machine suffix = ou=computers ldap passwd sync = Yes ldap suffix = dc=mydomain,dc=de ldap ssl = start tls ldap user suffix = ou=people idmap backend = ldap:ldap://pdc.mydomain.de idmap uid = 1-2 idmap
[Samba] Robert Gehr is NOT in the house
Ich werde ab 05.06.2006 nicht im Büro sein. Ich kehre zurück am 30.06.2006. Ich werde Ihre Nachricht nach meiner Rückkehr beantworten. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] acl and winbindd woes
Hello We have got a samba PDC and BDC running openldap as a backend and it works pretty well. I set up another samba File-Server and joined the domain all right. Also set up winbindd using the idmap facility via ldap. On the File-Server when I do a wbinfo -n joe I get S-1-5-21-1133090748-3639176701-2116357234-1062 User (1) wbinfo -s S-1-5-21-1133090748-3639176701-2116357234-1062 gives me My-Domain\joe wbinfo -S S-1-5-21-1133090748-3639176701-2116357234-1062 gives 10329 So far so good. Setting acls using the the explorer in Windows I add joe to directory temp works also but when I run the command getfacl temp I get # file: temp # owner: jack # group: Domain_Users user::rwx user:10329:rwx group::--- mask::rwx other::--- default:user::rwx default:user:10329:rwx default:group::--- default:mask::rwx default:other::--- User joe does not get listed by name, but only via its idmap ID. Now the problem is, user joe has no access to directory temp even though he should. What have I done wrong?? Anyone any ideas?? Thanks for helping. -- Best Regards Robert Gehr We make a living by what we get, but we make a life by what we give. ~ Winston Churchill o /\ /_ o__ o* ~(_) ,/'_ o__ Robert Gehr (_)\(_) ,/'_ o__ o__ Baumann GmbH, 92224 Amberg (_)\(_) ,/'_ ,/' visit: http://www.baumann-gmbh.de (_)\(_) (_)\(_) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] INTERNAL ERROR
Hi all I have got a samba-3.0.13 (hot off the press) PDC running here that also works as a print server printig via cups-1.1.23. As a backend I use openldap-2.2.11 What I get in my log files is what you see below. It seems this only happens when the user prints a *.pdf file. The message shows up once in a while, definetly not for every print job that gets submitted. Printing of those *.pdf files seems to work as well, bacause I don't here any complains and cries for solutions from Big Bill. I googled and checked the HOWTO to no avail. Help is greatly appreciated 12-100 (10.230.11.94) connect to service print$ initially as user graf (uid=1006, gid=513) (pid 5702) [2005/04/01 10:46:30, 0] lib/fault.c:fault_report(36) === [2005/04/01 10:46:30, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 5702 (3.0.13) Please read the appendix Bugs of the Samba HOWTO collection [2005/04/01 10:46:30, 0] lib/fault.c:fault_report(39) === [2005/04/01 10:46:30, 0] lib/util.c:smb_panic2(1495) PANIC: internal error [2005/04/01 10:46:30, 0] lib/util.c:smb_panic2(1503) BACKTRACE: 19 stack frames: #0 /usr/local/samba/sbin/smbd(smb_panic2+0x7c) [0x81dbc5c] #1 /usr/local/samba/sbin/smbd(smb_panic+0x1a) [0x81dbe5a] #2 /usr/local/samba/sbin/smbd [0x81c99c8] #3 [0xe420] #4 /usr/local/samba/sbin/smbd(smb_io_notify_info_data_strings+0x1be) [0x818381e] #5 /usr/local/samba/sbin/smbd [0x8183b47] #6 /usr/local/samba/sbin/smbd(spoolss_io_r_rfnpcnex+0x84) [0x81872e4] #7 /usr/local/samba/sbin/smbd [0x812240a] #8 /usr/local/samba/sbin/smbd(api_rpcTNP+0x248) [0x81545d8] #9 /usr/local/samba/sbin/smbd(api_pipe_request+0x90) [0x81549d0] #10 /usr/local/samba/sbin/smbd [0x8150b3c] #11 /usr/local/samba/sbin/smbd [0x808b9a3] #12 /usr/local/samba/sbin/smbd(reply_trans+0xa3f) [0x808c65f] #13 /usr/local/samba/sbin/smbd [0x80d2a84] #14 /usr/local/samba/sbin/smbd(process_smb+0x16a) [0x80d2e6a] #15 /usr/local/samba/sbin/smbd(smbd_process+0x145) [0x80d3b65] #16 /usr/local/samba/sbin/smbd(main+0x82b) [0x82454eb] #17 /lib/tls/libc.so.6(__libc_start_main+0xe0) [0x4020d500] #18 /usr/local/samba/sbin/smbd [0x8077eb1] -- Best Regards Robert Gehr It you want to live a happy life, tie it to a goal - not to people or things. ~ Albert Einstein o /\ /_ o__ o* ~(_) ,/'_ o__ Robert Gehr (_)\(_) ,/'_ o__ o__ Baumann GmbH, 92224 Amberg (_)\(_) ,/'_ ,/' visit: http://www.baumann-gmbh.de (_)\(_) (_)\(_) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
solved [Samba] net utility (3.0.12) acting strange
Hello I solved the problem myself. It seems to me that the compiler version gcc version 3.3.3 (SuSE Linux) coming with suse-9.1 is buggy. I installed gcc 3.4.3 and compiled the sources again. Now the net utility works all right. I did several compiler runs trying different configure options with the SuSE compiler to no avail. Hope it helps someone. Regards Rob Hi all I am running a Suse-9.1 distribution on a server and have been runnig samba from 3.0.4 up to 3.0.11 succesfully on the beast. I have got openldap 2.2.11 running and the server works as a PDC using the LDAP repository I always downloaded the sources compiled the stuff and off it went without any problems. Yesterday I compiled the 3.0.12 on the machine and when I fired it up I realized certain strange things concernig the net utility If I do a: net user -Uusername%passwd -S PDC I get Could not connect to server PDC The username or password was not correct. The username and password is correct because if I run this command with the net utility version 3.0.11 it works. If I do a net groupmap list with the 3.0.12 version it also works. If I get the net binary (version 3.0.12) from another server running suse-9.0 it also works. On both servers suse-9.1 and suse-9.0 I installed the the same tar ball (3.0.12) yesterday, compiled the source using exactly the same configure options and compiled the code without any errors only a couple of compiler warnings. My configure options: ./configure --prefix=/usr/local/samba-3.0.12-run --with-ldap --with-smbmount --enable-cups=yes --with-acl-support On the 9.1 server where it is broken, ldd gives: linux-gate.so.1 = (0xe000) libcrypt.so.1 = /lib/libcrypt.so.1 (0x4001f000) libresolv.so.2 = /lib/libresolv.so.2 (0x4005) libnsl.so.1 = /lib/libnsl.so.1 (0x40062000) libdl.so.2 = /lib/libdl.so.2 (0x40078000) libldap-2.2.so.7 = /usr/local/lib/libldap-2.2.so.7 (0x4007b000) liblber-2.2.so.7 = /usr/local/lib/liblber-2.2.so.7 (0x400a9000) libc.so.6 = /lib/tls/libc.so.6 (0x400b5000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000) libsasl2.so.2 = /usr/lib/libsasl2.so.2 (0x401ca000) libssl.so.0.9.7 = /usr/lib/libssl.so.0.9.7 (0x401e) libcrypto.so.0.9.7 = /usr/lib/libcrypto.so.0.9.7 (0x4021) The compiler version is: gcc -v Reading specs from /usr/lib/gcc-lib/i586-suse-linux/3.3.3/specs Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java,ada --disable-checking --libdir=/usr/lib --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit i586-suse-linux Thread model: posix gcc version 3.3.3 (SuSE Linux) The linker: ld -version GNU ld version 2.15.90.0.1.1 20040303 (SuSE Linux) Copyright 2002 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely no warranty. [EMAIL PROTECTED]:/usr/local/samba-3.0.12-run/bin # man ld On the Suse-9.0 Server the gcc version is 3.3.1 and ld gives 2.14.90.0.5 20030722 (SuSE Linux) What am I missing here? -- Best Regards Robert Gehr It you want to live a happy life, tie it to a goal - not to people or things. ~ Albert Einstein o /\ /_ o__ o* ~(_) ,/'_ o__ Robert Gehr (_)\(_) ,/'_ o__ o__ Baumann GmbH, 92224 Amberg (_)\(_) ,/'_ ,/' visit: http://www.baumann-gmbh.de (_)\(_) (_)\(_) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba --- -- Best Regards Robert Gehr -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 3.0.12 net utility acting strange
Hi all I am running a Suse-9.1 distribution on a server and have been runnig samba from 3.0.4 up to 3.0.11 succesfully on the beast. I have got openldap 2.2.11 running and the server works as a PDC using the LDAP repository I always downloaded the sources compiled the stuff and off it went without any problems. Yesterday I compiled the 3.0.12 on the machine and when I fired it up I realized certain strange things concernig the net utility If I do a: net user -Uusername%passwd -S PDC I get Could not connect to server PDC The username or password was not correct. The username and password is correct because if I run this command with the net utility version 3.0.11 it works. If I do a net groupmap list with the 3.0.12 version it also works. If I get the net binary (version 3.0.12) from another server running suse-9.0 it also works. On both servers suse-9.1 and suse-9.0 I installed the the same tar ball (3.0.12) yesterday, compiled the source using exactly the same configure options and compiled the code without any errors only a couple of compiler warnings. My configure options: ./configure --prefix=/usr/local/samba-3.0.12-run --with-ldap --with-smbmount --enable-cups=yes --with-acl-support On the 9.1 server where it is broken, ldd gives: linux-gate.so.1 = (0xe000) libcrypt.so.1 = /lib/libcrypt.so.1 (0x4001f000) libresolv.so.2 = /lib/libresolv.so.2 (0x4005) libnsl.so.1 = /lib/libnsl.so.1 (0x40062000) libdl.so.2 = /lib/libdl.so.2 (0x40078000) libldap-2.2.so.7 = /usr/local/lib/libldap-2.2.so.7 (0x4007b000) liblber-2.2.so.7 = /usr/local/lib/liblber-2.2.so.7 (0x400a9000) libc.so.6 = /lib/tls/libc.so.6 (0x400b5000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000) libsasl2.so.2 = /usr/lib/libsasl2.so.2 (0x401ca000) libssl.so.0.9.7 = /usr/lib/libssl.so.0.9.7 (0x401e) libcrypto.so.0.9.7 = /usr/lib/libcrypto.so.0.9.7 (0x4021) The compiler version is: gcc -v Reading specs from /usr/lib/gcc-lib/i586-suse-linux/3.3.3/specs Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java,ada --disable-checking --libdir=/usr/lib --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit i586-suse-linux Thread model: posix gcc version 3.3.3 (SuSE Linux) The linker: ld -version GNU ld version 2.15.90.0.1.1 20040303 (SuSE Linux) Copyright 2002 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely no warranty. [EMAIL PROTECTED]:/usr/local/samba-3.0.12-run/bin # man ld On the Suse-9.0 Server the gcc version is 3.3.1 and ld gives 2.14.90.0.5 20030722 (SuSE Linux) What am I missing here? -- Best Regards Robert Gehr It you want to live a happy life, tie it to a goal - not to people or things. ~ Albert Einstein o /\ /_ o__ o* ~(_) ,/'_ o__ Robert Gehr (_)\(_) ,/'_ o__ o__ Baumann GmbH, 92224 Amberg (_)\(_) ,/'_ ,/' visit: http://www.baumann-gmbh.de (_)\(_) (_)\(_) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] net utility (3.0.12) acting strange
Hi all I am running a Suse-9.1 distribution on a server and have been runnig samba from 3.0.4 up to 3.0.11 succesfully on the beast. I have got openldap 2.2.11 running and the server works as a PDC using the LDAP repository I always downloaded the sources compiled the stuff and off it went without any problems. Yesterday I compiled the 3.0.12 on the machine and when I fired it up I realized certain strange things concernig the net utility If I do a: net user -Uusername%passwd -S PDC I get Could not connect to server PDC The username or password was not correct. The username and password is correct because if I run this command with the net utility version 3.0.11 it works. If I do a net groupmap list with the 3.0.12 version it also works. If I get the net binary (version 3.0.12) from another server running suse-9.0 it also works. On both servers suse-9.1 and suse-9.0 I installed the the same tar ball (3.0.12) yesterday, compiled the source using exactly the same configure options and compiled the code without any errors only a couple of compiler warnings. My configure options: ./configure --prefix=/usr/local/samba-3.0.12-run --with-ldap --with-smbmount --enable-cups=yes --with-acl-support On the 9.1 server where it is broken, ldd gives: linux-gate.so.1 = (0xe000) libcrypt.so.1 = /lib/libcrypt.so.1 (0x4001f000) libresolv.so.2 = /lib/libresolv.so.2 (0x4005) libnsl.so.1 = /lib/libnsl.so.1 (0x40062000) libdl.so.2 = /lib/libdl.so.2 (0x40078000) libldap-2.2.so.7 = /usr/local/lib/libldap-2.2.so.7 (0x4007b000) liblber-2.2.so.7 = /usr/local/lib/liblber-2.2.so.7 (0x400a9000) libc.so.6 = /lib/tls/libc.so.6 (0x400b5000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000) libsasl2.so.2 = /usr/lib/libsasl2.so.2 (0x401ca000) libssl.so.0.9.7 = /usr/lib/libssl.so.0.9.7 (0x401e) libcrypto.so.0.9.7 = /usr/lib/libcrypto.so.0.9.7 (0x4021) The compiler version is: gcc -v Reading specs from /usr/lib/gcc-lib/i586-suse-linux/3.3.3/specs Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java,ada --disable-checking --libdir=/usr/lib --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit i586-suse-linux Thread model: posix gcc version 3.3.3 (SuSE Linux) The linker: ld -version GNU ld version 2.15.90.0.1.1 20040303 (SuSE Linux) Copyright 2002 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely no warranty. [EMAIL PROTECTED]:/usr/local/samba-3.0.12-run/bin # man ld On the Suse-9.0 Server the gcc version is 3.3.1 and ld gives 2.14.90.0.5 20030722 (SuSE Linux) What am I missing here? -- Best Regards Robert Gehr It you want to live a happy life, tie it to a goal - not to people or things. ~ Albert Einstein o /\ /_ o__ o* ~(_) ,/'_ o__ Robert Gehr (_)\(_) ,/'_ o__ o__ Baumann GmbH, 92224 Amberg (_)\(_) ,/'_ ,/' visit: http://www.baumann-gmbh.de (_)\(_) (_)\(_) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba --- -- Best Regards Robert Gehr It you want to live a happy life, tie it to a goal - not to people or things. ~ Albert Einstein o /\ /_ o__ o* ~(_) ,/'_ o__ Robert Gehr (_)\(_) ,/'_ o__ o__ Baumann GmbH, 92224 Amberg (_)\(_) ,/'_ ,/' visit: http://www.baumann-gmbh.de (_)\(_) (_)\(_) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Problem with SID
Hello all I have a Samba-3.0.0 server configured as PDC running agains openldap. So I have an entry of the form: sambaSIDS-1-5-21-x-y--rid in my dircectory If I check the properties of a file under Windows on the PDC I get the information all right displaying the owner of the file as: user[Domain\user] Now I have a couple of other Samba-3.0.0 servers which are not configured as PDC/BDC or whatever but are verifying the user information against LDAP also. Access rights to shares etc. work fine on those servers, the only thing ist that when I look in windows at the owner of a file I get S-1-5-21-x-y--rid and not user [server-name\user]. Because I do not know in advance what users will have to join the domain every user has a sambaSID entry with the SID of the PDC. I didn't have the problem with 2.2.8a in combination with LDAP. As far as I remember ther was no sambaSID such attribute in the 2.2.x LDAP scheme. Anyone knows how to solve that Problem?? Help is greatly appreciated. Best regards Robert Gehr What one man can invent, another can discover Sherlock Holmes web2CAD AG Emailfabrikstr. 12 92224 Amberg / Germany visit: http://www.web2cad.com -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] smb_panic + Backtrace
Hi all After running samba 3.0.0 for a couple of days I get messages like this in my logs which look a bit suspicious :-) to me. Anyone knows what this is all about? The result ist that copy jobs etc. are just signing off. Sorry for not entering this in the bugzilla thing. I am not too familiar using it. The samba version is 3.0.0 running against ldap 2.1.22 Here the globals from my smb.conf [global] workgroup = ARBEITSGRUPPE netbios name = FS1-LINUX encrypt passwords = Yes map to guest = Bad User username map = /usr/local/samba/lib/users.map password level = 2 username level = 2 socket options = TCP_NODELAY SO_RCVBUF=16384 SO_SNDBUF=16384 unix charset = ISO8859-1 display charset = ISO8859-1 logon script = %U.bat logon home = os level = 64 preferred master = Yes passdb backend = ldapsam:ldaps://ldap1.foo.bar ldap suffix = dc=foo,dc=bar ldap machine suffix = ou=computers ldap user suffix = ou=people ldap group suffix = ou=groups ldap admin dn = cn=xxx,dc=foo,dc=bar printer admin = xxx log level = 0 oplocks = No level2 oplocks = No Help is greatly appreciated. Thanks rob [2003/12/01 16:10:27, 0] lib/fault.c:fault_report(36) === [2003/12/01 16:10:27, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 12430 (3.0.0) Please read the appendix Bugs of the Samba HOWTO collection [2003/12/01 16:10:27, 0] lib/fault.c:fault_report(39) === [2003/12/01 16:10:27, 0] lib/util.c:smb_panic(1400) PANIC: internal error [2003/12/01 16:10:27, 0] lib/util.c:smb_panic(1407) BACKTRACE: 16 stack frames: #0 /usr/local/samba/sbin/smbd(smb_panic+0x16c) [0x8189c8c] #1 /usr/local/samba/sbin/smbd(dbgtext+0x194) [0x8179634] #2 /usr/local/samba/sbin/smbd(dbgtext+0x1f2) [0x8179692] #3 /lib/libc.so.6(__libc_sigaction+0x138) [0x401ac7f8] #4 /usr/local/samba/sbin/smbd(alloc_sub_basic+0x23) [0x818f343] #5 /usr/local/samba/sbin/smbd(lp_talloc_free+0x67) [0x80743f7] #6 /usr/local/samba/sbin/smbd(lp_servicename+0x37) [0x8075967] #7 /usr/local/samba/sbin/smbd(make_connection+0x2c0) [0x80bb270] #8 /usr/local/samba/sbin/smbd(reply_tcon_and_X+0x228) [0x8093eb8] #9 /usr/local/samba/sbin/smbd(respond_to_all_remaining_local_messages+0x65b) [0x80b85db] #10 /usr/local/samba/sbin/smbd(respond_to_all_remaining_local_messages+0x700) [0x80b8680] #11 /usr/local/samba/sbin/smbd(process_smb+0x18e) [0x80b893e] #12 /usr/local/samba/sbin/smbd(smbd_process+0x150) [0x80b92c0] #13 /usr/local/samba/sbin/smbd(main+0x69f) [0x81dcbef] #14 /lib/libc.so.6(__libc_start_main+0xbe) [0x4019b7ee] #15 /usr/local/samba/sbin/smbd(_start+0x21) [0x8073861] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] printer suddenly unavailable
Hi there I have a pretty strange problem that pops up once in a while. Running samba 2.2.7a having installed a Samba machine as password server sharing user info via NIS I have a couple of printers running here at our place. Several of them are only accessible to a select group of people so I defined the concerned printers share as: [PrinterX] valid users = user1, user2, user3 . Things work fine only once in a while one of the people who is allowed to print to this share and has done so numerous times in the previous weeks calls up and says he/she is unable to print. When I check the logs on samba I get Rejecting user '': authentication failed Reinstalling the printer on the client machine usually helps as well as a reboot of the concerned client. This has also happened versy seldom with shares once in a while. Concerned are W2000, XP and NT machines. Even though the person can not print anymore he/she can still access his/her private shares which are bound to proper authentication as well. Any ideas Best regards Robert Gehr It is an act of evil to accept the state of evil as either inevitable or final - Heschel acceptance speech for the Nobel Peace Prize, 1986 web2CAD AG Emailfabrikstrs. 12 92224 Amberg / Germany visit: http://www.web2cad.com -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
