DHCP problems using Windows 98 clients

Hi People.

I am experiencing a DHCP problem in the company i work that is described
below:

Windows 98 clients is apresenting IP conflict when it gets from DHCP server.
The important detail is that allways that it has a conflict, one of both
machines that had the conflict have subnet mask wrog. The IP range I use is
10.1.10.0 to 10.1.14.254 mask 255.255.0.0. When a conflict occurs, one of
then has a subnet mask 255.0.0.0, 255.255.255.0 or 255.255.255.255, the DHCP
server is allways the same (10.1.1.1) and the time of expiration is blank.

My DHCP Server is only DHCP Server, no procedure runs on it, only DHCP
service.

This problem is already known by Microsoft. This problem occurs because
Windows 95 and 98 clients, when configured automatic ip adressing, do not
follow 100% RFC 1541.

This problem occurs when a client with windows 95 and 98 have the lease
expired. If the client is not turned on in the moment of the expiration
(consequently impossibilited to renew the lease of his IP addres), the server
offer this address to other client. When the first client is turned on, it
will try to use the same IP that other one, asking for dhcp server permission
to use it. Thus this addres is already signed to other client, the server
will deny this permission.

In this moment, the client should initiate all the process to aquire another
IP address. The problem is in this moment is that the client ignores this
negation and try to use that address any way. The client checks if another
client has this address through an ARP request, and other client that has
this addres aswers. In this moment that it detects that exists another
machine with tha same IP Addres, the user receives the IP conflict message on
screen.

I am experiencing this problem a long time and do not know how to solve. The
network has about 500 clients. I have already tried to force the clients do
lease his IP address on shutdown. It works, but don't solved the problem. In
the machines that i have modified the registry to leave the ip adress on
shutdown, when it turns on, it really does not have an address, but does not
obtain an valid IP address, only the 169.*.*.*.

Any idea how to solve this?

"Fabio Martins" <Fabio (E-Mail Removed)> wrote in message
news:9412ACD2-0921-4D5B-8632-(E-Mail Removed)...
> Hi People.
>
> I am experiencing a DHCP problem in the company i work that is described
> below:
>
> Windows 98 clients is apresenting IP conflict when it gets from DHCP
> server.
> The important detail is that allways that it has a conflict, one of both
> machines that had the conflict have subnet mask wrog. The IP range I use
> is
> 10.1.10.0 to 10.1.14.254 mask 255.255.0.0. When a conflict occurs, one of
> then has a subnet mask 255.0.0.0, 255.255.255.0 or 255.255.255.255, the
> DHCP
> server is allways the same (10.1.1.1) and the time of expiration is blank.
>
> My DHCP Server is only DHCP Server, no procedure runs on it, only DHCP
> service.
>
> This problem is already known by Microsoft. This problem occurs because
> Windows 95 and 98 clients, when configured automatic ip adressing, do not
> follow 100% RFC 1541.
>
> This problem occurs when a client with windows 95 and 98 have the lease
> expired. If the client is not turned on in the moment of the expiration
> (consequently impossibilited to renew the lease of his IP addres), the
> server
> offer this address to other client. When the first client is turned on, it
> will try to use the same IP that other one, asking for dhcp server
> permission
> to use it. Thus this addres is already signed to other client, the server
> will deny this permission.
>
> In this moment, the client should initiate all the process to aquire
> another
> IP address. The problem is in this moment is that the client ignores this
> negation and try to use that address any way. The client checks if another
> client has this address through an ARP request, and other client that has
> this addres aswers. In this moment that it detects that exists another
> machine with tha same IP Addres, the user receives the IP conflict message
> on
> screen.
>
> I am experiencing this problem a long time and do not know how to solve.
> The
> network has about 500 clients. I have already tried to force the clients
> do
> lease his IP address on shutdown. It works, but don't solved the problem.
> In
> the machines that i have modified the registry to leave the ip adress on
> shutdown, when it turns on, it really does not have an address, but does
> not
> obtain an valid IP address, only the 169.*.*.*.
>
> Any idea how to solve this?
>
>

