On Mon, 10 Jan 2000 [EMAIL PROTECTED] wrote:
> oh yes I did understand : > .
:-)
I did not question you understanding it; from one of your prevoius posts I
realized that you are quite knowledgable in this.
>
> The problems I was referring to is as follows (I have run into this many
> times):
>
> - Win 95 client gets IP address from NT dhcp server.
> - NT server assigns IP address to another machine ( for one reason or
> another, maybe client problem, or server)
Oh, this seems to be fault of the server in the first place (I think). As
I wrote I tested NT, Novell, and Linux, and chose Linux for DHCP service.
I have not seen this problem with Linux server, so whatever I say is just
speculation....
That said, I did have a problem with NT WS clients and Linux DHCP server.
I use the server for our NT labs. I noticed that we were running
out of IP addresses on "C" subnets with only 100 clients.
Students being student, sometimes reboot the machines without any reason
whatsoever. Then I realized that some clients after reboot ask for a new
IP address and refuse to accept the old one they had before the reboot!!!!
So we were having several IP addresses assigned to one machine at a time!
(it is exactly opposite of what you described NT server does--assigning
one IP to several clients)
To solve the problem, I wrote a perl script that runs on the server every
hour. It tries to find out redandant and/or conflicting leases and resolve
it (using MAC address, pinging, etc.). It also finds machines (with
current leases) which are turned off; it returns the IP to the pool of
available IPs. And you know what, it works :-)
cheers,
Hossein
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
