[Samba] Numerous LDAP Queries
Hello All, Since upgrading to Samba 3.0.25 (RHEL4) from 3.0.9 (RHEL4) I've been noticing an increase in the number of ldap queries for group accounts that I have listed as invalid accounts in the smb.conf. The queries occur roughly every two minutes. I have one primary Samba DC and two secondary DC that geographically separate. The queries are generated by the secondary DC's to the primary DC. And I've been noticing numerous queries for what should be the MS Windows BuiltIn groups (S-1-5-32-544 thru S-1-5-31-546). I know it is not much but the frequency of the queries keep the ldap log file quite large (~300Mb/wk). Marcus O. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] The single WINS problem
On Sat, 2005-11-26 at 09:29 +0100, Tomasz Chmielewski wrote: John H Terpstra schrieb: On Friday 25 November 2005 17:41, Andreas Hasenack wrote: Em Sexta 25 Novembro 2005 21:45, John H Terpstra escreveu: With all due respect, I belive that your alarm and concern is a little excessive. What sort of response are you looking for? What are you hoping to achieve from your request? The point is not how often the wins service (or its machine) fails, but what happens to the rest of the network when it does. Considering netbios name resolution is not just about mapping name-IP, but also about locating services (who is the logon server? who is the domain master browser?), a single wins makes the windows network, which is already fragile, even more so. I've seen a wins server fail (kernel panic), and it wasn't pretty to the rest of the network. That failure was not the fault of the WINS server. Certainly the kernel panic wasn't the fault of Samba running WINS, but the consequences point us to the limitations of Samba. Even a single network disruption between WINS/PDC and the rest of your network can cause trouble similar to WINS/PDC kernel panicking. To prevent such cases, where networks are separate (i.e. in different cities) but use a single user database (in LDAP), I just set up PDCs instead of BDCs (they don't see each other via netbios anyway), and each of them is acting as a WINS server. I find it much more resistent to such failures. -- Tomek http://wpkg.org WPKG - software deployment and upgrades with Samba Are you replicating the LDAP database to each network? -- Marcus White [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Cannot get HP1055CM Color Plotter to work with Point and Click
Yes... All of these steps were performed. Before loading the drivers. Were the drivers for your plotter loaded directly on the Windows Workstation? Marcus O. On Thu, 2004-09-23 at 08:33, Olaf Eichhorn wrote: Hi Marcus, Is Your printqueue raw? You have to create one for Yoour Printer. I choosed swat to do that. Than You have to edit two files to allow unknown type of data to be printed via cups. I found this in the mailing list archive 1. Edit /etc/cups/mime.types to uncomment the line near the end of the file that has: #application/octet-stream 2. Do the same for the file /etc/cups/mime.convs. 3. Add a raw printer using the Web interface. Point your browser at http://localhost:631. Enter Administration, add the printer following the prompts. Do not install any drivers for it. Choose Raw. Choose queue name Raw It worked perfect for our HP 450C HPGL plotter. Olaf -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: FW: [Samba] Samba printers print$
On Wed, 2004-07-28 at 11:36, Kyle Miller wrote: My [print$] section is pretty basic (I'm connecting as 'kyle', who is also defined as a printer admin in global. Included global for completeness, even though it's uninteresting.) : [global] workgroup = TESTGROUP netbios name = KYLESMB server string = Samba Server for Testing log level = 4 log file = /var/log/samba/%m.log max log size = 50 dns proxy = No printer admin = kyle show add printer wizard = Yes [print$] comment = Print Driver Auto-Download path = /etc/samba/drivers write list = kyle read only = Yes browseable = No guest ok = No My /etc/drivers/samba looks like this. Only a W32X86 dir, since that's the only platform on which I have clients. [kyle]$ ls -al /etc/samba/drivers total 12 drwxrwxrwt 3 root root 4096 Jul 7 13:42 . drwxr-xr-x 3 root root 4096 Jul 12 15:11 .. drwxrwxrwt 2 root root 4096 Jul 7 13:42 W32X86 Any thoughts? Thanks, Kyle On Wed, 28 Jul 2004 05:37:21 -0400, Marcus White [EMAIL PROTECTED] wrote: BTW... Did you create the directory list similar to this in your drivers directory? [print$]--+ |--W32X86 # serves drivers to Windows NT x86 |--WIN40# serves drivers to Windows 95/98 |--W32ALPHA # serves drivers to Windows NT Alpha_AXP |--W32MIPS # serves drivers to Windows NT R4000 |--W32PPC # serves drivers to Windows NT PowerPC Marcus O. On Tue, 2004-07-27 at 09:56, Kyle Miller wrote: For what it's worth, I too have the same problem, which I posted to the list about a few weeks ago (unfortunately no response). I was following the section of the HOWTO that you linked to below. I think it's possible that there is a missing step in the documentation. I can print to my printer just fine, but cannot upload the drivers using the APW, as documented in the howto, even though my permissions appear to be correct. If anyone might be able to shed some more light on it, I'd sure appreciate it. In my case, details are in my previous email to the list, or I can provide them again. Maybe we can find some similarity between my setup and this guy's setup that leads to the problem. Kyle Please check out this link: http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/printing.html#id2550771 HTH, Marcus O. Do you have a [printers] section defined in the smb.conf file? Which linux printer system (ie cups, lprng, bsd) are you using? Have you tried adding root to the [print$] write list and using the root (admin) account to add drivers? Marcus O. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: FW: [Samba] Samba printers print$
On Wed, 2004-07-28 at 11:36, Kyle Miller wrote: My [print$] section is pretty basic (I'm connecting as 'kyle', who is also defined as a printer admin in global. Included global for completeness, even though it's uninteresting.) : [global] workgroup = TESTGROUP netbios name = KYLESMB server string = Samba Server for Testing log level = 4 log file = /var/log/samba/%m.log max log size = 50 dns proxy = No printer admin = kyle show add printer wizard = Yes [print$] comment = Print Driver Auto-Download path = /etc/samba/drivers write list = kyle read only = Yes browseable = No guest ok = No My /etc/drivers/samba looks like this. Only a W32X86 dir, since that's the only platform on which I have clients. [kyle]$ ls -al /etc/samba/drivers total 12 drwxrwxrwt 3 root root 4096 Jul 7 13:42 . drwxr-xr-x 3 root root 4096 Jul 12 15:11 .. drwxrwxrwt 2 root root 4096 Jul 7 13:42 W32X86 Any thoughts? Thanks, Kyle On Wed, 28 Jul 2004 05:37:21 -0400, Marcus White [EMAIL PROTECTED] wrote: BTW... Did you create the directory list similar to this in your drivers directory? [print$]--+ |--W32X86 # serves drivers to Windows NT x86 |--WIN40# serves drivers to Windows 95/98 |--W32ALPHA # serves drivers to Windows NT Alpha_AXP |--W32MIPS # serves drivers to Windows NT R4000 |--W32PPC # serves drivers to Windows NT PowerPC Marcus O. On Tue, 2004-07-27 at 09:56, Kyle Miller wrote: For what it's worth, I too have the same problem, which I posted to the list about a few weeks ago (unfortunately no response). I was following the section of the HOWTO that you linked to below. I think it's possible that there is a missing step in the documentation. I can print to my printer just fine, but cannot upload the drivers using the APW, as documented in the howto, even though my permissions appear to be correct. If anyone might be able to shed some more light on it, I'd sure appreciate it. In my case, details are in my previous email to the list, or I can provide them again. Maybe we can find some similarity between my setup and this guy's setup that leads to the problem. Kyle Please check out this link: http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/printing.html#id2550771 HTH, Marcus O. FYI... Here is a link to a pdf version of the Samba By Example book. http://us1.samba.org/samba/docs/Samba-Guide.pdf Marcus O. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: FW: [Samba] Samba printers print$
FWIW, this is the procedure that has worked for me with Samba Ver 3.2 and RHEL 3. How are you defining the printers? What does your [print$] section contain in your smb.conf? Marcus O. On Tue, 2004-07-27 at 09:56, Kyle Miller wrote: For what it's worth, I too have the same problem, which I posted to the list about a few weeks ago (unfortunately no response). I was following the section of the HOWTO that you linked to below. I think it's possible that there is a missing step in the documentation. I can print to my printer just fine, but cannot upload the drivers using the APW, as documented in the howto, even though my permissions appear to be correct. If anyone might be able to shed some more light on it, I'd sure appreciate it. In my case, details are in my previous email to the list, or I can provide them again. Maybe we can find some similarity between my setup and this guy's setup that leads to the problem. Kyle Please check out this link: http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/printing.html#id2550771 HTH, Marcus O. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: FW: [Samba] Samba printers print$
BTW... Did you create the directory list similar to this in your drivers directory? [print$]--+ |--W32X86 # serves drivers to Windows NT x86 |--WIN40# serves drivers to Windows 95/98 |--W32ALPHA # serves drivers to Windows NT Alpha_AXP |--W32MIPS # serves drivers to Windows NT R4000 |--W32PPC # serves drivers to Windows NT PowerPC Marcus O. On Tue, 2004-07-27 at 09:56, Kyle Miller wrote: For what it's worth, I too have the same problem, which I posted to the list about a few weeks ago (unfortunately no response). I was following the section of the HOWTO that you linked to below. I think it's possible that there is a missing step in the documentation. I can print to my printer just fine, but cannot upload the drivers using the APW, as documented in the howto, even though my permissions appear to be correct. If anyone might be able to shed some more light on it, I'd sure appreciate it. In my case, details are in my previous email to the list, or I can provide them again. Maybe we can find some similarity between my setup and this guy's setup that leads to the problem. Kyle Please check out this link: http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/printing.html#id2550771 HTH, Marcus O. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: FW: [Samba] Samba printers print$
On Thu, 2004-07-08 at 12:00, samba wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of samba Sent: Wednesday, July 07, 2004 4:37 PM To: [EMAIL PROTECTED] Subject: [Samba] Samba printers print$ I have installed samba on a linux OS suse 8.1. I have a printer installed locally on the machine and it prints ok from linux. I can see the printer in SWAT. The share print$ path = /srv/printers guest ok = yes browsable = yes read only = yes write list = @ntadmin,mm On the linux machine, I have the following path: /srv/printers The following folders are located at this path W32MIPS/ W32PPC/ W32X86/ WIN40/ From the samba manual I am using SAMBA Essentials it explains to upload the drivers by doing the following: -In the printers folder on the samba server, select server properties -Now Click the drivers tab and click the add button. There is no drivers tab or any add button. Can anyone point me in the right direction for using the samba server as a print server! The contents of this email may be confidential or protected from disclosure to other than intended recipients.If it has reached you by mistake, we apologise and request you to advise us by emailing [EMAIL PROTECTED] Thank you. BYTRON cannot accept responsibility for any loss or damage arising from the use of this email or attachments. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.708 / Virus Database: 464 - Release Date: 6/18/04 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.708 / Virus Database: 464 - Release Date: 6/18/04 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.708 / Virus Database: 464 - Release Date: 6/18/04 Please check out this link: http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/printing.html#id2550771 HTH, Marcus O. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Migration succesful , but can't add machine to domain
On Tue, 2004-04-27 at 01:14, LanRol wrote: To rule out the obvious... Did you perform smbpasswd -a root on the PDC? Did you also add admin users = root in your global section? Just curious are you actually using the network address 172.0.0.0 for your setup? Marcus O. No, I didn't add root to smbpasswd, but i don't want to use smbpasswd, I wanna use tdbsam, as well this case there isn't root in smbpasswd, is there? It isn't in global section. Yes, of course, 172.0.0.0, what is wrong, if I know well, it is a private IP range, like 10.x.x.x, well? Regards, Roland Private IP Address ranges are: 10.0.0.0/8 172.16.0.0/16 - 172.31.0.0/16 192.168.0.0/16 Yes, you will need to run smbpasswd -a root. The program will update the appropriate backend. Marcus O. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] (no subject)
On Tue, 2004-04-27 at 19:56, Andrew Phillips wrote: I have currently installed the fedora core onto a box of mine. Along with the fedora core came samba 3.0. I am trying to install and setup the swat util to work on my system but all the help files i can find online tell me to add the following line to my swat file in xinetd.conf: server = /usr/local/samba/bin/swat The problem is there is no /usr/loca/samba directory to be heard of at all. And all attempts to even find a binary for the swat util has turned up nothing to this point. Can anyone please point a lost soul in the direction needed. Thanks! Check to ensure samba swat is installed... rpm -q samba-swat If it is not then you must install it... rpm -Uvh /path-to-rpm/samba-swat*.rpm Marcus O. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba-3 HOWTO and ref. guide - need clarification please - printing chapter
On Tue, 2004-04-27 at 19:38, [EMAIL PROTECTED] wrote: Could someone who is familiar with the book Samba-3 HOWTO and reference guide and who is also familiar with printer setup please give me some advice... I am summarising the procedure for setting up a printer for automatic driver download which is described in chapter 17. There are a couple of processes mentioned that look very similar and I am wondering if both steps are required for correct setup. Chapter 17.7.2 Setting Device Modes on New Printers (page 237) is about setting Device mode on printer Browse to samba's Printers and Faxes folder Properties Connect 7. Go to the Advanced tab; click on Printing Defaults 8. Change the Portrait page setting to Landscape (and back) 9. Make sure to apply changes between swapping the page orientation to cause the change to actually take effect. 10.While you are at it, you may also want to set the desired printing defaults here, which then apply to all future client driver installations on the remaining from now on. Chapter 17.7.4 Always Make First Client Connection as root or printer admin (page 238) also mentions setting a device mode by changing the orientation and setting default printer options but I think this step is talking about doing this in the local Printers Faxes folder, not the samba Printers Faxes folder (I'm not sure) Now all the other users downloading and installing the driver the same way (called Point'n Print) will have the same defaults set for them. If you miss this step you'll get a lot of Help Desk calls from your users, but maybe you like to talk to people. Could somebody please tell me if both these steps are necessary to set device mode and to set default print settings? Or are these the same step only repeated in a different way? If both required, could you tell me, is the second step (chapter 17.7.4) referring to doing this in the local printers folder?? thanks. sorry if this seems obvious to most folks. -peter. Opinions contained in this e-mail do not necessarily reflect the opinions of the Queensland Department of Main Roads, Queensland Transport or Maritime Safety Queensland, or endorsed organisations utilising the same infrastructure. If you have received this electronic mail message in error, please immediately notify the sender and delete the message from your computer. First, will you be using CUPS printing support on the linux server? Using the APW (W2K and up), as described in 17.6.1, works very well for installing and configuring the printer drivers. Once this is performed skip to 17.7.1. I did perform 17.7.2 and 17.7.4. This last step is ensure that your setup is working before you give it to your users to try. Make sure that you read Chapter 18, if you using CUPS printing support. HTH, Marcus O. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] printing without server side drivers
On Tue, 2004-04-27 at 23:54, Gerald (Jerry) Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Cameron wrote: | Is there something I can configure differently so | the driver on CUPS isn't used? There's an new parameter added to 3.0.3rc1 that will allow you to set 'cups options = raw' to pass this onto the CUPS libs. I think this is what you want. cheers, jerry - -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc ...a hundred billion castaways looking for a home. --- Sting -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAjyruIR7qMdg1EfYRAnaDAJ4sy8/+jKg6rzEtuc+ifJQ0AbaWoACfWDyA e40TE6a/leMoMP7mzRbAn3s= =06K5 -END PGP SIGNATURE- You may also want to place use client driver = yes in your [printers] section. Also, if you have the Official Samba-3 HowTo and Ref. book refer to section 18.3.4. Marcus O. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Migration succesful , but can't add machine to domain
On Mon, 2004-04-26 at 16:38, LanRol wrote:
from [EMAIL PROTECTED]
What do your logs tell you?
What do you have for your add machine script = ?
Cheers!
--
my smb.conf is
[global]
workgroup = SOLARSYSTEM
netbios name= Sedna
server string = Samba szerver
wins support= yes
name resolve order = wins lmhosts hosts bcast
socket options = TCP_NODELAY SO_RCVBUF=8192
SO_SNDBUF=8192
os level = 64
local master= yes
preferred master= yes
domain master = yes
domain logons = yes
passdb backend = tdbsam:/etc/samba/passdb.tdb
dos charset = CP852
unix charset= ISO8859-2
case sensitive = no
default case= lower
preserve case = yes
security= user
encrypt passwords = yes
log file= /var/log/samba/log.%m
log level = 3
max log size= 50
hosts allow = 127.0.0.1 172.0.0.0/255.255.255.0
interfaces = eth1 172.0.0.0/255.255.255.0
127.0.0.1
logon path = \\samba\profiles\%U
logon script= %G.cmd
add user script = /usr/sbin/useradd -s /bin/false
'%u'
add group script= /usr/sbin/groupadd '%g' getent
group '%g' |awk -F: '{print $3}'
add user to group script= /usr/bin/gpasswd -a '%u' '%g'
add machine script = /usr/sbin/useradd -d /dev/null -g
machines -s /bin/false -M '%u'
set primary group script= /usr/sbin/usermod -g '%g' '%u'
delete user script = /usr/sbin/userdel '%s'
delete group script = /usr/sbin/groupdel '%g'
delete user from group script = /usr/bin/gpasswd -d '%u' '%g'
...
# smbclient -U% -L localhost
Domain=[SOLARSYSTEM] OS=[Unix] Server=[Samba 3.0.2-SuSE]
Sharename Type Comment
- ---
netlogon Disk login scriptek
installDisk telepitok
works Disk Munkakonyvtar
public Disk Kozos konyvtar
developmentDisk A fejlesztok cuccai
IPC$ IPC IPC Service (Samba szerver)
ADMIN$ IPC IPC Service (Samba szerver)
Domain=[SOLARSYSTEM] OS=[Unix] Server=[Samba 3.0.2-SuSE]
Server Comment
----
SEDNASamba szerver
WorkgroupMaster
----
SOLARSYSTEM SEDNA
# smbclient //sedna/netlogon -u admin
session setup failed: NT_STATUS_LOGON_FAILURE
and log file shows:
[2004/04/26 21:37:17, 3] smbd/sec_ctx.c:push_sec_ctx(256)
push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 1
[2004/04/26 21:37:17, 3] smbd/uid.c:push_conn_ctx(287)
push_conn_ctx(0) : conn_ctx_stack_ndx = 0
[2004/04/26 21:37:17, 3] smbd/sec_ctx.c:set_sec_ctx(288)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 1
[2004/04/26 21:37:17, 3] smbd/sec_ctx.c:pop_sec_ctx(386)
pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 0
[2004/04/26 21:37:17, 3] auth/auth.c:check_ntlm_password(219)
check_ntlm_password: Checking password for unmapped user
[EMAIL PROTECTED] with the new password interface
[2004/04/26 21:37:17, 3] auth/auth.c:check_ntlm_password(222)
check_ntlm_password: mapped user is: [EMAIL PROTECTED]
[2004/04/26 21:37:17, 3] smbd/sec_ctx.c:push_sec_ctx(256)
push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 1
[2004/04/26 21:37:17, 3] smbd/uid.c:push_conn_ctx(287)
push_conn_ctx(0) : conn_ctx_stack_ndx = 0
[2004/04/26 21:37:17, 3] smbd/sec_ctx.c:set_sec_ctx(288)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 1
[2004/04/26 21:37:17, 3] smbd/sec_ctx.c:pop_sec_ctx(386)
pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 0
[2004/04/26 21:37:17, 3] auth/auth_sam.c:check_sam_security(200)
check_sam_security: Couldn't find user 'root' in passdb file.
[2004/04/26 21:37:17, 3] auth/auth_winbind.c:check_winbind_security(80)
check_winbind_security: Not using winbind, requested domain [SOLARSYSTEM]
was for this SAM.
[2004/04/26 21:37:17, 2] auth/auth.c:check_ntlm_password(312)
check_ntlm_password: Authentication for user [root] - [root] FAILED with
error NT_STATUS_NO_SUCH_USER
[2004/04/26 21:37:17, 3] smbd/process.c:timeout_processing(1104)
timeout_processing: End of file from client
[Samba] SID differs for net getlocalsid and net rpc info
G'day All, I'm running Samba 3.0.2 on RHL9. Should the commands net getlocalsid and net rpc info return the same SID? If they should agree, how should get the net rpc info to agree with net getlocalsid? Marcus O. 2nd time 'round -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Panic in Samba 3.0.3Pre2
On Tue, 2004-04-20 at 16:36, Gerald (Jerry) Carter wrote: Jeramy Eling wrote: [2004/04/20 15:21:02, 0] lib/util.c:smb_panic2(1406) BACKTRACE: 27 stack frames: #0 smbd(smb_panic2+0x128) [0x81cb288] #1 smbd(smb_panic+0x19) [0x81cb159] #2 smbd [0x81b96f2] #3 /lib/tls/libc.so.6 [0x420275c8] #4 /lib/tls/libc.so.6(malloc+0x8b) [0x4207335b] ^^ #5 smbd(tdb_unpack+0x13b) [0x81e0b8b] #6 smbd [0x81f10ce] #7 smbd [0x81f1cd6] #8 smbd(get_a_printer+0x126) [0x81f3026] #9 smbd(_spoolss_getprinterdataex+0x1be) [0x8131dce] This points towards a heap corruption bug. Doesn't ring a bell. Cna you reproduce this at will ? If so what do I need to do ? 3.0.3rc1 will be out later today we hope. And while I can't say that for sure that this bug is addressed, you should test. We will also be spending a good bit of time stressing this release under valgrind before we hit 3.0.3. -- cheers, jerry -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc ...a hundred billion castaways looking for a home. --- Sting I've also noticed this behavior with RHL9 and Samba 3.0.2a.. It occurred each time I attempted to install a Samba networked printer on a Windows 98se workstation. Steps taken: 1) Installed and modified KDE's pdfdistiller script into /usr/local/sbin 2) cd /usr/lib/cups/backend 3) ln -s /usr/local/sbin/pdfdistiller pdf 4) d/l copied Adobe distiller.ppd file to /usr/share/cups/model 5) d/l installed CUPS Adobe postscript drivers to /usr/lib/cups/drivers 6) Restarted CUPS and Samba 7) Used lpadmin to created pdfwriter printer 8) Used cupsaddsmb to install pdfwriter drivers 9) From W98se PC: right click on pdfwriter printer icon. Select Install. The installer errors out. 10) The smbd error is noted in client machine error log. Ideas? Suggestions? Marcus O. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] No local SID -- net getlocalsid fails
On Sun, 2004-04-18 at 01:37, John Arthur wrote: Hi, I'm trying to get Samba 3.0.2a running on a redhat 9 system. No matter how long I leave samba running it fails to generate a local SID for my network and I'm stumpped. The following is a dump of my smb.conf [EMAIL PROTECTED] samba]# net getlocalsid [2004/04/18 14:59:21, 0] utils/net.c:net_getlocalsid(422) Can't fetch domain SID for name: OMEGA Regards John [EMAIL PROTECTED] samba]# testparm Load smb config files from /etc/samba/smb.conf Processing section [homes] Processing section [printers] Loaded services file OK. Server role: ROLE_DOMAIN_PDC Press enter to see a dump of your service definitions # Global parameters [global] workgroup = FOXY netbios name = RALPH server string = PDC [Samba %v] interfaces = 172.30.128.0/17, 172.30.64.0/18 passdb backend = tdbsam log level = 10 log file = /var/log/samba/log.%m max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 domain logons = Yes os level = 33 preferred master = Yes domain master = Yes wins support = Yes hosts allow = 172.30., 127. [homes] comment = Home Directories read only = No browseable = No [printers] comment = All Printers path = /var/spool/samba printable = Yes Try using 'net rpc info. Also, which computer is/was named OMEGA? Was this the original name of the server? Marcus O. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] No local SID -- net getlocalsid fails
On Mon, 2004-04-19 at 07:31, John Arthur wrote: Hi Marcus, The name OMEGA was just from a previous test. I do not know if I found the problem but after I added a user with smbpasswd it started working! ie; smbpasswd -a fred Regards John Try using 'net rpc info. Also, which computer is/was named OMEGA? Was this the original name of the server? Marcus O. Excellent!!! Glad it worked out... Just curious... Did you run net rpc info prior to adding a user? If so, did it return the proper SID? Marcus O. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Setting up Point 'n' Print
On Wed, 2004-04-14 at 13:36, Dustin Dortch wrote: I am having some problems with uploading printer drivers. I follow the procedures as outlined in both TOSHARG and Samba-3 by Example, and I use the Add Printer Drivers Wizard to upload the drivers. It looks OK, and the drivers make into the \\server\print$\W32X86\3 directory. But when I click okay, I get Printer settings could not be saved. Access is denied. This happens when changing any other settings as well. I am doing this as a printer admin, and I have set the directories and printing related .tdb's to 777 for testing. I tried to use the rpcclient and it returns WERR_ACCESS_DENIED. I am really lost. Using Samba 3.0.2a and Slackware-current. Dustin A Dortch Network+, MCSA/MCSE W2K [EMAIL PROTECTED] _ Limited-time offer: Fast, reliable MSN 9 Dial-up Internet access FREE for 2 months! http://join.msn.com/?page=dept/dialuppgmarket=en-usST=1/go/onm00200361ave/direct/01/ Check to make sure that the use client driver is set to no on the printer shares. I ran into a similar problem recently. Marcus O. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba-latest and tdbsam - unable to logon to domain?
Try setting the bind interfaces only to no Marcus O. On Wed, 2004-04-14 at 04:07, Eddie Lania wrote: Dear list members, I am unable to logon to the domain. I have created the tdbsam using the smbpasswd -a root command. I also added User Administrator as unix and samba account. I also mapped groups Domain Admins, Domain users and Domain Guests to unix groups domadmins, domusers and domguests using the net groupmap modify command. But is doesn't work. I cannot join a XP professional ws to the domain, I keep getting the message that the domain controller cannot be found. I am able to open the netlogon share from the ws when I am logged on the ws as a local Administrator, but that's about all I can do. Please help me! See below my smb.conf: [global] netbios name = C733LINUX workgroup = TECHDREAM server string = Samba 3.0 server security = user passdb backend = tdbsam encrypt passwords = Yes null passwords = Yes admin users = @Domain Admins guest account = Guest socket address = 192.168.169.192 interfaces = 192.168.169.192/24 bind interfaces only = True hosts allow = 127.0.0.1, 192.168.169.0/24, 192.168.168.0/24 ; add user script = /usr/sbin/useradd %u ; add group script = /usr/sbin/groupadd %g add machine script = /usr/sbin/adduser -n -g computers -c Computer -d /dev/null -s /bin/false %u ; delete user script = /usr/sbin/userdel %u ; delete user from group script = /usr/sbin/deluser %u %g ; delete group script = /usr/sbin/groupdel %g # wins partners = 192.168.168.150 wins support = Yes name resolve order = wins lmhosts host bcast os level = 64 prefered master = True domain master = True local master = Yes browse list = Yes enhanced browsing = Yes remote announce = 192.168.168.150 domain logons = Yes logon path = \\%L\profiles\%U logon drive = q: logon home = \\%L\%U\.profile logon script = login.bat socket options = TCP_NODELAY=1 debug uid = Yes log file = /var/log/samba/%m.log ; log level = 0 max log size = 0 pid directory = /var/run printing = cups printer admin = @Domain Admins [netlogon] comment = Network Logon Service path = /home/netlogon nt acl support = No read only = Yes guest only = Yes [homes] path = /home/users/%U valid users = @Domain Users, @Domain Admins read only = No browseable = No inherit acls = Yes inherit permissions = Yes csc policy = disable [profiles] comment = User Profiles share path = /home/profiles valid users = @Domain Users, @Domain Admins read only = No inherit acls = Yes inherit permissions = Yes csc policy = disable [printers] path = /var/spool/samba valid users = @Domain Users, @Domain Admins browseable = No printable = Yes guest ok = Yes ; print command = lpr -P %p -o raw %s -r ; lpq command = lpstat -o %p ; lprm command = cancel %p-%j [print$] path = /usr/local/samba/printers read only = Yes valid users = @Domain Admins write list = @Domain Admins, root guest ok = Yes [users] comment = Users directories path = /home/users valid users = @Domain Users, @Domain Admins read only = Yes write list = @Domain Admins inherit acls = Yes inherit permissions = Yes [public] comment = Public Files share path = /mnt/big_f32/public valid users = @Domain Users, @Domain Admins force user = nobody read only = No [apps] comment = Applications share path = /mnt/big_f32/apps valid users = @Domain Users, @Domain Admins force user = nobody read only = No -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba Outlook Express
If you are using roaming profiles the OE mailbox files will follow the user no matter which workstation that they login on. The drawback is that those files can get rather large depending on email and their associated attachments, which will mean longer load and save times. This is also true if you were to setup an IMAP server, unless you setup OE to only sync the headers and not the full message. The single most important advantage with an IMAP server is that messages are managed on the server. So if the OE mailbox(es) becomes corrupt deleting the local file and re-syncing will restore the messages locally to the user. HTH, Marcus O. On Tue, 2004-04-13 at 16:58, Ninja wrote: I will go to explain my situation: I have to set up a little net (max 15 clients, with Windows and Linux OS) for a school; they need that in every host of the net if they log in as FOO they can use FOO's preferences, and maybe have some restriction for student user. In particular for a teacher they want to be able to read their emails and get access to them in every computer they log in... To make this plain I have use samba as a PDC with roaming profiles, and I use poledit to create different policy files for every groups (I'm still working on it). Because the teachers would be little in number and because only a teacher would have an email account (with a free provider,probably different), I think that set up an Imap server is not a good solution (also because a teacher maybe would read the email at home)... I think I will use the default setup of Outlook that save a file in the user directory, that is then stored in the server, and setup Outlook to leave on the server the emails What do you think?? Thanks to everyone is helping me!! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexander Gretencord Sent: Tuesday, April 13, 2004 9:21 PM To: [EMAIL PROTECTED] Subject: Re: [Samba] Samba Outlook Express On Tuesday 13 April 2004 18:46, Ninja wrote: I'm agree with you, but not always you can use an Imap server, an usually who gives you an e-mail account for free gives only an Pop3 server... Yes indeed that is mostly true. But why do you use those anyway? As I understood you, you are trying to set up a PDC with samba (or even already have one) so I assume this is for a company. This company can surely either a) afford a service Provider which offers IMAP b) afford to run its own mailserver c) run its own IMAP Server off the samba PDC In case c) your server must of course fetch all the mail from the freemail provider. I do that for my own freemail accounts at home with fetchmail. It was born out of the need to read mail in Windows and Linux while I was still dual booting so yes this is so easy to setup, I did it as a linux newbie :) As I don't know anything about your organisation I don't know how feasible that is for you or how much work it would be to set up fetchmails configuration in a changing environment but hey this is linux and we got scripting languages :) If you are just looking for another mail Client, try out Mozilla Thunderbird, you can define the profile path. I have never tested storing it on a samba share though, as IMAP is the definite answer. Alex -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Restricting printer views
Or set load printers = no and define the printers as suggested. Marcus O. On Mon, 2004-04-12 at 16:23, Matthias Spork wrote: Hello Ryan, [EMAIL PROTECTED] schrieb: So when a client maps the print server (ie: \\printserver) then all the printers are displayed, available for point print. How do you hide printers from specific users? We have academic printers and administrative printers. Academic users should not be able to see administrative printers and vice versa. You can apply every printer as an own share. [HP-Drucker] printer name = hp1 valid users = max moritz ... Futher, you can hide a printer with browseable = no. matze -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Initial samba + ldap howto
Check out... http://sapiens.wustl.edu/~sysmain/info/openldap/openldap_configure.html for starters. Unless LDAP is configured properly nothing else will work. Then go to this one http://www.unav.es/cti/ldap-smb/smb-ldap-3-howto.html Marcus O. On Mon, 2004-04-12 at 12:33, John Schmerold wrote: Wim, Thanks for this information . Later this week, I'm scheduled to attempt installation of SAMBA+LDAP using the by Example book. I'll let you know how it goes. They by Example books seems better than the How-To in terms of practical information needed to get a server up and running. Only problem with the by Example book is that it's a bit long. In addition, it does the same thing every other Linux book does, that is it goes into detail about too many approaches to doing things. When I searched for the word Linux on Amazon, I came up with 3,735 books. I wish one of them specifically outlined how to do what I want done, that is a book the helps me configure a SBS (microsoft small business server) replacement. I may be missing something, but in essence it would be a series of books: Replacing SBS with Linux (second edition): 1. Download install Fedora 2. Install LDAP and configure for use with SAMBA postfix 3. Download install Samba 4. Download install postfix/courier/squirrelmail 5. Download install ClamAV/Spam Assassin/TDMA 6. Download install Apache 7. Keeping system up to date with YUM 8. Appendix 1 - Updating first edition of this book Replacing linksys with Linux 1. Configuring netfilter 2. Configuring VPN - Server 3. Configuring VPN - Client 4. Download install dansguardian. 5. Configure PPPOE There could be different books for different distributions. Most people reading (myself included) don't care about many of the decisions. For example I don't care about Fedora vs SUSE vs Debian, I am going with Fedora at this time because I wanted ACLs found in Kernel 2.6. I don't care about Courier vs Dovecot. I do care about LDAP because this is the holy grail of system administration, with LDAP, you can have a central addressbook / accout store etc just like NWAdmin or Domain manager. John Wim Bakker wrote: A couple of days ago I decided that I needed a samba and ldap setup. After reading the samba mailing list , specifically the thread Re: [Samba] Samba and LDAP backend - howto docs problems? I decided to buy the Official Samba-3 HowTo and Reference guide, (the Samba-3 By Example mentioned in that thread wasn't available in my bookstore and they could't order it for me too) expecting to find a workable example for a setup, as I made out more or less from the remarks in that thread there would be, chapter 2 specifically. That chapter has an example (page 26) but I wouldn't recommend to actually use it, it's very limited and inaccurate, lacks information of what more is needed, which additional system packages etc. It says in the beginning that a functioning os is assumed , but that's rather vague on what implies a functioning os. From page 136 on there are some more examples of ldap pwdbackend, but hardly sufficient. http://www.unav.es/cti/ldap-smb-howto.html contains some sketchy info on how to get samba-3 and ldap working, but that document seems to be incomplete and transitioning from samba-2 to samba-3. One of the posters on the aforementioned thread remarked that an accurate, complete into detail, config file is a great help for learning to grasp what has to be done , and how things work together, I agree and following are the steps I took to get a working samba-3 + ldap install. I hardly know anything of linux or samba , let alone ldap , but from the mailling list I understood that the following is neccessary: A goal: get samba + ldap on slackware 9.1 with support for acl's in a usable state working. The means: slackware-9.1 acl-2.2.22.src.tar.gz attr-2.4.14.src.tar.gz ea+acl+nfsacl+sec-2.4.24-0.8.69.diff.gz linux-2.4.24.tar.gz coreutils-5.0-attr+acl.tar.gz nss_ldap.tgz pam_ldap.tgz perl-5.8.3.tar.gz openldap-2.1.19.tgz ldap-account-manager_0.4.5.tar.gz Linux-PAM-0.77.tar.bz2 openssl-0.9.7d.tar.gz db-4.2.52.tar.gz samba-3.0.2a.tar.gz smbldap-tools-0.8.4.tgz I made the following install and configs, I don't know how correct or secure or unneccessary they were, in the end I had a complete and correct funcioning ldap + samba setup, that was usable.It was especially frustrating to get tls connection working, it kept failing with the following error: TLS: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca s3_pkt.c:1052 samba and ldap run on the same server. Besides the documented config for slapd: (etc/openldap/slapd.conf) TLSCertificateFile /etc/ssl/certs/smb.ahm.nl.pem TLSCertificateKeyFile /etc/ssl/keys/smb.ahm.nl.key TLSCACertificateFile/etc/ssl/certs/ca.pem quite important it is allso that ldap knows how to verify: (/etc/ldap.conf symlink to
[Samba] SID differs for net getlocalsid and net rpc info
G'day All, I'm running Samba 3.0.2 on RHL9. Should the commands net getlocalsid and net rpc info return the same SID? If they should agree, how should get the net rpc info to agree with net getlocalsid? Marcus O. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
