Re: [Samba] Printing not working after upgrading to 3.0.4

2004-05-24 Thread Skip Morrow
It's working now.  I think it was a combination of several of these things.  
This was actually a pretty good troubleshooting-samba-printing-in-general 
guide.  The bottom line is, I am now up and printing again.  Your logical 
thought process just pointed me in the Right Direction (tm).

Thanks.

Skip
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Printing not working after upgrading to 3.0.4

2004-05-23 Thread RRuegner
Kurt Pfeifle schrieb:
Skip Morrow skip-samba at pelorus.org
Sat May 22 22:54:26 GMT 2004
I had been running Samba to share my HP printer among my Windows XP 
clients.  When I upgraded to 3.0.4, I can no longer print.  When I 
start the print job in Windows XP, the printer lights blinks for a few 
seconds, and then stops. No pages come out.  The print job is shown as 
complete in the CUPS web intrface.  Printing from the Linux box works 
just fine.  I read the Samba pages concerning printing, and the 
chapter on CUPS, but I don't see anything that could cause this problem. 

I read your mail, but I don't see anything that could cause
your problem.
Please re-post with a few more details.
Tell us about your printer type(s), the driver(s) you use on
the Win clients, which Samba version you was using previously,
what the settings of your smb.conf are (please strip comments),
which CUPS version you use, which OS version your Samba is
installed on, etc.
The share is still listed in smbclient, and I have tried re-installing 
the printer from Windows.  

Cheers,
Kurt
Hi, i had many printing Problems as i upgraded to sernet suse samba rpms
3.04, i now use suse orginal rpms from ftp.suse.com projects samba ( 
which seems now is the valid update path )
and the problems are gone , so it looks like a compile problem to cups 
devel by sernet .. or something like this , this just for info
Regards
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Printing not working after upgrading to 3.0.4

2004-05-23 Thread Skip Morrow
 
  I read your mail, but I don't see anything that could cause
  your problem.
 
  Please re-post with a few more details.
 
  Tell us about your printer type(s), the driver(s) you use on
  the Win clients, which Samba version you was using previously,
  what the settings of your smb.conf are (please strip comments),
  which CUPS version you use, which OS version your Samba is
  installed on, etc.
 
I have an HP, 2100M printer.  The driver that I have loaded in Windows is HP 
Laserjet 2100 Series PS  Unfortunately, I don't have any more information 
about the driver becasue I can't print the test page.  Here are the pertinent 
setting from smb.conf:

[global]
netbios name = PELORUS
server string = samba server
interfaces = 192.168.0.1
bind interfaces only = yes
encrypt passwords = yes
log file = /var/log/samba/%m.log
max log size = 0
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = No
hosts allow = 192.168.0. 127.
printing = cups
load printers = yes
security = SHARE
printcap name = cups
guest ok = yes

