Excellent question. One test would be to try TFTP'ing a file from a
thick client on 192.168.0.0 and then trying the same thing from
Just occurred to me--check to see if there are any IPTABLES rules that
might be getting in the way.
Almquist Burke wrote:
-----BEGIN PGP SIGNED MESSAGE-----
On Dec 20, 2008, at 7:34 PM, Joseph Bishay wrote:
Sorry I wasn't able to try this earlier in the day.
I did as you said and I was able to get DHCPD to start successfully!
I rebooted a thin client, and it is able to see itself, the DHCP
server, the TFTP and the gateway. It does hang at " Loading
Is tftpd answering requests on the 192,168.4 subnet?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
-----END PGP SIGNATURE-----
K12OSN mailing list
K12OSN redhat com
For more info see <http://www.k12os.org>