Adam,
I've missed the initial conversation of what's going on.
If your client is saying 'Seeking server (DHCPD)' (btw, I think you
need to reread what it says on the screen, because although I've seen
something similar, I don't think that's exactly what it says).
Anyway, if it says something like that, then it sounds like the client
can't find the DHCP server. Any monkeying around with the
'next-server' parameter in dhcpd.conf won't have any effect on this, cuz
the client hasn't even found the dhcp server. next-server is for the
next step AFTER the dhcp reply.
Watch in your log files. Depends on the distro, but look in
/var/log/daemon.log, or /var/log/messages or /var/log/syslog for info,
as the client is searching for the dhcp server.
Also, try using tcpdump to watch the packets, and see if you are seeing
any DHCP packets. The syntax would be:
tcpdump -i eth1 port 67 or 68
Adjust your 'eth1' as appropriate for your server.
Once tcpdump is running, then turn on the client, and see what you get.
If you don't see anything, then your clients dhcp requests aren't
getting to the server. Check cables and switches.
If you do see DHCP requests, then the packets are getting to the server,
so now you need to figure out if the server is actually paying attention
to them.
Is dhcpd actually listening?
netstat -anp | grep ":67 "
Should tell you. If you get no output from that command, then you need
to figure out why dhcpd isn't listening.
Hope that helps,
Jim McQuillan
[EMAIL PROTECTED]
On Thu, 8 Sep 2005, Adam Bogacki wrote:
> On Tue, Sep 06, 2005 at 06:03:41PM +0200 or thereabouts, Dave Cotton wrote:
> > On Tue, 2005-09-06 at 21:01 +1200, Adam Bogacki wrote:
> > > On Tue, Sep 06, 2005 at 08:47:23AM +0200 or thereabouts, Dave Cotton
> > > wrote:
> > > > On Tue, 2005-09-06 at 18:40 +1200, Adam Bogacki wrote:
> > > >
> > > > > It seems I have the same problem but having looked at
> > > > > 'ltspcfg' I can find no 'next-server' entry.
> > > > >
> > > > > Could you be more specific where it may be found ?
> > > > >
> > > >
> > > > It isn't in ltspcfg (yet, Jim? :)) just edit dhcpd.conf directly.
> > > >
> > > > I now have:-
> > > >
> > > > next-server [ip-of-original-server];
> > > >
> > > > Seems also to give a speed boost to finding the server.
> > > >
> > > >
> > > > --
> > > > Dave Cotton <[EMAIL PROTECTED]>
> > > >
> > > Thanks .. but it still hangs at "Searching for server
> > > [DHCPD] ..."
> > >
> > > Is this what you had in mind ?
> > >
> > > Adam.
> > >
> > > [1] dhcpd.conf
> > >
> > > >option domain-name-servers 203.96.152.4, 203.96.152.12;
> > > >option routers 192.168.0.1;
> > > >option subnet-mask 255.255.255.0;
> > > >default-lease-time 21600;
> > > >max-lease-time 21600;
> > > >next-server 203.79.110.81;
> >
> > No, surely this is your external address.
> >
> > If this is running on 192.168.0.1, strange as it may seem, 192.168.0.1
> > is the next-server address.
> >
> Hmm .. thanks, but it still hangs at 'seeking server (DHCPD)'.
> What else am I missing here ?
>
> Adam Bogacki.
>
> "Anyone who believes that exponential growth can go on forever in a
> finite world is either a madman or an economist".
>
> -- Kenneth E. Boulding
> >
> > --
> > Dave Cotton <[EMAIL PROTECTED]>
> >
> >
>
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
