[Samba] samba print server - unable to change advanced settings from a client machine 3.5.6
Hello, I'm having trouble replacing our old print server (debian sarge) with a new one. When I enable print$ and force user root and give access to nobody, the print$ share is working properly. I can create delete, add files etc from a windows xp machine. What I need now is being able to go to printers and faxes, right click on the printer, go to advanced, and click new driver (this would upload the driver to the server. Unfortunately this does not work as advanced or any other settings are grayed out for me. The config files have same settings so I'm not sure what is the problem here. It works on my old server but it does not work on a new server. Samba version: 3.5.6 : [printers] comment = All Printers browseable = no path = /var/spool/samba guest ok = yes read only = yes create mask = 0700 # Windows clients look for this share name as a source of downloadable # printer drivers [print$] comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = no guest ok = yes write ok = yes write list = nobody, root force user = root Could somebody point me into proper direction here? Am I missing a permission? setting? how do I give access to everybody or nobody guest account to make changes?? Thanks, Lucas -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba print server - unable to change advanced settings from a client machine 3.5.6
On 09/28/2011 12:03 PM, Lukasz Szybalski wrote: Hello, I'm having trouble replacing our old print server (debian sarge) with a new one. When I enable print$ and force user root and give access to nobody, the print$ share is working properly. I can create delete, add files etc from a windows xp machine. What I need now is being able to go to printers and faxes, right click on the printer, go to advanced, and click new driver (this would upload the driver to the server. Unfortunately this does not work as advanced or any other settings are grayed out for me. The config files have same settings so I'm not sure what is the problem here. It works on my old server but it does not work on a new server. Samba version: 3.5.6 : [printers] comment = All Printers browseable = no path = /var/spool/samba guest ok = yes read only = yes create mask = 0700 # Windows clients look for this share name as a source of downloadable # printer drivers [print$] comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = no guest ok = yes write ok = yes write list = nobody, root force user = root Could somebody point me into proper direction here? Am I missing a permission? setting? how do I give access to everybody or nobody guest account to make changes?? Thanks, Lucas Okay, for the newer Samba releases, I think they have made it so you need to use the net command or something similar. In order to get these rights for myself on my setup, I had to run this: /usr/local/bin/net sam rights grant jax SePrintOperatorPrivilege Perhaps some variant of this will work for you -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba print server - unable to change advanced settings from a client machine 3.5.6
On Wed, Sep 28, 2011 at 1:03 PM, Lukasz Szybalski szybal...@gmail.comwrote: Hello, I'm having trouble replacing our old print server (debian sarge) with a new one. When I enable print$ and force user root and give access to nobody, the print$ share is working properly. I can create delete, add files etc from a windows xp machine. What I need now is being able to go to printers and faxes, right click on the printer, go to advanced, and click new driver (this would upload the driver to the server. Unfortunately this does not work as advanced or any other settings are grayed out for me. The config files have same settings so I'm not sure what is the problem here. It works on my old server but it does not work on a new server. Samba version: 3.5.6 : [printers] comment = All Printers browseable = no path = /var/spool/samba guest ok = yes read only = yes create mask = 0700 # Windows clients look for this share name as a source of downloadable # printer drivers [print$] comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = no guest ok = yes write ok = yes write list = nobody, root force user = root Could somebody point me into proper direction here? Am I missing a permission? setting? how do I give access to everybody or nobody guest account to make changes?? Thanks, Lucas Okay, for the newer Samba releases, I think they have made it so you need to use the net command or something similar. In order to get these rights for myself on my setup, I had to run this: /usr/local/bin/net sam rights grant jax SePrintOperatorPrivilege Perhaps some variant of this will work for you Thanks Jack, Here is what needed to be done: http://lists.samba.org/archive/samba/2007-March/129995.html smbpasswd -a root net rpc rights list accounts (enter root password) net rpc rights grant Everyone SePrintOperatorPrivilege Restart samba /etc/init.d/samba restart And we are good to go. Thank you. Lucas -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba Print Server problem
I have CentOS 5 machine with Samba sharing 5 cups printers. The two Canon iR's have no issues, I used the rpcclient method to add print drivers and this works flawlessly. However, the HP 2430N's that I setup work fine as raw cups printers, and I added the drivers the exact same way but when a windows client connects they are promoted for drivers (and they want the compressed files as well, *.dl_ which were never added??) and more often than not a client's explorer will crash if they access those printers? The HP drivers come as an install program and cab files, where as most others are simply dll's etc. Any ideas how to remedy this? Thanks! jlc -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba print server client job queues.
Hello, I'm working on setting up a corporate print server with samba 3.2.0-2.17 on a Fedora 9 install. I've been able to get the services up and running and added several printers via the cups interface, also been able to upload the windows drivers. This all works well, printing also works well. The problem that I am running into is that the old print jobs seem to be getting stored somewhere in samba and i've been unable to figure out how to turn this option off. I've set the PreserveJobHistory No PreserveJobFiles No options in my cupsd.conf file though this does not effect the queues viewed by the clients, only the jobs viewable via the cups interface. Even once the jobs have been manually deleted from the queue and no longer show up when it is opened up, windows still shows job counts in the printers and fax folder. These job counts seem to be getting stored in the /var/lib/samba/printing*.tdb files. If i delete these the print count goes back to 0 but will start counting back up as jobs move through the printer. My smb.conf is very basic [Global] netbios name = twcps01 workgroup = DOMAIN server string = Print Server wins server = x.x.x.x security = user encrypt passwords = yes socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 interfaces = lo eth0 bind interfaces only = yes username map=/etc/samba/smbusers passdb backend=tdbsam null passwords = no hide unreadable = yes hide dot files = yes printcap name = cups printing = cups cups options = raw use client driver = no load printers = yes [printers] comment = All Printers path = /var/spool/samba browseable = no public = yes guest ok = yes writable = no printable = yes [print$] comment = Windows Client Printer Drivers path = /var/lib/samba/windows_printer_drivers browseable = yes guest ok = yes read only = no -- Chris Jeter Senior IT Technician The World Company 785.312.6911 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba print server client job queues.
On Mon, Aug 11, 2008 at 03:05:10PM -0500, Chris Jeter wrote: Hello, I'm working on setting up a corporate print server with samba 3.2.0-2.17 on a Fedora 9 install. I've been able to get the services up and running and added several printers via the cups interface, also been able to upload the windows drivers. This all works well, printing also works well. The problem that I am running into is that the old print jobs seem to be getting stored somewhere in samba and i've been unable to figure out how to turn this option off. I've set the This is a known bug that was fixed for 3.2.1. Sorry for the problem. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba print server client job queues.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Jeter wrote: Hello, I'm working on setting up a corporate print server with samba 3.2.0-2.17 on a Fedora 9 install. I've been able to get the services up and running and added several printers via the cups interface, also been able to upload the windows drivers. This all works well, printing also works well. The problem that I am running into is that the old print jobs seem to be getting stored somewhere in samba and i've been unable to figure out how to turn this option off. This bug was fixed in Samba 3.2.1. cheers, jerry - -- = Samba--- http://www.samba.org Likewise Software - http://www.likewisesoftware.com What man is a man who does not make the world better? --Balian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIoKKOIR7qMdg1EfYRAqktAJ4vLuliGLmkjaVg6g7eOxOW2MXkZQCeM10P JFWdZBeMGuBhQTbr1MJMH8k= =ob1/ -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba print server client job queues.
On Mon, Aug 11, 2008 at 03:05:10PM -0500, Chris Jeter wrote: I'm working on setting up a corporate print server with samba 3.2.0-2.17 on a Fedora 9 install. I've been able to get the services up and running and added several printers via the cups interface, also been able to upload the windows drivers. This all works well, printing also works well. The problem that I am running into is that the old print jobs seem to be getting stored somewhere in samba and i've been unable to figure out how to turn this option off. I've set the PreserveJobHistory No PreserveJobFiles No This is fixed in 3.2.1. See https://bugzilla.samba.org/show_bug.cgi?id=5635 Volker pgp22kdvYBrFo.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Print server
Hello I am setting up Samba as a print server. Is it possible to setup driver auto download without user intervention ?I am looking for Novell's iprint like facility in Samba. Thank you Regards, Komal -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Print server
Hello I am setting up Samba as a print server. Is it possible to setup driver auto download without user intervention ?I am looking for Novell's iprint like facility in Samba. Thank you Regards, Komal -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Print Server
Hiya, Can someone explain why I am seeing chmod of W32X86/3/PSCRIPT5.DLL failed (Operation not permitted) in the log files. It is a samba 3.0.1pre3 print server, which has the drivers on it for loading to the clients. Here is the log file of errors. Thanx in advanced Kris [2003/11/27 16:29:15, 2] smbd/open.c:open_file(250) aclarke opened file W32X86/3/PSCRIPT.HLP read=Yes write=No (numopen=4) [2003/11/27 16:29:15, 2] smbd/close.c:close_normal_file(228) aclarke closed file W32X86/3/PSCRIPT.HLP (numopen=3) [2003/11/27 16:29:15, 2] smbd/open.c:open_file(250) aclarke opened file W32X86/3/PSCRIPT.HLP read=Yes write=No (numopen=4) [2003/11/27 16:29:15, 2] smbd/open.c:open_file(250) aclarke opened file W32X86/3/PSCRIPT.NTF read=Yes write=No (numopen=5) [2003/11/27 16:29:15, 2] smbd/close.c:close_normal_file(228) aclarke closed file W32X86/3/PSCRIPT.NTF (numopen=4) [2003/11/27 16:29:15, 2] smbd/open.c:open_file(250) aclarke opened file W32X86/3/PSCRIPT.NTF read=Yes write=No (numopen=5) [2003/11/27 16:29:15, 2] smbd/open.c:open_file(250) aclarke opened file W32X86/3/PSCRIPT5.DLL read=Yes write=No (numopen=6) [2003/11/27 16:29:15, 2] smbd/trans2.c:call_trans2setfilepathinfo(3105) chmod of W32X86/3/PSCRIPT5.DLL failed (Operation not permitted) [2003/11/27 16:29:15, 2] smbd/close.c:close_normal_file(228) aclarke closed file W32X86/3/PSCRIPT5.DLL (numopen=5) -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Print server
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 11 Mar 2003, Joseph Loo wrote: I rember awhile back someone mention there was a limitiation about 50 printers for samba. Does this still hold true or was it my imagination. tia You're think of a limitation in the 2.2 client rpc code that fails to handle fragmented PDU's. The problem showed up when enmerating more than 50 printers using rpcclient (give or take a few). This does not limit Samba's print server abilities in any way. cheers, jerry -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc You can never go home again, Oatman, but I guess you can shop there. --John Cusack - Grosse Point Blank (1997) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+cjhuIR7qMdg1EfYRAqdiAKC9ucxeTt0+YBmTB5KdO7PVYs/V/ACeK75X b/mRO3H+rL710wqApbsB9dc= =xBVw -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Print server
Thanks. I thought there was a problem. My recolleciton was on the wrong place. Gerald (Jerry) Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 11 Mar 2003, Joseph Loo wrote: I rember awhile back someone mention there was a limitiation about 50 printers for samba. Does this still hold true or was it my imagination. tia You're think of a limitation in the 2.2 client rpc code that fails to handle fragmented PDU's. The problem showed up when enmerating more than 50 printers using rpcclient (give or take a few). This does not limit Samba's print server abilities in any way. cheers, jerry -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc You can never go home again, Oatman, but I guess you can shop there. --John Cusack - Grosse Point Blank (1997) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+cjhuIR7qMdg1EfYRAqdiAKC9ucxeTt0+YBmTB5KdO7PVYs/V/ACeK75X b/mRO3H+rL710wqApbsB9dc= =xBVw -END PGP SIGNATURE- -- Joseph Loo [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Print server
Not to try and break any records, but we have servers that each serve up ~1500 printers under 2.0.X. Needless to say, attempts to upgrade to 2.2 resulted in some difficulty (servers coming nearly instantly to their knees as dozens of Windows boxes attempted to initiate RPC, etc.). But performance under 2.0.X is actually not at all bad. Bill Knox Senior Operating Systems Programmer/Analyst The MITRE Corporation On Wed, 12 Mar 2003, John H Terpstra wrote: Date: Wed, 12 Mar 2003 04:22:33 + (GMT) From: John H Terpstra [EMAIL PROTECTED] To: Joseph Loo [EMAIL PROTECTED] Cc: samba [EMAIL PROTECTED] Subject: Re: [Samba] Samba Print server On Tue, 11 Mar 2003, Joseph Loo wrote: I rember awhile back someone mention there was a limitiation about 50 printers for samba. Does this still hold true or was it my imagination. I guess your imagination - I am sure someone will correct me if I am wrong! I had a site that had well over 100 on one server in the days of samba-2.0.7. - John T. -- John H Terpstra Email: [EMAIL PROTECTED] -- 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
[Samba] Samba Print server
I rember awhile back someone mention there was a limitiation about 50 printers for samba. Does this still hold true or was it my imagination. tia -- Joseph Loo [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Print server
On Tue, 11 Mar 2003, Joseph Loo wrote: I rember awhile back someone mention there was a limitiation about 50 printers for samba. Does this still hold true or was it my imagination. I guess your imagination - I am sure someone will correct me if I am wrong! I had a site that had well over 100 on one server in the days of samba-2.0.7. - John T. -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Success! (was Re: [Samba] samba print server
Hello , I guess I'm talking to myself but I finally got the printer to work changing to security = share. My home directories still require authentication. I guess security = user doesn't permit printers to be active. I'm headed to replace the redhat with gentoo so that I can have just the right amount of software on the server and move my file server to another box with a fat hard drive. I would like to understand why security = user won't permit me to secure the printers. I'm on a private home network of 7 computers so it really doesn't matter with the firewall in place. Here's my smb.conf: #=== Global Settings = [global] # workgroup = NT-Domain-Name or Workgroup-Name workgroup = SLAUGHTERHOUSE # server string is the equivalent of the NT Description field server string = UTILITY # if you want to automatically load your printer list rather # than setting them up individually then you'll need this ; printcap name = /etc/printcap ; load printers = yes # added from doc: ; printing = bsd printcap name = /etc/printcap load printers = yes ; log file = /var/log/samba-log.%m ; lock directory = /var/lock/samba # this tells Samba to use a separate log file for each machine # that connects log file = /var/log/samba/%m.log # Put a capping on the size of the log files (in Kb). max log size = 0 # Security mode. Most people will want user level security. See # security_level.txt for details. ; security = user security = share # You may wish to use password encryption. Please read # ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation. # Do not enable this option unless you have read those documents encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd # Most people will find that this option gives better performance. # See speed.txt and the manual pages for details ; socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names # via DNS nslookups. The built-in default for versions 1.9.17 is yes, # this has been changed in version 1.9.18 to no. dns proxy = no # Share Definitions == [homes] comment = Home Directories browseable = no writable = yes valid users = %S create mode = 0664 directory mode = 0775 # NOTE: If you have a BSD-style print system there is no need to # specifically define each individual printer [printers] comment = All Printers ; path = /var/spool/lpd/lp path = /var/spool/samba browseable = no ; public = yes ; create mode = 0700 ;guest ok = yes # Set public = yes to allow user 'guest account' to print guest ok = no writable = no printable = yes end smb.conf I changed 2 things: I removed the socket line and changed security to share. -- See Ya, Clayton mailto:[EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba print server
Is it possible to create a linux samba based print server to be used
by Windows 98, 2000, and XP home edition?
I've successfully create a linux samba based file server, but I have
not been able to get the print server functional. My printers are an
HP4L (laserjet) and an HP882C (deskjet).
I'm using Red Hat 7.2 and installed samba 2.2.7a
My print shares use the load default process and I use user level
security. The users can get to the home drives but printers just
don't work.
The users are able to print locally.
I tried accessing from another linux machine via samba and it was
unsuccessful.
[2003/02/17 19:23:04, 0] smbd/nttrans.c:call_nt_transact_ioctl(1798)
call_nt_transact_ioctl: Currently not implemented.
[2003/02/17 18:12:10, 0] smbd/nttrans.c:call_nt_transact_ioctl(1798)
call_nt_transact_ioctl: Currently not implemented.
[2003/02/17 18:29:45, 0] smbd/service.c:make_connection(238)
playit (192.168.0.53) couldn't find service ::{2227a280-3aea-1069-a2de-08002b30309d}
[2003/02/17 18:57:40, 0] smbd/nttrans.c:call_nt_transact_ioctl(1798)
call_nt_transact_ioctl: Currently not implemented.
[2003/02/17 19:11:28, 0] smbd/nttrans.c:call_nt_transact_ioctl(1798)
call_nt_transact_ioctl: Currently not implemented.
[2003/02/17 22:24:50, 0] rpc_server/srv_spoolss_nt.c:_spoolss_fcpn(4663)
_spoolss_fcpn: Invalid handle (OTHER)
[2003/02/17 22:24:50, 0] rpc_server/srv_spoolss_nt.c:close_printer_handle(257)
close_printer_handle: Invalid handle (OTHER)
[2003/02/17 22:44:59, 0] lib/util_sock.c:read_socket_data(478)
read_socket_data: recv failure for 4. Error = No route to host
I have only spent about 300 hours on linux, so I'm a newbie.
any help would be appreciated.
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Print Server Problems
My Samba box consists of FreeBSD 4.7-RELEASE. It has samba version 2.2.7a compiled on
it.
The problem i have is printing via windows machines to the samba print share.
the clients can 'print' ie send the data to the samba share where i have got samba
setup to use bsd type printing.
smb.conf lines are
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
guest ok = no
writeable = no
printable = yes
printing = bsd
[lp]
printable = yes
browseable = yes
print command = lpr -s -P %p %s; rm %s
path = /tmp
I have configured lpd with the lines in /etc/printcap as
lp| Samsung Laser ML-4500:\
:lp=/dev/lpt0:sd=/var/spool/output/lpd:\
:if=/var/log/lpd-errs:sh:mx#0:
When the clients print to the printer via samba, the data does get to lpd but checking
the logs it spurts out
--
Feb 15 19:30:51 print lpd[221]: lp: unable to open dfA011print.domain.com('f' line)
Feb 15 19:30:51 print lpd[221]: lp: job could not be printed (cfA011print.domain.com)
---
Does anyone want know what is going on and how to make it print out instead of saying
this error message.
Many thanks
James Read.
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Print Server Problems
Can you print directly from the BSD box using the lp queue?
I ask because you have an oddly named file for your if parameter. That is
supposed to be your print filter.
I suspect, if these jobs are coming from a windows client, they are already
filtered. I would get rid of the if parameter, run checkpc -f, restart lpd,
and try it again.
Joel
On Sat, Feb 15, 2003 at 07:45:15PM -, James Read wrote:
My Samba box consists of FreeBSD 4.7-RELEASE. It has samba version 2.2.7a compiled
on it.
The problem i have is printing via windows machines to the samba print share.
the clients can 'print' ie send the data to the samba share where i have got samba
setup to use bsd type printing.
lp| Samsung Laser ML-4500:\
:lp=/dev/lpt0:sd=/var/spool/output/lpd:\
:if=/var/log/lpd-errs:sh:mx#0:
When the clients print to the printer via samba, the data does get to lpd but
checking the logs it spurts out
--
Feb 15 19:30:51 print lpd[221]: lp: unable to open dfA011print.domain.com('f' line)
Feb 15 19:30:51 print lpd[221]: lp: job could not be printed (cfA011print.domain.com)
---
Does anyone want know what is going on and how to make it print out instead of
saying this error message.
Many thanks
James Read.
--
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
[Samba] Samba print server as part of Win2000 domain, having access issues from winXP
Hello samba gurus, Here is my issue, it may actually be a windows issue but because samba is in the mix I feel like it should be presented here. Here are the three principle players: a) pdcbox - A windows 2000 server box functioning as a PDC (in compatibility mode) b) printbox - a SuSE linux box running Samba 2.2.3a functioning as a print server (with cups) and a WINS server. c) clientbox - An XP Pro machine trying to print. I am logged into clientbox as user tim, which is a user in my Win2K domain. When I attempt to print or look at my available printers I get an access denied message. If I open up printbox in Windows explorer it asks me for a username and password. If I type in my own username and password it fails. If I type in another username and password (just another user in the domain with the same priveledges as myself) it works, after this I can print. What gives? I have verified that my account is valid and no different from the one that works. printbox is configured thusly: [global] workgroup = somedomain security = domain password server = pdcbox map to guest = Bad Password socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY character set = ISO8859-15 os level = 0 local master = yes preferred master = no domain master = no wins support = yes DNS Proxy = no guest account = guest printing = cups encrypt passwords = yes [printers] comment = All Printers path = /var/tmp create mask = 0600 printable = Yes postscript = No browseable = No guest ok = yes [phaser3] path = /var/tmp read only = No create mask = 0600 guest ok = Yes printable = Yes postscript = Yes printer name = phaser3 use client driver = Yes oplocks = No Any help would be appreciated. Regards, Tim MacDonald [EMAIL PROTECTED] __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos More http://faith.yahoo.com -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Print Server on Windows XP/2000 Clients
To Whom This May Concern, Quite honestly, this email is a long-shot in the dark for me, since I'm not sure if this email account is still maintained or not. As I searched at google.com for Samba Print Server this afternoon, I was led to the USENIX site that contained this email link. I'm currently facing an issue which I'm hoping you can be of help. Our network employs Samba as our File and Print server and is enabled for Plain Text Passwords. This works fine with PCs running on Win9x and ME with the installation of the ptxt_on.inf file. However, with the advent of the Windows XP and 2000 systems, I'm having a hard time hooking up our network printers to these XP/2000 clients. Can I have your inputs so I can roll this off? Thanks in advance, Geron
