Re: Broken Domain
anonymous_at_discussions.microsoft.com
Date: 07/14/04
- Next message: anonymous_at_discussions.microsoft.com: "Re: Broken Domain"
- Previous message: Matt: "Re: Updates done without SUS Server"
- In reply to: Herb Martin: "Re: Broken Domain"
- Next in thread: Herb Martin: "Re: Broken Domain"
- Reply: Herb Martin: "Re: Broken Domain"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 14 Jul 2004 10:35:15 -0700
Thanks,
Backups did not help us. We actually built a new server
with the same domain name and copied the sysvol onto the
existing DC.
DNS was is bad shape too, but I thought we had fixed most
of the problems. I'll try your suggestion for setting DNS
to just the one DNS server I know is AD Integrated. I'll
give the DC a kick this weekend and see if it will allow
me to add a second DC.
Thanks again.
>-----Original Message-----
>"Rob Milman" <rmilman@graycon.com> wrote in message
>news:2c47a01c46924$aa0c52d0$a401280a@phx.gbl...
>> We had a rogue administrator, who is no longer employed
>> with us, do something really stupid. He deleted the
Sysvol
>> folders on all of our DC's. It tooks us a while, but we
>> were able to restore most functionality to our domain.
>> However, some things are still broken.
>
>I suppose backp tapes are out of the question?
>
>> We are unable to
>> add additional domain controllers or setup trusts
between
>> a new domain.
>
>That should NOT (though it might) be related to the
SysVol;
>usually that problem is due to DNS being wrong.
>
>DNS
> 1) Dynamic for the zone supporting AD
> 2) All internal DNS client NIC\IP properties must
specify SOLELY
> that internal, dynamic DNS server (set.)
> 3) DCs and even DNS servers are DNS clients too --
see #2
>
>Restart NetLogon on any DC if you change any of the above
that
>affects a DC.
>
>> Is there any troubleshooting or other
>> suggestions that can be made for us to fix this busted
>> domain? Or should we admit defeat and just rebuild from
>> scratch?
>
>If the DNS fixes the "add a DC" problem you might as well
>try that -- perhaps the "basic" Sysvol will load on a new
DC,
>but I suspect that gets copied from the other DCs as well.
>
>--
>Herb Martin
>
>
>"Rob Milman" <rmilman@graycon.com> wrote in message
>news:2c47a01c46924$aa0c52d0$a401280a@phx.gbl...
>> We had a rogue administrator, who is no longer employed
>> with us, do something really stupid. He deleted the
Sysvol
>> folders on all of our DC's. It tooks us a while, but we
>> were able to restore most functionality to our domain.
>> However, some things are still broken. We are unable to
>> add additional domain controllers or setup trusts
between
>> a new domain. Is there any troubleshooting or other
>> suggestions that can be made for us to fix this busted
>> domain? Or should we admit defeat and just rebuild from
>> scratch?
>>
>> Thanks in advance for your help.
>>
>> Rob Milman
>
>
>.
>
- Next message: anonymous_at_discussions.microsoft.com: "Re: Broken Domain"
- Previous message: Matt: "Re: Updates done without SUS Server"
- In reply to: Herb Martin: "Re: Broken Domain"
- Next in thread: Herb Martin: "Re: Broken Domain"
- Reply: Herb Martin: "Re: Broken Domain"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
