dhcp service stops

Hello *,

how do I prevent a dhcp server service to stop when another dhcp service is
detected?

I have a Windows Server 2003 dhcp server that is authorized in AD that stops
working after it detects a rogue dhcp server. The rogue dhcp server, however,
does not stop so clients get inappropriate ip addresses. Even after the rogue
dhcp server has been identified, the authorized server does not work any more
so clients end up getting no ip addresses at all.

I have tried it with another Windows 2003 dhcp: Whenever I start the dhcp
server service, it does start regardless of the official dhcp server
authorized in ad and the official dhcp server sservice stops.

/Klaus

/Klaus

What do you mean by 'stops working' ?

Does the DHCP service go from the Running state to the Stopped state? This
would be alarming and too difficult for me to understand.

Do newly powered up workstations only get IP addresses from the rogue DHCP
server? This means that it is faster to respond to broadcasts than your
authorized DHCP server.

You have to disable the rogue server by hand. MS term 'authorization' of a
DHCP server in AD is somewhat misleading. AD is made of software - how can it
control a device on the LAN which decides to start responding to DHCP
discover requests?
There are (fortunately) limits to the power of the imperium!
--
Regards,
Newell White

"Klaus Koehler" wrote:

> Hello *,
>
> how do I prevent a dhcp server service to stop when another dhcp service is
> detected?
>
> I have a Windows Server 2003 dhcp server that is authorized in AD that stops
> working after it detects a rogue dhcp server. The rogue dhcp server, however,
> does not stop so clients get inappropriate ip addresses. Even after the rogue
> dhcp server has been identified, the authorized server does not work any more
> so clients end up getting no ip addresses at all.
>
> I have tried it with another Windows 2003 dhcp: Whenever I start the dhcp
> server service, it does start regardless of the official dhcp server
> authorized in ad and the official dhcp server sservice stops.
>
> /Klaus

What do you mean by
--
Newell White

Exactly that is happening, the service goes to the stopped state.

I do not understand why the service on the machine that is authorized in ad
stops working where the service on a machine not authorized (not even member
of the domain) continues to work. It should be the other way round or at
least some kind of concurrency. I could live with that, disable the rogue
server and be happy. ut unfortunately, I have to enable the original server
manually.

/Klaus

"Newell White" wrote:

> What do you mean by 'stops working' ?
>
> Does the DHCP service go from the Running state to the Stopped state? This
> would be alarming and too difficult for me to understand.
>
> Do newly powered up workstations only get IP addresses from the rogue DHCP
> server? This means that it is faster to respond to broadcasts than your
> authorized DHCP server.
>
> You have to disable the rogue server by hand. MS term 'authorization' of a
> DHCP server in AD is somewhat misleading. AD is made of software - how can it
> control a device on the LAN which decides to start responding to DHCP
> discover requests?
> There are (fortunately) limits to the power of the imperium!
> --
> Regards,
> Newell White
>
> "Klaus Koehler" wrote:
>
> > Hello *,
> >
> > how do I prevent a dhcp server service to stop when another dhcp service is
> > detected?
> >
> > I have a Windows Server 2003 dhcp server that is authorized in AD that stops
> > working after it detects a rogue dhcp server. The rogue dhcp server, however,
> > does not stop so clients get inappropriate ip addresses. Even after the rogue
> > dhcp server has been identified, the authorized server does not work any more
> > so clients end up getting no ip addresses at all.
> >
> > I have tried it with another Windows 2003 dhcp: Whenever I start the dhcp
> > server service, it does start regardless of the official dhcp server
> > authorized in ad and the official dhcp server sservice stops.
> >
> > /Klaus
>
> What do you mean by
> --
> Newell White
>

I agree, that is strange.
On 23rd October I added a second router to our network, with intention of
using reservations in DHCP to point half our workstations to the new gateway
address.
Unfortunately I forgot to disable its DHCP server, and chaos quickly broke
out - but the DHCP service did not stop on either of our two DCs.

Both are W2k3 Standard, not R2, with SP2 and all subsequent critical updates.

--
Regards,
Newell White


"Klaus Koehler" wrote:

