Displaying 20 results from an estimated 700 matches similar to: "one printer doesn't print under samba"
2003 Dec 01
0
No subject
apply to this (security=domain) case, since auth is via the PDC.
So, shouldn't winbind_lookup_sid() be succeeding. Should I be
trying to track the failure in that code?
In case it's helpful, ldd /usr/sbin/smbd shows:
libdl.so.2 => /usr/lib/libdl.so.2 (0x40017000)
libnsl.so.1 => /lib/libnsl.so.1 (0x4001a000)
libpam.so.0 => /lib/libpam.so.0 (0x40030000)
libc.so.6 =>
2002 Jul 24
1
Print Jobs stuck in queue
Hi,
I have a RedHat7.3 distro running Samba-2.2.3a. I've never had this problem
before 2.2.x versions of samba. I'm using domain security and sharing 2
printers, an HP4050 and Ricoh. Everyone can print fine except that,
seemingly randomly, printjobs end up in the queue as paused (according to
winXPpro and Win98). Nobody can unpause or delete them. The only way to
remove them is to
1999 Jul 21
1
SAMBA digest 2174
Hi Andrew,
As I said, I checked for all the files mentioend and for this printer none
of them exist :(. And this is the problem! :(
Regards,
David Crisp
At 03:57 PM 21/07/99 +0800, Andrew Howell wrote:
>On Wed, Jul 21, 1999 at 12:07:55PM +1000, samba@samba.org wrote:
>>
>> Date: Wed, 21 Jul 1999 11:46:14 +1000
>> From: David Crisp <dcrisp@connect.com.au>
2009 Jan 08
2
cups_async_callback(504) error after upgrade to 3.2.7
Hello there -
I just upgraded to 3.2.7 via an rpm from fedora - running fc6:
# uname -a
Linux yoda.wrenkasky.com 2.6.22.14-72.fc6 #1
SMP Wed Nov 21 15:12:59 EST 2007 i686 i686 i386 GNU/Linux
Since upgrading, I am getting the following every hour or so:
[2009/01/07 15:19:08, 2] printing/print_cups.c:cups_async_callback(504)
cups_async_callback: failed to read a new printer list
There's
2000 Jul 16
0
Samba stopped working.
I have a problem I hope someone can help with.
We are using samba for over a month and have been having no trouble. The
other day I changed the IP address on the other side of our firewall as
well as the ISP assigned DNS address. I then made the changes on the DHCP
server so that all the clients (mixed Win95 and 98) would have the new
address. Since then samba has been down. It seems that
2000 Jul 17
0
Samba is back up
I rolled back all the changes I'd made last week and finally got samba back
up, but I still don't know what the problem was. I think it may have
something to do with name resolution but that is just based on the fact
that the only change I had made to the network was the DNS server. I was
still seeing DNS queries going out from the samba server to the old DNS
even after the change
2004 Apr 26
2
Printing in 3.0.1
Hi,
I'm running samba 3.0.1 on SuSE9, server is configured as member server in a
NT4 controlled domain.
now the problem:
it's possible to upload drivers;
it's possible to set default settings/ setting printer configuration;
Client:
add new printer -> network printer -> browse for network printers , and here
is the problem, the samba isn't shown as a print server,
2010 Jun 01
1
When normality test violate and sample size is large(n=400) can I use t-test
Dears
When normality test violate and sample size is large(n=400) can I use t-test?
best gards kourosh
[[alternative HTML version deleted]]
2003 May 11
2
printing issues - lprng
Hi,
I am running samba and lprng for 4 hp laserjets. Sometimes a
samba print job goes to the wrong printer. Normally everything works just
fine. Shown below is the lprng acct log file enries for the concerned print
job. Please notice that the print job was supposed to go to hp4050-mail,
but ended up in hp8100. Any suggestions are much appreciated.
Thanks
Balagopal
jobstart
2003 Sep 05
0
2.2.8a+Debian woody PDC share permission / print$ wizard does not work as it will
Hy every body,
I try to read all news in this channel before posting but none answer to my
problem...
Let show...
Debian/Woody + samba 2.2.8a acting as PDC, some WinNT clients, roaming
profiles disabled.
The users are all with primary group 106, and are members of other group.
They can log on correctly, quite everythink work fine but...
First,
I defined some share with the option valid users =
2003 Dec 01
0
No subject
for this process is "root", that is correct. The PID 7247 is one of the
users, but the UID shouldn't be "root" and should be the username that was
authenticated during logon.
Anyone have same or similar problem? and how do I prevent this problem
from happening again? I would appreciate any help.
Thanks.
Will Sun
wsun@jpl.nasa.gov
(818) 354-2311
Return-Path:
2017 Jun 06
0
unable to upload printer driver
I can install Kyocera Universal KPDL drivers once i delete the sections:
[PrinterPackageInstallation.x86]
PackageAware=TRUE
CoreDriverDependencies={D20EA372-DD35-4950-9ED8-A6335AFE79F1}
[PrinterPackageInstallation.amd64]
PackageAware=TRUE
CoreDriverDependencies={D20EA372-DD35-4950-9ED8-A6335AFE79F1}
in the OEMSETUP.inf file.
But editing the file invalidates signing.
Am 06.06.2017 um 12:59
2017 Jun 06
2
unable to upload printer driver
Hi Louis,
thank you for your answer.
- the link was already there
- I followed this hints:
https://lists.samba.org/archive/samba/2016-November/204773.html
did the chmod 2775
administrator is part of the PrintOperatorGroup
net rpc rights list privileges SePrintOperatorPrivilege -U "H955\administrator"
getfacl printerdrivers
# file: printerdrivers
# owner: root
# group:
2017 Jun 06
0
unable to upload printer driver
Hmm after another try an windows 7 client 32 and 64 bit can install such
an driver now. Sorry for the noise. :-)
Am 06.06.2017 um 15:10 schrieb Achim Gottinger via samba:
> Please ignore the recommendation, such an driver can not be assigned
> to an printer.
>
> Am 06.06.2017 um 14:54 schrieb Achim Gottinger via samba:
>> I can install Kyocera Universal KPDL drivers once i
2003 Jan 23
0
[iddwb@urbansrv1.pp.asu.edu: ]
This is very frustrating. I have a number of print shares defined in
smb.conf. Some of the printer shares open from the windows interface
and display the correct status. Other open with the message "access
denied" but printing continues to work. I spent an hour going over
the latest smb.conf man page and found two possible solutions:
1) using "dissable spoolss = yes"
2)
2003 Dec 01
0
No subject
<<<<<<<<<<<<<
I connect my homedir from the testserver and start Lotus Notes.
Lotus Notes is infamous for it's sensitivity for 'non-optimal' network
connections. Notes tries to lock certain files and complains immediately if
that fails.
> 3. does the log message always fail at the same offset/count:
> (fcntl_lock: lock failed at offset
2017 Jun 06
2
unable to upload printer driver
Please ignore the recommendation, such an driver can not be assigned to
an printer.
Am 06.06.2017 um 14:54 schrieb Achim Gottinger via samba:
> I can install Kyocera Universal KPDL drivers once i delete the sections:
>
> [PrinterPackageInstallation.x86]
> PackageAware=TRUE
> CoreDriverDependencies={D20EA372-DD35-4950-9ED8-A6335AFE79F1}
>
> [PrinterPackageInstallation.amd64]
2017 Jun 07
0
unable to upload printer driver
Hello Franz,
Out of curisoity I tried to install the old Kyocera Universal drivers we
use since a few years on an other samba server (4.6.5).
Found the old version here
https://www.rz.uni-osnabrueck.de/fileadmin/user_upload/Campuscard/Drucken/Treiber/win8/KyoceraClassicUniversalDriversCertified130315.zip.
It also fails now and the OEMSETUP.INF file also contains an
2006 Jun 20
1
Printer comments and other weirdness
Am running Samba 3.0.20 on SuSE 10.0 and cups as my printer provider. I've
used the cups gui to create a number of printers. They appeared correctly in
my Printers and Faxes folder in Explorer and I uploaded my print drivers
successfully. Now, a few days later, I'm looking at my printers and I notice
that the comments that show up on the print shares themselves still reflect
some old data
2001 Nov 16
2
Unable to print correctly html on Windows Printer (SMB) Share
Hi All,
After connecting a HP DeskJet 950C printer to my NT Server and configuring it as a share printer, I used samba and printconf to connect to it.
I setup the printer in printconf as a Samba (SMB) Printer/Windows Printer (SMB) Share
After restarting the lpd daemon, I can print successfully the ASCII test page and other linux files, e.g. smb.conf, /etc/fstab, etc.
My problem is that I am unable