[Samba] net ads join Core Dumps.
Hi, I have just installed Mandrake linux x84_64 (64 bit version) on my new dell poweredge server (1850 SMP) I am getting core dumps when trying to join the 2003 AD domain. ie. I run net ads join [EMAIL PROTECTED] running kinit worked ok. I am running samba version 3.0.20 samba-client-3.0.20-3mdk samba-server-3.0.20-3mdk samba-common-3.0.20-3mdk samba-winbind-3.0.20-3mdk Anyone help. I wish to user winbind for proxy auth. Chris Welsh -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] [Updateed] net ads join Core Dumps.
Tried the latest src, and still core dumps. Here's my configure args ./configure --with-pam --with-quotas --with-winbind --with-configdir=/etc/samba Here is what version samba-server-3.0.20-3mdk dumps to the log. I installed this on my (32 bit Mandrake 2006.0) laptop, and I have no problems. Any ideas? [2006/01/06 16:43:05, 0] lib/fault.c:fault_report(36) === [2006/01/06 16:43:05, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 5369 (3.0.20) Please read the appendix Bugs of the Samba HOWTO collection [2006/01/06 16:43:05, 0] lib/fault.c:fault_report(39) === [2006/01/06 16:43:05, 0] lib/util.c:smb_panic2(1548) PANIC: internal error [2006/01/06 16:43:05, 0] lib/util.c:smb_panic2(1556) BACKTRACE: 15 stack frames: #0 smbd(smb_panic2+0x189) [0x55734383] #1 smbd(smb_panic+0xe) [0x557341f8] #2 smbd [0x5571dbbc] #3 smbd [0x5571dc14] #4 /lib64/tls/libc.so.6 [0x2c1a1b60] #5 /usr/lib64/libldap-2.3.so.0(ldap_set_option+0x48) [0x2abe5978] #6 smbd(ads_do_search+0x1ce) [0x5579c9cc] #7 smbd(ads_server_info+0xb4) [0x557a0865] #8 smbd(ads_connect+0xea) [0x5579bc30] #9 smbd(check_published_printers+0xf1) [0x5575fa05] #10 smbd(nt_printing_init+0x46c) [0x55758a5c] #11 smbd(print_backend_init+0x186) [0x557528b1] #12 smbd(main+0x4c9) [0x557bc841] #13 /lib64/tls/libc.so.6(__libc_start_main+0xda) [0x2c18f4fa] #14 smbd [0x555a92ca] Quoting Christopher Peter Welsh [EMAIL PROTECTED]: Hi, I have just installed Mandrake linux x84_64 (64 bit version) on my new dell poweredge server (1850 SMP) I am getting core dumps when trying to join the 2003 AD domain. ie. I run net ads join [EMAIL PROTECTED] running kinit worked ok. I am running samba version 3.0.20 samba-client-3.0.20-3mdk samba-server-3.0.20-3mdk samba-common-3.0.20-3mdk samba-winbind-3.0.20-3mdk Anyone help. I wish to user winbind for proxy auth. Chris Welsh -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: [Updateed] net ads join Core Dumps.
It seems to be happening with other net command variations (ie. net group, net user). Net time works ok. Quoting Christopher Peter Welsh [EMAIL PROTECTED]: Tried the latest src, and still core dumps. Here's my configure args ./configure --with-pam --with-quotas --with-winbind --with-configdir=/etc/samba Here is what version samba-server-3.0.20-3mdk dumps to the log. I installed this on my (32 bit Mandrake 2006.0) laptop, and I have no problems. Any ideas? [2006/01/06 16:43:05, 0] lib/fault.c:fault_report(36) === [2006/01/06 16:43:05, 0] lib/fault.c:fault_report(37) INTERNAL ERROR: Signal 11 in pid 5369 (3.0.20) Please read the appendix Bugs of the Samba HOWTO collection [2006/01/06 16:43:05, 0] lib/fault.c:fault_report(39) === [2006/01/06 16:43:05, 0] lib/util.c:smb_panic2(1548) PANIC: internal error [2006/01/06 16:43:05, 0] lib/util.c:smb_panic2(1556) BACKTRACE: 15 stack frames: #0 smbd(smb_panic2+0x189) [0x55734383] #1 smbd(smb_panic+0xe) [0x557341f8] #2 smbd [0x5571dbbc] #3 smbd [0x5571dc14] #4 /lib64/tls/libc.so.6 [0x2c1a1b60] #5 /usr/lib64/libldap-2.3.so.0(ldap_set_option+0x48) [0x2abe5978] #6 smbd(ads_do_search+0x1ce) [0x5579c9cc] #7 smbd(ads_server_info+0xb4) [0x557a0865] #8 smbd(ads_connect+0xea) [0x5579bc30] #9 smbd(check_published_printers+0xf1) [0x5575fa05] #10 smbd(nt_printing_init+0x46c) [0x55758a5c] #11 smbd(print_backend_init+0x186) [0x557528b1] #12 smbd(main+0x4c9) [0x557bc841] #13 /lib64/tls/libc.so.6(__libc_start_main+0xda) [0x2c18f4fa] #14 smbd [0x555a92ca] Quoting Christopher Peter Welsh [EMAIL PROTECTED]: Hi, I have just installed Mandrake linux x84_64 (64 bit version) on my new dell poweredge server (1850 SMP) I am getting core dumps when trying to join the 2003 AD domain. ie. I run net ads join [EMAIL PROTECTED] running kinit worked ok. I am running samba version 3.0.20 samba-client-3.0.20-3mdk samba-server-3.0.20-3mdk samba-common-3.0.20-3mdk samba-winbind-3.0.20-3mdk Anyone help. I wish to user winbind for proxy auth. Chris Welsh -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Anyone Pls? Domain function levels, etc
Hi, I have resent this, as I have had no replies so far. I'm gonna have to be putting a good argument to my ICT team against going to 2003 in 2003 server mode ( I think thats what they call the highest mode for 2003 server) to keep samba at our school. I like what windows 2003 has to offer, but do not want to lock samba out forever. I know samba will work at lower mode. And that's what I'm pushing. Can people chip in with some arguments and advice. What is the highest 2003 mode (forest and domain) that we can go to and still have samba function as a member file server? What are the advantages for a school with only 2 domains and no geographical displacement in going to the highest 2003 server level (list of GPO advantages?, etc). We have the money to upgrade to 2003 on all our 20 servers(20 win2000 server and 2 samba servers). But could save money by consolidating and mixing samba and 2000. Is there really better security in that higher 2003 mode? What in particular? Will winbind (ADS and kerb mode) break? As we use it for squid auth, etc. How long before SAMBA can work at the highest level with 2003? I'm feeling that MS have provided some functional incentives to go with the highest mode. Can someone suggest some ways to take the hype out this higher level? I know from my reading, that once we make that jump, there is no turning back :-( Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] SAMBA - Domain function levels (resent)
Hi, Re-sent this; sorry, it came from my other account and it was not subscribed to this list. I'm gonna have to be putting a good argument to my ICT team against going to 2003 in 2003 server mode ( I think thats what they call the highest mode for 2003 server) to keep samba at our school. I like what windows 2003 has to offer, but do not want to lock samba out forever. I know samba will work at lower mode. And that's what I'm pushing. Can people chip in with some arguments and advice. What is the highest 2003 mode (forest and domain) that we can go to and still have samba function as a member file server? What are the advantages for a school with only 2 domains and no geographical displacement in going to the highest 2003 server level (list of GPO advantages?, etc). We have the money to upgrade to 2003 on all our 22 servers. But could save money by mixing with samba and 2000. Is there really better security in that higher mode? What in particular? Will winbind (ADS and kerb mode) break? As we use it for squid auth, etc. How long before SAMBA can work at the highest level with 2003? I'm feeling that MS have provided some functional incentives to go with the highest mode. Can someone suggest some ways to take the hype out this higher level? I know from my reading, that once we make that jump, there is no turning back :-( Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Windows XP machine cannot be accessed
FYI John, If you wish to automount shares when you login, you can try pam_mount. It should be a package on the mdk 10.1 CDs. You can set it to mount windows cifs and smb shares to your mandrake box. It's possible because Linux supports pluggable auth modules(PAM) I used it along with winbind auth to mount all my windows shares from servers at work to my Linux mandrake workstation (laptop) When ever I ssh'd in, the shares mounted. It can be set to mount based on preferred authentication system (local password file, winbind, nis, etc) and protocol. ie. mount windows shares if you login via ssh, or even if you login through the kde desktop (warning: kde requires special files relocated when mounting home directories). Having said that and seeing as how you are new, I believe Geoff's solution is a much easier way to go. You may however wish to read up on pam_mount anyway. For more info do a google on pam_mount Chris -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