[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
public = yes
guest ok = yes
writable = no
printable = yes
printer admin = skip, suzanne, sfm, root, @ntadmin, smorrow

I do not remember what version of Samba I had before.  I installed it so long 
ago, and it worked fine for so long, I really didn't think about it too much.

I am using CUPS version 1.1.20

#printers.conf
DefaultPrinter HP_LJ_2100M
Info HP LaserJet 2100M
Location Pelorus
DeviceURI parallel:/dev/lp0
State Idle
Accepting Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
/Printer

#cupsd.conf
ServerName localhost
Classification none
DefaultCharset UTF-8
DefaultLanguage en
Printcap /etc/printcap
PrintcapFormat BSD
RemoteRoot remroot
SystemGroup sys
ServerCertificate /etc/cups/ssl/server.crt
ServerKey /etc/cups/ssl/server.key
Location /
Encryption IfRequested
Satisfy All
Order deny,allow
Deny From All
Allow From 127.0.0.1
Allow From 192.168.0.*
/Location
Location /admin
AuthType Basic
AuthClass System
Encryption IfRequested
Satisfy All
Order deny,allow
Deny From All
Allow From 127.0.0.1
/Location
HostnameLookups On
KeepAlive On
KeepAliveTimeout 60
MaxClients 100
MaxRequestSize 0m
Timeout 300
Listen *:631
AccessLog /var/log/cups/access_log
ErrorLog /var/log/cups/error_log
PageLog /var/log/cups/page_log
MaxLogSize 1m
LogLevel debug2
PreserveJobHistory On
PreserveJobFiles No
AutoPurgeJobs No
MaxJobs 0
MaxJobsPerPrinter 0
MaxJobsPerUser 0
User lp
Group sys
RIPCache 80m
FilterLimit 0
DataDir /usr/share/cups
DocumentRoot /usr/share/cups/doc
RequestRoot /var/spool/cups
ServerBin /usr/lib/cups
ServerRoot /etc/cups
TempDir /var/spool/cups/tmp
Browsing On
BrowseProtocols CUPS 
BrowsePort 631
BrowseInterval 30
BrowseTimeout 300
BrowseAddress @IF(eth1)
BrowseOrder allow,deny
ImplicitClasses On
ImplicitAnyClasses Off
HideImplicitMembers Yes
BrowseShortNames Yes

# $Id: mime.convs,v 1.17 2002/08/09 00:00:54 mike Exp $
application/pdf application/postscript  33  pdftops
application/postscript  application/vnd.cups-postscript 66  pstops
application/vnd.hp-HPGL application/postscript  66  hpgltops
application/x-cshellapplication/postscript  33  texttops
application/x-perl  application/postscript  33  texttops
application/x-shell application/postscript  33  texttops
text/plain  application/postscript  33  texttops
text/html   application/postscript  33  texttops
image/gif   application/vnd.cups-postscript 66  imagetops
image/png   application/vnd.cups-postscript 66  imagetops
image/jpeg  application/vnd.cups-postscript 66  imagetops
image/tiff  application/vnd.cups-postscript 66  imagetops
image/x-photocd application/vnd.cups-postscript 66  imagetops
image/x-portable-anymap application/vnd.cups-postscript 66  imagetops
image/x-portable-bitmap application/vnd.cups-postscript 66  imagetops
image/x-portable-graymap application/vnd.cups-postscript66  imagetops
image/x-portable-pixmap application/vnd.cups-postscript 66  imagetops
image/x-sgi-rgb application/vnd.cups-postscript 66  imagetops
image/x-xbitmap application/vnd.cups-postscript 66  imagetops
image/x-xpixmap application/vnd.cups-postscript 66  imagetops
image/x-xwindowdump application/vnd.cups-postscript 66  imagetops
image/x-sun-raster  application/vnd.cups-postscript 66  imagetops
image/gif   application/vnd.cups-raster 100 imagetoraster
image/png   application/vnd.cups-raster 100 imagetoraster
image/jpeg  application/vnd.cups-raster 100 imagetoraster
image/tiff  

[Samba] Printing not working after upgrading to 3.0.4

2004-05-23 Thread Kurt Pfeifle
Skip Morrow skip-samba at pelorus.org
Sun May 23 10:47:12 GMT 2004

 I read your mail, but I don't see anything that could cause
 your problem.

 Please re-post with a few more details.

 Tell us about your printer type(s), the driver(s) you use on
 the Win clients, which Samba version you was using previously,
 what the settings of your smb.conf are (please strip comments),
 which CUPS version you use, which OS version your Samba is
 installed on, etc.

I have an HP, 2100M printer.  The driver that I have loaded in Windows is HP 
Laserjet 2100 Series PS.
*How* did you install that driver? And the printer you own is in
fact a PostScript-enabled modell? (Sorry, I don't know by heart
if that 2100M defaults to include PS, or if PS is only an upgrade
option)
If you installed it as a local client driver, you have to use
use client driver = yes in smb.conf (this is not the recommended
setting, but works also).
A locally installed driver (for a shared printer) on the client
can be more exposed with this commandline (in a Samba host shell),
even if the test page isn't printing:
  rpcclient -Uwindowsuser%windowspassword -c enumdrivers 3 windowshostname
This command shows up pretty much the same info as a printed
testpage would do
If you installed it via Point'n'Print, you should be able to
use that command in a Samba host shell:
  rpcclient -Uroot%smbpasswd-of-root -c enumdrivers 3 localhost
Unfortunately, I don't have any more information 
The operating system? Linux? Which distro? Who built the Samba
packages? Is CUPS support compiled into the Samba binaries?
about the driver becasue I can't print the test page. 
See above.
Here are the pertinent 
setting from smb.conf:

Is this the same smb.conf you inherited from your previous Samba
installation?
[global]
netbios name = PELORUS
server string = samba server
interfaces = 192.168.0.1
bind interfaces only = yes
encrypt passwords = yes
log file = /var/log/samba/%m.log
max log size = 0
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = No
hosts allow = 192.168.0. 127.
printing = cups
load printers = yes
security = SHARE
Change that to
security = user
as the Samba HOWTO Collections suggests. (Don't forget to set
Samba passwords with smbpasswd -a root and smbpasswd -a
username)

printcap name = cups
guest ok = yes
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
public = yes
guest ok = yes
writable = no
printable = yes
printer admin = skip, suzanne, sfm, root, @ntadmin, smorrow
I do not remember what version of Samba I had before.  I installed it so long 
ago, and it worked fine for so long, I really didn't think about it too much.

I am using CUPS version 1.1.20
So your old Samba with the same smb.conf setup did work with
CUPS-1.1.20 ??
#printers.conf
DefaultPrinter HP_LJ_2100M
Info HP LaserJet 2100M
Location Pelorus
DeviceURI parallel:/dev/lp0
State Idle
Accepting Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
/Printer
#cupsd.conf
ServerName localhost
This setting doesn't work for any other host as a client.
(It works for Samba, since smbd transmits the file to
cupsd from localhost...).
You should either comment the line out (in which case
cupsd will default to use the hostname for ServerName,
or use ServerName your host's IP address or explicitely
go for ServerName your hostname.
Classification none
DefaultCharset UTF-8
DefaultLanguage en
Printcap /etc/printcap
PrintcapFormat BSD
RemoteRoot remroot
SystemGroup sys
ServerCertificate /etc/cups/ssl/server.crt
ServerKey /etc/cups/ssl/server.key
Location /
Encryption IfRequested
Satisfy All
Order deny,allow
Deny From All
Allow From 127.0.0.1
Allow From 192.168.0.*
/Location
Location /admin
AuthType Basic
AuthClass System
Encryption IfRequested
Satisfy All
Order deny,allow
Deny From All
Allow From 127.0.0.1
/Location
HostnameLookups On
KeepAlive On
KeepAliveTimeout 60
MaxClients 100
MaxRequestSize 0m
Timeout 300
Listen *:631
AccessLog /var/log/cups/access_log
ErrorLog /var/log/cups/error_log
PageLog /var/log/cups/page_log
MaxLogSize 1m
LogLevel debug2
LogLevel debug2 will drown you in error messages. Considering
that you have limited the error_log file size to 1 MByte, this
will effectively prevent you from ever finding anything useful
in the log. 1 MByte of debug2 output fills the file in seconds
before it log-rotates.
Better use
  MaxLogSize 10m
  LogLevel debug
and have all the relevant info at your fingertips. In case there
is really a severe problem, you can always go for debug2 and
50 MByte for a limited period of troubleshooting.
What do you see in the /var/cups/log/error_log as noted when
the job arrives at CUPS? Look for a line containing
   print_job: auto-typing file...
and the following
   print_job: request file type is
What is it?
Also 

[Samba] Printing not working after upgrading to 3.0.4

2004-05-22 Thread Skip Morrow
I had been running Samba to share my HP printer among my Windows XP clients.  
When I upgraded to 3.0.4, I can no longer print.  When I start the print job 
in Windows XP, the printer lights blinks for a few seconds, and then stops. 
No pages come out.  The print job is shown as complete in the CUPS web 
intrface.  Printing from the Linux box works just fine.  I read the Samba 
pages concerning printing, and the chapter on CUPS, but I don't see anything 
that could cause this problem.  The share is still listed in smbclient, and I 
have tried re-installing the printer from Windows.  
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


[Samba] Printing not working after upgrading to 3.0.4

2004-05-22 Thread Kurt Pfeifle
Skip Morrow skip-samba at pelorus.org
Sat May 22 22:54:26 GMT 2004
I had been running Samba to share my HP printer among my Windows XP clients.  
When I upgraded to 3.0.4, I can no longer print.  When I start the print job 
in Windows XP, the printer lights blinks for a few seconds, and then stops. 
No pages come out.  The print job is shown as complete in the CUPS web 
intrface.  Printing from the Linux box works just fine.  I read the Samba 
pages concerning printing, and the chapter on CUPS, but I don't see anything 
that could cause this problem. 
I read your mail, but I don't see anything that could cause
your problem.
Please re-post with a few more details.
Tell us about your printer type(s), the driver(s) you use on
the Win clients, which Samba version you was using previously,
what the settings of your smb.conf are (please strip comments),
which CUPS version you use, which OS version your Samba is
installed on, etc.
The share is still listed in smbclient, and I 
have tried re-installing the printer from Windows.  
Cheers,
Kurt
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba