The Dreaded TFTP error 2 (Access Violation)

[George Gambill]

DISCLAIMER: I know nothing about thinclients.  :)

Dallas and Craig,

Thank you both for your ideas.  So far we haven't succeeded yet but tenacity
always wins out.

(first Dallas)

>DISCLAIMER: I know nothing about thinclients.  :)

You probably know more than I do!!!  8-)

>First idea - as root do a /sbin/iptables -F to flush the firewall >rules,

Did that, no change.

Went into WebMin and still saw some "FireWall" rules, both accept and
reject.  Erased all of those and flagged the FireWall to not start on boot.

>The /etc/hosts.allow you show - is that from the server or the client?  >If
>it is the server, it needs to allow 192.168.100.151 as well.

Wasn't sure of the line to allow 192.168.100.151 (client) so I took
everything out of /etc/hosts.allow except:
  ALL : ALL
Not sure about upper case or lower case but left it in upper case.

>You should also have a /etc/xinet.d/tftp file.  Edit that and make >sure
that
>disable = no.  If it doesn't, change it and restart xinetd.

Actually, I had already found this and changed it but it is OK to remind me
lest we overlook something which is best not overlooked.
 
>Your files should be in the /tftpboot directory.  Looking at your >example
>below, they should be in /tftpboot/lts.

It is.  I also created a directory /lts/ and copied the file there just
incase.

>That is it for my ideas.  If the above doesn't work, look through
>/var/log/messages and /var/log/secure for entries relating to tftpd >and
post those.

/var/log/messages =
Dec 20 15:54:09 nowhere dhcpd: DHCPDISCOVER from 00:04:5a:82:b6:5d via eth0
Dec 20 15:54:09 nowhere dhcpd: DHCPOFFER on 192.168.100.151 via eth0
Dec 20 15:54:09 nowhere dhcpd: DHCPREQUETS for 192.160.100.151
(192.168.100.66) from 00:04:5a:82:b6:5d via eth0
Dec 20 15:54:09 nowhere dhcpd: DHCPPACK on 192.168.100.151 to
00:04:5a:82:b6:5d via eth0

These 4 lines repeat about every 4 seconds (till I kill the client) which is
the cycle time for the Client to retry.

Notice, in the /etc/dhcpd.conf file the mac address is in all upper case.
But it seems to work.

/var/log/security =
Dec 20 15:54:09 nowhere xinetd[621]: START: tftp pid=902
from=192.168.100.151

This line also repeats at the same time periods as does /var/log/message but
with a different pid.

/var/log/secure



Craig

>for setup purposes...firewall rules & tcp-wrappers should probably be
>removed from contention...

>service iptables stop

Did a "service iptables stop" and got 3 green "OK"s.  Repeted "service
iptables stop" (just curious) and got the same 3 green "OK"s.  Go figure.

>/etc/hosts.allow
>all: all
> (you weren't allowing the workstation to connect)

Did this sort-of (upper case) see above.

>//etc/hosts.deny should all be commented out

Did this. /etc/hosts.deny is one empty puppy (# to every line except blank)

>if you aren't going to use dns...is /etc/nsswitch.conf gonna allow that?

>hosts:	files nisplus dns

Good thought, that line now reads "#hosts:	files nisplus dns" (no
quotes)

Rebooted the server to be safe.
Issued "service iptables stop" and got the 3 green "OK"s.

Rebooted the client.  Same messages.  

One more thing I hate to mention but should.  I have come to understand that
RH8 brings tftp with it.  I didn't know that and didn't see it.  Therefore,
I downloaded a internet copy and installed (I think) it with tar.  I am
wondering if that haste may have done bad things.  I am tempted to reformat
the HD and reinstall knowing what I know now.  Got no problem with that.
What do you thing???

Thanks again

George