PXE boot, expects DHCP and TFTP to be on the same server, once the Kernel has been
downloaded from the TFTP/DHCP server, then the LTSP session can be started on a
separate server.
Message: 15
Date: Wed, 11 Feb 2004 07:59:47 -0500
From: Tom Allison <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [Ltsp-discuss] SuSE 90 : tftp trouble
Hello,
I'm trying to get ltsp v4.0 set up on my SuSE box.
I've installed tftp and not SuSE's advanced tftp package.
This is a PXE boot configuration.
ltsp server ip: 192.168.1.10
tftp server ip: 192.168.1.10
dhcp server ip: 192.168.1.1
DHCP configuration file entry:
subnet 192.168.1.0 netmask 255.255.255.0
{
option subnet-mask 255.255.255.0;
option domain-name "home.tacocat.net";
option routers 192.168.1.1;
option domain-name-servers 192.168.1.1;
range dynamic-bootp 192.168.1.2 192.168.1.200;
default-lease-time 3600;
max-lease-time 7200;
option root-path "192.168.1.10:/opt/ltsp/i386";
}
host loki
{
hardware ethernet 00:0D:61:37:36:30;
fixed-address 192.168.1.10;
}
group {
use-host-decl-names on;
next-server 192.168.1.10;
option log-servers 192.168.1.1;
host ws001 {
hardware ethernet 00:d0:59:39:a8:a1;
fixed-address 192.168.1.201;
filename "/lts/2.4.24-ltsp-1/pxelinux.0";
}
}
From a non-ltsp machine, I can use tftp to get
/lts/2.4.24-ltsp-1/pxelinux.o repeatedly.
From this I conclude that the basics of tftp work.
I also see DHCP requests/acks going back and forth to the LTSP client
Here is what I see on the client
DHCP MAC ADDR: 00 D0 59 38 A7 A1
DHCP...
CLIENT IP: 192.168.1.201 MASK:255.255.255.0 DHCP IP: 192.168.1.1 GATEWAY IP:
192.168.1.1 TFTP.......
PXE-E32: TFTP open timeout
TFTP...
PXE-E32: TFTP open timeout
TFTP...
PXE-E32: TFTP open timeout
TFTP...
and then it gives up.
I'm kind of at a loss because I'm at least able to see the DHCP working
correctly with regard to the IP assignment. However, I checked the
/var/log/xinetd.log entry and cannot find an entry to show attempted
access from 192.168.1.201. However, my successfuly download of the pxe
kernel from my other linux box does show up on the xinetd.log entries.
--__--__--
Message: 16
Cc: [EMAIL PROTECTED]
From: Brian Payst <[EMAIL PROTECTED]>
Subject: Re: [Ltsp-discuss] SuSE 90 : tftp trouble
Date: Wed, 11 Feb 2004 08:24:12 -0500
To: Tom Allison <[EMAIL PROTECTED]>
Do you have a firewall in between the LTSP clients and the server?
Opening up TFTP in the firewall (or local IPTables config) doesn't seem
to let PXE requests through. Opening up PXE also doesn't seem to.
There's some high port requests early on that need to get through.
Drop your firewall and see if it works. Also check your hosts.allow and
hosts.deny files to see if the IP range of your clients is allowed to
connect to bootp and TFTP.
On Feb 11, 2004, at 7:59 AM, Tom Allison wrote:
> Hello,
>
> I'm trying to get ltsp v4.0 set up on my SuSE box.
> I've installed tftp and not SuSE's advanced tftp package. This is a
> PXE boot configuration.
>
> ltsp server ip: 192.168.1.10
> tftp server ip: 192.168.1.10
> dhcp server ip: 192.168.1.1
>
> DHCP configuration file entry:
>
> subnet 192.168.1.0 netmask 255.255.255.0
> {
> option subnet-mask 255.255.255.0;
> option domain-name "home.tacocat.net";
> option routers 192.168.1.1;
> option domain-name-servers 192.168.1.1;
> range dynamic-bootp 192.168.1.2 192.168.1.200;
> default-lease-time 3600;
> max-lease-time 7200;
> option root-path "192.168.1.10:/opt/ltsp/i386";
> }
>
> host loki
> {
> hardware ethernet 00:0D:61:37:36:30;
> fixed-address 192.168.1.10;
> }
>
> group {
> use-host-decl-names on;
> next-server 192.168.1.10;
> option log-servers 192.168.1.1;
>
> host ws001 {
> hardware ethernet 00:d0:59:39:a8:a1;
> fixed-address 192.168.1.201;
> filename
> "/lts/2.4.24-ltsp-1/pxelinux.0";
> }
> }
>
> From a non-ltsp machine, I can use tftp to get
> /lts/2.4.24-ltsp-1/pxelinux.o repeatedly.
> From this I conclude that the basics of tftp work.
> I also see DHCP requests/acks going back and forth to the LTSP client
>
>
> Here is what I see on the client
>
> DHCP MAC ADDR: 00 D0 59 38 A7 A1
> DHCP...
> CLIENT IP: 192.168.1.201 MASK:255.255.255.0 DHCP IP: 192.168.1.1
> GATEWAY IP: 192.168.1.1 TFTP.......
> PXE-E32: TFTP open timeout
> TFTP...
> PXE-E32: TFTP open timeout
> TFTP...
> PXE-E32: TFTP open timeout
> TFTP...
>
> and then it gives up.
>
> I'm kind of at a loss because I'm at least able to see the DHCP
> working correctly with regard to the IP assignment. However, I
> checked the /var/log/xinetd.log entry and cannot find an entry to show
> attempted access from 192.168.1.201. However, my successfuly download
> of the pxe kernel from my other linux box does show up on the
> xinetd.log entries.
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration See the
> breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _____________________________________________________________________
> 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
--__--__--
Message: 17
Date: Wed, 11 Feb 2004 14:40:48 +0100
From: "Dennis van der Aalst" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: [Ltsp-discuss] TFTP
Can somebody please explain to me how to set up tftp?
And how do I configure tftp?
And how do I check if tftp is running?
Best regards
--__--__--
Message: 18
Cc: <[EMAIL PROTECTED]>
From: Brian Payst <[EMAIL PROTECTED]>
Subject: Re: [Ltsp-discuss] TFTP
Date: Wed, 11 Feb 2004 08:58:13 -0500
To: "Dennis van der Aalst" <[EMAIL PROTECTED]>
Install TFTP for your distribution. Assuming you are using
RedHat/Fedora or a similar distro it will create /tftpboot and a
configuration file in /etc/xinetd.d/tftpd
Edit /etc/xinetd.d/tftp and change disable = yes to disable = no.
Restart xinetd with service xinetd restart
To see if it is running:
netstat -a | grep tftp
If it isn't check /var/log/messages for tftp info with grep tftp
/var/log/messages for clues
Installing the LTSP kernel will drop the necessary files into
/tftpboot/lts and you need to configure DHCP to hand out the necessary
steps to the client. There's a good how-to in the documentation on the
LTSP site as well.
On Feb 11, 2004, at 8:40 AM, Dennis van der Aalst wrote:
> Can somebody please explain to me how to set up tftp?
> And how do I configure tftp?
> And how do I check if tftp is running?
>
> Best regards
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration See the
> breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _____________________________________________________________________
> 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
--__--__--
Message: 19
Date: Wed, 11 Feb 2004 15:59:04 +0200 (CAT)
From: [EMAIL PROTECTED]
To: Dennis van der Aalst <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
Subject: Re: [Ltsp-discuss] TFTP
You have not indicated which operating system you use but is you are in
the Red Hat distributions on Linux then:
TFTP runs under xinetd or ofcourse under inetd(depends on which Red Hat
Linux distribution). In the first case you will just have to confirm that in.tftpd is
installed and then in xinetd.d
switch on tftp to run. The same of course goes for inetd just have to
enable tftp in inetd.conf.
Well, if enabled tftp will always run under inetd or xinetd as long as it
is enabled--well mind the iptables and ipchain rules in any case.
Regards,
Isaiah.
On Wed, 11 Feb 2004, Dennis van der Aalst wrote:
> Can somebody please explain to me how to set up tftp?
> And how do I configure tftp?
> And how do I check if tftp is running?
>
> Best regards
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration See the
> breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _____________________________________________________________________
> 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
>
--__--__--
Message: 20
From: "Atli Thorbjornsson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Date: Wed, 11 Feb 2004 14:48:29 -0000
Subject: [Ltsp-discuss] Intel LANDesk
Hi,
trying to etherboot a toshiba portege 3110ct with ltsp. I read somewhere
people have had problems with the PXE solution on the BIOS (Intel LANDesk) for version
.99 (eepro100 nic), which just happens to be the version I am running.
It queries dhcp alright:
Feb 11 14:58:38 burton dhcpd: DHCPDISCOVER from 00:00:39:bf:d6:16 via eth0 Feb 11
14:58:38 burton dhcpd: DHCPOFFER on 192.168.0.20 to 00:00:39:bf:d6:16 via eth0 Feb 11
14:58:39 burton dhcpd: DHCPREQUEST for 192.168.0.20 (192.168.0.2) from
00:00:39:bf:d6:16 via eth0 Feb 11 14:58:39 burton dhcpd: DHCPACK on 192.168.0.20 to
00:00:39:bf:d6:16 via eth0
5 times and then it quits with no errors or warnings.
M
y dhcpd.conf is setup according to pxe guidelines on ltsp.org:
class "Etherboot" {
match if substring (option vendor-class-identifier, 0, 9) =
"Etherboot";
option ebootmagic = E4:45:74:68:00:00;
option vendor-encapsulated-options 3c:09:45:74:68:65:72:62:6f:6f:74:ff;
filename = "lts/vmlinuz-2.4.24-ltsp-1";
}
class "PXEClient" {
match if substring (option vendor-class-identifier, 0, 9) =
"PXEClient";
option vendor-class-identifier "PXEClient";
filename "pxe/eb-5.0.9-eepro100.lzpxe";
}
.
.
.
host bastard {
hardware ethernet 00:00:39:bf:d6:16;
fixed-address 192.168.0.20;
}
So now I'm thinking I have to flash the bios a la
http://www.rom-o-matic.net/5.0.2/contrib/eepro100notes/ and wondering whether I should
be trying to update LANDesk to 2.0 which I read somewhere works fine or simply stick
an etherboot image in like the flash.txt files describe... Never having done something
like that before I am a little wary, so any advice on how to proceed or how to make my
existing setup work would be greatly appreciated.
By the by if flashing is the way to go I would appreciate FBOOT.EXE from someone
seeing how it is nowhere to be found on intel.com.
Thanks,
Atli Thorbjornsson.
--__--__--
Message: 21
From: "Atli Thorbjornsson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Date: Wed, 11 Feb 2004 15:19:07 -0000
Subject: [Ltsp-discuss] RE: Intel LANDesk
Hi, please disregard my last posting :)
Got it working, seems the match thing was not working and after I updated the .zpxe
file it gets through the etherboot process and starts "Uncompressing Linux" and then
the screen just starts blinking... Gonna l= ook google a bit before I bother you again
unneededly :)
Atli
-----Original Message-----
From: Atli Thorbjornsson [mailto:[EMAIL PROTECTED]
Sent: 11. febr=FAar 2004 14:48
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Intel LANDesk
Hi,
trying to etherboot a toshiba portege 3110ct with ltsp. I read somewhere
people have had problems with the PXE solution on the BIOS (Intel LANDesk=
)
for version .99 (eepro100 nic), which just happens to be the version I am running.
It queries dhcp alright:
Feb 11 14:58:38 burton dhcpd: DHCPDISCOVER from 00:00:39:bf:d6:16 via eth= 0 Feb 11
14:58:38 burton dhcpd: DHCPOFFER on 192.168.0.20 to 00:00:39:bf:d6= :16 via eth0 Feb
11 14:58:39 burton dhcpd: DHCPREQUEST for 192.168.0.20 (192.168.0.2) from
00:00:39:bf:d6:16 via eth0 Feb 11 14:58:39 burton dhcpd: DHCPACK on 192.168.0.20 to
00:00:39:bf:d6:1= 6 via eth0
5 times and then it quits with no errors or warnings.
M
y dhcpd.conf is setup according to pxe guidelines on ltsp.org:
class "Etherboot" {
match if substring (option vendor-class-identifier, 0, 9)= =3D
"Etherboot";
option ebootmagic =3D E4:45:74:68:00:00;
option vendor-encapsulated-options 3c:09:45:74:68:65:72:62:6f:6f:74:ff;
filename =3D "lts/vmlinuz-2.4.24-ltsp-1";
}
class "PXEClient" {
match if substring (option vendor-class-identifier, 0, 9)= =3D
"PXEClient";
option vendor-class-identifier "PXEClient";
filename "pxe/eb-5.0.9-eepro100.lzpxe";
}
=2E
=2E
=2E
host bastard {
hardware ethernet 00:00:39:bf:d6:16;
fixed-address 192.168.0.20;
}
So now I'm thinking I have to flash the bios a la
http://www.rom-o-matic.net/5.0.2/contrib/eepro100notes/ and wondering whether I should
be trying to update LANDesk to 2.0 which I read somewher= e works fine or simply stick
an etherboot image in like the flash.txt files describe... Never having done something
like that before I am a little wary, so any advice on how to proceed or how to make my
existing setup work would be greatly appreciated.
By the by if flashing is the way to go I would appreciate FBOOT.EXE from someone
seeing how it is nowhere to be found on intel.com.
Thanks,
Atli Thorbjornsson.
--__--__--
Message: 22
From: Peter Lister <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: Atli Thorbjornsson <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Organization:
Date: 11 Feb 2004 15:36:41 +0000
Subject: [Ltsp-discuss] Re: [Etherboot-users] RE: Intel LANDesk
On Wed, 2004-02-11 at 15:19, Atli Thorbjornsson wrote:
> Hi, please disregard my last posting :)
I was about to say "whatever you do, test with Etherboot on a floppy BEFORE flashing
anything".
BTW "Intel LANDesk" is not a BIOS, its a management tool. It has no bearing on using
PXE in this way. A BIOS upgrade might not hurt though if Toshiba can provide one which
has a more recent PXE.
> Got it working, seems the match thing was not working and after I
> updated the .zpxe file it gets through the etherboot process and
> starts "Uncompressing Linux" and then the screen just starts
> blinking... Gonna look google a bit before I bother you again
> unneededly :)
If it gets this far, it's an Linux / LTSP problem. Etherboot is no longer involved.
--__--__--
Message: 23
Date: Wed, 11 Feb 2004 10:58:46 -0500 (EST)
From: [EMAIL PROTECTED]
To: "Mike O'Toole" <[EMAIL PROTECTED]>
cc: roland gaulon <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>
Subject: RE: [Ltsp-discuss] printing on server
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?
Are you sure that the PRINTER_0_DEVICE and PRINTER_0_TYPE are setup in the section for
that workstation ?
Jim McQuillan
[EMAIL PROTECTED]
>
> 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
>
--__--__--
Message: 24
Date: Wed, 11 Feb 2004 11:00:15 -0500 (EST)
From: [EMAIL PROTECTED]
To: "Mike O'Toole" <[EMAIL PROTECTED]>
cc: roland gaulon <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>
Subject: RE: [Ltsp-discuss] printing on server
On Tue, 9 Dec 2003, Mike O'Toole wrote:
> 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??
Is there a 'RAW' print driver ?
I think that if you set it to Generic text, that the print spooler is
going to try to convert whatever you are trying to print, into text.
with Raw, it shouldn't do that.
Jim McQuillan
[EMAIL PROTECTED]
>
> 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
>
--__--__--
_____________________________________________________________________
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
End of Ltsp-discuss Digest
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&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
