Thin client configuration problems

[DB Clinton]

Hi again,

> > Sounds like your DHCP isn't working.  If you run the command:
> > >         ps aux |grep dhcp
> >
> > I just ran it and it looks like dhcp is working fine.
>
> Well, it's running but perhaps not fine.  Make sure there's a line with
> dhcpd in it.


Here's my actual output (I was actually having trouble passing
clipboard data between programs yesterday) :
=====
dhcp 6046 0.0 0.0 2412 740 ? S<s 10:18 0:00 dhclient3 -e IF_METRIC=100 -pf
/var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0
dhcpd 6386 0.0 0.1 2872 972 ? S<s 10:18 0:00 /usr/sbin/dhcpd3 -q -pf
/var/run/dhcp3-server/dhcpd.pid -cf /etc/ltsp/dhcpd.conf
1000 7294 0.0 0.0 2976 752 pts/0 R+ 10:23 0:00 grep dhcp
=====

> > eth1 needs to run a DHCP server, so it shouldn't use DHCP, it needs to
> > > have a static ip address.  Also, the fact that there is another DHCP
> > > server on that eth1's network is a cause for concern -- you shouldn't
> > > usually have two dhcp servers on one network.
> >
> > I changed eth1 to a static address (192.168.0.254).
>
> Okay but is there another dhcp server on that network?  That will
> definitely cause problems.


I tried booting with nothing else running on the LAN with the same results.

> Apparently it wasn't that alone. I'm still getting no ip assignments for
> > my client (that still returned the message "RPL-ROM-FFC" and then "no ip
> > address" a number of times)
>
> That suggests to me that either your dhcp server is not running on the
> interface facing the clients or there's something wrong with the network
> (ie a bad cable, etc.).  On the server run:
>
> sudo tcpdump -i eth1 udp port 68 or port 67
>
> and then try rebooting a client.  If the above command reports no packets,
> you need to look at your network cards, etc. and see is there really a
> link
> between the server and clients.


Here are those results:
=====
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
=====
Nother else showed up (even though I tried booting two separate clients).

>
> > > Can you ping them by ip address?  Samba is a rather complex thing
> which
> > > can fail for a multitude of reasons.
> >
> > I have managed in the past (at least one way, oddly enough) but right
> > now they're not talking at all.
>
> Okay, you need to look at the network I think.  Once you can set
> compatible
> ip addresses and ping across the wires, then dhcp and booting have some
> chance.


I should mention that this is already a fairly successful LAN linking
various flavors of Windows (my WinXP server and a number
of Win2K and Win98se boxes). The "thin clients" I want to use actually
have Windows hard drives which I'd like to bypass with
network boots to Ubuntu. Which means that, while I've had some
connectivity issues over
the years (and the two 98se boxes
upstairs can conflict with each other from time to time causing some
lost packets) the network architecture is
basically sound.

> There are two entries for ppp0 (216.254.132.30 / 255.255.255.255 / UH and
> > 0.0.0.0 / 0.0.0.0 / U)
> > and one for eth1 (192.168.0.0 / 255.255.255.0 / U)
>
> It would be preferable if you copy and paste the output, though I guess
> maybe you have no net access on that machine.  Paraphrased descriptions
> like this can be misleading.  That said, the above sounds okay.  Can you
> ping your DNS server (which you should see listed in /etc/resolv.conf)?


I'm not sure this is a problem, but I can see a folder /etc/resolvconf but no
resolv.conf file (only  ahavi-daemon).
I reinstalled resolvconf through synaptic - and there is now a whole whack
of files in that folder that weren't there before - and I'm going to try
restarting Edubuntu now (I never know which updates
require reboot and which don't...)
Thanks!
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/edubuntu-users/attachments/20071228/9cad9371/attachment.htm