I don't have a physical box to put in the subnet right now. This is for a school where we have 3 subnets: staff, students, and servers. We have a router in place that limits access to certain ports and IP addresses in the server subnet and the internet. Mainly to keep the students from doing bad things. DHCP is being done with a DHCP Relay agent on the router. The router is actually a little 6 port Soekris 4801 m0n0wall (http://www.m0n0.ch/wall) box that is routing packets between my three subnets and acting as a firewall. You just turn on the DHCP Relay agent and tell it where to forward the all DHCP requests. The relay agent attaches enough info to the DHCP request that the receiving DHCP server can tell what subnet the request came from and assign the IP address accordingly. You just have to create a dhcpd.conf file that configures all of the subnets that you are servicing instead of just the local subnet. It's pretty slick actually. I'll be replacing the m0n0wall box with an OpenBSD router this summer (4 NICs) to take into account the increased throughput once I get the thin clients into production. I've got LTSP running in a VMware VM (Ubuntu Dapper) on a Windows server in another subnet with the rest of my servers. That VM server is doing DHCP, TFTP, and NFS. The thin clients are going to be accessing a Windows terminal server using rdesktop on SCREEN_01 and a separate Ubuntu server on SCREEN_02. Those servers may end up with a NIC in the thin client subnet(s), but I really want the DHCP, TFTP, and NFS functions centralized as I have several subnets and I don't want to have to maintain multiple LTSP servers. The good news is that I've got things working. I went into /tftpboot/lts/2.6.16.1-ltsp-2/pxelinux.cfg/default and modified the MOPTS line to the following: append rw root=/dev/ram0 initrd=initramfs.gz MOPTS=nolock,ro,wsize=2048,rsize=2048,proto=tcp Now everything is running very happily and the rdesktop client is screamin' fast. Casey Scott Balneaves wrote: On Tue, May 16, 2006 at 11:22:56AM -0600, Casey Woods wrote: <snip>I'm not doing any filtering that should affect anything. It's just doing IP forwarding between subnets.Doing any UDP forwarding? NFS uses UDP for it's work. That's probably the root of your problem. How are you handling dhcp with a router in between? Why not just put the ltsp server on the same subnet? Scott |