Samsung CLP 510N User Manual (ENGLISH) - Page 200

On my PCL or GDI, Printing Package.

Page 200 highlights

Problem Possible Cause and Solution I can't print to an SMB (Windows) printer. To be able to configure and use SMB-shared printers (such as printers shared on a Windows printer), you need to have a correct installation of the SAMBA package that enables that feature. The "smbclient" command should be available and usable on your system. My application seems to be frozen while LLPR is running. Most Unix applications will expect a command like the regular "lpr" command to be non-interactive and thus return immediately. Since LLPR is waiting for user input before passing the job on to the print spooler, very often the application will wait for the process to return, and thus will appear to be frozen (its windows won't refresh). This is normal and the application should resume functioning correctly after the user exits LLPR. How do I specify the IP address of my SMB server? It can be specified in the "Add Printer" dialogue of the configuration tool, if you don't use the CUPS printing system. Unfortunately, CUPS currently doesn't allow you to specify the IP address of SMB printers, so you will have to be able to browse the resource with SAMBA in order to be able to print. Some documents come out Some versions of CUPS, especially those shipped with as white pages when Mandrake Linux before the 8.1 release, have some known printing. bugs when processing PostScript output from some applications. Try upgrading to the latest version of CUPS (at least 1.1.14). Some RPM packages for the most popular distributions are provided as a convenience with this Linux Printing Package. 7 I have CUPS and some There may be some local options defined in your ~/ options (such as N-up) .lpoptions file, which are manipulated by the lpoptions seem to be always enabled command. These options are always used if not overridden by even though I don't choose LLPR settings. To get rid of all options for a printer, run the them in LLPR. following command, replacing "printer" with the name of the queue: lpoptions -x printer I configured a printer to print to a file, but I get "Permission denied" errors. Most printing systems will not run as the super-user but as a special user (usually "lp"). Therefore, make sure that the file you have chosen to print to is accessible to the user owning the spooler daemon. On my PCL (or GDI) printer, I sometimes get error messages printing instead of my document. Unfortunately, some Unix applications may generate noncompliant PostScript output that may not be supported by Ghostscript, or even the printer itself in PostScript mode. You can try to capture the output to a file and view the results with Ghostscript (gv or ghostview will allow you to do so interactively) and see if you get error messages. However, since the application is probably at fault, contact your software vendor to inform them of the issue. SOLVING PROBLEMS 7.33

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266

S
OLVING
P
ROBLEMS
7.
33
7
I can’t print to an SMB
(Windows) printer.
To be able to configure and use SMB-shared printers (such as
printers shared on a Windows printer), you need to have a
correct installation of the SAMBA package that enables that
feature. The “smbclient” command should be available and
usable on your system.
My application seems to be
frozen while LLPR is
running.
Most Unix applications will expect a command like the regular
“lpr” command to be non-interactive and thus return
immediately. Since LLPR is waiting for user input before
passing the job on to the print spooler, very often the
application will wait for the process to return, and thus will
appear to be frozen (its windows won’t refresh). This is
normal and the application should resume functioning
correctly after the user exits LLPR.
How do I specify the IP
address of my SMB server?
It can be specified in the “Add Printer” dialogue of the
configuration tool, if you don’t use the CUPS printing system.
Unfortunately, CUPS currently doesn’t allow you to specify the
IP address of SMB printers, so you will have to be able to
browse the resource with SAMBA in order to be able to print.
Some documents come out
as white pages when
printing.
Some versions of CUPS, especially those shipped with
Mandrake Linux before the 8.1 release, have some known
bugs when processing PostScript output from some
applications. Try upgrading to the latest version of CUPS (at
least 1.1.14). Some RPM packages for the most popular
distributions are provided as a convenience with this Linux
Printing Package.
I have CUPS and some
options (such as N-up)
seem to be always enabled
even though I don’t choose
them in LLPR.
There may be some local options defined in your
~/
.lpoptions
file, which are manipulated by the lpoptions
command. These options are always used if not overridden by
LLPR settings. To get rid of all options for a printer, run the
following command, replacing “printer” with the name of the
queue: lpoptions -x printer
I configured a printer to
print to a file, but I get
“Permission denied” errors.
Most printing systems will not run as the super-user but as a
special user (usually “lp”). Therefore, make sure that the file
you have chosen to print to is accessible to the user owning
the spooler daemon.
On my PCL (or GDI)
printer, I sometimes get
error messages printing
instead of my document.
Unfortunately, some Unix applications may generate non-
compliant PostScript output that may not be supported by
Ghostscript, or even the printer itself in PostScript mode. You
can try to capture the output to a file and view the results
with Ghostscript (gv or ghostview will allow you to do so
interactively) and see if you get error messages. However,
since the application is probably at fault, contact your
software vendor to inform them of the issue.
Problem
Possible Cause and Solution