1) check (and send to the list) # cat /etc/inetd.conf
2) same with # netstat -na
3) # date > /tftpboot/myfile
4) # cat /tftpboot/myfile
5) # ls -l /tftproot
6) (from another fat box) $ tftp thinclient
get /myfile
7) (from this same fat box) $ cat myfile
---- Original message ----
>Date: Tue, 15 Feb 2005 21:15:01 +1100
>From: "Tim Bates" <[email protected]>
>Subject: Re: [pxes-devel] PXES thin client as a TFTP Server
>To: <[email protected]>
>
> Oh right... Misread and therefore misunderstood what
> you were trying to do.
>
> Tim
>
> ----- Original Message -----
> From: Galina Bari
> To: [email protected]
> Sent: Tuesday, February 15, 2005 8:22 PM
> Subject: Re: [pxes-devel] PXES thin client as a
> TFTP Server
>
> Hi Tim,
>
> Thank you for replying. I don't think the NICs are
> the problem. Tftp works fine when a thin client
> tries to tftp-get a file from a fat box.
>
> In this thread:
> http://sourceforge.net/forum/message.php?msg_id=2873158
Diego
> wrote that all it takes to make a PXES thin client
> into a tftp server is to set
> LOCAL_TFTPD_ENABLED=1 in its conf file, but
> obviously I miss something because my thin client
> does not become a tftp server.
>
> It would be a pity to miss such an efficient tftp
> solution!
>
> Galina.
>
> Tim Bates <[email protected]> wrote:
>
> Wasn't there a dodgy PXE implementation on early
> Intel cards that did
> something like that? It would get DHCP response
> try to connect to TFTP
> then say timed out even though the TFTP server
> responded... Something
> like that anyway.
>
> What network cards are you using? What version
> number do they say they
> have for PXE when they attempt to boot?
>
> Tim
>
> Diego Torres Milano wrote:
> > You didn't.
> > TFTP is UDP based, no connection until you get
> a file.
>
> >>Well, I manage to connect to the tftp on the
> local_tftp_thin_client,
> >>but whenever I try to tftp get a file from
> this local_tftp I receive a
> >>"Transfer timed out" error message. Tftp get
> command from a thin
> >>client to a fat box completes successfully. Do
> I have to configure
> >>anything in LOCAL_TFTPD_OPTIONS? Any other
> suggestions?
>
>
**********************************************************************
> This message is intended for the addressee named
> and may contain
> privileged information or confidential
> information or both. If you
> are not the intended recipient please delete it
> and notify the sender.
>
**********************************************************************
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT
> Products from real users.
> Discover which products truly live up to the
> hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> pxes-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pxes-devel
>
> ------------------------------------------------
>
> Do you Yahoo!?
> Yahoo! Search presents - Jib Jab's 'Second Term'
Diego Torres Milano <[email protected]>
PXES Universal Linux Thin Client
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.