I tried to install the dhcp-rpm (DHCP: dhcpcd-1.3.18p18-10.i386.rpm) and
it said that it was already installed.

I created /etc/dhcpd.conf as it was not present:
subnet 192.168.0.0 netmask 255.255.255.0 (
range 192.168.0.11 192.168.0.250;
default-lease-time 57600;
max-lease-time 259200;
option subnet-mask 255.255.255.0; # required subnet mask

I created the dhcpd.leases:
touch /var/lib/dhcpd.leases

Then I tried to start the service and trouble started:
/sbin/service dhcpd start
--> dhcpd: unrecognized service
I can't find any file that says dhcpd!

Are there some files missing  or do I need ot install some more things?

Thanks, for you help!

What you want is the DHCP *server*. dhcpcd is the client. The server
package will be called dhcp or maybe dhcp-server, depending on your
distro.

I think that dhcpd is the server.  The client is called dhcp-client or
something like that.
On my distribution, Caldera, the dhcpd executable is in the /usr/sbin
directory.  
You can find where dhcpd (or any file) resides on your machine by
entering
which dhcpd
You may need to be root when you run this because root typically has
additional entries in it's PATH that point to directories that contain
system executables (daemons etc.).

Good luck
Jon

Please read the post above more carefully. Indeed dhcpd (DHCP daemon) is a
DHCP server, but dhcpcd (DHCP *Client* daemon) is a client (and a good one
too).

Didn't work on my Debian box. However, locate dhcpd works.

When using ISC's dhcpd, the file /usr/sbin/dhpcd is only a script which
starts determines the kernel version being used and starts the real dhcpd.

-Timo

It does help to install the proper software. Thanks for pointing that
out, I would have gone nuts without it ;-)

In RH7.1 the DHCPD server package is called dhcp-2.0pl5-4.i386.rpm.

--
Remove '-123' (no quotes) from the e-mail address when you wish to reply

-Happy Trails ;-)

and launch the executable.

news:3D1A6927.1040601@ivwnet.com...

hey Pieter,
If you can ping (unless you are killing ICMP on your network) your DHCP
server, after logging in without using the domain log in,  You should be
able to connect fine to your SMB/Domain Server. That means your network
configuration is fine. (I somehow doubt if your new you have messed with
packet filtering or any of the things that could make your network act
silly, like killing ICMP packets on your network.)

It might be helpfull to make sure the range of addresses that Samba will
allow (hosts allow & hosts deny in your smb.conf) connections from is the
same as the ones your DHCP server is passing out. If the ip you are setting
staticly is the SAME as the one your DHCP server is giving you then it has
to be an authentication issue.

I did notice that your host allow line is 192.168.0.127
but the IP you're trying to connect from is 192.168.0.7
Could this be part of the problem??
Something like hosts allow = 192.168.0.0/255.255.255.0 might be more usefull
for all of your LAN to connections.

These are just thoughts.... Based on what I can see in your configs.

Making sure the the range of IP addresses your dhcp server is passing out is
on the same subnet that the server is on. (if its done any other way your
network will be goofy. It doesn't sound like this is the problem but... hey.
It's a thought that might help out.)

<rant>
in all honesty,
It really sounds Robert doesn't know what is wrong so he is blowing smoke up
your azz... to make you feel like your stupid. (no offence dude but if your
not going to be helpfull why post?? Giving someone more to think about in a
given direction is much better then saying "Oh, ah, your computer, it's
broke you better read up on computers.")
</rant>

news:3D1A6927.1040601@ivwnet.com...

news:3D1D1FE8.7070709@ivwnet.com...