Kent West wrote:
Kent West wrote:
Kent West wrote:
Kent West wrote:
When I boot the client pc ("bi-12x"), it gets the IP address
150.252.217.49 from my dhcpd/tftp server, as indicated by the BIOS's
PXE messages. But then, instead of finding the pxelinux.0 file on my
dhcpd/tftp server, it find
Kent West wrote:
Kent West wrote:
Kent West wrote:
When I boot the client pc ("bi-12x"), it gets the IP address
150.252.217.49 from my dhcpd/tftp server, as indicated by the BIOS's PXE
messages. But then, instead of finding the pxelinux.0 file on my
dhcpd/tftp server, it finds the campus's cen
Kent West wrote:
Kent West wrote:
When I boot the client pc ("bi-19x"), it gets the IP address
150.252.x.y from my dhcpd/tftp server, as indicated by the BIOS's PXE
messages. But then, instead of finding the pxelinux.0 file on my
dhcpd/tftp server, it finds the campus's central RIS server inst
Kent West wrote:
When I boot the client pc ("bi-19x"), it gets the IP address
150.252.x.y from my dhcpd/tftp server, as indicated by the BIOS's PXE
messages. But then, instead of finding the pxelinux.0 file on my
dhcpd/tftp server, it finds the campus's central RIS server instead.
How do I get
Kent West wrote:
Albert Dengg wrote:
On Tue, 02 Dec 2003 10:38:34 -0600
Kent West <[EMAIL PROTECTED]> wrote:
How do I get my client to get my tftp offering instead of the RIS
offering? BTW, the RIS server is on a different network segment.
you can simply add "next-server yourserver;" to your
On Tue, 02 Dec 2003 15:26:40 -0600,
Kent West <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>:
> Arnt Karlsen wrote:
> > On Tue, 02 Dec 2003 10:38:34 -0600,
> > Kent West <[EMAIL PROTECTED]> wrote in message
>
> >> fixed-address 150.252.x.y; # x & y to protect the innocent
>
Arnt Karlsen wrote:
On Tue, 02 Dec 2003 10:38:34 -0600,
Kent West <[EMAIL PROTECTED]> wrote in message
fixed-address 150.252.x.y; # x & y to protect the innocent
..said Kent posting from 128.51. ;-)
Ssh-h-h! That's a secret!
I've always wondered if it was of any worth to not publish full I
Albert Dengg wrote:
On Tue, 02 Dec 2003 10:38:34 -0600
Kent West <[EMAIL PROTECTED]> wrote:
How do I get my client to get my tftp offering instead of the RIS
offering? BTW, the RIS server is on a different network segment.
you can simply add "next-server yourserver;" to your dhcpd.conf, either
fo
On Tue, 02 Dec 2003 10:38:34 -0600,
Kent West <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>:
> I'm trying to put together a proof-of-concept thin-client Debian
> computer lab at my university.
>
> Here at the university, we have a centralized RIS (Remote Imaging
> Server? Microsoft
On Tue, 02 Dec 2003 10:38:34 -0600
Kent West <[EMAIL PROTECTED]> wrote:
...
> host bi-19x {
>hardware ethernet 00:03:47:16:e2:58;
>fixed-address 150.252.x.y; # x & y to protect the innocent
>filename "/lts/2.4.22-ltsp-1/pxelinux.0";
> }
>
> When I boot the client pc ("bi-19x"), it get
I'm trying to put together a proof-of-concept thin-client Debian
computer lab at my university.
Here at the university, we have a centralized RIS (Remote Imaging
Server? Microsoft?) that provides a means whereby Tech Support can
instruct a client PC's BIOS to boot off the network (PXE) and then
11 matches
Mail list logo
