Re: dhcp clients & new dhcp server

From: Rob Elder MVP-Networking (relder_at_thisisnotright.com)
Date: 09/19/04


Date: Sun, 19 Sep 2004 08:13:38 -0400

Steve's reply is the best solution.

To answer you second question, DHCP requests are made by a discover
broadcast. You don't configure them to point to a specific server. As long
as the new DHCP server is on the same subnet, your clients won't have a
problem getting a new IP address.

"Espowari" <Espowari@discussions.microsoft.com> wrote in message
news:B5AB3A7B-4125-42F7-837E-A3A0DC346672@microsoft.com...
> Thanks Steve.
>
> One further question: I am unsure if we'll be changing the IP address of
the
> new DHCP server to match the NT4 machine that we're bringing down. While
that
> would be ideal for the clients to hit the same machine, if it is a
different
> IP, DHCP requests will go out to a non-existent address, get no reply, and
> then broadcast for a DHCP ack - the new server will then complete the DORA
> process and clients will be properly addressed.
>
> This isn't really a question I know, but just wanted to bounce this idea
off
> you.
>
> Thanks,
>
> E
>
> "Steve Bruce, mct" wrote:
>
> > The default lease is for 7 or 8 days. Reduce the lease interval to 1
hour
> > on the NT4 DHCP server, one week in advance of shutting it down. By the
> > time you take the NT4 server off-line they clients will be renewing
every 1
> > hour and will make the transition to the new DHCP server within an hour
of
> > shutting down the old.
> >
> >
> > "Espowari" <Espowari@discussions.microsoft.com> wrote in message
> > news:66B4073C-A7E9-4534-981A-B8C91CBA2EA3@microsoft.com...
> > > We're moving our dhcp service off of an NT4 box, onto a 2k or 2k3
server.
> > > I understand how to migrate the data, but have a question about the
client
> > > side of the house.
> > > How will our 2K and XP dhcp clients weather the storm? One suggestion
was
> > > to
> > > turn off all the client PCs, migrate the server and then turn the
clients
> > > back on.
> > > This seems a little excessive, as there are over 700 machines in our
> > > office.
> > > It seems to me that clients will have their address and when they send
out
> > > the dhcp request, they will be granted the same IP. DHCP is smart
enough
> > > to
> > > understand what IP's are already in use and this is a non issue.
> > >
> > > Thoughts and suggestions appreciated
> > >
> > >
> >
> >
> >



Relevant Pages

  • RE: DHCP for Simple Security
    ... > our clients to have a unique User-Defined Class in IPconfig. ... > Microsoft DHCP server would support IP assignment by User-Defined ... User Class option. ...
    (microsoft.public.windows.server.networking)
  • Re: wireless router
    ... David's suggestion to check the DHCP server bindings is where I'd be ... If I found that DHCP server was bound to the external NIC I'd probably run ... The internal clients will be using DHCP of the internal ... >> wireless clients who come into the office to connect to the internet ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS Scavenged all my Service records!
    ... I made the changes to our DHCP scope as per your suggestions below, ... Good, in most cases, I see DNS scavenging as an unnecessary process, if the ... DHCP clients are properly configured. ... DHCP server is configured to dynamically update DNS.... ...
    (microsoft.public.windows.server.dns)
  • Re: DHCP issue
    ... - if you set up a static pool then remote clients will be distributed IP ... the DHCP settings. ... However if your DHCP server is on a different subnet then ...
    (microsoft.public.win2000.ras_routing)
  • Re: Windows clients unable to obtain DHCP lease after server move.
    ... and dhcp configuration, but now the clients cannot obtain a lease ... process of obtaining an IP address from the DHCP server. ... moving ISC dhcp server to serverB, my Windows clients can no longer ...
    (comp.os.linux.networking)