Ubuntu Networking :: LTSP Server Doesn't Have Client Network Card Driver
Sep 1, 2010
I'm setting up an LTSP server using Ubuntu 10.4 64bit, and PXE connecting with thin clients using Atheros cards. The ltsp environment is 32bit.
Unfortunately I get an error message with "No interfaces found! Aborting..." and a kernel panic early during PXE boot.
After an enormous amount of investigation, I've narrowed it down to (probably) being the fact that the ltsp chroot environment doesn't have the correct driver for my network card (I believe it's atl1c). The correct driver IS available in Ubuntu, though, as I can successfully boot the thin client from both 64bit and 32bit live CDs and bring up the network interface.
how can I install the correct driver in the PXE environment?
how to get USB disks/sticks to mount on the clients. Is there something with some configfile that needs to be enabled or in the setup of the default image?
Cannot even move files from the USB drive via the servers USB as it is virtual one on a ESXi host.
the school starts on monday (8 hours) and there is about 10GB files that need to put in place before that.
PS. OpenSuse 11.3 all patched with minimum XFCE desktop on the server. easy-ltsp install via 1-click install on the opensuse/kiwi-ltsp page. Server + 20 clients Everything else functions properly but no CD or USB on clients
My 32-bit Ubuntu 9.10 [Karmic Koala] LTSP server has two NICs, one with Dynamic IP set by a DSL modem and the other with static IP of 192.168.0.254. I also have 4 thin Clients that boot from this server without any problems and another computer with Ubuntu 9.04 running some PHP programs with dynamic IP given by the same DSL modem. When I send requests to these PHP programs from thin clients, they all give the LTSP server's dynamic IP as their IP so I cannot trace who has sent this request to response back.
I actually know this is logical. Because the requests are sent by a program that's actually running on the LTSP server rather than the thin client. But my question is How can I run a program on a thin client with it's own IP? I also should mention that the dhcp3-server service running on the LTSP server has no conflicts with the DSL dhcp on the network and I know that the 4 thin clients get the IPs ranging from 192.168.1.101 through 192.168.1.104 from the dhcp3-server service. Because I can ping them while they're on. but /sbin/ifconfig on them shows info about the LTSP server.
I am trying to install and configure LTSP on a server for a HP thin client to boot off. The version of Ubuntu that I am using is 11.04 x86 and it is a fresh install on a dual core system with 2GB RAM. I followed a guide which comprised of these commands.
sudo apt-get install ltsp-server-standalone openssh-server sudo ltsp-build-client or if your on a 64-bit system with 32-bit machines do sudo ltsp-build-client arch i386 for editing the servers IP values use /etc/ltsp/dhcpd.conf after that you need to restart DHCP server sudo /etc/init.d/dhcp3-server restart and update sshkeys -sudo ltsp-update-sshkeys and if you updated dhcpd.conf then you need to update you image also by typing in terminal ltsp-update-image
Everything seemed to install as it should but when I try to boot from the thin client it just times out and says no DHCP or proxy invites received. I turned DHCP off on the router and even tried another router, but I still get nothing. I am at a bit of a loose end and I hope someone on here can point me in the right direction of where I am going wrong.
I have configured server ubuntu 11.04. Everything works fine, but there is a need for some clients to connect local hard drive. What should I do? How and what modules are added to the ltsp-image? How to register in the fstab on the client? Maybe I'm going the wrong way?
I have x11 forwarding enabled in /etc/ssh/sshd_config on a suse 11.2 32 bit box running kde I can open x apps on a windows machine using xming and putty just fine, but when I boot the same machine into suse 11.2 64 bit using kde and try using konsole I get: cannot connect to x server
The command I'm using to log in is: ssh -X -l username host I doubt the problem is with the server I'm logging into or it wouldn't work in windows, not really sure what to look for as I've never had a problem using x11 forwarding from a linux client before only windows ones
I'm trying to configure my network card using the b43 driver. I'm running 10.04.2 on the kernel version 2.6.35-25-generic-pae.
Surprisingly, I was able to connect to my home wireless network using the b43 driver without a problem. The only issue is that it doesn't automatically connect. I have to use the following command in order to get it to work:
After typing my password, I wait for 10 seconds and am automatically connected. My question is, how do I configure my system to do this for me permanently (or at least automatically) so I don't have to type it every time I log on?
I just recently installed a fresh copy of 9.10 server on an older machine I had laying around to use as a router and home server. Everything is setup and I'm on the net on it, except for some reason the Netgear GA311 I'm using for the internal network doesn't seem to be loading a driver. I've tried modprobing 8139 (which it says isn't found) as well as 8139too, 8139 too goes through ok, but it doesn't make any change, with lshw still claiming that it is "unclaimed". It seems that the Realtek chipset this card is based on is extremely compatible with Linux and I'm having trouble finding anyone with a similar issue with it.
I have a Netgear WG511GE PCMCIA card, and a driver from the original installation disk. I used an ndiswrapper-utils gui called ndisgtk to install the driver. I then do the following to verify an installation:
Unfortunately, when I put the PCMCIA card in, nothing happens. On Windows, a green light flashes even if the card is not connected to any network. At first I thought this might be a hardware issue, so I did #lspci and got:
Lo and behold, when I put a different unbranded Wireless PC Card in it works. I'm no expert in Networks, but to me this suggests a driver problem (i.e. the card is physically detected it just won't work). However, the correct driver was installed with ndisgtk and this was verified with #ndiswrapper -l, hence the confusion.
I'd be grateful if anyone else has had this problem/knows of this problem and is willing to share the solution with me/point me in the right direction. So far, Google has returned a few posts from a few years ago talking about patching kernels and manually building files etc (just before Prism54 became integrated into the Linux kernel).
I recently installed Ubuntu 9.10 on an old family laptop. It is a Compaq Presario V2000. Everything works perfectly except no wireless networks are recognized, even though I know there are available networks. My network controller is detected but is not doing it's job, which is finding available wireless networks! Using "system testing" I found this out about my network controller:
"Detecting your network controller(s):
Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)"
I'm trying to activate a wireless network on an ubuntu server 10.04. The machine has a TPLink PCI wireless card. Card is well recognized, and scanning for wireless connection it finds correctly the essid of the access point in the room. But when I try:
Code: $ sudo iwconfig wlan0 essid "apoint" key s:my_key_8 this error is returned: Code: Error for wireless request "Set Encode" (8B2A) :
SET failed on device wlan0 ; Invalid argument.I looked for similar situations over many forums, and I found that it could be the card doesn't support the encryption type (My AP uses WPA with TKIP). However if I use an ubuntu desktop live CD on the same machine, I can connect witouth any problem with NetworkManager 0.8.
I have the following problem:I have to networks in remote places.I have an opnvpn client in one network that connects to the the router (openvpn server).My question is,can i connect the network where the openvpn client is,throught the computer with the client to the other network.If yes,how? (please make it an idiot proof anwser because i have limited knowledge about iptables). I was thinking like forwarding (the router in the network with the openvpn client is also firewalling with iptables) the request of the ip class of the openvpn network to the computer with the client,which masquarades the interface
I installed newest Ubuntu system, 11.04, Natty-Narwhal, and PC is running smoothly. It is solid machine, Celeron 430, 1 gb of DDR2 memory and I have both LAN card and graphics integrated on the mobo which is MSI 7529, based on G31/P35/P31 chipset.
I plugged lan cable directly from my PC to the ADSL router. There is another Win Xp machine on the same router and it has connection, and internet is working fine. Right now Im writing from the Win 7 laptop, which is connected to the same router via wifi link... all working like a charm...
But, when I plug the Ubuntu desk I cannot get access to bot lan and internet...
I searched the net and it seems that ubuntu didnt install proper driver during the OS installation. Here are some diagnostics of the current config and state:
Code: Module Size Used by binfmt_misc 13213 1 snd_hda_codec_realtek 255820 1 code....
As you can see I need to install driver named r8101 instead this one r8169 and I think it will work that way. I found driver here only problem is dont know how to replace them.
I am having a terrible time getting any networking to work with a new RedHat Enterprise 6 64 bit install. I am installing on an HP Proliant DL380G7.I have downloaded the driver - hp-netxtreme2-6.2.23-2.src.rpm from the HP website.Followed directions and did the following:1.Build Environment Setup - installed redhat-rpm-config and kernel-devel2.Installed the source (hp-netxtreme) rpm.3. Build the Binary RPM - installed rpm-build and ran the following:rpmbuild -bb /root/rpmbuild/SPECS/hp-netxtreme2.specIt runs through the build process and near the end I get the following:make -C /lib/modules/2.6.3271.el6.x86_64/build UBDIRS=/root/rpmbuild/BUILD/hpnetxtreme26.2.23/obj/default/bnx2-2.0.23b/src modulesexpr: syntax erromake: Entering directory '/usr/src/kernels/2.6.32-71.el6.x86_64'/usr/src/kernels/2.6.32-1.el6.x86_64/arch/x86/makefile:81: stack protector enabled but no compiler supportmake: gcc: command not found
I just installed x64 Fedora, and as the title says, NM fails to detect my WiFi card. It's an Encore ENLWI-N with a RaLink RT2800 chipset. The card does show up when I run lspci, although iwconfig yields nothing.Not sure if this helps, but when Ias running Karmic Koala, Ubuntu detected the card immediately and required no configuration
I have a Broadcom Corporation NetXtreme BCM5721 network card on my server at work.Everything works fine for a few weeks, then randomly the network connection on the server will stop working. After it stops working, I will try to reconnect with the network manager, it shows a wired connection available, it shows the "connection in progress"animation, then the "connection disabled" icon.
I uninstalled the network manager and used manual configuration, but do you think the network manager was the issue? I can't have the server disconnecting randomly every few weeks with no way to know what the real problem is. Was there an issue with the network manager with 10.04?
I installed in Virtualbox many times and the clients would not connect. The config of the dhcpd.conf was the problem.Now, Everywhere I kept reading it said I had to turn off my hardware routers dhcp. Thats wrong, I have it working with it on and with one network card. Heres the nuts and bolts. Dlink 4100 hardware router assigning address block 192.168.2.200-250 to pcs on the lan. Router is set to reserve and IP for the ltps server nic so it gets the same IP assigned every time from the hardware router. No need to force linux to an ip when it can be set in the router. Then installed LTSP from alt-cd. Once done, dhcp wont run because it conflicts with the hardware dhcp. Found out by trying to restart it and it said stop - Fail when it tried to stop it.
sudo /etc/init.d/dhcp3-server restart So edit /etc/ltsp/dhcpd.conf. sudo gedit /etc/ltsp/dhcpd.conf
Mine attached below: The subnet, as long as the 1st three numbers match the rest of lan setup it will work.(192.168.2.0), rest of my lan is 192.168.2.x. Now notice the range is a different block than the hardware dhcp server uses. So all thin clients that connect will be assigned something 192.168.2.100-150 and all hardware connected pcs will be assigned 192.168.2.200-250 from the hardware router. So no conflicts. Then for the domain name server, set it to the hardware router ip. My hardware router is 192.168.2.2. Set option router to the same as hardware router of 192.168.2.2 Nothing in my dhcpd.conf file is pointing to the ltsp dhcp server. Nothing else had to be edited in the dhcpd.conf Next hurdle I had, after any change of the dhcpd.conf, ip's might have changed and you have to reconfig the ssh and the image. run these 2 commands.
sudo ltsp-update-sshkeys then sudo ltsp-upadte-image then sudo /etc/init.d/dhcp3-server restart
Then thin clients/lan boot pcs all can connect after that.
I have since installed again at work in virtual box, booted from another vbox client and booted from a separate lan pc. Then installed again at home on AMD 3200 Athlon, 1 gig mem. Booted from my main pc PhenomX4, no problems. Pc's must have lan boot available in the bios or net boot available on the network card(most consumer add on cards do not). But most motherboard lan connection do.
I just installed Linux Mint 9 as a dual boot install with Win XP. Trying to activate wireless network card driver and video driver. Pops up: "You are not authorized to perform this action".How do I get authorized?
Now every time I boot Win XP, the Internet Explorer menu bar is all blacked out and goofy. If I log out and back in it corrects itself. If I reboot it's blacked out again. Re-installed IE8. Still blacks out.Also Firefox in Win XP crashes expectantly. It has NEVER crashed on me previously.
I just finished setting up a new computer lab at my kids school, using LTSP and 22 think clients connecting to Ubuntu.Everything is going beautifully, and I'm using static IPs and autologin so that when each computer is turned on it logs itself in with no userintervention. The problem is, when users go to the top right system menu and select "Shut Down", they are brought out to the login screen for a second and then immediately logged back in automatically to the Desktop. How should I be shutting down the thin clients?he only way to do it at the moment is to have everyone hold the power button down until the CPU shuts off, but it feels sloppy and unhealthy.
I have been working/implementing LTSP based thin clients now using Ubuntu 10.04 LTS 32bit server. I intend to change the default purple Ubuntu splash. I have already removed the "quiet splash" parameters in the pxeconfig file. And it works, giving me a text boot. But what i needed was a replacement for the splash.
Currently have a problem with my LTSP server when using a gigabit switch with a megabit thin client.I am using K12LTSP with Fedora 9.The thin clients get most of the way through booting up then I get error messages saying:nfs: server 172.31.6.1 not responding, still trying.I don't get this problem if I use a 100 meg switch though.I have found several forum posts on the internet which all seem to point to the following webpage with a solution:However, when I make the recommended changes It doesnt make a difference.Below is an example of the default file located at /var/lib/tftpboot/ltsp/i386/pxelinux.cfg with its default settings:
I've just set up an LTSP server, with all its clients on a separate subnet to my main network - the main network is 192.168.1.x, and the LTSP clients are all 192.168.2.x. My LTSP server has 2 NICs, one on each network, and is merrily forwarding normal IP traffic from the clients to the rest of the network. I have a client/server application that has a server on one machine, and clients locate and attach to it using multicast protocols. The server is on the main network, and any other machines on the network can locate and talk to the server quite happily. The LTSP clients, however, cannot - I assume because the multicast communications aren't being forwarded by the LTSP server. How I can get this working?
I have recently installed an ltsp system, client and server. Everything works except i cannot get my client side serial ports to work or register for that matter. Can anyone point me to the steps i should take to get these working.
I have an Edubuntu server with two nics joined to the primary windows domain and I can log on with domain credentials and everything is AOK. I used LikewiseOpen 6 to join the server to the primary domain. So, on my Edubuntu server eth1 is connected to the primary domain and has a static IP. eth2 also has a static IP and is the DHCP for the thin client subnet, connected to a switch. IP forwarding is enabled.
So far, so good: I can log on the thin clients with one of the local accounts specified on the Edubuntu server and with that account I can surf the net and, if I supply domain credentials, browse the primary domain. Problem I have is:
I can't work out how to log on to the primary domain with a Active Directory account directly from a thin client. If I try DOMAINuser to log on, after giving the password, the password screen refreshes and 'domainuser@11.*.21.*'s password' appears under the blank password box. The IP in that message is the IP for the subnet and not the primary domain. I feel like I'm miss-understanding some basic simple step but I just can't figure it out.
I have setup Ubuntu 9.10 ltsp server, and have the client connected with login screen. I can log on the client successfully , but I did not get to the window environment, just see a busy mouse pointer on client screen and the screen of the server is scrambled ... and not viewable. I built the image by ltsl-build-client The server is amd64 version and the client is i386 version.
I am looking for a gigabit network card for my centos 5.4 server. I am looking for something known to work well with linux. I have been on the bestbuy site and I found a DLink (DGE-530T) card with support for linux from the vendor but after reading feedback from users with that card I am not so sure it is linux friendly. I am now thinking of buying online.