> Exactly that is happening, the service goes to the stopped state.
>
> I do not understand why the service on the machine that is authorized in ad
> stops working where the service on a machine not authorized (not even member
> of the domain) continues to work. It should be the other way round or at
> least some kind of concurrency. I could live with that, disable the rogue
> server and be happy. ut unfortunately, I have to enable the original server
> manually.
>
> /Klaus
>
> "Newell White" wrote:
>
> > What do you mean by 'stops working' ?
> >
> > Does the DHCP service go from the Running state to the Stopped state? This
> > would be alarming and too difficult for me to understand.
> >
> > Do newly powered up workstations only get IP addresses from the rogue DHCP
> > server? This means that it is faster to respond to broadcasts than your
> > authorized DHCP server.
> >
> > You have to disable the rogue server by hand. MS term 'authorization' of a
> > DHCP server in AD is somewhat misleading. AD is made of software - how can it
> > control a device on the LAN which decides to start responding to DHCP
> > discover requests?
> > There are (fortunately) limits to the power of the imperium!
> > --
> > Regards,
> > Newell White
> >
> > "Klaus Koehler" wrote:
> >
> > > Hello *,
> > >
> > > how do I prevent a dhcp server service to stop when another dhcp service is
> > > detected?
> > >
> > > I have a Windows Server 2003 dhcp server that is authorized in AD that stops
> > > working after it detects a rogue dhcp server. The rogue dhcp server, however,
> > > does not stop so clients get inappropriate ip addresses. Even after the rogue
> > > dhcp server has been identified, the authorized server does not work any more
> > > so clients end up getting no ip addresses at all.
> > >
> > > I have tried it with another Windows 2003 dhcp: Whenever I start the dhcp
> > > server service, it does start regardless of the official dhcp server
> > > authorized in ad and the official dhcp server sservice stops.
> > >
> > > /Klaus
> >
> > What do you mean by
> > --
> > Newell White
> >

Thats exactly the behaviour I would like to see on my machines. I have R2 but
I don't think that matters. Did you configure your server manually or using
the server wizards? Maybe the wizard does strange things and I can remember
me trying out the wizards to check whether they are suitable for anything
useful ;-)

"Newell White" wrote:

> I agree, that is strange.
> On 23rd October I added a second router to our network, with intention of
> using reservations in DHCP to point half our workstations to the new gateway
> address.
> Unfortunately I forgot to disable its DHCP server, and chaos quickly broke
> out - but the DHCP service did not stop on either of our two DCs.
>
> Both are W2k3 Standard, not R2, with SP2 and all subsequent critical updates.
>
> --
> Regards,
> Newell White
>
>
> "Klaus Koehler" wrote:
>
> > Exactly that is happening, the service goes to the stopped state.
> >
> > I do not understand why the service on the machine that is authorized in ad
> > stops working where the service on a machine not authorized (not even member
> > of the domain) continues to work. It should be the other way round or at
> > least some kind of concurrency. I could live with that, disable the rogue
> > server and be happy. ut unfortunately, I have to enable the original server
> > manually.
> >
> > /Klaus
> >
> > "Newell White" wrote:
> >
> > > What do you mean by 'stops working' ?
> > >
> > > Does the DHCP service go from the Running state to the Stopped state? This
> > > would be alarming and too difficult for me to understand.
> > >
> > > Do newly powered up workstations only get IP addresses from the rogue DHCP
> > > server? This means that it is faster to respond to broadcasts than your
> > > authorized DHCP server.
> > >
> > > You have to disable the rogue server by hand. MS term 'authorization' of a
> > > DHCP server in AD is somewhat misleading. AD is made of software - how can it
> > > control a device on the LAN which decides to start responding to DHCP
> > > discover requests?
> > > There are (fortunately) limits to the power of the imperium!
> > > --
> > > Regards,
> > > Newell White
> > >
> > > "Klaus Koehler" wrote:
> > >
> > > > Hello *,
> > > >
> > > > how do I prevent a dhcp server service to stop when another dhcp service is
> > > > detected?
> > > >
> > > > I have a Windows Server 2003 dhcp server that is authorized in AD that stops
> > > > working after it detects a rogue dhcp server. The rogue dhcp server, however,
> > > > does not stop so clients get inappropriate ip addresses. Even after the rogue
> > > > dhcp server has been identified, the authorized server does not work any more
> > > > so clients end up getting no ip addresses at all.
> > > >
> > > > I have tried it with another Windows 2003 dhcp: Whenever I start the dhcp
> > > > server service, it does start regardless of the official dhcp server
> > > > authorized in ad and the official dhcp server sservice stops.
> > > >
> > > > /Klaus
> > >
> > > What do you mean by
> > > --
> > > Newell White
> > >

