similar to: Samba 3.0.21 requires OS to be IPV6 Compliant ?

Displaying 20 results from an estimated 2000 matches similar to: "Samba 3.0.21 requires OS to be IPV6 Compliant ?"

2006 Jan 06
1
Repost: Help - compilation of winbind_nss_solaris.c/3.0.21a/Solaris 7 and older fails
I would really appreciate help ! I did not have any reply to my two posts and I don't know what to do. I can't build 3.0.21a and I have to migrate 54 Solaris 2.5.1 servers from 2.2.8a to 3.0.x. I'm afraid we could not move to newer solaris versions before 12 or 18 months. Under is the problem description. Thank you for your help. Pierre --------- SOLARIS 7 --------- On Solaris 7
2005 Dec 29
1
SAMBA 3.0.21 - Compile error on SOLARIS 7 & SOLARIS 2.5.1
Hi, Compilation fails on Solaris 7 + GCC and Solaris 2.5.1 + SUN CC. Each time the problem is on winbind. I have no idea about what's going wrong. I didn't have any trouble with SAMBA 3.0.21rc1. Can you help me ? Thank you, Pierre --------- SOLARIS 7 --------- Configure ./configure --with-acl-support --with-ldap=no --disable-cups --enable-static=yes --with-included-popt --------
2006 Mar 13
1
nsswitch segfaults with Samba 3.0.21 on Solaris 9
I've built Samba 3.0.21 with Kerb ADS, NSS, Winbind and PAM support on Solaris 9 using gcc 3.3.2. I'm able to compile and install and authentication works fine - I can query and authenticate with AD, but when I su, passwd or some other local auth Solaris command the command segfaults. This even happens if a valid user is in any of the databases previous in the search pattern to
2002 Mar 07
1
Compile problems with latest CVS
Hi, I get these compilation problems with today's CVS on Solaris configured with winbind: /usr/local/bin/gcc -O -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -o nsswitch/winbind_nss_solaris nsswitch/winbind_nss_solaris.c nsswitch/winbind_nss_solaris.c:14: includes.h: No such file or directory In file included from nsswitch/winbind_nss_solaris.c:15: nsswitch/winbind_nss_config.h:30: config.h:
2002 Jun 03
2
Help with 2.2.4 binary build
Hi folks, I'm getting these messages when compiling 2.2.4 on Solaris 7 with gcc version 2.95.3: % ./configure --with-utmp % make Compiling smbd/password.c smbd/password.c: In function `grab_server_mutex': smbd/password.c:1198: warning: passing arg 1 of `message_named_mutex' discards qualifiers from pointer target type Compiling lib/system.c lib/system.c: In function
2003 Apr 07
1
build samba in 64bit mode
I have a problem when I try build samba in 64bit mode (CFLAGS=-O -m64). It builds ok in 32bit. The problem arises when linking nsswitch/libnss_winbind.so On Solaris 9 I'm using bash-2.05$ /usr/local/tools/gcc/bin/gcc -v Reading specs from /usr/local/tools/gcc/lib/gcc-lib/sparc-sun-solaris2.9/3.2.2/specs Configured with: ../configure --with-as=/usr/local/tools/binutils/bin/as
2007 Feb 05
0
[SAMBA-SECURITY] CVE-2007-0453: Buffer overrun in nss_winbind.so.1 on Solaris
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ========================================================== == == Subject: Buffer overrun in NSS host lookup Winbind == library on Solaris == CVE ID#: CVE-2007-0453 == == Versions: Samba 3.0.21 - 3.0.23d (inclusive) running on == Sun Solaris == == Summary: A potential overrun in the gethostbyname() == and getipnodebyname() in the
2007 Feb 05
0
[SAMBA-SECURITY] CVE-2007-0453: Buffer overrun in nss_winbind.so.1 on Solaris
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ========================================================== == == Subject: Buffer overrun in NSS host lookup Winbind == library on Solaris == CVE ID#: CVE-2007-0453 == == Versions: Samba 3.0.21 - 3.0.23d (inclusive) running on == Sun Solaris == == Summary: A potential overrun in the gethostbyname() == and getipnodebyname() in the
2000 Jan 17
1
pre27 compilation fails on Sol7 box
Something strange happens when I compile the pre27 SSH: ocal/ssh//include -DETCDIR=\"/usr/local/ssh//etc\" \ -DSSH_PROGRAM=\"/usr/local/ssh//bin/ssh\" \ -DSSH_ASKPASS_DEFAULT=\"/usr/local/ssh//libexec/ssh/ssh-askpass\" \ -DHAVE_CONFIG_H -c atomicio.c In file included from includes.h:106, from atomicio.c:26: fake-socket.h:30: parse error before
2007 Jun 06
1
Building samba on HP-UX 11.23
Hello All, I am trying to build samba on HP-UX IA 64, for 64 bit using GCC 4.1.2. I am hitting a compilation error. Can someone throw some light on how to handle this problem? Here is what the build log says: Linking bin/winbindd Compiling nsswitch/wbinfo.c Linking bin/wbinfo Compiling utils/smbcontrol.c Compiling locking/locking.c Compiling locking/brlock.c Compiling
2005 Dec 22
2
Samba 3.0.21 + PANIC: internal error + lib/fault.c
Hi, yesterday I compiled an installed samba 3.0.21 on a solaris 8 box (gcc 3.4.2). Since then I frequently see this error message in the log. [2005/12/22 15:55:39, 0] lib/fault.c:fault_report(36) =============================================================== [2005/12/22 15:55:39, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 10 in pid 27816 (3.0.21) Please read the
2007 Jan 08
2
Re: [nut-commits] svn commit r714 - in trunk: . server
OK, I have removed the autoconf test for s6_addr32 (which is no longer used), and wrote a new test for IN6_IS_ADDR_V4MAPPED. The latter is probably portable, but since we're already in the business of testing, it does not hurt to do so. Arjen, I wonder about server/access.c, line 60-61: return (IN6_IS_ADDR_V4MAPPED(ip6) && ((((const u_int32_t *)ip6)[3] &
2006 Jan 04
1
samba 3.0.21 error
Hi! Today I installed samba 3.0.21 on debian sarge. I see this error in syslog: Jan 4 18:07:27 2T-Samba smbd[8352]: [2006/01/04 18:07:27, 1] libads/ldap.c:ads_connect(292) Jan 4 18:07:27 2T-Samba smbd[8352]: Failed to get ldap server info why? I upgrade my pdc from samba 3.0.20b to 3.0.21 and in the previous version I didn't see this error. Can you help me? Thanks, Fabio
2011 Sep 25
1
[nut-commits] buildbot failure in Network UPS Tools on FreeBSD-x86
On Sep 24, 2011, at 3:54 PM, clepple+buildbot at ghz.cc wrote: > The Buildbot has detected a new failure of FreeBSD-x86 on Network > UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/FreeBSD-x86/builds/266 http://buildbot.ghz.cc/public/nut/builders/FreeBSD-x86/builds/266/steps/compile/logs/stdio : libtool: compile: gcc
2005 Dec 28
6
3.0.21 and "Rejecting auth request from client"
Hi, I have migrate from samba 3.0.20b to 3.0.21. I restored the backup of all .tdb and when starting samba and a Windows XP tries to connect, I get this error: [2005/12/28 09:19:04, 0] libsmb/credentials.c:creds_server_check(159) creds_server_check: credentials check failed. [2005/12/28 09:19:04, 0] rpc_server/srv_netlog_nt.c:_net_sam_logon(667) _net_sam_logon: creds_server_step failed.
2015 Jan 30
0
[PATCH v2 1/3] ipv6: Select fragment id during UFO segmentation if not set.
If the IPv6 fragment id has not been set and we perform fragmentation due to UFO, select a new fragment id. We now consider a fragment id of 0 as unset and if id selection process returns 0 (after all the pertrubations), we set it to 0x80000000, thus giving us ample space not to create collisions with the next packet we may have to fragment. When doing UFO integrity checking, we also select the
2007 Mar 19
9
[BUG?] ip ru flush && RTNETLINK answers: Numerical result out of range
After an: # ip ru flush I loose all my ip rules but the priority 0 one. root@sarasvati:~# ip ru 0: from all lookup 255 root@sarasvati:~# Ok with that, but now i''m not able to insert any new rule. This leads to a total loose of conectivity. root@sarasvati:~# ip ru add from all table default RTNETLINK answers: Numerical result out of range root@sarasvati:~# ip ru add from all
2015 Jan 30
0
[PATCH v2 1/3] ipv6: Select fragment id during UFO segmentation if not set.
If the IPv6 fragment id has not been set and we perform fragmentation due to UFO, select a new fragment id. We now consider a fragment id of 0 as unset and if id selection process returns 0 (after all the pertrubations), we set it to 0x80000000, thus giving us ample space not to create collisions with the next packet we may have to fragment. When doing UFO integrity checking, we also select the
2015 Feb 03
0
[PATCH v3 net 1/3] ipv6: Select fragment id during UFO segmentation if not set.
If the IPv6 fragment id has not been set and we perform fragmentation due to UFO, select a new fragment id. We now consider a fragment id of 0 as unset and if id selection process returns 0 (after all the pertrubations), we set it to 0x80000000, thus giving us ample space not to create collisions with the next packet we may have to fragment. When doing UFO integrity checking, we also select the
2015 Feb 03
0
[PATCH v3 net 1/3] ipv6: Select fragment id during UFO segmentation if not set.
If the IPv6 fragment id has not been set and we perform fragmentation due to UFO, select a new fragment id. We now consider a fragment id of 0 as unset and if id selection process returns 0 (after all the pertrubations), we set it to 0x80000000, thus giving us ample space not to create collisions with the next packet we may have to fragment. When doing UFO integrity checking, we also select the