Tobias Abt wrote: > > That would not really help as the NIC BIOSes would not use it then. > I am making a boot disk with the Rom-O-Matic site and it give the option so I wanted to try it.
Tobias Abt wrote: > > Maybe you got some things wrong. > a) we don't supply a DHCP server, just a DHCP proxy. You need to have > a DHCP server already. > b) when running the server on a Linux host, this can not be the > same as the DHCP server due to the way the servers bind to the port. > c) if you have such a setup you will have to disable the OTC DHCP > proxy by deinstalling it via the package manager and add manual > DHCP options: > filename "/pxelinux.0"; > next-server <IP>; > For some reason without the hard coded info the client will just sit there and say No IP over and over. Tobias Abt wrote: > > If you are going to use a boot disk you will have to create a disk > containing syslinux/lilo/grub, an appropriate config file and the > vmlinuz kernel and the initrd file. > Using the Rom-O-Matic disk I was able to get the machine to find the server however I now get an error that says "Alert: got a fragmented packet. reconfigure your server" Any ideas on that? -- View this message in context: http://www.nabble.com/Changing-DHCP-Ports-tp20442169p20443570.html Sent from the openthinclient.org users' mailing list mailing list archive at Nabble.com. ------------------------------------------------------------------------- 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=/ _______________________________________________ The Open Source Thin Client Solution http://openthinclient.org [email protected] https://lists.sourceforge.net/lists/listinfo/openthinclient-user
