Re: [opensuse] setting up SMB printer using Yast - Suse 11.1
Hello, On Jul 30 11:31 jdd (kim2) wrote:
Could you describe more explicite what you mean. Is "most of the time" just your personal experience or could you provide information about possible reasons why it does not work "most of the time" - i.e. what changes from time to time so that it does sometimes work but most of the time it does not work. I ask because I am not in a Windows-like environment so that I like to learn what I must have in mind when I re-implement it. If it does not work I would like to show a meaningful error message to the user instead of leaving the user alone with an empty list of remote SMB printer shares. I am not talking about autodetection of the actual printer "behind" a remote SMB printer share. I only like to autodetect the values of remote SMB printer shares i.e. SMB host name, SMB printer share name, SMB workgroup. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
Johannes Meixner a écrit :
"detect server" on *network* printer never worked for me - and anyway the YaST terminology is so cryptic I wonder if anybody understand it most of the time (not to say always) the socket://ip:9100 gives access to the printer though
I ask because I am not in a Windows-like environment so that I like to learn what I must have in mind when I re-implement it.
I don't anymore have windows shared printers, but used to have I always wonder how work a smb network, because it's completely unpredicable. Usually it works better from linux than from windows (at leas in linux we have debugging tools) for example, just now (I have a windows machine open), in konqueror, smb:/ gives an error (no group found), when smb://192.168.0.13/ gives access to the computer I have to type smb:/192.168.0.13/ (only one "/" before the 192), and the second come automatically. If I type smb://, I get my root folder... Under windows, when it works (!), one can browse the net and if he find a printer can install it directly, very handy jdd -- http://www.dodin.net http://valerie.dodin.org http://news.opensuse.org/2009/04/13/people-of-opensuse-jean-daniel-dodin/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Jul 30, 2009 at 12:13:11PM +0200, Johannes Meixner wrote:
The majority of issues are caused by a non working name resolution. Even if Microsoft is DNS aware since quite some time a lot of the name resolution in smaller (Microsoft) networks is still done by NetBIOS over IP name service requests. Therefore starting the nmb service - which is part of the package named samba - by calling service nmb start might lower the pain, delay, or waiting time while looking for printing resources in a Microsoft Windows environment. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Lars Müller a écrit :
on my config, it's always started jdd -- http://www.dodin.net http://valerie.dodin.org http://news.opensuse.org/2009/04/13/people-of-opensuse-jean-daniel-dodin/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Jul 30, 2009 at 12:13:11PM +0200, Johannes Meixner wrote:
Therefore starting the nmb service - which is part of the package named samba - by calling service nmb start ~~~~~~~ Thank you for the feed back. On a similar topic, if I have jobs stuck in the print queue, how can I force the jobs to be printed or send the queued jobs to another printer? When testing remote SMB access from Yast the printer is accessible, however the jobs are still stuck in the queue. Many thanks for your help. James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I recently installed VMware Player 2.5.2 that I downloaded directly from the www.vmware.com website. The install went fine and the player works great. However, since installing it I now get a pop-up box each and every time I run any program. The dialog states: "An error occurred while loading or saving configuration information for slab. Some of your configuration settings may not work properly." I can then press "Details" or "OK". Pressing "Details" provides the following error message: "Bad key or directory name: "/desktop/gnome/url-handlers/": Key/directory may not end with a slash '/'" This only occurred after installing the VMware Player. Does anyone know how I can eliminate this error message besides uninstalling VMWare Player. While I'm not a fan of Windows, I am currently required to use Internet Explorer for accessing information from ACS, a partner of Novell. Any help would be greatly appreciated. OpenSUSE 11.1 2.6.27.25-0.1-pae #1 SMP 2009-07-01 15:37:09 +0200 i686 i686 i386 GNU/Linux -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello, On Jul 30 09:35 James D. Parra wrote (shortened):
On a similar topic, if I have jobs stuck in the print queue, how can I force the jobs to be printed
I cannot guess why they are "stuck in the print queue" in your particular case. Perhaps http://en.opensuse.org/SDB:CUPS_in_a_Nutshell "The Backends" which is a usual reason might help in your particular case too: ----------------------------------------------------------------- If the data transmission to the recipient fails (usually after several attempts by the backend), the backend will report an error to the print system (more precisely, to cupsd). The backend decides if and how many attempts make sense before it reports that the data transmission has failed. As further attempts would be futile, cupsd disables printing on the affected queue. After eliminating the cause of the problem, the system administrator must reenable printing with /usr/bin/enable (for CUPS 1.1 - i.e. up to Suse Linux 10.1) or with cupsenable (since CUPS 1.2 - i.e. since openSUSE 10.2). -----------------------------------------------------------------
or send the queued jobs to another printer?
Use /usr/sbin/lpmove as root, see "man lpmove". As normal user it might help to run it as /usr/sbin/lpmove -U root oldprinter-123 newprinter Regarding "-U root" compare "man cancel": ----------------------------------------------------------------- Administrators wishing to prevent unauthorized cancellation of jobs via the -u option should require authentication for Cancel-Jobs operations in cupsd.conf(5). ----------------------------------------------------------------- and note in particular "CUPS-Move-Job" at http://www.cups.org/documentation.php/doc-1.3/policies.html
When testing remote SMB access from Yast the printer is accessible, however the jobs are still stuck in the queue.
Have a look at http://en.opensuse.org/SDB:Printing_via_SMB_(Samba)_Share_or_Windows_Share how you may debug it further and you may also have a look at https://bugzilla.novell.com/show_bug.cgi?id=503772#c5 and regarding the special case of percent-encoding which is required for special characters in the DeviceURI see the "By the way" section in https://bugzilla.novell.com/show_bug.cgi?id=512549#c1 Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Jul 30 09:35 James D. Parra wrote (shortened):
On a similar topic, if I have jobs stuck in the print queue, how can I force the jobs to be printed
I cannot guess why they are "stuck in the print queue" in your particular case. Perhaps http://en.opensuse.org/SDB:CUPS_in_a_Nutshell "The Backends" which is a usual reason might help in your particular case too: ----------------------------------------------------------------- If the data transmission to the recipient fails (usually after several attempts by the backend), the backend will report an error to the print system (more precisely, to cupsd). The backend decides if and how many attempts make sense before it reports that the data transmission has failed. As further attempts would be futile, cupsd disables printing on the affected queue. After eliminating the cause of the problem, the system administrator must reenable printing with /usr/bin/enable (for CUPS 1.1 - i.e. up to Suse Linux 10.1) or with cupsenable (since CUPS 1.2 - i.e. since openSUSE 10.2). -----------------------------------------------------------------
or send the queued jobs to another printer?
Use /usr/sbin/lpmove as root, see "man lpmove". As normal user it might help to run it as /usr/sbin/lpmove -U root oldprinter-123 newprinter Regarding "-U root" compare "man cancel": ----------------------------------------------------------------- Administrators wishing to prevent unauthorized cancellation of jobs via the -u option should require authentication for Cancel-Jobs operations in cupsd.conf(5). ----------------------------------------------------------------- and note in particular "CUPS-Move-Job" at http://www.cups.org/documentation.php/doc-1.3/policies.html
When testing remote SMB access from Yast the printer is accessible, however the jobs are still stuck in the queue.
Have a look at http://en.opensuse.org/SDB:Printing_via_SMB_(Samba)_Share_or_Windows_Share how you may debug it further and you may also have a look at https://bugzilla.novell.com/show_bug.cgi?id=503772#c5 and regarding the special case of percent-encoding which is required for special characters in the DeviceURI see the "By the way" section in https://bugzilla.novell.com/show_bug.cgi?id=512549#c1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Again, many thanks for all the details. Using 'lpmove' I moved one job to another printer, however now it is sitting in its queue and I am not sure how to initiate a printing of the job. For example, this is the output of lpc; lpc> status printerHP: printer is on device 'socket' speed -1 queuing is enabled printing is enabled 1 entries daemon present <snip> ...and 'lpq'; # lpq printerHP is ready Rank Owner Job File(s) Total Size 1st Me 148 J2PrinterWorks print document 185344 bytes <snip> How do I force the job to print? Thanks for your help, James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
James D. Parra -
jdd (kim2) -
Johannes Meixner -
Lars Müller -
Todd Kap