Hi Guys,
I've have an issue (or perhaps more accurately a feature) with my
production system running Samba 3.0.24 (Cups 1.2.9). We do not make use
of server side print drivers, the reason for this is below. We therefore
install drivers manually on our client systems. The issue that has
arisen lat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marcio Garcia wrote:
> Dear,
>
>I tried to configure my Samba Server just to print, but i had some
> problems:
>
>In Windows 2000 everything works nicely, but in windows 98 i can't
> see the printer of my Samba Server and i really don't know
Dear,
I tried to configure my Samba Server just to print, but i had some
problems:
In Windows 2000 everything works nicely, but in windows 98 i can't
see the printer of my Samba Server and i really don't know why.
The printer that a configures its: LaserJet-2200
My OS its: Debia
Joy is me! Upgrading to 3.0.9 (from 3.0.7) quashed the print properties
dialog problem I was seeing.
FYI,
Chuck Theobald
System Administrator
The Robert and Beverly Lewis Center for Neuroimaging
University of Oregon
P: 541-346-0343
F: 541-346-0345
--
To unsubscribe from this list go to the follo
Further information on this issue includes output from my smblog file:
[2004/12/08 11:48:13, 2] passdb/pdb_ldap.c:init_sam_from_ldap(485)
init_sam_from_ldap: Entry found for user: chuck
[2004/12/08 11:48:13, 2] passdb/pdb_ldap.c:init_ldap_from_sam(864)
init_ldap_from_sam: Setting entry for user
Chuck Theobald schrieb:
Hi All,
I finally signed up for the list after years of using Samba
successfully - a testament to the quality of Samba. Yet now I have a
problem with the point-and-print functionality. I am able to
authenticate against my server (Solaris 8, Samba 3.0.7, OpenLDAP
2.1.25
Hi All,
I finally signed up for the list after years of using Samba successfully -
a testament to the quality of Samba. Yet now I have a problem with the
point-and-print functionality. I am able to authenticate against my server
(Solaris 8, Samba 3.0.7, OpenLDAP 2.1.25) as user 'chuck' in my L
Hi,
could it be that recent versions of samba have some problems when
collaborating with LPRng? I have a bunch of windows clients printing
via Samba and LPRng and ran into the following problems:
- In my environment it is desirable that people can kill other
people's print jobs. LPRng is config