I suppose you have tried setting aside a range of IP's on the DHCP server
and using those as static IP's on the problem computers.?

Hi Haggis,

thank you for answering.

No, theese IP addresses have never been used as static. Simply is like that
Windows 98 clients do not want to lease his address or use another one, and
insists to use the last it has used. It occurs for a time out problem in MS
DHCP implementation, that how i have mentioned, it does not follow the RFC
1541. I'll find the link in Microsoft website and post here.

Thank's again!

FM

"Haggis" wrote:

>
>
>
> "Fabio Martins" <Fabio (E-Mail Removed)> wrote in message
> news:9412ACD2-0921-4D5B-8632-(E-Mail Removed)...
> > Hi People.
> >
> > I am experiencing a DHCP problem in the company i work that is described
> > below:
> >
> > Windows 98 clients is apresenting IP conflict when it gets from DHCP
> > server.
> > The important detail is that allways that it has a conflict, one of both
> > machines that had the conflict have subnet mask wrog. The IP range I use
> > is
> > 10.1.10.0 to 10.1.14.254 mask 255.255.0.0. When a conflict occurs, one of
> > then has a subnet mask 255.0.0.0, 255.255.255.0 or 255.255.255.255, the
> > DHCP
> > server is allways the same (10.1.1.1) and the time of expiration is blank.
> >
> > My DHCP Server is only DHCP Server, no procedure runs on it, only DHCP
> > service.
> >
> > This problem is already known by Microsoft. This problem occurs because
> > Windows 95 and 98 clients, when configured automatic ip adressing, do not
> > follow 100% RFC 1541.
> >
> > This problem occurs when a client with windows 95 and 98 have the lease
> > expired. If the client is not turned on in the moment of the expiration
> > (consequently impossibilited to renew the lease of his IP addres), the
> > server
> > offer this address to other client. When the first client is turned on, it
> > will try to use the same IP that other one, asking for dhcp server
> > permission
> > to use it. Thus this addres is already signed to other client, the server
> > will deny this permission.
> >
> > In this moment, the client should initiate all the process to aquire
> > another
> > IP address. The problem is in this moment is that the client ignores this
> > negation and try to use that address any way. The client checks if another
> > client has this address through an ARP request, and other client that has
> > this addres aswers. In this moment that it detects that exists another
> > machine with tha same IP Addres, the user receives the IP conflict message
> > on
> > screen.
> >
> > I am experiencing this problem a long time and do not know how to solve.
> > The
> > network has about 500 clients. I have already tried to force the clients
> > do
> > lease his IP address on shutdown. It works, but don't solved the problem.
> > In
> > the machines that i have modified the registry to leave the ip adress on
> > shutdown, when it turns on, it really does not have an address, but does
> > not
> > obtain an valid IP address, only the 169.*.*.*.
> >
> > Any idea how to solve this?
> >
> >
>
> I suppose you have tried setting aside a range of IP's on the DHCP server
> and using those as static IP's on the problem computers.?
>
>
>

The registry key that I have changed to lease IP address @ shutdown is
described in:http://support.microsoft.com/?kbid=217035

I have already tryied this too:
http://support.microsoft.com/kb/194790/en-us
But the server is not busy, it's a server machine only with DHCP service
runing.

I have not found the article that discribes the time out problem thant i
believe i am experiencing this, but i am going to search this and post here.

FM

"Fabio Martins" wrote:

