DHCP 003 Router dissappears after server reboot

  • Thread starter Thread starter MacMan0295@gmail.com
  • Start date Start date
M

MacMan0295@gmail.com

Guest
I am having an issue with 003 Router dissappearing after I reboot my
Windows 2003 Server. I did some research and I thought I found the
problem to be http://support.microsoft.com/kb/936009/. Unfortunatly I
applied this patch and nothing happened. It still dissappears after
a reboot. The server is running Windows Server 2003 r2 SP2.

Thanks for any help

Craig
 
Re: DHCP 003 Router dissappears after server reboot


<MacMan0295@gmail.com> wrote in message
news:2c6762d4-98dd-44f6-9830-5c40ad5699c4@d1g2000hsg.googlegroups.com...
>I am having an issue with 003 Router dissappearing after I reboot my
> Windows 2003 Server. I did some research and I thought I found the
> problem to be http://support.microsoft.com/kb/936009/. Unfortunatly I
> applied this patch and nothing happened. It still dissappears after
> a reboot. The server is running Windows Server 2003 r2 SP2.

Your question is pretty vague. You mention "003 Router" as if
you are talking about DHCP (I would guess) but never mention
DHCP, whether you are using and internal or exteran DHCP
server etc.

If this is strictly a DHCP CLIENT issue, then you always need
to post the full, unedited, TEXT-ONLY output from "ipconfig /all".

Preferably you would post the one before when it worked
correctly, then the other where it was not correct....

Have you tried the obvious "ipconfig /refresh"?
 
Re: DHCP 003 Router dissappears after server reboot

On May 26, 2:39 pm, "Herb Martin" <n...@learnquick.com> wrote:
> <MacMan0...@gmail.com> wrote in message
>
> news:2c6762d4-98dd-44f6-9830-5c40ad5699c4@d1g2000hsg.googlegroups.com...
>
> >I am having an issue with 003 Router dissappearing after I reboot my
> > Windows 2003 Server.  I did some research and I thought I found the
> > problem to behttp://support.microsoft.com/kb/936009/. Unfortunatly I
> > applied this patch and nothing happened.  It still dissappears after
> > a reboot.  The server is running Windows Server 2003 r2 SP2.
>
> Your question is pretty vague.  You mention "003 Router" as if
> you are talking about DHCP (I would guess) but never mention
> DHCP, whether you are using and internal or exteran DHCP
> server etc.
>
> If this is strictly a DHCP CLIENT issue, then you always need
> to post the full, unedited, TEXT-ONLY output from "ipconfig /all".
>
> Preferably you would post the one before when it worked
> correctly, then the other where it was not correct....
>
> Have you tried the obvious "ipconfig /refresh"?

This is a DHCP server issue. In the title I mention that it is a DHCP
issue. On the server, when configuring the Scope options, when I add
the "003 Router" option and configure it, the next time I reboot the
server it has disappeared. Please let me know if I am missing any
other information that can help figure this darn thing out. Thanks.

Craig
 
Re: DHCP 003 Router dissappears after server reboot


<MacMan0295@gmail.com> wrote in message
news:326a9ded-d9eb-4753-88d8-178208b08490@f63g2000hsf.googlegroups.com...
On May 26, 2:39 pm, "Herb Martin" <n...@learnquick.com> wrote:
> <MacMan0...@gmail.com> wrote in message
>
> news:2c6762d4-98dd-44f6-9830-5c40ad5699c4@d1g2000hsg.googlegroups.com...
>
> >I am having an issue with 003 Router dissappearing after I reboot my
> > Windows 2003 Server. I did some research and I thought I found the
> > problem to behttp://support.microsoft.com/kb/936009/. Unfortunatly I
> > applied this patch and nothing happened. It still dissappears after
> > a reboot. The server is running Windows Server 2003 r2 SP2.
>
> Your question is pretty vague. You mention "003 Router" as if
> you are talking about DHCP (I would guess) but never mention
> DHCP, whether you are using and internal or exteran DHCP
> server etc.
>
> If this is strictly a DHCP CLIENT issue, then you always need
> to post the full, unedited, TEXT-ONLY output from "ipconfig /all".
>
> Preferably you would post the one before when it worked
> correctly, then the other where it was not correct....
>
> Have you tried the obvious "ipconfig /refresh"?

#This is a DHCP server issue. In the title I mention that it is a DHCP
#issue.

Yes, but you didn't specific "DHCP Client" or "DHCP Server" (servers
and workstations may both be such clients) and thus have wasted
a lot of time when you might have gotten a reply already.

#On the server, when configuring the Scope options, when I add
#the "003 Router" option and configure it, the next time I reboot the
#server it has disappeared. Please let me know if I am missing any
#other information that can help figure this darn thing out. Thanks.

What happens if you close, then re-open the MMC?

That should save immediately -- that is a bug or something weird
is going on that is not experience by most people.

