| 1 |
On Mon, 26 Sep 2005 16:55:51 +1200 |
| 2 |
Nick Rout wrote: |
| 3 |
|
| 4 |
> from http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/VI.CUPS-Connections/VI.tutorial-handout-cups-connections.html |
| 5 |
> |
| 6 |
> |
| 7 |
> "The "smbspool" program is provided with SAMBA starting with SAMBA |
| 8 |
> 2.0.6. Once you have made the link [1] and restarted CUPS you can |
| 9 |
> configure your printers with one of the following device URIs: |
| 10 |
> |
| 11 |
> smb://<workgroup>/<server>/<sharename> |
| 12 |
> smb://<server>/<sharename> |
| 13 |
> smb://<user>:<password>@<workgroup>/<server>/<sharename> |
| 14 |
> smb://<user>:<password>@<server>/<sharename>" |
| 15 |
|
| 16 |
Ooops I probably should have included this: |
| 17 |
|
| 18 |
"The workgroup name needs only to be specified if your system is using a |
| 19 |
different workgroup than the server. The "<user>:<password>" strings are |
| 20 |
required when printing to Windows NT/2000 servers or to shares with |
| 21 |
passwords enabled under Windows 95, 98, or XP. |
| 22 |
|
| 23 |
Note: The Samba client transmits the password in clear text! This makes |
| 24 |
printing to Samba servers insecure! (One only needs to enter "ps -auxwww |
| 25 |
| grep smb" during the job transmission to the Windows server to see the |
| 26 |
whole URI-string including the password...) It is therefore strongly |
| 27 |
recommended to either use a separate account only for printing on the |
| 28 |
Windows server (best without writable home directory). Otherwise, |
| 29 |
connect all printers to servers running GNU/Linux or Unix. |
| 30 |
|
| 31 |
The KDEPrint "Add Printer Wizard" has a comfortable facility for |
| 32 |
scanning the network for available printer shares on Windows (and Samba) |
| 33 |
servers." |
| 34 |
|
| 35 |
-- |
| 36 |
Nick Rout <nick@×××××××.nz> |
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-user@g.o mailing list |
Archives