Home All Groups Group Topic Archive Search About

DHCP Event ID 1046 AD/DNS Issues



Author
29 Nov 2007 1:50 PM
DHegler
I am having issues on getting DHCP to work on the new server I just installed
on our network.  I get:

Event ID 1046:
The DHCP/BINL service on the local machine, belonging to the Windows
Administrative domain ilttoyotalift.local, has determined that it is not
authorized to start.  It has stopped servicing clients.  The following are
some possible reasons for this:
    This machine is part of a directory service enterprise and is  not
authorized in the same domain.  (See help on the DHCP Service  Management
Tool for additional information).

    This machine cannot reach its directory service enterprise and  it has
encountered another DHCP service on the network belonging to  a directory
service enterprise on which the local machine is not authorized.

    Some unexpected network error occurred.

Then I get:

Event ID 1044:
The DHCP/BINL service on the local machine, belonging to the Windows
Administrative domain ilttoyotalift.local, has determined that it is
authorized to start. It is servicing clients now.


However, DHCP does not service any clients.  Here is the background as to
how this environment was configured...

It was a Windows server 2003 SBS server running everything - DHCP, DNS, AD,
DC, GC, all 5 FSMO, Exchange, etc.  We hit the 50-user limit and have
multiple sites, so I decided to buy what we should have bought before my time
here - Standard Server, etc...

I installed a new Standard Server into AD, added as DC, GC, DNS, DHCP, added
Exchange 2003 Standard.  I seized all 5 FSMO roles, then demoted the original
SBS Server, removed DNS, DHCP.  It still runs Exchange, but there are no
active users on it and our firewall is forwarding SMTP to the new server just
fine.

It still appears as if somewhere in AD, it has records of the original SBS
server being registered as a DNS server.  The only live DNS server is the new
server and it has itself listed as its DNS server in its IP settings.

Also, something else weird about this server is that when I look at the IP
settings in the network connection, I set the static IPs, but when I save
them it always shows that it will use DHCP, but even after I reboot the
server it does keep its static settings.  I have also tried to reset the
static settings a few times and rebooted, but it always shows it will use
DHCP, but keeps the static settings from an ipconfig.

Any ideas from anyone?  It has been a while since I have gotten this far
into networking, as I used to be a MCSE+I, MCDBA and all that good stuff
until I moved into finance.

FYI - I also ran through Microsoft's ntdsutil steps to make sure that the
demotion of the SBS server was graceful, and I have checked the record for
the new server using ADSI Edit under Configuration, Services, Net Services -
it shows up fine.  And, yes, I have authorized, unauthorized, restarted and
removed/reinstalled the DHCP service on this machine as well, but the actions
are still the same.

It feels to me that it is trying to authorize itself with the old server,
but can't see it and won't work.  However, before I made any changes to the
old SBS server, I had installed DHCP on the new server and it acted the same
way as well, so maybe I'm crazy.

Thanks,
Dan Hegler

