Is there any ways to config the DHCP client in WinXP?

In my network environment, there are more than one DHCP servers. They
have different IP scope, but only one of them is what I need.
Unfortunately, the right DHCP server is "slower" than others, so every
time I want to renew an IP address, I get a wrong one from that
"faster" but "improper" DHCP server.

Therefore, I want ask that is there any ways for us to config the DHCP
client in WinXP? Say, we can specify a DHCP server that we want to
renew our IP address from, or delay our DHCP acknowledgement so that
we can accept a slower DHCP reply...Anyone has an idea?

Thanks!

Either I'm misunderstanding your question or you have a very badly
configured network. Are you saying that you have two or more DHCP servers
in the same address range? That's a very poor design and prone to real
problems, if true.

The only way to control what DHCP server hands out addresses to which
clients is to use routing, and to put the preferred PCs behind a router that
addresses the server/range you want them to get addresses from. There is no
way to configure WinXP (or any other Windows operating system) to do
otherwise, as DHCP is a broadcast request and the first server to respond
gets to hand out the address.

--
Richard G. Harper [MVP Shell/User]
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"GiGi" wrote in message
...
In my network environment, there are more than one DHCP servers. They have
different IP scope, but only one of them is what I need. Unfortunately,
the right DHCP server is "slower" than others, so every time I want to
renew an IP address, I get a wrong one from that "faster" but "improper"
DHCP server.

Therefore, I want ask that is there any ways for us to config the DHCP
client in WinXP? Say, we can specify a DHCP server that we want to renew
our IP address from, or delay our DHCP acknowledgement so that we can
accept a slower DHCP reply...Anyone has an idea?

Thanks!

Sorry for making you confused. The situation is, in my network
environment, there is an official DHCP server which provids IP
address, say, 10.0.*.*, but somebody else has set up a "fake" DHCP
server on his PC and it provides IP address of 192.168.*.*, and it is
faster than the official DHCP server. So you can imagine that I cannot
get the right IP I want.

There is such kind of DHCP client configurer in Linux which allows us
to assign a DHCP server so that we can only accept its DHCP reply, and
also allows us to set a delay when we begin to accept DHCP reply.

Does any MICROSOFTer care about this problem? Or any third-party
software can solve this?

Many thanks!


Richard G. Harper wrote:

Either I'm misunderstanding your question or you have a very badly
configured network. Are you saying that you have two or more DHCP servers
in the same address range? That's a very poor design and prone to real
problems, if true.

The only way to control what DHCP server hands out addresses to which
clients is to use routing, and to put the preferred PCs behind a router that
addresses the server/range you want them to get addresses from. There is no
way to configure WinXP (or any other Windows operating system) to do
otherwise, as DHCP is a broadcast request and the first server to respond
gets to hand out the address.

GiGi wrote:
Sorry for making you confused. The situation is, in my network
environment, there is an official DHCP server which provids IP address,
say, 10.0.*.*, but somebody else has set up a "fake" DHCP server on his
PC and it provides IP address of 192.168.*.*, and it is faster than the
official DHCP server. So you can imagine that I cannot get the right IP
I want.

There is such kind of DHCP client configurer in Linux which allows us to
assign a DHCP server so that we can only accept its DHCP reply, and also
allows us to set a delay when we begin to accept DHCP reply.

Does any MICROSOFTer care about this problem? Or any third-party
software can solve this?

Many thanks!


Richard G. Harper wrote:

Either I'm misunderstanding your question or you have a very badly
configured network. Are you saying that you have two or more DHCP
servers in the same address range? That's a very poor design and
prone to real problems, if true.

The only way to control what DHCP server hands out addresses to which
clients is to use routing, and to put the preferred PCs behind a
router that addresses the server/range you want them to get addresses
from. There is no way to configure WinXP (or any other Windows
operating system) to do otherwise, as DHCP is a broadcast request and
the first server to respond gets to hand out the address.



Have your IT administrator track down the faker and disconnect his account.
--
Cheers, Bob