DHCP servers were configured manually, with one scope only (we have about 50
clients).
Only scope options configured arE
003
006 (both DCs)
015
044 (both DCs)
046 (0x8)

I dont think the wizards (any) are useful - they hide what is going on in
the engine and gearbox!
--
Regards,
Newell White


"Klaus Koehler" wrote:

> Thats exactly the behaviour I would like to see on my machines. I have R2 but
> I don't think that matters. Did you configure your server manually or using
> the server wizards? Maybe the wizard does strange things and I can remember
> me trying out the wizards to check whether they are suitable for anything
> useful ;-)
>
> "Newell White" wrote:
>
> > I agree, that is strange.
> > On 23rd October I added a second router to our network, with intention of
> > using reservations in DHCP to point half our workstations to the new gateway
> > address.
> > Unfortunately I forgot to disable its DHCP server, and chaos quickly broke
> > out - but the DHCP service did not stop on either of our two DCs.
> >
> > Both are W2k3 Standard, not R2, with SP2 and all subsequent critical updates.
> >
> > --
> > Regards,
> > Newell White
> >
> >
> > "Klaus Koehler" wrote:
> >
> > > Exactly that is happening, the service goes to the stopped state.
> > >
> > > I do not understand why the service on the machine that is authorized in ad
> > > stops working where the service on a machine not authorized (not even member
> > > of the domain) continues to work. It should be the other way round or at
> > > least some kind of concurrency. I could live with that, disable the rogue
> > > server and be happy. ut unfortunately, I have to enable the original server
> > > manually.
> > >
> > > /Klaus
> > >
> > > "Newell White" wrote:
> > >
> > > > What do you mean by 'stops working' ?
> > > >
> > > > Does the DHCP service go from the Running state to the Stopped state? This
> > > > would be alarming and too difficult for me to understand.
> > > >
> > > > Do newly powered up workstations only get IP addresses from the rogue DHCP
> > > > server? This means that it is faster to respond to broadcasts than your
> > > > authorized DHCP server.
> > > >
> > > > You have to disable the rogue server by hand. MS term 'authorization' of a
> > > > DHCP server in AD is somewhat misleading. AD is made of software - how can it
> > > > control a device on the LAN which decides to start responding to DHCP
> > > > discover requests?
> > > > There are (fortunately) limits to the power of the imperium!
> > > > --
> > > > Regards,
> > > > Newell White
> > > >
> > > > "Klaus Koehler" wrote:
> > > >
> > > > > Hello *,
> > > > >
> > > > > how do I prevent a dhcp server service to stop when another dhcp service is
> > > > > detected?
> > > > >
> > > > > I have a Windows Server 2003 dhcp server that is authorized in AD that stops
> > > > > working after it detects a rogue dhcp server. The rogue dhcp server, however,
> > > > > does not stop so clients get inappropriate ip addresses. Even after the rogue
> > > > > dhcp server has been identified, the authorized server does not work any more
> > > > > so clients end up getting no ip addresses at all.
> > > > >
> > > > > I have tried it with another Windows 2003 dhcp: Whenever I start the dhcp
> > > > > server service, it does start regardless of the official dhcp server
> > > > > authorized in ad and the official dhcp server sservice stops.
> > > > >
> > > > > /Klaus
> > > >
> > > > What do you mean by
> > > > --
> > > > Newell White
> > > >

I would hate to think it is a difference between plain old vanilla 2003 and R2.

Try summarising what we have been over and start a new thread titled
"calling Phillip Windell" - he seems to know more about DHCP than most.
--
Regards,
Newell White


"Klaus Koehler" wrote:

> Thats exactly the behaviour I would like to see on my machines. I have R2 but
> I don't think that matters. Did you configure your server manually or using
> the server wizards? Maybe the wizard does strange things and I can remember
> me trying out the wizards to check whether they are suitable for anything
> useful ;-)
>

Windows DHCP Server is not smart enough to detect to a rouge dhcp
server. But if you have a Cisco switch you can use DHCP snooping.

Klaus Koehler;3361640 Wrote:
> Hello *,
>
> I have a Windows Server 2003 dhcp server that is authorized in AD that
> stops
> working after it detects a rogue dhcp server. The rogue dhcp server,
> however,
> does not stop so clients get inappropriate ip addresses.
> /Klaus
>
> /Klaus


--
dennyd
------------------------------------------------------------------------
dennyd's Profile: http://forums.techarena.in/member.php?userid=50495
View this thread: http://forums.techarena.in/showthread.php?t=866298

http://forums.techarena.in