Author
29 Nov 2007 4:07 PM
ctvader
On Nov 29, 8:50 am, DHegler <DHeg***@discussions.microsoft.com> wrote:
Show quote
> I am having issues on getting DHCP to work on the new server I just installed
> on our network.  I get:
>
> Event ID 1046:
> The DHCP/BINL service on the local machine, belonging to the Windows
> Administrative domain ilttoyotalift.local, has determined that it is not
> authorized to start.  It has stopped servicing clients.  The following are
> some possible reasons for this:
>         This machine is part of a directory service enterprise and is  not
> authorized in the same domain.  (See help on the DHCP Service  Management
> Tool for additional information).
>
>         This machine cannot reach its directory service enterprise and  it has
> encountered another DHCP service on the network belonging to  a directory
> service enterprise on which the local machine is not authorized.
>
>         Some unexpected network error occurred.
>
> Then I get:
>
> Event ID 1044:
> The DHCP/BINL service on the local machine, belonging to the Windows
> Administrative domain ilttoyotalift.local, has determined that it is
> authorized to start. It is servicing clients now.
>
> However, DHCP does not service any clients.  Here is the background as to
> how this environment was configured...
>
> It was a Windows server 2003 SBS server running everything - DHCP, DNS, AD,
> DC, GC, all 5 FSMO, Exchange, etc.  We hit the 50-user limit and have
> multiple sites, so I decided to buy what we should have bought before my time
> here - Standard Server, etc...
>
> I installed a new Standard Server into AD, added as DC, GC, DNS, DHCP, added
> Exchange 2003 Standard.  I seized all 5 FSMO roles, then demoted the original
> SBS Server, removed DNS, DHCP.  It still runs Exchange, but there are no
> active users on it and our firewall is forwarding SMTP to the new server just
> fine.
>
> It still appears as if somewhere in AD, it has records of the original SBS
> server being registered as a DNS server.  The only live DNS server is the new
> server and it has itself listed as its DNS server in its IP settings.
>
> Also, something else weird about this server is that when I look at the IP
> settings in the network connection, I set the static IPs, but when I save
> them it always shows that it will use DHCP, but even after I reboot the
> server it does keep its static settings.  I have also tried to reset the
> static settings a few times and rebooted, but it always shows it will use
> DHCP, but keeps the static settings from an ipconfig.
>
> Any ideas from anyone?  It has been a while since I have gotten this far
> into networking, as I used to be a MCSE+I, MCDBA and all that good stuff
> until I moved into finance.
>
> FYI - I also ran through Microsoft's ntdsutil steps to make sure that the
> demotion of the SBS server was graceful, and I have checked the record for
> the new server using ADSI Edit under Configuration, Services, Net Services -
> it shows up fine.  And, yes, I have authorized, unauthorized, restarted and
> removed/reinstalled the DHCP service on this machine as well, but the actions
> are still the same.
>
> It feels to me that it is trying to authorize itself with the old server,
> but can't see it and won't work.  However, before I made any changes to the
> old SBS server, I had installed DHCP on the new server and it acted the same
> way as well, so maybe I'm crazy.
>
> Thanks,
> Dan Hegler

Did you authorize the DHCP/RIS Server?  In dhcpmgmt.msc, right click
on the server and select authorize from the fly-out menu.
Author
29 Nov 2007 4:40 PM
DHegler
I wish it were that easy.  In the second last paragraph:
> And, yes, I have authorized, unauthorized, restarted and
> removed/reinstalled the DHCP service on this machine as well, but the actions
> are still the same."

Any other ideas anywhere?  I have tried to reinstall DHCP, unauthorize,
reauthorize, etc.  Every time I do that, I see it making what I believe to be
the correct entries in <domain>.Configuration.Services.NetServices for the
server.

Thanks for the try!

Dan

Show quote
"DHegler" wrote:

> I am having issues on getting DHCP to work on the new server I just installed
> on our network.  I get:
>
> Event ID 1046:
> The DHCP/BINL service on the local machine, belonging to the Windows
> Administrative domain ilttoyotalift.local, has determined that it is not
> authorized to start.  It has stopped servicing clients.  The following are
> some possible reasons for this:
>     This machine is part of a directory service enterprise and is  not
> authorized in the same domain.  (See help on the DHCP Service  Management
> Tool for additional information).
>
>     This machine cannot reach its directory service enterprise and  it has
> encountered another DHCP service on the network belonging to  a directory
> service enterprise on which the local machine is not authorized.
>
>     Some unexpected network error occurred.
>
> Then I get:
>
> Event ID 1044:
> The DHCP/BINL service on the local machine, belonging to the Windows
> Administrative domain ilttoyotalift.local, has determined that it is
> authorized to start. It is servicing clients now.
>
>
> However, DHCP does not service any clients.  Here is the background as to
> how this environment was configured...
>
> It was a Windows server 2003 SBS server running everything - DHCP, DNS, AD,
> DC, GC, all 5 FSMO, Exchange, etc.  We hit the 50-user limit and have
> multiple sites, so I decided to buy what we should have bought before my time
> here - Standard Server, etc...
>
> I installed a new Standard Server into AD, added as DC, GC, DNS, DHCP, added
> Exchange 2003 Standard.  I seized all 5 FSMO roles, then demoted the original
> SBS Server, removed DNS, DHCP.  It still runs Exchange, but there are no
> active users on it and our firewall is forwarding SMTP to the new server just
> fine.
>
> It still appears as if somewhere in AD, it has records of the original SBS
> server being registered as a DNS server.  The only live DNS server is the new
> server and it has itself listed as its DNS server in its IP settings.
>
> Also, something else weird about this server is that when I look at the IP
> settings in the network connection, I set the static IPs, but when I save
> them it always shows that it will use DHCP, but even after I reboot the
> server it does keep its static settings.  I have also tried to reset the
> static settings a few times and rebooted, but it always shows it will use
> DHCP, but keeps the static settings from an ipconfig.
>
> Any ideas from anyone?  It has been a while since I have gotten this far
> into networking, as I used to be a MCSE+I, MCDBA and all that good stuff
> until I moved into finance.
>
> FYI - I also ran through Microsoft's ntdsutil steps to make sure that the
> demotion of the SBS server was graceful, and I have checked the record for
> the new server using ADSI Edit under Configuration, Services, Net Services -
> it shows up fine.  And, yes, I have authorized, unauthorized, restarted and
> removed/reinstalled the DHCP service on this machine as well, but the actions
> are still the same.
>
> It feels to me that it is trying to authorize itself with the old server,
> but can't see it and won't work.  However, before I made any changes to the
> old SBS server, I had installed DHCP on the new server and it acted the same
> way as well, so maybe I'm crazy.
>
> Thanks,
> Dan Hegler
Author
29 Nov 2007 6:15 PM
Dylan
There may be a conflict between the old and new server in your AD.  Check
this link for more info.

