<html> <body> Excuse me, Friends ... 1. Yesterday I was too HASTY ! 2. Please see your replies to my the problem in the message # 1873 >>>>> It sounds like you are not using the dual NIC setup for k12ltsp. eth0 should be connected to a hub/switch for the clients and eth1 should connect to the Internet. This way you can have as many servers as you want. Each will boot only clients connected via the hub on eth0. (Paul) --- You should add another ethernet card to each machine, and plug eth1 into your internet connection. Do this on both machines and these problems will go away. This card does not need to be an expensive one. Any old junk 10 mbit card will work well. When you add the ethernet cards, plug them into the internet socket first, *then* reboot your K12LTSP Terminal Server everything *should* be completely automatic. FYI, it is very important that K12LTSP eth0 connection is kept clear from other networks, *unless* special attention is paid to reconfiguring K12LTSP. Connect eth0 only to your Terminals on their own switch. NEVER connect eth0 to unknown networks since you will almost certainly take that network down. (Steve) --- Pauls solution is a good one, but requires two switches/hubs (switches please :-). I like to have one DHCP, TFTP, LDAP server, and multiple application servers. The -query option to X I change to -indirect, in the LTSP startup scripts. Then you can choose the host machine - put the load on the users :-) It also adds a little redundancy to the system - especially if you mount home directories via NFS. Or you could customise lts.conf with the MAC address of all the clients to indicate their XSERVER. (Andy) >>>>> 3. This is the report of what I have done. STEP 1 I inserted a second NIC into the Server of Lab A. So I have two NICs: - eth0: 3C905C-TX - eth1: 3C905B-TX I connected eth0 to the Hub that connects the Clients and eth1 to the Internet. STEP 2 When I boot the Server: - The NICs are regularly recognized; - Apps, like OpenOffice.org, work correctly; - I can navigate the Internet. STEP 3 When I boot Terminal 1 it doesn't connect to the Server. A. On booting, the terminal screen reads: ------------------------------------------------------------ MAC Address = 00:50:DA:63:F7 Connectors present: 10 Base-T / 100Base-TX Searching for server (DHCP) ... ...Me: 192.168.1.87, Server: 192.168.1.88, Gateway: 192.168.1.88 Loading 192.168.1.88:/lts/vmlinuz.ltsp ........................................ B. After a long lapse of time the screen reads: Unable to load file. ( Of course, the file ' vmlinuz.ltsp ' is present in /tftpboot/lts/vmlinuz.ltsp ! ) The Terminal doesn't connect to the Server even if I unplug the Server from the Internet. STEP 4 Here are the technical info that may interest you. A. Server settings [root@www root]# ifconfig eth0 Link encap:Ethernet HWaddr 00:B0:D0:15:A2:5C inet addr:192.168.1.88 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1911 (1.8 Kb) TX bytes:1326 (1.2 Kb) Interrupt:5 Base address:0xe880 eth1 Link encap:Ethernet HWaddr 00:10:5A:C4:31:9B inet addr:192.168.1.89 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:199 errors:0 dropped:0 overruns:0 frame:0 TX packets:14 errors:0 dropped:0 overruns:0 carrier:2 collisions:0 txqueuelen:1000 RX bytes:18808 (18.3 Kb) TX bytes:840 (840.0 b) Interrupt:5 Base address:0xec00 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2241 errors:0 dropped:0 overruns:0 frame:0 TX packets:2241 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1964328 (1.8 Mb) TX bytes:1964328 (1.8 Mb) B. Content of the DHCPD.CONF file: default-lease-time 21600; max-lease-time 21600; ddns-update-style none; allow booting; allow bootp; option subnet-mask 255.255.255.0; option broadcast-address 192.168.1.255; option routers 192.168.1.88; option domain-name-servers 192.168.1.88; option domain-name "ltsp"; option root-path "192.168.1.88:/opt/ltsp/i386"; option option-128 code 128 = string; option option-129 code 129 = text; shared-network WORKSTATIONS { subnet 192.168.1.0 netmask 255.255.255.0 { range dynamic-bootp 192.168.1.86 192.168.1.87; use-host-decl-names on; option log-servers 192.168.1.88; # trick from Peter Rundle <peter.rundle@au.interpath.net> if substring (option vendor-class-identifier, 0, 9) = "PXEClient" { filename "/lts/pxe/pxelinux.bin"; # NOTE: kernels are specified in /tftpboot/lts/pxe/pxelinux.cfg/ } else { filename "/lts/vmlinuz.ltsp"; } } Dear Friends, will you help me, please, to solve this problem ? Thanks ! Angelo Nera --------------------------------------------------------------------------- DIDASCA The First Italian Cyber Schools for Lifelong Learning Via Ragazzi del 99 n. 19 I-23100 Sondrio So (Italy) T: +39 0342 513351 F: +39 0342 514953 U: <a href="http://www.didasca.it/" eudora="autourl">http://www.didasca.it</a> </body> </html>