Jim, I am running K12LTSP on our main LAN segment and have DHCP configured with dhcpd.conf in the following fashion. default-lease-time 21600; max-lease-time 21600; ddns-update-style none; allow booting; allow bootp; authoritative; option subnet-mask 255.255.252.0; option broadcast-address 172.16.103.255; option routers 172.16.100.1; option domain-name-servers 172.16.100.21, 172.16.100.60, 168.169.8.8; option domain-name "franklinville.local"; option root-path "172.16.100.60:/opt/ltsp/i386"; # option root-path "172.16.100.60:/tftpboot/lts/"; option option-128 code 128 = string; option option-129 code 129 = text; option option-221 code 221 = text; shared-network WORKSTATIONS { subnet 172.16.100.0 netmask 255.255.252.0 { range 172.16.101.1 172.16.101.254; range 172.16.102.1 172.16.102.254; range dynamic-bootp 172.16.103.100 172.16.103.253; use-host-decl-names on; option log-servers 172.16.100.60; Do I need to make changes in /etc/hosts to insure that only the thin clients get those addresses that are specified in "range dynamic-bootp"? The dhcp server is doing a great job serving dhcp for our LAN I just need it to work with LTSP. It was working a couple of days ago and then I rebooted the server and I began to have the issues with ping. Thanks, Don "Do not go where the path may lead, go instead where there is no path and leave a trail"--Ralph Waldo Emerson Don Watkins, Technology Director Franklinville Central School Tel: 716-676-8004 Mobile: 716-474-5675 This message may contain confidential information. It is intended for the use of the addressee only. Unauthorized use of this e-mail may be unlawful.