hi brian, i'am pretty sure the concerns of your network admins are unnecessary. if you have multiple ip helper-addresses defined, any UDP broadcasts recieved on the allowed udp ports will be unicasted to EACH of the IP helpers. as the openthinclient DHCP proxy does not interfere with DHCP servers it's absolutely save to add the second ip helper-addresses.
furthermore this is best practice for using DHCP proxies and i've seen this setup working dozens of times at more complex otc installations. however, there is an alternative solution for your problem. apparently you will lose the "auto-discover" feature of openthinclient and you have to add your thin clients manually: you can add two DHCP options to tell your thin client where to boot from and which Network Bootstrap Program (NBP) to use. these options depend on your DHCP implementation and should be set to: next-server/TFTP Boot Server Host (DHCP Option 66): <IP_OR_NAME_OF_YOUR_OTC_SERVER> filename/Bootfile Name (DHCP Option 67): pxelinux.0 or /pxelinux.0 regards, martin Clarke, Brian schrieb: > Thanks again for the reply Martin, > > It seems that the network guys had considered this. But, they said that > since they already have an ip helper-address assigned to the dhcp > server, that if they configured another IP-helper address in the system, > that the clients would only look to either the DHCP server OR the OTC > server, meaning that both can't be configured at the same time. Does > this sound accurate to you? Perhaps I'll ask them about it again. But I > was hoping that there were other configurations that we could do, say on > the DHCP server, that would simply point the clients to the OTC server. > Let me know what you think. > > Regards, > > Brian > > -----Original Message----- > From: Martin Kreiner [mailto:m.krei...@levigo.de] > Sent: Monday, May 03, 2010 7:10 AM > To: openthinclient-user@lists.sourceforge.net > Subject: Re: [openthinclient-user] OTC server with clientsin > differentsubnets > > hi brian, > > as there are no *NIX machines involved you won't hit SUITE-39: good. > > simply spoken, you have to make sure that the otc server will receive > the > broadcast DHCP discover packages sent by your thin clients. the otc > server > basically needs the same switch/ip helper setup as you DHCP server. so > what you > have to do is: > > - make sure the otc server gets a persistent IP (via DHCP or static) > - add an ip helper-address of your otc server IP to any swich which has > already > an ip helper-address entry of your DHCP server > > for detailed informations have a look at page 18 in Intel's "Preboot > Execution > Environment (PXE) Specification": > http://download.intel.com/design/archives/wfm/downloads/pxespec.pdf > > > cheers, > martin > > > Clarke, Brian schrieb: >> Hi Martin >> >> The OTC server is running on windows 2003 server R2. I have it > installed on a virtual machine on vmware workstation 6.x. Like it said, > it worked fine when it was on the same subnet as the Thin clients. But > it doesn't work at all when on a different subnet. The host machine > which is hosting the virtual machines is also running windows server > 2003 R2. Any assistance would be greatly appreciated. >> >> regards, >> >> Brian >> >> ________________________________ >> >> From: Martin Kreiner [mailto:m.krei...@levigo.de] >> Sent: Fri 4/30/2010 5:03 PM >> To: openthinclient-user@lists.sourceforge.net >> Subject: Re: [openthinclient-user] OTC server with clients in > differentsubnets >> >> >> hi brian, >> >> to give you further instructions i need to know the operating system > your >> openthinclient server is running and if there is any kind of > virtualisation >> layer in between. >> just to make sure you will not hit the following problem: >> https://issues.openthinclient.org/otc/browse/SUITE-39 >> >> >> regards, >> martin >> >> Clarke, Brian schrieb: >>> Good day, >>> >>> >>> >>> I'm a new user of openthinclient and I am unable to get the OTC > server >>> to work across multiple subnets. >>> >>> >>> >>> We have 3 or 4 different subnets (192.168.210, 192.168.212 etc...) > for our >>> clients. The OTC server is on a another subnet which is strictly for >>> servers - 172.30.1. The Dhcp server is on its own subnet also, but >>> they have a IP helper configured so that it works for all of the > client >>> subnets (excluding the 172.30.1 subnet which doesn't use DHCP). If I >>> have the OTC server on the same subnet as the client it will work. >>> However, if I have it on the server subnet (172.....) it doesn't work > at >>> all. I have checked the logs on the OTC server and they don't show > any >>> incoming traffic from the other subnets. What do I need to configure > to >>> get this working? My knowledge of networking is a bit limited when it >>> comes to switches and what have you, so please explain as easily as >>> possible. Although I don't manage the switches or DHCP servers, I > know >>> the guys who do, so I can tell them what to do. Any assistance would > be >>> much appreciated. >>> >>> >>> >>> Regards, >>> >>> >>> >>> Brian Clarke ------------------------------------------------------------------------------ _______________________________________________ The Open Source Thin Client Solution http://openthinclient.org openthinclient-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openthinclient-user
