Thin client configuration problems

[DB Clinton]

On 12/28/07, Gavin McCullagh <gmccullagh at gmail.com> wrote:
>
> Fair enough.  Do bear in mind though that once you get things running, you
> should have only one dhcp server.


Ok

>
> > > 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.
>
> So, can you boot windows and ping the linux machine?  I suspect not.  You
> can do
>
>         sudo tcpdump -i eth1 icmp
>
> to spot ping packets arriving to eth1.


Nothing at all came in. I noticed that the ip addresses on the Windows
machines (
169.254.186.66 and 169.254.158.136) seemed to have been set by the Win2K
machine and not my Linux box (which was running first). Also, their subnet
was 255.255.0.0 as opposed to mine which is 255.255.255.0 I'm not sure if
that's significant.

> 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.
>
> Well, there's something wrong here.  It could be firestarter is blocking
> things (you turned it off right?), but I think tcpdump as a raw socket
> user
> would see things before the firewall blocked them.


I actually uninstalled Firestarter completely.

Make sure you have link lights on the network cards. Make sure you have
> eth1 and eth0 plugged into the right networks (you can ping each
> interface's own ip and watch the light flash to see which is which).


Now that's not easy (lying on the floor underneath my desk while
reaching up and hitting enter on the keyboard).
But, in any case, I got uneven results: I think I saw
flashing on what should be eth1 (the card connected to the LAN) one of the
times but certainly not every time I pinged 192.168.0.254
 and pinging my ppp0 address (which goes through eth1) produced
some flashing, but there are flashed every few seconds on that card anyway.

If you can't ping the linux machine from windows and see the icmp packets
> on the tcpdump, I'd be inclined to say there's something wrong with the
> network or something very strange wrong with the linux machine.


The two windows computers now access each other but not my Linux
"server". I'm going to boot into Windows myself to confirm
that it's connected that way.
Thanks

Gavin
>
>
> --
> edubuntu-users mailing list
> edubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/edubuntu-users/attachments/20071228/b49462b7/attachment.htm