Hi,
On Mon, 26 Apr 2010, Joseph Hartman wrote:
> Anyways, I initially connected my XP laptop to the LTSP network and couldn't
> get Internet, which means NAT wasn't working.
Do your thin clients generally get their internet access via NAT on your
LTSP server?
> Then I changed to our alternate DNS server address in dhcpd.conf on the
> server, renewed the DHCP lease on my laptop it gets Internet! I tried it
> with an Ubuntu laptop and it works too.
So it appears that the DNS may be your problem. Are you running a DNS
server on the thin client server or do you connect upstream to DNS servers?
It simplify your life to install a simple DNS server like dnsmasq on your
thin client server and point both the server itself and the clients at your
dnsmasq implementation. You can then just change what dns servers dnsmasq
points at and every client will get the new dns settings transparently.
It would be worth your while learning how to use tcpdump and or wireshark
as those will help you enormously to debug these things, eg. run tcpdump on
the client on port 53 and watch the DNS requests go out and responses come
back, etc.
> The clients still don't get Internet though. I thought this might mean the
> problem was with the first DNS server, but I restarted the DHCP server,
> restarted the clients with new IP addresses (and I assume the updated DNS
> server address), and I still have the same problem. If I don't use localapps
> the Internet works just fine.
One would have thought the DNS would update to all clients alright. You
need to verify that.
Assuming DNS access goes through the server, you can run this command on
the server:
sudo tcpdump -ni eth0 udp port 53 and host <ip_of_client>
which will show you all DNS traffic passing through eth0 (change to
whatever interface points toward your thin clients) with your client's IP
address. The other IP address on the traffic will show you what DNS server
the client is talking to.
> Finally, it seems like firefox as a localapp is taking way longer to load in
> the first place than it used to. I'm not sure what would cause this, but if
> any of you have any insight I'd appreciate it. I'm waiting on a call back
> from the district and I'd love to know what to ask of them (if anything).
If there's no net access or DNS timeouts, that might well delay firefox's
start-up as it checks for updates, etc.
> P.S. how do I see what the client's network information is and force a DHCP
> lease renew? When I use terminal on a client I just see the server's
> information.
You should be able to set the password in the chroot doing something like
this:
sudo -i
chroot /opt/ltsp/i386/
passwd
and then you need to rebuild the NBD root image. I'm afraid I'm a little
out of touch with LTSP so I can't recall how that's done.
Gavin
--
edubuntu-users mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