> Hi People.
>
> I am experiencing a DHCP problem in the company i work that is described
> below:
>
> Windows 98 clients is apresenting IP conflict when it gets from DHCP server.
> The important detail is that allways that it has a conflict, one of both
> machines that had the conflict have subnet mask wrog. The IP range I use is
> 10.1.10.0 to 10.1.14.254 mask 255.255.0.0. When a conflict occurs, one of
> then has a subnet mask 255.0.0.0, 255.255.255.0 or 255.255.255.255, the DHCP
> server is allways the same (10.1.1.1) and the time of expiration is blank.
>
> My DHCP Server is only DHCP Server, no procedure runs on it, only DHCP
> service.
>
> This problem is already known by Microsoft. This problem occurs because
> Windows 95 and 98 clients, when configured automatic ip adressing, do not
> follow 100% RFC 1541.
>
> This problem occurs when a client with windows 95 and 98 have the lease
> expired. If the client is not turned on in the moment of the expiration
> (consequently impossibilited to renew the lease of his IP addres), the server
> offer this address to other client. When the first client is turned on, it
> will try to use the same IP that other one, asking for dhcp server permission
> to use it. Thus this addres is already signed to other client, the server
> will deny this permission.
>
> In this moment, the client should initiate all the process to aquire another
> IP address. The problem is in this moment is that the client ignores this
> negation and try to use that address any way. The client checks if another
> client has this address through an ARP request, and other client that has
> this addres aswers. In this moment that it detects that exists another
> machine with tha same IP Addres, the user receives the IP conflict message on
> screen.
>
> I am experiencing this problem a long time and do not know how to solve. The
> network has about 500 clients. I have already tried to force the clients do
> lease his IP address on shutdown. It works, but don't solved the problem. In
> the machines that i have modified the registry to leave the ip adress on
> shutdown, when it turns on, it really does not have an address, but does not
> obtain an valid IP address, only the 169.*.*.*.
>
> Any idea how to solve this?
>
>

Do what I do and place a link to Ipconfig.exe in the start menu, then tell
people how to Release all and Renew all. The only other problem with this
workaround is Ipconfig.exe sometimes locks up and the only thing you can do
to fix that is reboot. To my knowledge this problem has never and probably
will never be fixed. Your correct in that this problem has absolutely
nothing to do with a busy DHCP server.

"Fabio Martins" <(E-Mail Removed)> wrote in message
news:7A27D225-148F-4AEF-9C13-(E-Mail Removed)...
> The registry key that I have changed to lease IP address @ shutdown is
> described in:http://support.microsoft.com/?kbid=217035
>
> I have already tryied this too:
> http://support.microsoft.com/kb/194790/en-us
> But the server is not busy, it's a server machine only with DHCP service
> runing.
>
> I have not found the article that discribes the time out problem thant i
> believe i am experiencing this, but i am going to search this and post
here.
>
> FM
>
> "Fabio Martins" wrote:
>
> > Hi People.
> >
> > I am experiencing a DHCP problem in the company i work that is described
> > below:
> >
> > Windows 98 clients is apresenting IP conflict when it gets from DHCP
server.
> > The important detail is that allways that it has a conflict, one of both
> > machines that had the conflict have subnet mask wrog. The IP range I use
is
> > 10.1.10.0 to 10.1.14.254 mask 255.255.0.0. When a conflict occurs, one
of
> > then has a subnet mask 255.0.0.0, 255.255.255.0 or 255.255.255.255, the
DHCP
> > server is allways the same (10.1.1.1) and the time of expiration is
blank.
> >
> > My DHCP Server is only DHCP Server, no procedure runs on it, only DHCP
> > service.
> >
> > This problem is already known by Microsoft. This problem occurs because
> > Windows 95 and 98 clients, when configured automatic ip adressing, do
not
> > follow 100% RFC 1541.
> >
> > This problem occurs when a client with windows 95 and 98 have the lease
> > expired. If the client is not turned on in the moment of the expiration
> > (consequently impossibilited to renew the lease of his IP addres), the
server
> > offer this address to other client. When the first client is turned on,
it
> > will try to use the same IP that other one, asking for dhcp server
permission
> > to use it. Thus this addres is already signed to other client, the
server
> > will deny this permission.
> >
> > In this moment, the client should initiate all the process to aquire
another
> > IP address. The problem is in this moment is that the client ignores
this
> > negation and try to use that address any way. The client checks if
another
> > client has this address through an ARP request, and other client that
has
> > this addres aswers. In this moment that it detects that exists another
> > machine with tha same IP Addres, the user receives the IP conflict
message on
> > screen.
> >
> > I am experiencing this problem a long time and do not know how to solve.
The
> > network has about 500 clients. I have already tried to force the clients
do
> > lease his IP address on shutdown. It works, but don't solved the
problem. In
> > the machines that i have modified the registry to leave the ip adress on
> > shutdown, when it turns on, it really does not have an address, but does
not
> > obtain an valid IP address, only the 169.*.*.*.
> >
> > Any idea how to solve this?
> >
> >

