Well, using routed connections, each location should have its own ip address range. Routing rather than bridged would cut down on a lot of bandwidth wasted to useless netbios and other types of traffic.
When you say the (2.1.2) EFW is 192.168.100.200, I'm assuming the efw is serving a lan in the 192.168.100.x range? I have to say, in terms of reliability, I would use a DHCP server at each location rather than try use a central one over an internet connection. In the past, I have set up a Windows Server DHCP service to handle 4 different subnets, but each subnet was served on different network cards installed in the server. In other words, each nic had its own range, and this worked very well. But how does your server know which client gets which address range? I'm assuming you only have one or two nics in the server? ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Efw-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/efw-user