Do any clients actually receive the value (if you don't first reboot)?
(Perhaps the value is never getting set.)

Play around with activating/de-activating. Stop/start JUST the
service -- to see if the reboot is part of the problem and for
faster testing.

Perhaps this Google search will help:

[ site:microsoft.com dhcp options ~missing | ~disappear after server ~reboot
| ~restart ]

First hit is this article:
After you restart the DHCP Server service, some DHCP options
disappear on a Windows Server 2003-based DHCP server
http://support.microsoft.com/kb/938134
(there is a hotfix referenced)
 
Re: DHCP 003 Router dissappears after server reboot

On May 26, 4:29 pm, "Herb Martin" <n...@learnquick.com> wrote:
> <MacMan0...@gmail.com> wrote in message
>
> news:326a9ded-d9eb-4753-88d8-178208b08490@f63g2000hsf.googlegroups.com...
> On May 26, 2:39 pm, "Herb Martin" <n...@learnquick.com> wrote:
>
>
>
>
>
> > <MacMan0...@gmail.com> wrote in message
>
> >news:2c6762d4-98dd-44f6-9830-5c40ad5699c4@d1g2000hsg.googlegroups.com...
>
> > >I am having an issue with 003 Router dissappearing after I reboot my
> > > Windows 2003 Server. I did some research and I thought I found the
> > > problem to behttp://support.microsoft.com/kb/936009/. Unfortunatly I
> > > applied this patch and nothing happened. It still dissappears after
> > > a reboot. The server is running Windows Server 2003 r2 SP2.
>
> > Your question is pretty vague. You mention "003 Router" as if
> > you are talking about DHCP (I would guess) but never mention
> > DHCP, whether you are using and internal or exteran DHCP
> > server etc.
>
> > If this is strictly a DHCP CLIENT issue, then you always need
> > to post the full, unedited, TEXT-ONLY output from "ipconfig /all".
>
> > Preferably you would post the one before when it worked
> > correctly, then the other where it was not correct....
>
> > Have you tried the obvious "ipconfig /refresh"?
>
> #This is a DHCP server issue.  In the title I mention that it is a DHCP
> #issue.
>
> Yes, but you didn't specific "DHCP Client" or "DHCP Server" (servers
> and workstations may both be such clients) and thus have wasted
> a lot of time when you might have gotten a reply already.
>
> #On the server, when configuring the Scope options, when I add
> #the "003 Router" option and configure it, the next time I reboot the
> #server it has disappeared.  Please let me know if I am missing any
> #other information that can help figure this darn thing out.  Thanks.
>
> What happens if you close, then re-open the MMC?
>
> That should save immediately -- that is a bug or something weird
> is going on that is not experience by most people.
>
> Do any clients actually receive the value (if you don't first reboot)?
> (Perhaps the value is never getting set.)
>
> Play around with activating/de-activating.  Stop/start JUST the
> service -- to see if the reboot is part of the problem and for
> faster testing.
>
> Perhaps this Google search will help:
>
> [ site:microsoft.com dhcp options ~missing | ~disappear after server ~reboot
> | ~restart ]
>
> First hit is this article:
> After you restart the DHCP Server service, some DHCP options
> disappear on a Windows Server 2003-based DHCP serverhttp://support.microsoft.com/kb/938134
> (there is a hotfix referenced)- Hide quoted text -
>
> - Show quoted text -

Once I make the entry, It saves and people are able to get the value
with no problem. If the MMC closes, there is no problem there. If
you stop/start the service or reboot the server then the entry
disappears. thanks.

Craig
 
Check for invalid data elsewhere in the scope..

Check for invalid data elsewhere in the scope..

I had this exact same problem on one of our DHCP server scopes.

As I got to the point where I was going to delete and recreate the scope, I started taking note of the reservations and other scope detail.

I found a reservation that was set to an invalid IP address for the scope. (Scope was 172.23.3.0/24 giving range 172.23.3.1 - 172.23.3.254 and the reservation was set to 172.23.3.0 !?)

Once this reservation was removed, things were happy again through DHCPServer restarts.

I think I've seen this kind of thing before as well. Check and double check all your scope details; ranges, exclusions, reservations. Make sure they're all correct and do not break any networking rules. Sometimes Microsoft DHCP lets you put stuff in that's just plain wrong and invalid.

HTH
Simon.
 
Check for invalid data elsewhere in the scope..

Check for invalid data elsewhere in the scope..

I had this exact same issue on one particular DHCP scope on a server I support.

Just as I was about to resort to deletion and recreation of the scope in question, I starting making notes of the various settings / options / reservations and found a reservation that had been set to an IP outside the range given by the scope.

Scope was 172.23.3.0/24
Range 172.23.3.1 -> 172.23.3.254
Reservation somehow ended up on 172.23.3.0

Deleted the invalid reservation, and all was happy again.

I think I've seen this kind of thing before with MS DHCP. Sometimes, you can put crazy settings in there that make no logical sense. When you do, it can cause other odd side-effects.

Check all your scope range / exclusions / reservations etc. and make sure there's no invalid data in there. It could be as simple as this.

HTH
Simon.
 
RE: Check for invalid data elsewhere in the scope..

RE: Check for invalid data elsewhere in the scope..

That was exactly the issue. Thanks for the info. Soooo simple.

Craig

"Simon Lowe" wrote:

> I had this exact same issue on one particular DHCP scope on a server I support.
>
> Just as I was about to resort to deletion and recreation of the scope in question, I starting making notes of the various settings / options / reservations and found a reservation that had been set to an IP outside the range given by the scope.
>
> Scope was 172.23.3.0/24
> Range 172.23.3.1 -> 172.23.3.254
> Reservation somehow ended up on 172.23.3.0
>
> Deleted the invalid reservation, and all was happy again.
>
> I think I've seen this kind of thing before with MS DHCP. Sometimes, you can put crazy settings in there that make no logical sense. When you do, it can cause other odd side-effects.
>
> Check all your scope range / exclusions / reservations etc. and make sure there's no invalid data in there. It could be as simple as this.
>
> HTH
> Simon.
>
 
Back
Top