http://support.microsoft.com/kb/938456/en-us

Show quote
"DHegler" wrote:

> I am having issues on getting DHCP to work on the new server I just installed
> on our network.  I get:
>
> Event ID 1046:
> The DHCP/BINL service on the local machine, belonging to the Windows
> Administrative domain ilttoyotalift.local, has determined that it is not
> authorized to start.  It has stopped servicing clients.  The following are
> some possible reasons for this:
>     This machine is part of a directory service enterprise and is  not
> authorized in the same domain.  (See help on the DHCP Service  Management
> Tool for additional information).
>
>     This machine cannot reach its directory service enterprise and  it has
> encountered another DHCP service on the network belonging to  a directory
> service enterprise on which the local machine is not authorized.
>
>     Some unexpected network error occurred.
>
> Then I get:
>
> Event ID 1044:
> The DHCP/BINL service on the local machine, belonging to the Windows
> Administrative domain ilttoyotalift.local, has determined that it is
> authorized to start. It is servicing clients now.
>
>
> However, DHCP does not service any clients.  Here is the background as to
> how this environment was configured...
>
> It was a Windows server 2003 SBS server running everything - DHCP, DNS, AD,
> DC, GC, all 5 FSMO, Exchange, etc.  We hit the 50-user limit and have
> multiple sites, so I decided to buy what we should have bought before my time
> here - Standard Server, etc...
>
> I installed a new Standard Server into AD, added as DC, GC, DNS, DHCP, added
> Exchange 2003 Standard.  I seized all 5 FSMO roles, then demoted the original
> SBS Server, removed DNS, DHCP.  It still runs Exchange, but there are no
> active users on it and our firewall is forwarding SMTP to the new server just
> fine.
>
> It still appears as if somewhere in AD, it has records of the original SBS
> server being registered as a DNS server.  The only live DNS server is the new
> server and it has itself listed as its DNS server in its IP settings.
>
> Also, something else weird about this server is that when I look at the IP
> settings in the network connection, I set the static IPs, but when I save
> them it always shows that it will use DHCP, but even after I reboot the
> server it does keep its static settings.  I have also tried to reset the
> static settings a few times and rebooted, but it always shows it will use
> DHCP, but keeps the static settings from an ipconfig.
>
> Any ideas from anyone?  It has been a while since I have gotten this far
> into networking, as I used to be a MCSE+I, MCDBA and all that good stuff
> until I moved into finance.
>
> FYI - I also ran through Microsoft's ntdsutil steps to make sure that the
> demotion of the SBS server was graceful, and I have checked the record for
> the new server using ADSI Edit under Configuration, Services, Net Services -
> it shows up fine.  And, yes, I have authorized, unauthorized, restarted and
> removed/reinstalled the DHCP service on this machine as well, but the actions
> are still the same.
>
> It feels to me that it is trying to authorize itself with the old server,
> but can't see it and won't work.  However, before I made any changes to the
> old SBS server, I had installed DHCP on the new server and it acted the same
> way as well, so maybe I'm crazy.
>
> Thanks,
> Dan Hegler
Author
29 Nov 2007 7:44 PM
DHegler
Sorry, already found and tried it...

