Yes, I had already authorized the server, but simply by using the shortcut
menu.
I have solved the problem by moving the DHCP to a non-AD member server. I
found one small paragraph in a Microsoft article headed "Caution" that
recommended not running DHCP on an AD machine. I still don't yet understand
why and what has changed between 2000 and 2003, but at least I have solved
my problem for now.
I would really like to have a fuller explanation on this though.
Thanks for your assistance.
Colin
"Bill Grant" <not.available@online> wrote in message
news:OX$(E-Mail Removed)...
> No, you need to authorise the DHCP server to start work! You must be an
> AD admin to do it.
>
> In W2k3 help search for DHCP, then read the article "Authorizing DHCP
> Servers". Follow the link "To authorize a DHCP Server in Active
Directory".
>
> "Colin Halliday" <colinh..at..kothes..com..au> wrote in message
> news:#(E-Mail Removed)...
> > I have "authorized" the DHCP server to make dynamic updates to DNS. Is
> > there anything else to do in AD Users & Computers for example.
> >
> > Also I am not certain about the Credentials button in DHCP - which
account
> > to use and exactly what groups does this account need to be in?
> >
> > Thanks
> >
> > Colin
> >
> >
> > "Bill Grant" <not.available@online> wrote in message
> > news:%23a$(E-Mail Removed)...
> > > I think you will find that DHCP has to be registered in AD before
> it
> > > can issue info to clients. This is a safety measure to prevent rogue
> DHCP
> > > servers.
> > >
> > > "Colin Halliday" <colhal at ozemail. com. au> wrote in message
> > > news:(E-Mail Removed)...
> > > > I have rebooted 100 times!! That was a given.
> > > >
> > > > Colin
> > > >
> > > > "sharad" <(E-Mail Removed)> wrote in message
> > > > news:(E-Mail Removed)...
> > > > > Why not reboot other 22 cleints?
> > > > >
> > > > > Sharad
> > > > > "Colin Halliday" <colhal..at..kothes..com..au> wrote in message
> > > > > news:%(E-Mail Removed)...
> > > > > > I upgraded an existing AD machine from Server 2000 to Server
2003.
> > It
> > > > was
> > > > > > also running DHCP for a simple single subnet (30 clients).
> > > > > >
> > > > > > After upgrade, all client machines that were switched on during
> the
> > > > > upgrade
> > > > > > (26 of them) lost their IPCONFIG settings and returned to
default
> > > > address
> > > > > of
> > > > > > 169. ... None of them can now find a DHCP server.
> > > > > >
> > > > > > I have only 2000 Pro and XP Pro clients.
> > > > > >
> > > > > > So I stopped DHCP on that server and started it on a brand new
> > machine
> > > > > which
> > > > > > came with Server 2003 pre-installed. I re-created from scratch
> the
> > > > single
> > > > > > scope with options, reservations etc. Authorized it as well.
> > > > > >
> > > > > > Still the clients cannot find a DHCP server!
> > > > > >
> > > > > > Four client machines had been switched off during the upgrade
> > process.
> > > > > > After all of the above I booted them and they talked to the new
> DHCP
> > > > > server
> > > > > > fine and have leases.
> > > > > >
> > > > > > I have had to manually assign addresses to the 26 clients to get
> > them
> > > to
> > > > > > talk on the network. Changing any of them to DHCP will not
work.
> > > After
> > > > > > doing so and doing an ipconfig /renew returns an error that no
> DHCP
> > > > server
> > > > > > can be found.
> > > > > >
> > > > > > Can anybody through some light on this for me?
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Colin Halliday
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
Similar Threads
Linear Mode
