Networking Forums

Networking Forums > Computer Networking > Windows Networking > assistanc with setting up 2nd domain controller on windows 2003 network

Reply
Thread Tools Display Modes

assistanc with setting up 2nd domain controller on windows 2003 network

 
 
Eddie Walker
Guest
Posts: n/a

 
      08-23-2007, 05:51 PM
I want to create some redundancy in my network.
I would like to have a 2nd server configured as a 2nd domain controller.
When I tried to do this before, i got asked stuff about DNS, I thought last
time it automaticall configured itself to be a 2nd domain controller et.

anyway can someone give me some pointers on what to do

is it possible to have this 2nd DC also serve up DHCP in the even the other
DC is down and vice versa? Also would ike it to act as a 2nd DNS server
(which is set to forward to the external isp's dns servers)

i know id have to put a copy of gobal catalog on it if i want it to be able
to handle logins, but i want full replication between the two servers so if
one is down the other can serve the logins etc.

thanks,

ed

 
Reply With Quote
 
 
 
 
Mathieu CHATEAU
Guest
Posts: n/a

 
      08-23-2007, 06:01 PM
Hello,

To make this server dc:
install the DNS Server component
run dcpromo
Add your AD integrated zone

For the DHCP:
install DHCP
Split your scope in two (50%-50%, or 80% - 20%).
If your workstations move only a few, you may just put a longer dhcp lease
so you would still be ok without dhcp server for one or two days

Global catalog is used with multiple domain/ forest or exchange.



--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"Eddie Walker" <(E-Mail Removed)> wrote in message
news:F90B726D-0A31-4AF0-AA16-(E-Mail Removed)...
>I want to create some redundancy in my network.
> I would like to have a 2nd server configured as a 2nd domain controller.
> When I tried to do this before, i got asked stuff about DNS, I thought
> last
> time it automaticall configured itself to be a 2nd domain controller et.
>
> anyway can someone give me some pointers on what to do
>
> is it possible to have this 2nd DC also serve up DHCP in the even the
> other
> DC is down and vice versa? Also would ike it to act as a 2nd DNS server
> (which is set to forward to the external isp's dns servers)
>
> i know id have to put a copy of gobal catalog on it if i want it to be
> able
> to handle logins, but i want full replication between the two servers so
> if
> one is down the other can serve the logins etc.
>
> thanks,
>
> ed
>


 
Reply With Quote
 
Eddie Walker
Guest
Posts: n/a

 
      08-27-2007, 03:13 AM
here is the error in event log from server at issue;
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 8/25/2007
Time: 3:41:46 PM
User: N/A
Computer: BEREAN04
Description:
The File Replication Service is having trouble enabling replication from
BEREAN03 to BEREAN04 for c:\windows\sysvol\domain using the DNS name
berean03.bereanwpb.org. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name berean03.bereanwpb.org from
this computer.
[2] FRS is not running on berean03.bereanwpb.org.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.


also at the existing DC here is the error:

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 8/23/2007
Time: 7:57:48 PM
User: N/A
Computer: BEREAN03
Description:
The File Replication Service has detected that the replica set "DOMAIN
SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to
read from the NTFS USN journal is not found. This can occur because of one
of the following reasons.

[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can
truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long
time.
[5] File Replication Service could not keep up with the rate of Disk IO
activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1
will cause the following recovery steps to be taken to automatically recover
from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be
deleted from the replica set. If you do not want to wait 5 minutes, then run
"net stop ntfrs" followed by "net start ntfrs" to restart the File
Replication Service.
[2] At the poll following the deletion this computer will be re-added to
the replica set. The re-addition will trigger a full tree sync for the
replica set.

WARNING: During the recovery process data in the replica tree may be
unavailable. You should reset the registry parameter described above to 0 to
prevent automatic recovery from making the data unexpectedly unavailable if
this error condition occurs again.

To change this registry parameter, run regedit.

Click on Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameter s"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.

If the value name is not present you may add it with the New->DWORD Value
function under the Edit Menu item. Type the value name exactly as shown
above.

For more information, see Help and Support Center at
http://go.microsoft.co
"Mathieu CHATEAU" <(E-Mail Removed)> wrote in message
news:%23kaVf%(E-Mail Removed)...
> Hello,
>
> To make this server dc:
> install the DNS Server component
> run dcpromo
> Add your AD integrated zone
>
> For the DHCP:
> install DHCP
> Split your scope in two (50%-50%, or 80% - 20%).
> If your workstations move only a few, you may just put a longer dhcp lease
> so you would still be ok without dhcp server for one or two days
>
> Global catalog is used with multiple domain/ forest or exchange.
>
>
>
> --
> Cordialement,
> Mathieu CHATEAU
> http://lordoftheping.blogspot.com
>
>
> "Eddie Walker" <(E-Mail Removed)> wrote in message
> news:F90B726D-0A31-4AF0-AA16-(E-Mail Removed)...
>>I want to create some redundancy in my network.
>> I would like to have a 2nd server configured as a 2nd domain controller.
>> When I tried to do this before, i got asked stuff about DNS, I thought
>> last
>> time it automaticall configured itself to be a 2nd domain controller et.
>>
>> anyway can someone give me some pointers on what to do
>>
>> is it possible to have this 2nd DC also serve up DHCP in the even the
>> other
>> DC is down and vice versa? Also would ike it to act as a 2nd DNS server
>> (which is set to forward to the external isp's dns servers)
>>
>> i know id have to put a copy of gobal catalog on it if i want it to be
>> able
>> to handle logins, but i want full replication between the two servers so
>> if
>> one is down the other can serve the logins etc.
>>
>> thanks,
>>
>> ed
>>

>


 
Reply With Quote
 
Meinolf Weber (Myweb)
Guest
Posts: n/a

 
      08-27-2007, 09:42 AM
Hello Eddie,

Please post an ipconfig /all from both dc's.

Best regards

Meinolf Weber (Myweb)
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> here is the error in event log from server at issue;
> Event Type: Warning
> Event Source: NtFrs
> Event Category: None
> Event ID: 13508
> Date: 8/25/2007
> Time: 3:41:46 PM
> User: N/A
> Computer: BEREAN04
> Description:
> The File Replication Service is having trouble enabling replication
> from
> BEREAN03 to BEREAN04 for c:\windows\sysvol\domain using the DNS name
> berean03.bereanwpb.org. FRS will keep retrying.
> Following are some of the reasons you would see this warning.
> [1] FRS can not correctly resolve the DNS name berean03.bereanwpb.org
> from
> this computer.
> [2] FRS is not running on berean03.bereanwpb.org.
> [3] The topology information in the Active Directory for this replica
> has
> not yet replicated to all the Domain Controllers.
> also at the existing DC here is the error:
>
> Event Type: Error
> Event Source: NtFrs
> Event Category: None
> Event ID: 13568
> Date: 8/23/2007
> Time: 7:57:48 PM
> User: N/A
> Computer: BEREAN03
> Description:
> The File Replication Service has detected that the replica set "DOMAIN
> SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
> Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
> Replica root path is : "c:\windows\sysvol\domain"
> Replica root volume is : "\\.\C:"
> A Replica set hits JRNL_WRAP_ERROR when the record that it is trying
> to
> read from the NTFS USN journal is not found. This can occur because
> of one
> of the following reasons.
>
> [1] Volume "\\.\C:" has been formatted.
> [2] The NTFS USN journal on volume "\\.\C:" has been deleted.
> [3] The NTFS USN journal on volume "\\.\C:" has been truncated.
> Chkdsk can
> truncate the journal if it finds corrupt entries at the end of the
> journal.
> [4] File Replication Service was not running on this computer for a
> long
> time.
> [5] File Replication Service could not keep up with the rate of Disk
> IO
> activity on "\\.\C:".
> Setting the "Enable Journal Wrap Automatic Restore" registry
> parameter to 1
> will cause the following recovery steps to be taken to automatically
> recover
> from this error state.
> [1] At the first poll, which will occur in 5 minutes, this computer
> will be
> deleted from the replica set. If you do not want to wait 5 minutes,
> then run
> "net stop ntfrs" followed by "net start ntfrs" to restart the File
> Replication Service.
> [2] At the poll following the deletion this computer will be re-added
> to
> the replica set. The re-addition will trigger a full tree sync for the
> replica set.
>
> WARNING: During the recovery process data in the replica tree may be
> unavailable. You should reset the registry parameter described above
> to 0 to prevent automatic recovery from making the data unexpectedly
> unavailable if this error condition occurs again.
>
> To change this registry parameter, run regedit.
>
> Click on Start, Run and type regedit.
>
> Expand HKEY_LOCAL_MACHINE.
> Click down the key path:
> "System\CurrentControlSet\Services\NtFrs\Parameter s"
> Double click on the value name
> "Enable Journal Wrap Automatic Restore"
> and update the value.
> If the value name is not present you may add it with the New->DWORD
> Value function under the Edit Menu item. Type the value name exactly
> as shown above.
>
> For more information, see Help and Support Center at
> http://go.microsoft.co
> "Mathieu CHATEAU" <(E-Mail Removed)> wrote in message
> news:%23kaVf%(E-Mail Removed)...
>> Hello,
>>
>> To make this server dc:
>> install the DNS Server component
>> run dcpromo
>> Add your AD integrated zone
>> For the DHCP:
>> install DHCP
>> Split your scope in two (50%-50%, or 80% - 20%).
>> If your workstations move only a few, you may just put a longer dhcp
>> lease
>> so you would still be ok without dhcp server for one or two days
>> Global catalog is used with multiple domain/ forest or exchange.
>>
>> --
>> Cordialement,
>> Mathieu CHATEAU
>> http://lordoftheping.blogspot.com
>> "Eddie Walker" <(E-Mail Removed)> wrote in message
>> news:F90B726D-0A31-4AF0-AA16-(E-Mail Removed)...
>>
>>> I want to create some redundancy in my network.
>>> I would like to have a 2nd server configured as a 2nd domain
>>> controller.
>>> When I tried to do this before, i got asked stuff about DNS, I
>>> thought
>>> last
>>> time it automaticall configured itself to be a 2nd domain controller
>>> et.
>>> anyway can someone give me some pointers on what to do
>>>
>>> is it possible to have this 2nd DC also serve up DHCP in the even
>>> the
>>> other
>>> DC is down and vice versa? Also would ike it to act as a 2nd DNS
>>> server
>>> (which is set to forward to the external isp's dns servers)
>>> i know id have to put a copy of gobal catalog on it if i want it to
>>> be
>>> able
>>> to handle logins, but i want full replication between the two
>>> servers so
>>> if
>>> one is down the other can serve the logins etc.
>>> thanks,
>>>
>>> ed
>>>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Windows 2003 domain controller with IBM Domino Thomas Moeller Nexoe Windows Networking 4 02-12-2010 10:21 AM
Can't Ping Windows 2003 Domain Controller stefano.debellis@gmail.com Windows Networking 0 05-12-2006 05:25 PM
Can't Ping Windows 2003 Domain Controller stefano.debellis@gmail.com Windows Networking 0 05-12-2006 05:12 PM
Windows 2003 Server as Domain Controller Esther Vasa Windows Networking 0 06-11-2004 09:24 PM
Windows 2003 Clustering Domain Controller =?Utf-8?B?RG92IEdvbGRtYW4=?= Windows Networking 1 01-07-2004 09:10 PM



1 2 3 4 5 6 7 8 9 10 11