Hi! Thank u for answering.

My network has about 600 PC's over 4 buildings. Put ipconfig in start menu I
do not think that's a good idea, because users will not understand for what
they're doing this and will rain a lot of phone calls asking for explanations
and orientation.

How about clean the DHCP Database and me and some other people go to any pc
and renew the leases on each client? I can do this and one stays on DHCP
server monitoring the leases.

If u (and all other is reading this posting) don't mind, add me add msn
messenger (E-Mail Removed) for exchanging some ideas.

Thank you!

"Muddle" wrote:

> Do what I do and place a link to Ipconfig.exe in the start menu, then tell
> people how to Release all and Renew all. The only other problem with this
> workaround is Ipconfig.exe sometimes locks up and the only thing you can do
> to fix that is reboot. To my knowledge this problem has never and probably
> will never be fixed. Your correct in that this problem has absolutely
> nothing to do with a busy DHCP server.
>
> "Fabio Martins" <(E-Mail Removed)> wrote in message
> news:7A27D225-148F-4AEF-9C13-(E-Mail Removed)...
> > The registry key that I have changed to lease IP address @ shutdown is
> > described in:http://support.microsoft.com/?kbid=217035
> >
> > I have already tryied this too:
> > http://support.microsoft.com/kb/194790/en-us
> > But the server is not busy, it's a server machine only with DHCP service
> > runing.
> >
> > I have not found the article that discribes the time out problem thant i
> > believe i am experiencing this, but i am going to search this and post
> here.
> >
> > FM
> >
> > "Fabio Martins" wrote:
> >
> > > Hi People.
> > >
> > > I am experiencing a DHCP problem in the company i work that is described
> > > below:
> > >
> > > Windows 98 clients is apresenting IP conflict when it gets from DHCP
> server.
> > > The important detail is that allways that it has a conflict, one of both
> > > machines that had the conflict have subnet mask wrog. The IP range I use
> is
> > > 10.1.10.0 to 10.1.14.254 mask 255.255.0.0. When a conflict occurs, one
> of
> > > then has a subnet mask 255.0.0.0, 255.255.255.0 or 255.255.255.255, the
> DHCP
> > > server is allways the same (10.1.1.1) and the time of expiration is
> blank.
> > >
> > > My DHCP Server is only DHCP Server, no procedure runs on it, only DHCP
> > > service.
> > >
> > > This problem is already known by Microsoft. This problem occurs because
> > > Windows 95 and 98 clients, when configured automatic ip adressing, do
> not
> > > follow 100% RFC 1541.
> > >
> > > This problem occurs when a client with windows 95 and 98 have the lease
> > > expired. If the client is not turned on in the moment of the expiration
> > > (consequently impossibilited to renew the lease of his IP addres), the
> server
> > > offer this address to other client. When the first client is turned on,
> it
> > > will try to use the same IP that other one, asking for dhcp server
> permission
> > > to use it. Thus this addres is already signed to other client, the
> server
> > > will deny this permission.
> > >
> > > In this moment, the client should initiate all the process to aquire
> another
> > > IP address. The problem is in this moment is that the client ignores
> this
> > > negation and try to use that address any way. The client checks if
> another
> > > client has this address through an ARP request, and other client that
> has
> > > this addres aswers. In this moment that it detects that exists another
> > > machine with tha same IP Addres, the user receives the IP conflict
> message on
> > > screen.
> > >
> > > I am experiencing this problem a long time and do not know how to solve.
> The
> > > network has about 500 clients. I have already tried to force the clients
> do
> > > lease his IP address on shutdown. It works, but don't solved the
> problem. In
> > > the machines that i have modified the registry to leave the ip adress on
> > > shutdown, when it turns on, it really does not have an address, but does
> not
> > > obtain an valid IP address, only the 169.*.*.*.
> > >
> > > Any idea how to solve this?
> > >
> > >
>
>
>