Just swapped our Solaris SAMBA PDC for a SuSE Linux machine. It's the domain controller as well as print server (via CUPS). It's running SuSE 9.3 with Samba-3.0.20b. The setup is identical to the old Solaris machine, had to re-add all machines to the domain. Has been working OK for 2 days then suddenly some people couldn't print and I can no longer add printers to any XP machine. Nothing has changed in the last couple of days (though obviously something has). When I try to add a printer now as a non-admin user I now get this error: "You do not have sufficient access to your computer to connect the selected printer" When I add as a (domain) admin it asks for a print driver. Previously printers were being added with no problem. Anyone got any ideas? Am a bit desperate. Below is my smb.conf file: [global] workgroup = BOSTON server string = %h log file = /var/log/samba/%m.log load printers = yes printing = cups printcap name = cups domain master = yes domain logons = yes local master = yes preferred master = yes name resolve order = wins lmhosts host bcast wins support = yes os level = 65 encrypt passwords = yes security = user logon script = netlogon.bat logon path = \\%N\profile\%a\%u logon drive = q: socket options = TCP_NODELAY IPTOS_LOWDELAY [profile] comment = User Profiles path = /home/samba_shark/profile browseable = no guest ok = yes writeable = yes [printers] comment = All Printers path = /home/samba_shark/var/spool/public browseable = no public = yes guest ok = yes writable = no printable = yes [print$] comment = Printer Drivers path = /home/samba_shark/drivers browseable = yes guest ok = yes read only = yes write list = root [homes] comment = Home Directories browseable = yes guest ok = no writable = yes [netlogon] comment = Network Logon Service path = /home/samba_shark/%a/netlogon guest ok = yes writeable = no share modes = no This is what is in my drivers dir: . ./WIN40 ./WIN40/0 ./WIN40/0/ljbos1.PPD ./WIN40/0/ljbos2.PPD ./WIN40/0/ljbos3.PPD ./WIN40/0/ADOBEPS4.DRV ./WIN40/0/ADOBEPS4.HLP ./WIN40/0/topdf.PPD ./WIN40/0/PSMON.DLL ./WIN40/0/ICONLIB.DLL ./WIN40/0/lj162.PPD ./WIN40/0/lj163.PPD ./WIN40/0/ricoh.PPD ./WIN40/0/ADFONTS.MFM ./WIN40/ljbos1.PPD ./WIN40/ljbos2.PPD ./WIN40/ljbos3.PPD ./WIN40/ADOBEPS4.DRV ./WIN40/ADOBEPS4.HLP ./WIN40/topdf.PPD ./WIN40/PSMON.DLL ./WIN40/ICONLIB.DLL ./WIN40/lj162.PPD ./WIN40/lj163.PPD ./WIN40/ricoh.PPD ./WIN40/ADFONTS.MFM ./W32X86 ./W32X86/2 -- Michael Keightley <Michael.Keightley@quadstone.com> Tel: +44 131 220 4491 Systems Manager, Quadstone Limited, Fax: +44 131 220 4492 16 Chester Street, Edinburgh EH3 7RA, Scotland http://www.quadstone.com
El mié, 09-11-2005 a las 15:31 -0500, Michael Keightley escribió:> Just swapped our Solaris SAMBA PDC for a SuSE Linux machine. It's the domain > controller as well as print server (via CUPS). It's running SuSE 9.3 with > Samba-3.0.20b. > The setup is identical to the old Solaris machine, had to re-add all machines > to the domain. Has been working OK for 2 days then suddenly some peopleargh... I think that you could migrate/upgrade samba from system and version without needing to re-add all machines to the domain. I made some similiar movement from samba 2.2.8a on Redhat 8 to 3.0.14a on Debian Sarge after some troubles some days ago. I'm actually documenting the movement before post anything here :(> When I try to add a printer now as a non-admin user I now get this error: > > "You do not have sufficient access to your computer to connect the selected printer" > > When I add as a (domain) admin it asks for a print driver. Previously printers > were being added with no problem. > Anyone got any ideas? Am a bit desperate. > > Below is my smb.conf file: > > [global] > workgroup = BOSTON > server string = %h >In theory, you can aggregate a domain user in the local machine users accounts to give access to some administrative rights ( for example, install printers ). May be the local machine is not recognizing the user as a trusted users from the domain ? ( This launches another question: Are the machines really log in the domain? . netlogon script is being created well? Try to delete netlogon.bat in one user and try to begin session on the windows machine again. If netlogon.bat is created again, the domain log on process is OK, if not then your problem could be a bad domain client authentication. HTH ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es