Bob is right - this isn't a software or Microsoft problem, it's a network
problem being caused by your rogue DHCP server. Track it down and get it
off your network.

--
Richard G. Harper [MVP Shell/User]
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"GiGi" wrote in message
...
Sorry for making you confused. The situation is, in my network
environment, there is an official DHCP server which provids IP address,
say, 10.0.*.*, but somebody else has set up a "fake" DHCP server on his PC
and it provides IP address of 192.168.*.*, and it is faster than the
official DHCP server. So you can imagine that I cannot get the right IP I
want.

There is such kind of DHCP client configurer in Linux which allows us to
assign a DHCP server so that we can only accept its DHCP reply, and also
allows us to set a delay when we begin to accept DHCP reply.

Does any MICROSOFTer care about this problem? Or any third-party software
can solve this?

Many thanks!


Richard G. Harper wrote:

Either I'm misunderstanding your question or you have a very badly
configured network. Are you saying that you have two or more DHCP
servers in the same address range? That's a very poor design and prone
to real problems, if true.

The only way to control what DHCP server hands out addresses to which
clients is to use routing, and to put the preferred PCs behind a router
that addresses the server/range you want them to get addresses from.
There is no way to configure WinXP (or any other Windows operating
system) to do otherwise, as DHCP is a broadcast request and the first
server to respond gets to hand out the address.

Thanks, Richard and Bob. I know this is not the problem of Microsoft.
And I just want to know that whether Microsoft or someone else
provides such a tool to simplify our life. You know, I'm not the
administrator of our network, so once it happens I can only record the
MAC address of that fake DHCP server, report to the admin and then
wait...Nothing else I can do. And the admin may not be so efficient to
solve the problem quickly...

Anyway, thank you two very much. Then I think I can only employ some
firewall softwares to filter the packages from that fake server.

Best Regards,
GiGi

Richard G. Harper wrote:
Bob is right - this isn't a software or Microsoft problem, it's a network
problem being caused by your rogue DHCP server. Track it down and get it
off your network.

You can't firewall or protect your PC to "prevent the problem" - it is doing
what it is expected to do. Accepting an address from the first DHCP server
that responds. The only fix would be to stop using DHCP and put static
addressing in place.

--
Richard G. Harper [MVP Shell/User]
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"GiGi" wrote in message
...
Thanks, Richard and Bob. I know this is not the problem of Microsoft. And
I just want to know that whether Microsoft or someone else provides such a
tool to simplify our life. You know, I'm not the administrator of our
network, so once it happens I can only record the MAC address of that fake
DHCP server, report to the admin and then wait...Nothing else I can do.
And the admin may not be so efficient to solve the problem quickly...

Anyway, thank you two very much. Then I think I can only employ some
firewall softwares to filter the packages from that fake server.

Best Regards,
GiGi

Richard G. Harper wrote:
Bob is right - this isn't a software or Microsoft problem, it's a network
problem being caused by your rogue DHCP server. Track it down and get it
off your network.

Thanks. But actually I can block the IP address of that fake DHCP
server. That means any DHCP reply packet from that server will be
filtered and abandoned.

And I'm afraid that "the only fix" cannot be carried out because it is
forbidden by the network admin.


Richard G. Harper wrote:
You can't firewall or protect your PC to "prevent the problem" - it is doing
what it is expected to do. Accepting an address from the first DHCP server
that responds. The only fix would be to stop using DHCP and put static
addressing in place.

I'm not so sure that a firewall is going to do the trick, but wish you luck.

--
Richard G. Harper [MVP Shell/User]
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"GiGi" wrote in message
...
Thanks. But actually I can block the IP address of that fake DHCP server.
That means any DHCP reply packet from that server will be filtered and
abandoned.

And I'm afraid that "the only fix" cannot be carried out because it is
forbidden by the network admin.


Richard G. Harper wrote:
You can't firewall or protect your PC to "prevent the problem" - it is
doing what it is expected to do. Accepting an address from the first
DHCP server that responds. The only fix would be to stop using DHCP and
put static addressing in place.