DHCP server Unauthorized, Need to Authorize (Not in an AD environm

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

DHCP server Unauthorized, Need to Authorize (Not in an AD environment)

Greetings,

Recently we had our old DHCP server go down (running nt 4.0) and rebuilt it
as a win 2k box.

We are starting to have some conflicts on other systems due to this.

The main problem were running into is our phone system (which runs on a
workgroup and has its own DHCP server that handles all the phone ips) is not
working.
"When a DHCP server that is not a member server of the domain (such as a
member of a workgroup) comes up, the following happens: The server broadcasts
a DHCPINFORM message on the network. Any other server that receives this
message responds with DHCPACK message and provides the name of the directory
domain it is part of. If a workgroup DHCP server detects another member DHCP
server of a domain on the network, the workgroup DHCP server assumes that it
is unauthorized on that network and does not service requests. If the
workgroup DHCP server detects the presence of another workgroup server, it
ignores it; this means that there can be multiple workgroup servers active
at the same time, as long as there is no directory service.

Even when a workgroup server comes up and finds itself allowed to run
(because no other domain member server or workgroup server is on the
network), it continues to probe DHCPINFORM every five minutes. If an
authorized domain member DHCP server comes up later, the workgroup server
becomes unauthorized and stops servicing."

The DHCP on the main server sees it as unauthorized, and tells it to shut
down.

Is there a way to authorize my workgroup dhcp server with the main DHCP
server so it does not shut down? When I go on our main DHCP server, and try
to authorize it there, it tells me that the DHCP service could not contact
the AD (which is correct because were not running AD)

Any help would be appreciated
 
castiron999 said:
DHCP server Unauthorized, Need to Authorize (Not in an AD environment)

Greetings,

Recently we had our old DHCP server go down (running nt 4.0) and rebuilt it
as a win 2k box.

We are starting to have some conflicts on other systems due to this.

The main problem were running into is our phone system (which runs on a
workgroup and has its own DHCP server that handles all the phone ips) is not
working.
"When a DHCP server that is not a member server of the domain (such as a
member of a workgroup) comes up, the following happens: The server broadcasts
a DHCPINFORM message on the network. Any other server that receives this
message responds with DHCPACK message and provides the name of the directory
domain it is part of. If a workgroup DHCP server detects another member DHCP
server of a domain on the network, the workgroup DHCP server assumes that it
is unauthorized on that network and does not service requests. If the
workgroup DHCP server detects the presence of another workgroup server, it
ignores it; this means that there can be multiple workgroup servers active
at the same time, as long as there is no directory service.

Even when a workgroup server comes up and finds itself allowed to run
(because no other domain member server or workgroup server is on the
network), it continues to probe DHCPINFORM every five minutes. If an
authorized domain member DHCP server comes up later, the workgroup server
becomes unauthorized and stops servicing."

The DHCP on the main server sees it as unauthorized, and tells it to shut
down.

Is there a way to authorize my workgroup dhcp server with the main DHCP
server so it does not shut down? When I go on our main DHCP server, and try
to authorize it there, it tells me that the DHCP service could not contact
the AD (which is correct because were not running AD)

Any help would be appreciated
Click to expand...

First of all, a question. How does the "phone" DHCP server know to only
hand out IP addresses to phones? Since DHCP is broadcast, ANY DHCP
server will normally hand out IP addresses to any DHCP client requesting
one.

Second - the quotation you cited seems to disagree with what you have
stated. The quote refers to an AD DHCP server's ability to shut down a
rogue DHCP server. You have said that you are not running an Active
Directory. "If the workgroup DHCP server detects the presence of
another workgroup server, it ignores it; this means that there can be
multiple workgroup servers active at the same time, as long as there is
no directory service." So what do you want to authorize your new DHCP
server with since you are not running an AD? If you mean that the "main"
DHCP server IS an AD member, and you want to run a workgroup server
along with it, the only way to do that would be to join the new server o
the domain.

....kurt
 
Back
Top