Okay... I finally got it working...after double and triple checking my lts.conf file, I found that it was referencing ws1 as ws01, that is why it was not working...DOH!!!.
The printing now works to one of my clients, however I am still having problems with my second one. The printer is a Sato Barcode printer which I have setup on the server as Generic Text, and it is being sent barcode label files. I keep getting the following error: lpr - unable to print file: client-error-document-format-not-supported I am surprised this is not working, as the printer is set to Generic Text.....has anyone else had problems printing barcode labels in this?? Thanks, Mike -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 09, 2003 9:55 AM To: Mike O'Toole Cc: roland gaulon; [EMAIL PROTECTED] Subject: RE: [Ltsp-discuss] printing on server Mike, Are you sure that the workstation knows its own hostname ? It needs that, in order to get the correct entries from the lts.conf file. Try setting 'RUNLEVEL = 3' in the lts.conf file, and see if you get a bash prompt when booting the client. If you do, then type: hostname and see what it returns. If you don't get a bash prompt, then try setting 'RUNLEVEL = 3' up in the [Default] section of lts.conf and see what that does. If you aren't getting a hostname, it may be because you are using a pool of addresses (range statement) in the dhcpd.conf file, or because you don't have the 'use-host-decl-names on;' statement in the dhcpd.conf file. Another way to specify entries in the lts.conf file is by IP address or MAC address: On my network, all of these are equivalent: [ws001] PRINTER_0_DEVICE = /dev/lp0 [192.168.0.1] PRINTER_0_DEVICE = /dev/lp0 [00:50:41:01:93:42] PRINTER_0_DEVICE = /dev/lp0 The big difference is that if you are using a range statement in dhcpd.conf to hand out dynamic ip addresses, the 1st and 2nd example aren't good, because they might not be the same each time you boot that client. But, the 3rd example is the MAC address, and it is never going to change. Hope that helps, Jim McQuillan [EMAIL PROTECTED] On Tue, 9 Dec 2003, Mike O'Toole wrote: > Hi Guys, > > I too am having some issues with local client printing. I have setup a > printer on my ws1, and edited the lts.conf file to contain the following > under the config for ws1: > > PRINTER_0_DEVICE = /dev/lp0 and > PRINTER_0_TYPE = P > > On the server, I then created the printer with the printer wizard and > configured it to be a "Jet Direct" printer on port 9100. > > However, when I try to print to it, it tells me the network connection is > buys, and when I try to telnet to it I get the following message: > > Trying 192.168.50.151... > telnet: Connect to address 192.168.50.151: Connection refused > > Is there anything I need to configure on the client to get this working? > > Thanks, > > Mike > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 03, 2003 2:01 PM > To: roland gaulon > Cc: [EMAIL PROTECTED] > Subject: Re: [Ltsp-discuss] printing on server > > > > Roland, > > Did you tell CUPS that the printer is on a JetDirect interface > at port 9100 ? > > That's what you need, because the lp_server daemon acts just like > an HP JetDirect printer server. > > To test that the printer is actually working, you can > try this: > > telnet 192.168.100.6 9100 > > Then, whatever you type should appear on the printer. > Press Ctrl-J to advance a line and Ctrl-L to do a form-feed. > > When done with that test, Ctrl-] and 'q' to quit. > > Jim McQuillan > [EMAIL PROTECTED] > > > > > On Wed, 3 Dec 2003, roland gaulon wrote: > > > bonjour > > I tried to install a printer on a workstation running ltsp 3.0 with a > > server mandrake 9.2 > > i modified the cups configuration of the printer running quite well on > > the server to print with the remote similar printer by only changing > > the location: 192.168.100.6 > > then i modified the lts.conf adding 2 lines: > > PRINTER_0_DEVICE = /dev/lp0 and > > PRINTER_0_TYPE = P > > i got no printing and i did not see where spooling is made, but > > something was sent out from the server ethernet interface. > > what did i do wrong? > > thanks for your help > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by OSDN's Audience Survey. > > Help shape OSDN's sites and tell us what you think. Take this > > five minute survey and you could win a $250 Gift Certificate. > > http://www.wrgsurveys.com/2003/osdntech03.php?site=8 > > _____________________________________________________________________ > > Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: > > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss > > For additional LTSP help, try #ltsp channel on irc.freenode.net > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by OSDN's Audience Survey. > Help shape OSDN's sites and tell us what you think. Take this > five minute survey and you could win a $250 Gift Certificate. > http://www.wrgsurveys.com/2003/osdntech03.php?site=8 > _____________________________________________________________________ > Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss > For additional LTSP help, try #ltsp channel on irc.freenode.net > ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