I am ont eh phone with a MS tech rep and trying to uninstall Symantec
Endpoint Protection and reboot right now. 

Show quote
"DHegler" wrote:

> I am having issues on getting DHCP to work on the new server I just installed
> on our network.  I get:
>
> Event ID 1046:
> The DHCP/BINL service on the local machine, belonging to the Windows
> Administrative domain ilttoyotalift.local, has determined that it is not
> authorized to start.  It has stopped servicing clients.  The following are
> some possible reasons for this:
>     This machine is part of a directory service enterprise and is  not
> authorized in the same domain.  (See help on the DHCP Service  Management
> Tool for additional information).
>
>     This machine cannot reach its directory service enterprise and  it has
> encountered another DHCP service on the network belonging to  a directory
> service enterprise on which the local machine is not authorized.
>
>     Some unexpected network error occurred.
>
> Then I get:
>
> Event ID 1044:
> The DHCP/BINL service on the local machine, belonging to the Windows
> Administrative domain ilttoyotalift.local, has determined that it is
> authorized to start. It is servicing clients now.
>
>
> However, DHCP does not service any clients.  Here is the background as to
> how this environment was configured...
>
> It was a Windows server 2003 SBS server running everything - DHCP, DNS, AD,
> DC, GC, all 5 FSMO, Exchange, etc.  We hit the 50-user limit and have
> multiple sites, so I decided to buy what we should have bought before my time
> here - Standard Server, etc...
>
> I installed a new Standard Server into AD, added as DC, GC, DNS, DHCP, added
> Exchange 2003 Standard.  I seized all 5 FSMO roles, then demoted the original
> SBS Server, removed DNS, DHCP.  It still runs Exchange, but there are no
> active users on it and our firewall is forwarding SMTP to the new server just
> fine.
>
> It still appears as if somewhere in AD, it has records of the original SBS
> server being registered as a DNS server.  The only live DNS server is the new
> server and it has itself listed as its DNS server in its IP settings.
>
> Also, something else weird about this server is that when I look at the IP
> settings in the network connection, I set the static IPs, but when I save
> them it always shows that it will use DHCP, but even after I reboot the
> server it does keep its static settings.  I have also tried to reset the
> static settings a few times and rebooted, but it always shows it will use
> DHCP, but keeps the static settings from an ipconfig.
>
> Any ideas from anyone?  It has been a while since I have gotten this far
> into networking, as I used to be a MCSE+I, MCDBA and all that good stuff
> until I moved into finance.
>
> FYI - I also ran through Microsoft's ntdsutil steps to make sure that the
> demotion of the SBS server was graceful, and I have checked the record for
> the new server using ADSI Edit under Configuration, Services, Net Services -
> it shows up fine.  And, yes, I have authorized, unauthorized, restarted and
> removed/reinstalled the DHCP service on this machine as well, but the actions
> are still the same.
>
> It feels to me that it is trying to authorize itself with the old server,
> but can't see it and won't work.  However, before I made any changes to the
> old SBS server, I had installed DHCP on the new server and it acted the same
> way as well, so maybe I'm crazy.
>
> Thanks,
> Dan Hegler
Author
29 Nov 2007 8:55 PM
DHegler
It was Symantec Endpoint Protection.  I removed it and everything worked
fine.  Odd thing is, even when I disabled the "NEtwork Threat" portion, it
would still block DHCP traffic on the server.  Symantec never used to install
firewall-type services on their corporate edition protection before v11 - I
should have looked.
Author
29 Nov 2007 9:25 PM
Leythos
In article <E5D8D376-259D-4319-A0E3-44B4D234A***@microsoft.com>,
DHeg***@discussions.microsoft.com says...
> It was Symantec Endpoint Protection.  I removed it and everything worked
> fine.  Odd thing is, even when I disabled the "NEtwork Threat" portion, it
> would still block DHCP traffic on the server.  Symantec never used to install
> firewall-type services on their corporate edition protection before v11 - I
> should have looked.

I have been unable to get SEPP to work with anything on any of our test
or the customers that are willing to beta. I have one workstation left
running it and with all features installed it still causes problems.

Most of my Toshiba laptops wireless won't work with it installed at all.

SEPP is bad voodoo.

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
  drug dealer an "unlicensed pharmacist"
spam999free@rrohio.com (remove 999 for proper email address)

AddThis Social Bookmark Button