Hi all,

I am receiving a 0X80040e37 error when I fire up AD. I
have just reinstalled AD and DNS after desinstalling DNS.
Is it a reinstall issue/deinstall issue. I have seen this
problem before, but don't remember the fix. I am on
Server 2000.

Thanks

Re: Can't connect AD to DNS server on the same server by Susan

Susan
Wed Jul 09 14:35:31 CDT 2003

Is this SBS 2k or Win2k? As normally in SBS2k that AD/DNS is done for
you and there is no need to mess with this.

Jim wrote:

> Hi all,
>
> I am receiving a 0X80040e37 error when I fire up AD. I
> have just reinstalled AD and DNS after desinstalling DNS.
> Is it a reinstall issue/deinstall issue. I have seen this
> problem before, but don't remember the fix. I am on
> Server 2000.
>
> Thanks


Re: Can't connect AD to DNS server on the same server by Mark

Mark
Wed Jul 09 18:16:43 CDT 2003

You reinstalled AD?!?! So you ran dcpromo? Or you just uninstalled DNS?
It must have been in REAL bad shape b/c to REALLY mess up DNS you have to
bypass the wizards.

--
Sincerely,
Mark Mancini, CCA, CCNA, Master CIW&CI, CNE 4&5, MCSE+I 4&2000
www.MCSE2000.com
www.AppLauncher.com



"Jim" <jcadams10@msn.com> wrote in message
news:9ccb01c3464f$771484e0$a401280a@phx.gbl...
> Hi all,
>
> I am receiving a 0X80040e37 error when I fire up AD. I
> have just reinstalled AD and DNS after desinstalling DNS.
> Is it a reinstall issue/deinstall issue. I have seen this
> problem before, but don't remember the fix. I am on
> Server 2000.
>
> Thanks



Re: Can't connect AD to DNS server on the same server by Jim

Jim
Thu Jul 10 09:36:57 CDT 2003

Mark,

1. Yes, it was in bad shape. I was called in after the
fact to help someone who is just learning about AD and DNS.
With that said, I don't know how he originally set it up.

2. I did remove AD by running dcpromo. Since AD can't
run without DNS, I went to the run command and ran
dcpromo. It said it removed DNS successfully, which
would mean AD was removed. I rebooted and I reinstalled
AD following the wizards, it said I needed to install DNS
(we all know DNS is needed for AD). So, I did that,
following the wizards. Rebooted the PC. Set up a
forwarding zone. Then, I went to AD and recieved the
0X80040e37. When I went to the Site Manager, same error.

3. Now, with that all said, I can still log into the
domain on a PC and create a PC account on the domain. It
is almost as if the local AD on the server can't attach.

Any help to resolve is appreciated.
>-----Original Message-----
>You reinstalled AD?!?! So you ran dcpromo? Or you just
uninstalled DNS?
>It must have been in REAL bad shape b/c to REALLY mess up
DNS you have to
>bypass the wizards.
>
>--
>Sincerely,
>Mark Mancini, CCA, CCNA, Master CIW&CI, CNE 4&5, MCSE+I
4&2000
>www.MCSE2000.com
>www.AppLauncher.com
>
>
>
>"Jim" <jcadams10@msn.com> wrote in message
>news:9ccb01c3464f$771484e0$a401280a@phx.gbl...
>> Hi all,
>>
>> I am receiving a 0X80040e37 error when I fire up AD. I
>> have just reinstalled AD and DNS after desinstalling
DNS.
>> Is it a reinstall issue/deinstall issue. I have seen
this
>> problem before, but don't remember the fix. I am on
>> Server 2000.
>>
>> Thanks
>
>
>.
>

Re: Can't connect AD to DNS server on the same server by rayfong

rayfong
Thu Jul 10 17:34:05 CDT 2003

Ok, let's try these:
1. Go to DNS, hightlight your server, right click and Delete.
2. Go to Services, stop the DNS, stop the Netlogon.
3. Delete netlogon.dbn, and netlogon.dns from system32\config folder. <Make
a backup of the files first>
4. Start the DNS, and Netlogon.
5. Back to DNS, right click DNs, and Connect to Computer, then select This
Computer.
6. If you are not getting error here, then go ahead to recreate the Forward
Lookup Zone, and Reverse Lookup Zone.

Ray Fong
Microsoft SBS Product Support

This posting is provided "AS IS" with no warranties, and confers no rights.

-