How to Troubleshoot Missing SYSVOL and NETLOGON Shares

Wednesday, February 11, 2009

How to Troubleshoot Missing SYSVOL and NETLOGON Shares
Missing SYSVOL and NETLOGON shares typically occur on replica domain controllers in an existing domain, but may also occur on the first domain controller in a new domain. You following these steps with the replica domain controllers, but you can also use them with the first domain controller in the domain by ignoring the replication-specific steps.
NTDS Connection objects exist in the DS of each replication partner.NTDS Connections are one way connections. These connections are used by the Directory service to replicate the Active Directory and the File Replication Service (FRS) to replicate the file system portion of system policy in the SYSVOL folder. The Knowledge Consistency Checker (KCC) is responsible for building NTDS connection objects to form a well-connected topology between domain controllers in the domain and forest. If you do not have automatic connections, an administrator may also create manual connection objects. Use the "Sites and Services" (Dssite.msc) snap-in to examine the connection objects that exist between the problem computer and existing domain controllers. For replication to occur between computer \\M1 and \\M2, \\M1 must have an inbound connection object from \\M2, and \\M2 must have an inbound connection object from \\M1. Use the Connect to Domain Controller command in Dssites.msc to view and compare each domain controller's perspective of the intra-domain connection objects. If no connection objects exist for the new replica member, use the Check Replication Topology command in Dssites.msc to force KCC to build the automatic connection objects. After you do so, press F5 to refresh the view. If KCC cannot build automatic connections, administrators must build manual connection objects for domain controllers with no inbound or outbound connections to or from other domain controllers in the domain. KCC may successfully build the automatic connection objects if you build a single working manual connection object. Delete duplicate manual or automatic connections from the same domain controller in the domain to avoid a replication-blocking configuration.For additional information about this issue, click the article number below to view the article in the Microsoft Knowledge Base:
251250 NTFRS Event ID 13557 Is Recorded When Duplicate NTDS Connection Objects Exist
Active Directory replication occurs between the new and existing domain controllers in the domain.Use Repadmin.exe to confirm that Active Directory replication occurs between the source and destination domain controllers in the same domain in the scheduled replication interval. Default replication intervals are 5 minutes between domain controllers in the same site, and one time every 3 hours between domain controllers in different sites with a minimum of 15 minutes.
REPADMIN /SHOWREPS %UPSTREAMCOMPUTER% REPADMIN /SHOWREPS %DOWNSTREAMCOMPUTER%
FRS replication is dependent on the Active Directory to replicate the configuration information between domain controllers in the domain. If you think that replication is the problem, examine replication events in Event Viewer. Do so after you set the "replication events" entry in the following registry key to 5 on potential source computers (\\M1) and the destination computer (\\M2):
HKEY_LOCAL_MACHINE\System\CCS\Services\NTDS\Diagnostics\
After you set this entry, force replication from \\M1 to \\M2 and \\M2 to \\M1 by using the replicate now command in Dssites.msc or its equivalent command in REPLMON.
The server that is used to source the Active Directory and SYSVOL folder should have created NETLOGON and SYSVOL shares itself.After the Dcpromo.exe program has restarted the computer, FRS first tries to source the SYSVOL share from the computer that is identified in the following "Replica Set Parent" registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTFRS\Parameters\SysVol\ DomainName
NOTE: This key is temporary and is deleted after SYSVOL is sourced or the information under SYSVOL has been successfully replicated.The 2195 release of Ntfrs.exe prevents replication from this initial source server. This delays SYSVOL replication until FRS can try replication from an inbound replication partner in the domain over an automatic or manual NTDS connection object. All potential source domain controllers in the domain typically have already shared the NETLOGON and SYSVOL shares and applied default domain and domain controllers policy.SYSVOL folder structure:
domain
DO_NOT_REMOVE_NtFrs_PreInstall_Directory
Policies
{GUID}
Adm
MACHINE
USER
{GUID}
Adm
MACHINE
USER
{etc.,}
scripts
staging
staging areas
MyDomainName.com
scripts
sysvol(sysvol share)
MyDomainName.com
DO_NOT_REMOVE_NtFrs_PreInstall_Directory
Policies
{GUID}
Adm
MACHINE
USER
{GUID}
Adm
MACHINE
USER
{etc.,}
scripts(NETLOGON share)
For additional information about the problem of sourcing from the initial replica, click the article number below to view the article in the Microsoft Knowledge Base:
250545 SYSVOL Directory Is Slow to Synchronize, Delays Creation of SYSVOL Share and Domain Controller Registration
The "Enterprise Domain Controllers" group must be granted the "access this computer from network" right in the default domain controllers policy on the domain controllers organizational unit.Replication of the Active Directory during the use of the Dcpromo.exe program uses the credentials that are provided in the Active Directory Installation Wizard. Upon restart, replication occurs in the context of the domain controller's computer account. All source domain controllers in the domain must successfully replicate and apply the policy that gives the "Enterprise Domain Controllers" group the "Access this computer from network right. For quick verification, look for event 1704s in the Application log of potential source domain controllers. For detailed verification, run a security configuration analysis against the Basicdc.inf template and examine the log output. Note that this requires defining environment variables for SYSVOL, DSLOG and DSIT. For additional information about how to do this, click the article number below to view the article in the Microsoft Knowledge Base:
250454 Error Returned Importing Security Template
In Windows Server 2003, the Basicdc.inf template no longer exists. To reapply the default settings or to compare current settings with the default settings, use the "Setup security.inf" template.
Each domain controller must be able to resolve (ping) the fully qualified computer names of computers that are participating in the replica set. For SYSVOL, this means pinging the fully qualified computer name of all domain controllers in the domain. Confirm that the address that is returned by the ping command matches the IP address that is returned by IPCONFIG at the console of each replica set partner.
The FRS service must have created an NTFRS jet database.Run the DIR \\computername\Admin$\NTFRS\Jet command against each domain controller in the domain to confirm the existence of the Ntfrs.jdb file. The date and size of the jet database may be incorrect while the NTFRS service is running. This behavior is by design.
Each domain controller must be a member of the SYSVOL replica set.Run the NTFRSUTL DS [computername] command on all replica set members. Confirm that all domain controllers in the domain show up under the "SET: DOMAIN SYSTEMVOLUME (SYSVOL SHARE)" portion of the NTFRSUTL output. The SYSVOL Replica set and its members can also be displayed under cn="domain system volume",cn=file replication service,cn=system,dc=FQDN in the User and Computers (Dsa.msc) snap-in when "Advanced Features" is turned on under the View menu.
Each domain controller must be a subscriber of the replica set.Run the NTFRSUTL DS [computername] command on all replica set members. Subscriber objects appear in cn=domain system volume (SYSVOL share),cn=NTFRS Subscriptions,CN=DCNAME,OU=Domain Controllers,DC=FQDN. This requires that the machine object exists and has replicated in. NTFRSUTL generates the following message when the subscriber object is missing:
SUBSCRIPTION: NTFRS SUBSCRIPTIONS DN : cn=ntfrs subscriptions,cn=W2KPDC,ou=domain controllers,dc=d... Guid :5c44b60b-8f01-48c6-8604c630a695dcddWorking : f:\winnt\ntfrsActual Working: f:\winnt\ntfrsWIN2K-PDC IS NOT A MEMBER OF A REPLICA SET!
The Replication Schedule must be turned on.
The logical drive that is hosting the SYSVOL share and staging folder has plenty of available disk space on upstream and downstream partners. For example, 50 percent of the content that you are trying to replicate and three times the largest file size that is being replicated.
Check the destination folder and the staging folder (displayed in "NTFRSUTL DS") of the new replica to see if files are replicating. Files in the staging folder must be in the process of being moved to the final location. That the number of files in the staging or destination folder is constantly changing is a good sign as either files are being replicated in, or transitioned to the destination folder.
READ MORE - How to Troubleshoot Missing SYSVOL and NETLOGON Shares

How to Troubleshoot Missing SYSVOL and NETLOGON Shares

How to Troubleshoot Missing SYSVOL and NETLOGON Shares
Missing SYSVOL and NETLOGON shares typically occur on replica domain controllers in an existing domain, but may also occur on the first domain controller in a new domain. You following these steps with the replica domain controllers, but you can also use them with the first domain controller in the domain by ignoring the replication-specific steps.
NTDS Connection objects exist in the DS of each replication partner.NTDS Connections are one way connections. These connections are used by the Directory service to replicate the Active Directory and the File Replication Service (FRS) to replicate the file system portion of system policy in the SYSVOL folder. The Knowledge Consistency Checker (KCC) is responsible for building NTDS connection objects to form a well-connected topology between domain controllers in the domain and forest. If you do not have automatic connections, an administrator may also create manual connection objects. Use the "Sites and Services" (Dssite.msc) snap-in to examine the connection objects that exist between the problem computer and existing domain controllers. For replication to occur between computer \\M1 and \\M2, \\M1 must have an inbound connection object from \\M2, and \\M2 must have an inbound connection object from \\M1. Use the Connect to Domain Controller command in Dssites.msc to view and compare each domain controller's perspective of the intra-domain connection objects. If no connection objects exist for the new replica member, use the Check Replication Topology command in Dssites.msc to force KCC to build the automatic connection objects. After you do so, press F5 to refresh the view. If KCC cannot build automatic connections, administrators must build manual connection objects for domain controllers with no inbound or outbound connections to or from other domain controllers in the domain. KCC may successfully build the automatic connection objects if you build a single working manual connection object. Delete duplicate manual or automatic connections from the same domain controller in the domain to avoid a replication-blocking configuration.For additional information about this issue, click the article number below to view the article in the Microsoft Knowledge Base:
251250 NTFRS Event ID 13557 Is Recorded When Duplicate NTDS Connection Objects Exist
Active Directory replication occurs between the new and existing domain controllers in the domain.Use Repadmin.exe to confirm that Active Directory replication occurs between the source and destination domain controllers in the same domain in the scheduled replication interval. Default replication intervals are 5 minutes between domain controllers in the same site, and one time every 3 hours between domain controllers in different sites with a minimum of 15 minutes.
REPADMIN /SHOWREPS %UPSTREAMCOMPUTER% REPADMIN /SHOWREPS %DOWNSTREAMCOMPUTER%
FRS replication is dependent on the Active Directory to replicate the configuration information between domain controllers in the domain. If you think that replication is the problem, examine replication events in Event Viewer. Do so after you set the "replication events" entry in the following registry key to 5 on potential source computers (\\M1) and the destination computer (\\M2):
HKEY_LOCAL_MACHINE\System\CCS\Services\NTDS\Diagnostics\
After you set this entry, force replication from \\M1 to \\M2 and \\M2 to \\M1 by using the replicate now command in Dssites.msc or its equivalent command in REPLMON.
The server that is used to source the Active Directory and SYSVOL folder should have created NETLOGON and SYSVOL shares itself.After the Dcpromo.exe program has restarted the computer, FRS first tries to source the SYSVOL share from the computer that is identified in the following "Replica Set Parent" registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTFRS\Parameters\SysVol\ DomainName
NOTE: This key is temporary and is deleted after SYSVOL is sourced or the information under SYSVOL has been successfully replicated.The 2195 release of Ntfrs.exe prevents replication from this initial source server. This delays SYSVOL replication until FRS can try replication from an inbound replication partner in the domain over an automatic or manual NTDS connection object. All potential source domain controllers in the domain typically have already shared the NETLOGON and SYSVOL shares and applied default domain and domain controllers policy.SYSVOL folder structure:
domain
DO_NOT_REMOVE_NtFrs_PreInstall_Directory
Policies
{GUID}
Adm
MACHINE
USER
{GUID}
Adm
MACHINE
USER
{etc.,}
scripts
staging
staging areas
MyDomainName.com
scripts
sysvol(sysvol share)
MyDomainName.com
DO_NOT_REMOVE_NtFrs_PreInstall_Directory
Policies
{GUID}
Adm
MACHINE
USER
{GUID}
Adm
MACHINE
USER
{etc.,}
scripts(NETLOGON share)
For additional information about the problem of sourcing from the initial replica, click the article number below to view the article in the Microsoft Knowledge Base:
250545 SYSVOL Directory Is Slow to Synchronize, Delays Creation of SYSVOL Share and Domain Controller Registration
The "Enterprise Domain Controllers" group must be granted the "access this computer from network" right in the default domain controllers policy on the domain controllers organizational unit.Replication of the Active Directory during the use of the Dcpromo.exe program uses the credentials that are provided in the Active Directory Installation Wizard. Upon restart, replication occurs in the context of the domain controller's computer account. All source domain controllers in the domain must successfully replicate and apply the policy that gives the "Enterprise Domain Controllers" group the "Access this computer from network right. For quick verification, look for event 1704s in the Application log of potential source domain controllers. For detailed verification, run a security configuration analysis against the Basicdc.inf template and examine the log output. Note that this requires defining environment variables for SYSVOL, DSLOG and DSIT. For additional information about how to do this, click the article number below to view the article in the Microsoft Knowledge Base:
250454 Error Returned Importing Security Template
In Windows Server 2003, the Basicdc.inf template no longer exists. To reapply the default settings or to compare current settings with the default settings, use the "Setup security.inf" template.
Each domain controller must be able to resolve (ping) the fully qualified computer names of computers that are participating in the replica set. For SYSVOL, this means pinging the fully qualified computer name of all domain controllers in the domain. Confirm that the address that is returned by the ping command matches the IP address that is returned by IPCONFIG at the console of each replica set partner.
The FRS service must have created an NTFRS jet database.Run the DIR \\computername\Admin$\NTFRS\Jet command against each domain controller in the domain to confirm the existence of the Ntfrs.jdb file. The date and size of the jet database may be incorrect while the NTFRS service is running. This behavior is by design.
Each domain controller must be a member of the SYSVOL replica set.Run the NTFRSUTL DS [computername] command on all replica set members. Confirm that all domain controllers in the domain show up under the "SET: DOMAIN SYSTEMVOLUME (SYSVOL SHARE)" portion of the NTFRSUTL output. The SYSVOL Replica set and its members can also be displayed under cn="domain system volume",cn=file replication service,cn=system,dc=FQDN in the User and Computers (Dsa.msc) snap-in when "Advanced Features" is turned on under the View menu.
Each domain controller must be a subscriber of the replica set.Run the NTFRSUTL DS [computername] command on all replica set members. Subscriber objects appear in cn=domain system volume (SYSVOL share),cn=NTFRS Subscriptions,CN=DCNAME,OU=Domain Controllers,DC=FQDN. This requires that the machine object exists and has replicated in. NTFRSUTL generates the following message when the subscriber object is missing:
SUBSCRIPTION: NTFRS SUBSCRIPTIONS DN : cn=ntfrs subscriptions,cn=W2KPDC,ou=domain controllers,dc=d... Guid :5c44b60b-8f01-48c6-8604c630a695dcddWorking : f:\winnt\ntfrsActual Working: f:\winnt\ntfrsWIN2K-PDC IS NOT A MEMBER OF A REPLICA SET!
The Replication Schedule must be turned on.
The logical drive that is hosting the SYSVOL share and staging folder has plenty of available disk space on upstream and downstream partners. For example, 50 percent of the content that you are trying to replicate and three times the largest file size that is being replicated.
Check the destination folder and the staging folder (displayed in "NTFRSUTL DS") of the new replica to see if files are replicating. Files in the staging folder must be in the process of being moved to the final location. That the number of files in the staging or destination folder is constantly changing is a good sign as either files are being replicated in, or transitioned to the destination folder.
READ MORE - How to Troubleshoot Missing SYSVOL and NETLOGON Shares

How to Troubleshoot Missing SYSVOL and NETLOGON Shares

How to Troubleshoot Missing SYSVOL and NETLOGON Shares
Missing SYSVOL and NETLOGON shares typically occur on replica domain controllers in an existing domain, but may also occur on the first domain controller in a new domain. You following these steps with the replica domain controllers, but you can also use them with the first domain controller in the domain by ignoring the replication-specific steps.
NTDS Connection objects exist in the DS of each replication partner.NTDS Connections are one way connections. These connections are used by the Directory service to replicate the Active Directory and the File Replication Service (FRS) to replicate the file system portion of system policy in the SYSVOL folder. The Knowledge Consistency Checker (KCC) is responsible for building NTDS connection objects to form a well-connected topology between domain controllers in the domain and forest. If you do not have automatic connections, an administrator may also create manual connection objects. Use the "Sites and Services" (Dssite.msc) snap-in to examine the connection objects that exist between the problem computer and existing domain controllers. For replication to occur between computer \\M1 and \\M2, \\M1 must have an inbound connection object from \\M2, and \\M2 must have an inbound connection object from \\M1. Use the Connect to Domain Controller command in Dssites.msc to view and compare each domain controller's perspective of the intra-domain connection objects. If no connection objects exist for the new replica member, use the Check Replication Topology command in Dssites.msc to force KCC to build the automatic connection objects. After you do so, press F5 to refresh the view. If KCC cannot build automatic connections, administrators must build manual connection objects for domain controllers with no inbound or outbound connections to or from other domain controllers in the domain. KCC may successfully build the automatic connection objects if you build a single working manual connection object. Delete duplicate manual or automatic connections from the same domain controller in the domain to avoid a replication-blocking configuration.For additional information about this issue, click the article number below to view the article in the Microsoft Knowledge Base:
251250 NTFRS Event ID 13557 Is Recorded When Duplicate NTDS Connection Objects Exist
Active Directory replication occurs between the new and existing domain controllers in the domain.Use Repadmin.exe to confirm that Active Directory replication occurs between the source and destination domain controllers in the same domain in the scheduled replication interval. Default replication intervals are 5 minutes between domain controllers in the same site, and one time every 3 hours between domain controllers in different sites with a minimum of 15 minutes.
REPADMIN /SHOWREPS %UPSTREAMCOMPUTER% REPADMIN /SHOWREPS %DOWNSTREAMCOMPUTER%
FRS replication is dependent on the Active Directory to replicate the configuration information between domain controllers in the domain. If you think that replication is the problem, examine replication events in Event Viewer. Do so after you set the "replication events" entry in the following registry key to 5 on potential source computers (\\M1) and the destination computer (\\M2):
HKEY_LOCAL_MACHINE\System\CCS\Services\NTDS\Diagnostics\
After you set this entry, force replication from \\M1 to \\M2 and \\M2 to \\M1 by using the replicate now command in Dssites.msc or its equivalent command in REPLMON.
The server that is used to source the Active Directory and SYSVOL folder should have created NETLOGON and SYSVOL shares itself.After the Dcpromo.exe program has restarted the computer, FRS first tries to source the SYSVOL share from the computer that is identified in the following "Replica Set Parent" registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTFRS\Parameters\SysVol\ DomainName
NOTE: This key is temporary and is deleted after SYSVOL is sourced or the information under SYSVOL has been successfully replicated.The 2195 release of Ntfrs.exe prevents replication from this initial source server. This delays SYSVOL replication until FRS can try replication from an inbound replication partner in the domain over an automatic or manual NTDS connection object. All potential source domain controllers in the domain typically have already shared the NETLOGON and SYSVOL shares and applied default domain and domain controllers policy.SYSVOL folder structure:
domain
DO_NOT_REMOVE_NtFrs_PreInstall_Directory
Policies
{GUID}
Adm
MACHINE
USER
{GUID}
Adm
MACHINE
USER
{etc.,}
scripts
staging
staging areas
MyDomainName.com
scripts
sysvol(sysvol share)
MyDomainName.com
DO_NOT_REMOVE_NtFrs_PreInstall_Directory
Policies
{GUID}
Adm
MACHINE
USER
{GUID}
Adm
MACHINE
USER
{etc.,}
scripts(NETLOGON share)
For additional information about the problem of sourcing from the initial replica, click the article number below to view the article in the Microsoft Knowledge Base:
250545 SYSVOL Directory Is Slow to Synchronize, Delays Creation of SYSVOL Share and Domain Controller Registration
The "Enterprise Domain Controllers" group must be granted the "access this computer from network" right in the default domain controllers policy on the domain controllers organizational unit.Replication of the Active Directory during the use of the Dcpromo.exe program uses the credentials that are provided in the Active Directory Installation Wizard. Upon restart, replication occurs in the context of the domain controller's computer account. All source domain controllers in the domain must successfully replicate and apply the policy that gives the "Enterprise Domain Controllers" group the "Access this computer from network right. For quick verification, look for event 1704s in the Application log of potential source domain controllers. For detailed verification, run a security configuration analysis against the Basicdc.inf template and examine the log output. Note that this requires defining environment variables for SYSVOL, DSLOG and DSIT. For additional information about how to do this, click the article number below to view the article in the Microsoft Knowledge Base:
250454 Error Returned Importing Security Template
In Windows Server 2003, the Basicdc.inf template no longer exists. To reapply the default settings or to compare current settings with the default settings, use the "Setup security.inf" template.
Each domain controller must be able to resolve (ping) the fully qualified computer names of computers that are participating in the replica set. For SYSVOL, this means pinging the fully qualified computer name of all domain controllers in the domain. Confirm that the address that is returned by the ping command matches the IP address that is returned by IPCONFIG at the console of each replica set partner.
The FRS service must have created an NTFRS jet database.Run the DIR \\computername\Admin$\NTFRS\Jet command against each domain controller in the domain to confirm the existence of the Ntfrs.jdb file. The date and size of the jet database may be incorrect while the NTFRS service is running. This behavior is by design.
Each domain controller must be a member of the SYSVOL replica set.Run the NTFRSUTL DS [computername] command on all replica set members. Confirm that all domain controllers in the domain show up under the "SET: DOMAIN SYSTEMVOLUME (SYSVOL SHARE)" portion of the NTFRSUTL output. The SYSVOL Replica set and its members can also be displayed under cn="domain system volume",cn=file replication service,cn=system,dc=FQDN in the User and Computers (Dsa.msc) snap-in when "Advanced Features" is turned on under the View menu.
Each domain controller must be a subscriber of the replica set.Run the NTFRSUTL DS [computername] command on all replica set members. Subscriber objects appear in cn=domain system volume (SYSVOL share),cn=NTFRS Subscriptions,CN=DCNAME,OU=Domain Controllers,DC=FQDN. This requires that the machine object exists and has replicated in. NTFRSUTL generates the following message when the subscriber object is missing:
SUBSCRIPTION: NTFRS SUBSCRIPTIONS DN : cn=ntfrs subscriptions,cn=W2KPDC,ou=domain controllers,dc=d... Guid :5c44b60b-8f01-48c6-8604c630a695dcddWorking : f:\winnt\ntfrsActual Working: f:\winnt\ntfrsWIN2K-PDC IS NOT A MEMBER OF A REPLICA SET!
The Replication Schedule must be turned on.
The logical drive that is hosting the SYSVOL share and staging folder has plenty of available disk space on upstream and downstream partners. For example, 50 percent of the content that you are trying to replicate and three times the largest file size that is being replicated.
Check the destination folder and the staging folder (displayed in "NTFRSUTL DS") of the new replica to see if files are replicating. Files in the staging folder must be in the process of being moved to the final location. That the number of files in the staging or destination folder is constantly changing is a good sign as either files are being replicated in, or transitioned to the destination folder.
READ MORE - How to Troubleshoot Missing SYSVOL and NETLOGON Shares

How to Troubleshoot Missing SYSVOL and NETLOGON Shares

How to Troubleshoot Missing SYSVOL and NETLOGON Shares
Missing SYSVOL and NETLOGON shares typically occur on replica domain controllers in an existing domain, but may also occur on the first domain controller in a new domain. You following these steps with the replica domain controllers, but you can also use them with the first domain controller in the domain by ignoring the replication-specific steps.
NTDS Connection objects exist in the DS of each replication partner.NTDS Connections are one way connections. These connections are used by the Directory service to replicate the Active Directory and the File Replication Service (FRS) to replicate the file system portion of system policy in the SYSVOL folder. The Knowledge Consistency Checker (KCC) is responsible for building NTDS connection objects to form a well-connected topology between domain controllers in the domain and forest. If you do not have automatic connections, an administrator may also create manual connection objects. Use the "Sites and Services" (Dssite.msc) snap-in to examine the connection objects that exist between the problem computer and existing domain controllers. For replication to occur between computer \\M1 and \\M2, \\M1 must have an inbound connection object from \\M2, and \\M2 must have an inbound connection object from \\M1. Use the Connect to Domain Controller command in Dssites.msc to view and compare each domain controller's perspective of the intra-domain connection objects. If no connection objects exist for the new replica member, use the Check Replication Topology command in Dssites.msc to force KCC to build the automatic connection objects. After you do so, press F5 to refresh the view. If KCC cannot build automatic connections, administrators must build manual connection objects for domain controllers with no inbound or outbound connections to or from other domain controllers in the domain. KCC may successfully build the automatic connection objects if you build a single working manual connection object. Delete duplicate manual or automatic connections from the same domain controller in the domain to avoid a replication-blocking configuration.For additional information about this issue, click the article number below to view the article in the Microsoft Knowledge Base:
251250 NTFRS Event ID 13557 Is Recorded When Duplicate NTDS Connection Objects Exist
Active Directory replication occurs between the new and existing domain controllers in the domain.Use Repadmin.exe to confirm that Active Directory replication occurs between the source and destination domain controllers in the same domain in the scheduled replication interval. Default replication intervals are 5 minutes between domain controllers in the same site, and one time every 3 hours between domain controllers in different sites with a minimum of 15 minutes.
REPADMIN /SHOWREPS %UPSTREAMCOMPUTER% REPADMIN /SHOWREPS %DOWNSTREAMCOMPUTER%
FRS replication is dependent on the Active Directory to replicate the configuration information between domain controllers in the domain. If you think that replication is the problem, examine replication events in Event Viewer. Do so after you set the "replication events" entry in the following registry key to 5 on potential source computers (\\M1) and the destination computer (\\M2):
HKEY_LOCAL_MACHINE\System\CCS\Services\NTDS\Diagnostics\
After you set this entry, force replication from \\M1 to \\M2 and \\M2 to \\M1 by using the replicate now command in Dssites.msc or its equivalent command in REPLMON.
The server that is used to source the Active Directory and SYSVOL folder should have created NETLOGON and SYSVOL shares itself.After the Dcpromo.exe program has restarted the computer, FRS first tries to source the SYSVOL share from the computer that is identified in the following "Replica Set Parent" registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTFRS\Parameters\SysVol\ DomainName
NOTE: This key is temporary and is deleted after SYSVOL is sourced or the information under SYSVOL has been successfully replicated.The 2195 release of Ntfrs.exe prevents replication from this initial source server. This delays SYSVOL replication until FRS can try replication from an inbound replication partner in the domain over an automatic or manual NTDS connection object. All potential source domain controllers in the domain typically have already shared the NETLOGON and SYSVOL shares and applied default domain and domain controllers policy.SYSVOL folder structure:
domain
DO_NOT_REMOVE_NtFrs_PreInstall_Directory
Policies
{GUID}
Adm
MACHINE
USER
{GUID}
Adm
MACHINE
USER
{etc.,}
scripts
staging
staging areas
MyDomainName.com
scripts
sysvol(sysvol share)
MyDomainName.com
DO_NOT_REMOVE_NtFrs_PreInstall_Directory
Policies
{GUID}
Adm
MACHINE
USER
{GUID}
Adm
MACHINE
USER
{etc.,}
scripts(NETLOGON share)
For additional information about the problem of sourcing from the initial replica, click the article number below to view the article in the Microsoft Knowledge Base:
250545 SYSVOL Directory Is Slow to Synchronize, Delays Creation of SYSVOL Share and Domain Controller Registration
The "Enterprise Domain Controllers" group must be granted the "access this computer from network" right in the default domain controllers policy on the domain controllers organizational unit.Replication of the Active Directory during the use of the Dcpromo.exe program uses the credentials that are provided in the Active Directory Installation Wizard. Upon restart, replication occurs in the context of the domain controller's computer account. All source domain controllers in the domain must successfully replicate and apply the policy that gives the "Enterprise Domain Controllers" group the "Access this computer from network right. For quick verification, look for event 1704s in the Application log of potential source domain controllers. For detailed verification, run a security configuration analysis against the Basicdc.inf template and examine the log output. Note that this requires defining environment variables for SYSVOL, DSLOG and DSIT. For additional information about how to do this, click the article number below to view the article in the Microsoft Knowledge Base:
250454 Error Returned Importing Security Template
In Windows Server 2003, the Basicdc.inf template no longer exists. To reapply the default settings or to compare current settings with the default settings, use the "Setup security.inf" template.
Each domain controller must be able to resolve (ping) the fully qualified computer names of computers that are participating in the replica set. For SYSVOL, this means pinging the fully qualified computer name of all domain controllers in the domain. Confirm that the address that is returned by the ping command matches the IP address that is returned by IPCONFIG at the console of each replica set partner.
The FRS service must have created an NTFRS jet database.Run the DIR \\computername\Admin$\NTFRS\Jet command against each domain controller in the domain to confirm the existence of the Ntfrs.jdb file. The date and size of the jet database may be incorrect while the NTFRS service is running. This behavior is by design.
Each domain controller must be a member of the SYSVOL replica set.Run the NTFRSUTL DS [computername] command on all replica set members. Confirm that all domain controllers in the domain show up under the "SET: DOMAIN SYSTEMVOLUME (SYSVOL SHARE)" portion of the NTFRSUTL output. The SYSVOL Replica set and its members can also be displayed under cn="domain system volume",cn=file replication service,cn=system,dc=FQDN in the User and Computers (Dsa.msc) snap-in when "Advanced Features" is turned on under the View menu.
Each domain controller must be a subscriber of the replica set.Run the NTFRSUTL DS [computername] command on all replica set members. Subscriber objects appear in cn=domain system volume (SYSVOL share),cn=NTFRS Subscriptions,CN=DCNAME,OU=Domain Controllers,DC=FQDN. This requires that the machine object exists and has replicated in. NTFRSUTL generates the following message when the subscriber object is missing:
SUBSCRIPTION: NTFRS SUBSCRIPTIONS DN : cn=ntfrs subscriptions,cn=W2KPDC,ou=domain controllers,dc=d... Guid :5c44b60b-8f01-48c6-8604c630a695dcddWorking : f:\winnt\ntfrsActual Working: f:\winnt\ntfrsWIN2K-PDC IS NOT A MEMBER OF A REPLICA SET!
The Replication Schedule must be turned on.
The logical drive that is hosting the SYSVOL share and staging folder has plenty of available disk space on upstream and downstream partners. For example, 50 percent of the content that you are trying to replicate and three times the largest file size that is being replicated.
Check the destination folder and the staging folder (displayed in "NTFRSUTL DS") of the new replica to see if files are replicating. Files in the staging folder must be in the process of being moved to the final location. That the number of files in the staging or destination folder is constantly changing is a good sign as either files are being replicated in, or transitioned to the destination folder.
READ MORE - How to Troubleshoot Missing SYSVOL and NETLOGON Shares

How to Troubleshoot Missing SYSVOL and NETLOGON Shares

How to Troubleshoot Missing SYSVOL and NETLOGON Shares
Missing SYSVOL and NETLOGON shares typically occur on replica domain controllers in an existing domain, but may also occur on the first domain controller in a new domain. You following these steps with the replica domain controllers, but you can also use them with the first domain controller in the domain by ignoring the replication-specific steps.
NTDS Connection objects exist in the DS of each replication partner.NTDS Connections are one way connections. These connections are used by the Directory service to replicate the Active Directory and the File Replication Service (FRS) to replicate the file system portion of system policy in the SYSVOL folder. The Knowledge Consistency Checker (KCC) is responsible for building NTDS connection objects to form a well-connected topology between domain controllers in the domain and forest. If you do not have automatic connections, an administrator may also create manual connection objects. Use the "Sites and Services" (Dssite.msc) snap-in to examine the connection objects that exist between the problem computer and existing domain controllers. For replication to occur between computer \\M1 and \\M2, \\M1 must have an inbound connection object from \\M2, and \\M2 must have an inbound connection object from \\M1. Use the Connect to Domain Controller command in Dssites.msc to view and compare each domain controller's perspective of the intra-domain connection objects. If no connection objects exist for the new replica member, use the Check Replication Topology command in Dssites.msc to force KCC to build the automatic connection objects. After you do so, press F5 to refresh the view. If KCC cannot build automatic connections, administrators must build manual connection objects for domain controllers with no inbound or outbound connections to or from other domain controllers in the domain. KCC may successfully build the automatic connection objects if you build a single working manual connection object. Delete duplicate manual or automatic connections from the same domain controller in the domain to avoid a replication-blocking configuration.For additional information about this issue, click the article number below to view the article in the Microsoft Knowledge Base:
251250 NTFRS Event ID 13557 Is Recorded When Duplicate NTDS Connection Objects Exist
Active Directory replication occurs between the new and existing domain controllers in the domain.Use Repadmin.exe to confirm that Active Directory replication occurs between the source and destination domain controllers in the same domain in the scheduled replication interval. Default replication intervals are 5 minutes between domain controllers in the same site, and one time every 3 hours between domain controllers in different sites with a minimum of 15 minutes.
REPADMIN /SHOWREPS %UPSTREAMCOMPUTER% REPADMIN /SHOWREPS %DOWNSTREAMCOMPUTER%
FRS replication is dependent on the Active Directory to replicate the configuration information between domain controllers in the domain. If you think that replication is the problem, examine replication events in Event Viewer. Do so after you set the "replication events" entry in the following registry key to 5 on potential source computers (\\M1) and the destination computer (\\M2):
HKEY_LOCAL_MACHINE\System\CCS\Services\NTDS\Diagnostics\
After you set this entry, force replication from \\M1 to \\M2 and \\M2 to \\M1 by using the replicate now command in Dssites.msc or its equivalent command in REPLMON.
The server that is used to source the Active Directory and SYSVOL folder should have created NETLOGON and SYSVOL shares itself.After the Dcpromo.exe program has restarted the computer, FRS first tries to source the SYSVOL share from the computer that is identified in the following "Replica Set Parent" registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTFRS\Parameters\SysVol\ DomainName
NOTE: This key is temporary and is deleted after SYSVOL is sourced or the information under SYSVOL has been successfully replicated.The 2195 release of Ntfrs.exe prevents replication from this initial source server. This delays SYSVOL replication until FRS can try replication from an inbound replication partner in the domain over an automatic or manual NTDS connection object. All potential source domain controllers in the domain typically have already shared the NETLOGON and SYSVOL shares and applied default domain and domain controllers policy.SYSVOL folder structure:
domain
DO_NOT_REMOVE_NtFrs_PreInstall_Directory
Policies
{GUID}
Adm
MACHINE
USER
{GUID}
Adm
MACHINE
USER
{etc.,}
scripts
staging
staging areas
MyDomainName.com
scripts
sysvol(sysvol share)
MyDomainName.com
DO_NOT_REMOVE_NtFrs_PreInstall_Directory
Policies
{GUID}
Adm
MACHINE
USER
{GUID}
Adm
MACHINE
USER
{etc.,}
scripts(NETLOGON share)
For additional information about the problem of sourcing from the initial replica, click the article number below to view the article in the Microsoft Knowledge Base:
250545 SYSVOL Directory Is Slow to Synchronize, Delays Creation of SYSVOL Share and Domain Controller Registration
The "Enterprise Domain Controllers" group must be granted the "access this computer from network" right in the default domain controllers policy on the domain controllers organizational unit.Replication of the Active Directory during the use of the Dcpromo.exe program uses the credentials that are provided in the Active Directory Installation Wizard. Upon restart, replication occurs in the context of the domain controller's computer account. All source domain controllers in the domain must successfully replicate and apply the policy that gives the "Enterprise Domain Controllers" group the "Access this computer from network right. For quick verification, look for event 1704s in the Application log of potential source domain controllers. For detailed verification, run a security configuration analysis against the Basicdc.inf template and examine the log output. Note that this requires defining environment variables for SYSVOL, DSLOG and DSIT. For additional information about how to do this, click the article number below to view the article in the Microsoft Knowledge Base:
250454 Error Returned Importing Security Template
In Windows Server 2003, the Basicdc.inf template no longer exists. To reapply the default settings or to compare current settings with the default settings, use the "Setup security.inf" template.
Each domain controller must be able to resolve (ping) the fully qualified computer names of computers that are participating in the replica set. For SYSVOL, this means pinging the fully qualified computer name of all domain controllers in the domain. Confirm that the address that is returned by the ping command matches the IP address that is returned by IPCONFIG at the console of each replica set partner.
The FRS service must have created an NTFRS jet database.Run the DIR \\computername\Admin$\NTFRS\Jet command against each domain controller in the domain to confirm the existence of the Ntfrs.jdb file. The date and size of the jet database may be incorrect while the NTFRS service is running. This behavior is by design.
Each domain controller must be a member of the SYSVOL replica set.Run the NTFRSUTL DS [computername] command on all replica set members. Confirm that all domain controllers in the domain show up under the "SET: DOMAIN SYSTEMVOLUME (SYSVOL SHARE)" portion of the NTFRSUTL output. The SYSVOL Replica set and its members can also be displayed under cn="domain system volume",cn=file replication service,cn=system,dc=FQDN in the User and Computers (Dsa.msc) snap-in when "Advanced Features" is turned on under the View menu.
Each domain controller must be a subscriber of the replica set.Run the NTFRSUTL DS [computername] command on all replica set members. Subscriber objects appear in cn=domain system volume (SYSVOL share),cn=NTFRS Subscriptions,CN=DCNAME,OU=Domain Controllers,DC=FQDN. This requires that the machine object exists and has replicated in. NTFRSUTL generates the following message when the subscriber object is missing:
SUBSCRIPTION: NTFRS SUBSCRIPTIONS DN : cn=ntfrs subscriptions,cn=W2KPDC,ou=domain controllers,dc=d... Guid :5c44b60b-8f01-48c6-8604c630a695dcddWorking : f:\winnt\ntfrsActual Working: f:\winnt\ntfrsWIN2K-PDC IS NOT A MEMBER OF A REPLICA SET!
The Replication Schedule must be turned on.
The logical drive that is hosting the SYSVOL share and staging folder has plenty of available disk space on upstream and downstream partners. For example, 50 percent of the content that you are trying to replicate and three times the largest file size that is being replicated.
Check the destination folder and the staging folder (displayed in "NTFRSUTL DS") of the new replica to see if files are replicating. Files in the staging folder must be in the process of being moved to the final location. That the number of files in the staging or destination folder is constantly changing is a good sign as either files are being replicated in, or transitioned to the destination folder.
READ MORE - How to Troubleshoot Missing SYSVOL and NETLOGON Shares

Event ID – 1063 :

Event ID – 1063 :
Observation: We observed that the event id 1063 which state that there are no ip addresses available for lease in the scope.
Action to be taken: Provide new scope with more IP Address to avoid such events in future.
OR
Observation: The DHCP/BINL service on the local machine has determined that it is authorized to start. It is servicing clients now.
Also we have observed warning event that Scope, 192.168.254.0, is 83 percent full with only 11 IP addresses remaining. Kindly update the scope configuration.
OR
Action Needed: We are unable to troubleshoot the problem because of unavailability of Credentials. To solve this problem you need to delete Inactive ip addresses or create a new scope.
READ MORE - Event ID – 1063 :

Event ID – 1063 :

Event ID – 1063 :
Observation: We observed that the event id 1063 which state that there are no ip addresses available for lease in the scope.
Action to be taken: Provide new scope with more IP Address to avoid such events in future.
OR
Observation: The DHCP/BINL service on the local machine has determined that it is authorized to start. It is servicing clients now.
Also we have observed warning event that Scope, 192.168.254.0, is 83 percent full with only 11 IP addresses remaining. Kindly update the scope configuration.
OR
Action Needed: We are unable to troubleshoot the problem because of unavailability of Credentials. To solve this problem you need to delete Inactive ip addresses or create a new scope.
READ MORE - Event ID – 1063 :

Event ID – 1063 :

Event ID – 1063 :
Observation: We observed that the event id 1063 which state that there are no ip addresses available for lease in the scope.
Action to be taken: Provide new scope with more IP Address to avoid such events in future.
OR
Observation: The DHCP/BINL service on the local machine has determined that it is authorized to start. It is servicing clients now.
Also we have observed warning event that Scope, 192.168.254.0, is 83 percent full with only 11 IP addresses remaining. Kindly update the scope configuration.
OR
Action Needed: We are unable to troubleshoot the problem because of unavailability of Credentials. To solve this problem you need to delete Inactive ip addresses or create a new scope.
READ MORE - Event ID – 1063 :

Event ID – 1063 :

Event ID – 1063 :
Observation: We observed that the event id 1063 which state that there are no ip addresses available for lease in the scope.
Action to be taken: Provide new scope with more IP Address to avoid such events in future.
OR
Observation: The DHCP/BINL service on the local machine has determined that it is authorized to start. It is servicing clients now.
Also we have observed warning event that Scope, 192.168.254.0, is 83 percent full with only 11 IP addresses remaining. Kindly update the scope configuration.
OR
Action Needed: We are unable to troubleshoot the problem because of unavailability of Credentials. To solve this problem you need to delete Inactive ip addresses or create a new scope.
READ MORE - Event ID – 1063 :

Event ID – 1063 :

Event ID – 1063 :
Observation: We observed that the event id 1063 which state that there are no ip addresses available for lease in the scope.
Action to be taken: Provide new scope with more IP Address to avoid such events in future.
OR
Observation: The DHCP/BINL service on the local machine has determined that it is authorized to start. It is servicing clients now.
Also we have observed warning event that Scope, 192.168.254.0, is 83 percent full with only 11 IP addresses remaining. Kindly update the scope configuration.
OR
Action Needed: We are unable to troubleshoot the problem because of unavailability of Credentials. To solve this problem you need to delete Inactive ip addresses or create a new scope.
READ MORE - Event ID – 1063 :

Event ID – 1051 :

Event ID – 1051 :
Issue: The users will not be leased an IP Address if their lease has expired or they restart their computers.
Description: The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain.
Action Needed: Please verify if the client is authorizing another DHCP Server in the network or changing the IP address of the original DHCP server or if there are two DHCP servers in the network."
"Ref Link:
http://support.microsoft.com/kb/306925/en-us
READ MORE - Event ID – 1051 :

Event ID – 1051 :

Event ID – 1051 :
Issue: The users will not be leased an IP Address if their lease has expired or they restart their computers.
Description: The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain.
Action Needed: Please verify if the client is authorizing another DHCP Server in the network or changing the IP address of the original DHCP server or if there are two DHCP servers in the network."
"Ref Link:
http://support.microsoft.com/kb/306925/en-us
READ MORE - Event ID – 1051 :

Event ID – 1051 :

Event ID – 1051 :
Issue: The users will not be leased an IP Address if their lease has expired or they restart their computers.
Description: The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain.
Action Needed: Please verify if the client is authorizing another DHCP Server in the network or changing the IP address of the original DHCP server or if there are two DHCP servers in the network."
"Ref Link:
http://support.microsoft.com/kb/306925/en-us
READ MORE - Event ID – 1051 :

Event ID – 1051 :

Event ID – 1051 :
Issue: The users will not be leased an IP Address if their lease has expired or they restart their computers.
Description: The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain.
Action Needed: Please verify if the client is authorizing another DHCP Server in the network or changing the IP address of the original DHCP server or if there are two DHCP servers in the network."
"Ref Link:
http://support.microsoft.com/kb/306925/en-us
READ MORE - Event ID – 1051 :

Event ID – 1051 :

Event ID – 1051 :
Issue: The users will not be leased an IP Address if their lease has expired or they restart their computers.
Description: The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain.
Action Needed: Please verify if the client is authorizing another DHCP Server in the network or changing the IP address of the original DHCP server or if there are two DHCP servers in the network."
"Ref Link:
http://support.microsoft.com/kb/306925/en-us
READ MORE - Event ID – 1051 :

Event ID – 1041 : The DHCP service failed.

Event ID – 1041:
Description: The DHCP service failed.
Action required: To resolve this behavior, configure the bindings for the DHCP Server service:
1. Click Start, point to Programs, click Administrative Tools, and then click DHCP .
2. In the DHCP Console, right-click the server objects, and then click Properties.
3. Click the Advanced tab, and then click Bindings.
4. Under Connections and Server Bindings, enable the user interface that is to be used to service DHCP client requests.
5. Click OK, click OK, and then close the DHCP Console.
6. Click Start, point to Programs, click Administrative Tools, and then click Services.
7. Locate and restart the DHCP server service.
Action Needed: We have observed that DHCP service not installed on this server. Please approve us for install the same to ignore the issue.
Issue: We have received an alert which indicates that The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain: hr-innovations.com
We suspect that there is another DHCP server which is being authorized or the Ip address of the original DHCP server has changed or there are two DHCP server in the network
Action Needed: To resolve the issue please follow the below KB article or provide us credentials to check the issue.
http://support.microsoft.com/kb/306925/en-us
http://support.microsoft.com/kb/299363/en-us
READ MORE - Event ID – 1041 : The DHCP service failed.

Event ID – 1041 :

Event ID – 1041:
Description: The DHCP service failed.
Action required: To resolve this behavior, configure the bindings for the DHCP Server service:
1. Click Start, point to Programs, click Administrative Tools, and then click DHCP .
2. In the DHCP Console, right-click the server objects, and then click Properties.
3. Click the Advanced tab, and then click Bindings.
4. Under Connections and Server Bindings, enable the user interface that is to be used to service DHCP client requests.
5. Click OK, click OK, and then close the DHCP Console.
6. Click Start, point to Programs, click Administrative Tools, and then click Services.
7. Locate and restart the DHCP server service.
Action Needed: We have observed that DHCP service not installed on this server. Please approve us for install the same to ignore the issue.
Issue: We have received an alert which indicates that The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain: hr-innovations.com
We suspect that there is another DHCP server which is being authorized or the Ip address of the original DHCP server has changed or there are two DHCP server in the network
Action Needed: To resolve the issue please follow the below KB article or provide us credentials to check the issue.
http://support.microsoft.com/kb/306925/en-us
http://support.microsoft.com/kb/299363/en-us
READ MORE - Event ID – 1041 :

Event ID – 1041 :

Event ID – 1041:
Description: The DHCP service failed.
Action required: To resolve this behavior, configure the bindings for the DHCP Server service:
1. Click Start, point to Programs, click Administrative Tools, and then click DHCP .
2. In the DHCP Console, right-click the server objects, and then click Properties.
3. Click the Advanced tab, and then click Bindings.
4. Under Connections and Server Bindings, enable the user interface that is to be used to service DHCP client requests.
5. Click OK, click OK, and then close the DHCP Console.
6. Click Start, point to Programs, click Administrative Tools, and then click Services.
7. Locate and restart the DHCP server service.
Action Needed: We have observed that DHCP service not installed on this server. Please approve us for install the same to ignore the issue.
Issue: We have received an alert which indicates that The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain: hr-innovations.com
We suspect that there is another DHCP server which is being authorized or the Ip address of the original DHCP server has changed or there are two DHCP server in the network
Action Needed: To resolve the issue please follow the below KB article or provide us credentials to check the issue.
http://support.microsoft.com/kb/306925/en-us
http://support.microsoft.com/kb/299363/en-us
READ MORE - Event ID – 1041 :

Event ID – 1041 :

Event ID – 1041:
Description: The DHCP service failed.
Action required: To resolve this behavior, configure the bindings for the DHCP Server service:
1. Click Start, point to Programs, click Administrative Tools, and then click DHCP .
2. In the DHCP Console, right-click the server objects, and then click Properties.
3. Click the Advanced tab, and then click Bindings.
4. Under Connections and Server Bindings, enable the user interface that is to be used to service DHCP client requests.
5. Click OK, click OK, and then close the DHCP Console.
6. Click Start, point to Programs, click Administrative Tools, and then click Services.
7. Locate and restart the DHCP server service.
Action Needed: We have observed that DHCP service not installed on this server. Please approve us for install the same to ignore the issue.
Issue: We have received an alert which indicates that The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain: hr-innovations.com
We suspect that there is another DHCP server which is being authorized or the Ip address of the original DHCP server has changed or there are two DHCP server in the network
Action Needed: To resolve the issue please follow the below KB article or provide us credentials to check the issue.
http://support.microsoft.com/kb/306925/en-us
http://support.microsoft.com/kb/299363/en-us
READ MORE - Event ID – 1041 :

Event ID – 1041 :

Event ID – 1041:
Description: The DHCP service failed.
Action required: To resolve this behavior, configure the bindings for the DHCP Server service:
1. Click Start, point to Programs, click Administrative Tools, and then click DHCP .
2. In the DHCP Console, right-click the server objects, and then click Properties.
3. Click the Advanced tab, and then click Bindings.
4. Under Connections and Server Bindings, enable the user interface that is to be used to service DHCP client requests.
5. Click OK, click OK, and then close the DHCP Console.
6. Click Start, point to Programs, click Administrative Tools, and then click Services.
7. Locate and restart the DHCP server service.
Action Needed: We have observed that DHCP service not installed on this server. Please approve us for install the same to ignore the issue.
Issue: We have received an alert which indicates that The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain: hr-innovations.com
We suspect that there is another DHCP server which is being authorized or the Ip address of the original DHCP server has changed or there are two DHCP server in the network
Action Needed: To resolve the issue please follow the below KB article or provide us credentials to check the issue.
http://support.microsoft.com/kb/306925/en-us
http://support.microsoft.com/kb/299363/en-us
READ MORE - Event ID – 1041 :

Event id – 1046 :

Event id – 1046 :
The DHCP server could not be authorized because no domain controller was found.
1) Verify that the domain controller is running.
2) Check if any old Domain controller is brought on this has the same domain name.
3) One of the key things that need’s to be checked is whether DNS name resolution working properly. This can verified using Nslookup command line tool and type the name of the server or any of the DNS client’s names which should be resolved to corresponding name.
4) Check the DNS Zone records for duplicate name or IP address.
5) Verify that the DHCP server had authorized in AD.
READ MORE - Event id – 1046 :

Event id – 1046 :

Event id – 1046 :
The DHCP server could not be authorized because no domain controller was found.
1) Verify that the domain controller is running.
2) Check if any old Domain controller is brought on this has the same domain name.
3) One of the key things that need’s to be checked is whether DNS name resolution working properly. This can verified using Nslookup command line tool and type the name of the server or any of the DNS client’s names which should be resolved to corresponding name.
4) Check the DNS Zone records for duplicate name or IP address.
5) Verify that the DHCP server had authorized in AD.
READ MORE - Event id – 1046 :

Event id – 1046 :

Event id – 1046 :
The DHCP server could not be authorized because no domain controller was found.
1) Verify that the domain controller is running.
2) Check if any old Domain controller is brought on this has the same domain name.
3) One of the key things that need’s to be checked is whether DNS name resolution working properly. This can verified using Nslookup command line tool and type the name of the server or any of the DNS client’s names which should be resolved to corresponding name.
4) Check the DNS Zone records for duplicate name or IP address.
5) Verify that the DHCP server had authorized in AD.
READ MORE - Event id – 1046 :

Event id – 1046 :

Event id – 1046 :
The DHCP server could not be authorized because no domain controller was found.
1) Verify that the domain controller is running.
2) Check if any old Domain controller is brought on this has the same domain name.
3) One of the key things that need’s to be checked is whether DNS name resolution working properly. This can verified using Nslookup command line tool and type the name of the server or any of the DNS client’s names which should be resolved to corresponding name.
4) Check the DNS Zone records for duplicate name or IP address.
5) Verify that the DHCP server had authorized in AD.
READ MORE - Event id – 1046 :

Event id – 1046 :

Event id – 1046 :
The DHCP server could not be authorized because no domain controller was found.
1) Verify that the domain controller is running.
2) Check if any old Domain controller is brought on this has the same domain name.
3) One of the key things that need’s to be checked is whether DNS name resolution working properly. This can verified using Nslookup command line tool and type the name of the server or any of the DNS client’s names which should be resolved to corresponding name.
4) Check the DNS Zone records for duplicate name or IP address.
5) Verify that the DHCP server had authorized in AD.
READ MORE - Event id – 1046 :

Difference in Windows server2000 and 2003?

Difference in Windows server2000 and 2003?

1) When installing terminal services for win2000 u r
prompted to select application server functions or
administrative functions sets can be installed sequently on
one server but it performs only one function at one time.
But in 2003 still distinguishes between application and
administrative services but installation and management are
now consolidated.
2) In Win 2000 server we can apply 620 group policies
but in 2003 we can apply nearly 720 so Win2003 server is
more secure than win 2000 server.
3) In 2000 we cannot rename domain whereas in 2003 we
can rename Domain.
4) In 2000 it supports of 8 processors and 64 GB RAM
(In 2000 Advance Server) whereas in 2003 supports up to 64
processors and max of 512GB RAM.
5) 2000 Supports IIS 5.0 and 2003 Supports IIS6.0
6) 2000 doesn’t support Dot net whereas 2003 Supports
Microsoft .NET 2.0
7) 2000 has Server and Advance Server editions whereas
2003 has Standard, Enterprise, Datacenter and Web server
Editions.
8) 2000 doesn’t have any 64 bit server operating
system whereas 2003 has 64 bit server operating systems
(Windows Server 2003 X64 Std and Enterprise Edition)
9) 2000 has basic concept of DFS (Distributed File
systems) with defined roots whereas 2003 has Enhanced DFS
support with multiple roots.
10) In 2000 there is complexality in administering
Complex networks whereas 2003 is easy administration in all
& Complex networks.
11) In 2000 we can create 1 million users and in 2003
we can create 1 billion users.
12) In 2003 we have concept of Volume shadow copy
service which is used to create hard disk snap shot which
is used in Disaster recovery and 2000 doesn’t have this
service.
13) In 2000 we don’t have end user policy management,
whereas in 2003 we have a End user policy management which
is done in GPMC (Group policy management console).
14) In 2000 we have cross domain trust relation ship
and 2003 we have Cross forest trust relationship.
15) 2000 Supports 4-node clustering and 2003 supports 8-
node clustering.
16) 2003 has High HCL Support (Hardware Compatibility
List) issued by Microsoft.
17) Code name of 2000 is Win NT 5.0 and Code name of
2003 is Win NT 5.1
18) 2003 has service called ADFS (Active Directory
Federation Services) which is used to communicate between
branches with safe authentication.
19) In 2003 their is improved storage management using
service File Server Resource Manager (FSRM).
20) 2003 has service called Windows Share point
Services (It is an integrated portfolio of collaboration
and communication services designed to connect people,
information, processes, and systems both within and beyond
the organizational firewall).
21) 2003 has Improved Print management compared to 2000
server.
22) 2003 has telnet sessions available.
23) 2000 supports IPV4 whereas 2003 supports IPV4 and
IPV6.
And Active Directory Differences-- -2000AD:--
1. Only one million object can be created.
2. Universal group membership is not present.
3. Between parent and child, there is no built in trust .It
is called as non-transitive trust.
4. There is only three AD partition, Domain partition,
configuration partition, schema partition.
5. In Win 2000 server we can apply 620 group policies .
6. but 2k only Emergency Repair Disk(ERD) is there.
2003AD:-
1. 2 Million object can be created .
2. It is a new feature available in 2003.
3. Between parent and child, there is built in trust .It
is called as transitive trust.
4. Same partitions are there in 2003, but one additional
partition called Application directory partition is present.
5. but in 2003 we can apply nearly 720 so Win2003 server is
more secure than win 2000 server.
6. Automated System Recovery(ASR) is there
READ MORE - Difference in Windows server2000 and 2003?

Difference in Windows server2000 and 2003?

Difference in Windows server2000 and 2003?

1) When installing terminal services for win2000 u r
prompted to select application server functions or
administrative functions sets can be installed sequently on
one server but it performs only one function at one time.
But in 2003 still distinguishes between application and
administrative services but installation and management are
now consolidated.
2) In Win 2000 server we can apply 620 group policies
but in 2003 we can apply nearly 720 so Win2003 server is
more secure than win 2000 server.
3) In 2000 we cannot rename domain whereas in 2003 we
can rename Domain.
4) In 2000 it supports of 8 processors and 64 GB RAM
(In 2000 Advance Server) whereas in 2003 supports up to 64
processors and max of 512GB RAM.
5) 2000 Supports IIS 5.0 and 2003 Supports IIS6.0
6) 2000 doesn’t support Dot net whereas 2003 Supports
Microsoft .NET 2.0
7) 2000 has Server and Advance Server editions whereas
2003 has Standard, Enterprise, Datacenter and Web server
Editions.
8) 2000 doesn’t have any 64 bit server operating
system whereas 2003 has 64 bit server operating systems
(Windows Server 2003 X64 Std and Enterprise Edition)
9) 2000 has basic concept of DFS (Distributed File
systems) with defined roots whereas 2003 has Enhanced DFS
support with multiple roots.
10) In 2000 there is complexality in administering
Complex networks whereas 2003 is easy administration in all
& Complex networks.
11) In 2000 we can create 1 million users and in 2003
we can create 1 billion users.
12) In 2003 we have concept of Volume shadow copy
service which is used to create hard disk snap shot which
is used in Disaster recovery and 2000 doesn’t have this
service.
13) In 2000 we don’t have end user policy management,
whereas in 2003 we have a End user policy management which
is done in GPMC (Group policy management console).
14) In 2000 we have cross domain trust relation ship
and 2003 we have Cross forest trust relationship.
15) 2000 Supports 4-node clustering and 2003 supports 8-
node clustering.
16) 2003 has High HCL Support (Hardware Compatibility
List) issued by Microsoft.
17) Code name of 2000 is Win NT 5.0 and Code name of
2003 is Win NT 5.1
18) 2003 has service called ADFS (Active Directory
Federation Services) which is used to communicate between
branches with safe authentication.
19) In 2003 their is improved storage management using
service File Server Resource Manager (FSRM).
20) 2003 has service called Windows Share point
Services (It is an integrated portfolio of collaboration
and communication services designed to connect people,
information, processes, and systems both within and beyond
the organizational firewall).
21) 2003 has Improved Print management compared to 2000
server.
22) 2003 has telnet sessions available.
23) 2000 supports IPV4 whereas 2003 supports IPV4 and
IPV6.
And Active Directory Differences-- -2000AD:--
1. Only one million object can be created.
2. Universal group membership is not present.
3. Between parent and child, there is no built in trust .It
is called as non-transitive trust.
4. There is only three AD partition, Domain partition,
configuration partition, schema partition.
5. In Win 2000 server we can apply 620 group policies .
6. but 2k only Emergency Repair Disk(ERD) is there.
2003AD:-
1. 2 Million object can be created .
2. It is a new feature available in 2003.
3. Between parent and child, there is built in trust .It
is called as transitive trust.
4. Same partitions are there in 2003, but one additional
partition called Application directory partition is present.
5. but in 2003 we can apply nearly 720 so Win2003 server is
more secure than win 2000 server.
6. Automated System Recovery(ASR) is there
READ MORE - Difference in Windows server2000 and 2003?

Difference in Windows server2000 and 2003?

Difference in Windows server2000 and 2003?

1) When installing terminal services for win2000 u r
prompted to select application server functions or
administrative functions sets can be installed sequently on
one server but it performs only one function at one time.
But in 2003 still distinguishes between application and
administrative services but installation and management are
now consolidated.
2) In Win 2000 server we can apply 620 group policies
but in 2003 we can apply nearly 720 so Win2003 server is
more secure than win 2000 server.
3) In 2000 we cannot rename domain whereas in 2003 we
can rename Domain.
4) In 2000 it supports of 8 processors and 64 GB RAM
(In 2000 Advance Server) whereas in 2003 supports up to 64
processors and max of 512GB RAM.
5) 2000 Supports IIS 5.0 and 2003 Supports IIS6.0
6) 2000 doesn’t support Dot net whereas 2003 Supports
Microsoft .NET 2.0
7) 2000 has Server and Advance Server editions whereas
2003 has Standard, Enterprise, Datacenter and Web server
Editions.
8) 2000 doesn’t have any 64 bit server operating
system whereas 2003 has 64 bit server operating systems
(Windows Server 2003 X64 Std and Enterprise Edition)
9) 2000 has basic concept of DFS (Distributed File
systems) with defined roots whereas 2003 has Enhanced DFS
support with multiple roots.
10) In 2000 there is complexality in administering
Complex networks whereas 2003 is easy administration in all
& Complex networks.
11) In 2000 we can create 1 million users and in 2003
we can create 1 billion users.
12) In 2003 we have concept of Volume shadow copy
service which is used to create hard disk snap shot which
is used in Disaster recovery and 2000 doesn’t have this
service.
13) In 2000 we don’t have end user policy management,
whereas in 2003 we have a End user policy management which
is done in GPMC (Group policy management console).
14) In 2000 we have cross domain trust relation ship
and 2003 we have Cross forest trust relationship.
15) 2000 Supports 4-node clustering and 2003 supports 8-
node clustering.
16) 2003 has High HCL Support (Hardware Compatibility
List) issued by Microsoft.
17) Code name of 2000 is Win NT 5.0 and Code name of
2003 is Win NT 5.1
18) 2003 has service called ADFS (Active Directory
Federation Services) which is used to communicate between
branches with safe authentication.
19) In 2003 their is improved storage management using
service File Server Resource Manager (FSRM).
20) 2003 has service called Windows Share point
Services (It is an integrated portfolio of collaboration
and communication services designed to connect people,
information, processes, and systems both within and beyond
the organizational firewall).
21) 2003 has Improved Print management compared to 2000
server.
22) 2003 has telnet sessions available.
23) 2000 supports IPV4 whereas 2003 supports IPV4 and
IPV6.
And Active Directory Differences-- -2000AD:--
1. Only one million object can be created.
2. Universal group membership is not present.
3. Between parent and child, there is no built in trust .It
is called as non-transitive trust.
4. There is only three AD partition, Domain partition,
configuration partition, schema partition.
5. In Win 2000 server we can apply 620 group policies .
6. but 2k only Emergency Repair Disk(ERD) is there.
2003AD:-
1. 2 Million object can be created .
2. It is a new feature available in 2003.
3. Between parent and child, there is built in trust .It
is called as transitive trust.
4. Same partitions are there in 2003, but one additional
partition called Application directory partition is present.
5. but in 2003 we can apply nearly 720 so Win2003 server is
more secure than win 2000 server.
6. Automated System Recovery(ASR) is there
READ MORE - Difference in Windows server2000 and 2003?

Difference in Windows server2000 and 2003?

Difference in Windows server2000 and 2003?

1) When installing terminal services for win2000 u r
prompted to select application server functions or
administrative functions sets can be installed sequently on
one server but it performs only one function at one time.
But in 2003 still distinguishes between application and
administrative services but installation and management are
now consolidated.
2) In Win 2000 server we can apply 620 group policies
but in 2003 we can apply nearly 720 so Win2003 server is
more secure than win 2000 server.
3) In 2000 we cannot rename domain whereas in 2003 we
can rename Domain.
4) In 2000 it supports of 8 processors and 64 GB RAM
(In 2000 Advance Server) whereas in 2003 supports up to 64
processors and max of 512GB RAM.
5) 2000 Supports IIS 5.0 and 2003 Supports IIS6.0
6) 2000 doesn’t support Dot net whereas 2003 Supports
Microsoft .NET 2.0
7) 2000 has Server and Advance Server editions whereas
2003 has Standard, Enterprise, Datacenter and Web server
Editions.
8) 2000 doesn’t have any 64 bit server operating
system whereas 2003 has 64 bit server operating systems
(Windows Server 2003 X64 Std and Enterprise Edition)
9) 2000 has basic concept of DFS (Distributed File
systems) with defined roots whereas 2003 has Enhanced DFS
support with multiple roots.
10) In 2000 there is complexality in administering
Complex networks whereas 2003 is easy administration in all
& Complex networks.
11) In 2000 we can create 1 million users and in 2003
we can create 1 billion users.
12) In 2003 we have concept of Volume shadow copy
service which is used to create hard disk snap shot which
is used in Disaster recovery and 2000 doesn’t have this
service.
13) In 2000 we don’t have end user policy management,
whereas in 2003 we have a End user policy management which
is done in GPMC (Group policy management console).
14) In 2000 we have cross domain trust relation ship
and 2003 we have Cross forest trust relationship.
15) 2000 Supports 4-node clustering and 2003 supports 8-
node clustering.
16) 2003 has High HCL Support (Hardware Compatibility
List) issued by Microsoft.
17) Code name of 2000 is Win NT 5.0 and Code name of
2003 is Win NT 5.1
18) 2003 has service called ADFS (Active Directory
Federation Services) which is used to communicate between
branches with safe authentication.
19) In 2003 their is improved storage management using
service File Server Resource Manager (FSRM).
20) 2003 has service called Windows Share point
Services (It is an integrated portfolio of collaboration
and communication services designed to connect people,
information, processes, and systems both within and beyond
the organizational firewall).
21) 2003 has Improved Print management compared to 2000
server.
22) 2003 has telnet sessions available.
23) 2000 supports IPV4 whereas 2003 supports IPV4 and
IPV6.
And Active Directory Differences-- -2000AD:--
1. Only one million object can be created.
2. Universal group membership is not present.
3. Between parent and child, there is no built in trust .It
is called as non-transitive trust.
4. There is only three AD partition, Domain partition,
configuration partition, schema partition.
5. In Win 2000 server we can apply 620 group policies .
6. but 2k only Emergency Repair Disk(ERD) is there.
2003AD:-
1. 2 Million object can be created .
2. It is a new feature available in 2003.
3. Between parent and child, there is built in trust .It
is called as transitive trust.
4. Same partitions are there in 2003, but one additional
partition called Application directory partition is present.
5. but in 2003 we can apply nearly 720 so Win2003 server is
more secure than win 2000 server.
6. Automated System Recovery(ASR) is there
READ MORE - Difference in Windows server2000 and 2003?

Difference in Windows server2000 and 2003?

Difference in Windows server2000 and 2003?

1) When installing terminal services for win2000 u r
prompted to select application server functions or
administrative functions sets can be installed sequently on
one server but it performs only one function at one time.
But in 2003 still distinguishes between application and
administrative services but installation and management are
now consolidated.
2) In Win 2000 server we can apply 620 group policies
but in 2003 we can apply nearly 720 so Win2003 server is
more secure than win 2000 server.
3) In 2000 we cannot rename domain whereas in 2003 we
can rename Domain.
4) In 2000 it supports of 8 processors and 64 GB RAM
(In 2000 Advance Server) whereas in 2003 supports up to 64
processors and max of 512GB RAM.
5) 2000 Supports IIS 5.0 and 2003 Supports IIS6.0
6) 2000 doesn’t support Dot net whereas 2003 Supports
Microsoft .NET 2.0
7) 2000 has Server and Advance Server editions whereas
2003 has Standard, Enterprise, Datacenter and Web server
Editions.
8) 2000 doesn’t have any 64 bit server operating
system whereas 2003 has 64 bit server operating systems
(Windows Server 2003 X64 Std and Enterprise Edition)
9) 2000 has basic concept of DFS (Distributed File
systems) with defined roots whereas 2003 has Enhanced DFS
support with multiple roots.
10) In 2000 there is complexality in administering
Complex networks whereas 2003 is easy administration in all
& Complex networks.
11) In 2000 we can create 1 million users and in 2003
we can create 1 billion users.
12) In 2003 we have concept of Volume shadow copy
service which is used to create hard disk snap shot which
is used in Disaster recovery and 2000 doesn’t have this
service.
13) In 2000 we don’t have end user policy management,
whereas in 2003 we have a End user policy management which
is done in GPMC (Group policy management console).
14) In 2000 we have cross domain trust relation ship
and 2003 we have Cross forest trust relationship.
15) 2000 Supports 4-node clustering and 2003 supports 8-
node clustering.
16) 2003 has High HCL Support (Hardware Compatibility
List) issued by Microsoft.
17) Code name of 2000 is Win NT 5.0 and Code name of
2003 is Win NT 5.1
18) 2003 has service called ADFS (Active Directory
Federation Services) which is used to communicate between
branches with safe authentication.
19) In 2003 their is improved storage management using
service File Server Resource Manager (FSRM).
20) 2003 has service called Windows Share point
Services (It is an integrated portfolio of collaboration
and communication services designed to connect people,
information, processes, and systems both within and beyond
the organizational firewall).
21) 2003 has Improved Print management compared to 2000
server.
22) 2003 has telnet sessions available.
23) 2000 supports IPV4 whereas 2003 supports IPV4 and
IPV6.
And Active Directory Differences-- -2000AD:--
1. Only one million object can be created.
2. Universal group membership is not present.
3. Between parent and child, there is no built in trust .It
is called as non-transitive trust.
4. There is only three AD partition, Domain partition,
configuration partition, schema partition.
5. In Win 2000 server we can apply 620 group policies .
6. but 2k only Emergency Repair Disk(ERD) is there.
2003AD:-
1. 2 Million object can be created .
2. It is a new feature available in 2003.
3. Between parent and child, there is built in trust .It
is called as transitive trust.
4. Same partitions are there in 2003, but one additional
partition called Application directory partition is present.
5. but in 2003 we can apply nearly 720 so Win2003 server is
more secure than win 2000 server.
6. Automated System Recovery(ASR) is there
READ MORE - Difference in Windows server2000 and 2003?

have a laugh Nice Joke

Niceeeeeeeeee Jokessssssssss


TEACHER : Why are you late? BALGOBIN : Because of the sign. TEACHER : What sign? BALGOBIN : The one that says, "School Ahead, Go Slow." *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, why are you doing your math sums on the floor? BALGOBIN : You told me to do it without using tables! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, how do you spell "crocodile"? BALGOBIN : "K-R-O-K-O-D-A-I-L" TEACHER : No, that's wrong BALGOBIN : Maybe it's wrong, but you asked me how I spell it! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : What is the chemical formula for water? BALGOBIN : "HIJKLMNO"!! TEACHER : What are you talking about? BALGOBIN : Yesterday you said it's H to O! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, go to the map and find North America . BALGOBIN : Here it is! TEACHER : Correct. Now, class, who discovered America ? CLASS : Balgobin! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, name one important thing we have today that we didn't have ten years ago. BALGOBIN : Me! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, why do you always get so dirty? BALGOBIN : Well, I'm a lot closer to the ground than you are. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* BALGOBIN : Dad, can you write in the dark? FATHER : I think so. What do you want me to write? BALGOBIN : Your name on this report card.*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : How can you prevent diseases caused by biting insects? BALGOBIN : Don't bite any. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-**-*-*-*-* TEACHER : Balgobin, give me a sentence starting with "I". BALGOBIN : I is... TEACHER : No, Balgobin. Always say, "I am." BALGOBIN : All right... "I am the ninth letter of the alphabet
READ MORE - have a laugh Nice Joke

have a laugh Nice Joke

Niceeeeeeeeee Jokessssssssss


TEACHER : Why are you late? BALGOBIN : Because of the sign. TEACHER : What sign? BALGOBIN : The one that says, "School Ahead, Go Slow." *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, why are you doing your math sums on the floor? BALGOBIN : You told me to do it without using tables! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, how do you spell "crocodile"? BALGOBIN : "K-R-O-K-O-D-A-I-L" TEACHER : No, that's wrong BALGOBIN : Maybe it's wrong, but you asked me how I spell it! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : What is the chemical formula for water? BALGOBIN : "HIJKLMNO"!! TEACHER : What are you talking about? BALGOBIN : Yesterday you said it's H to O! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, go to the map and find North America . BALGOBIN : Here it is! TEACHER : Correct. Now, class, who discovered America ? CLASS : Balgobin! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, name one important thing we have today that we didn't have ten years ago. BALGOBIN : Me! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, why do you always get so dirty? BALGOBIN : Well, I'm a lot closer to the ground than you are. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* BALGOBIN : Dad, can you write in the dark? FATHER : I think so. What do you want me to write? BALGOBIN : Your name on this report card.*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : How can you prevent diseases caused by biting insects? BALGOBIN : Don't bite any. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-**-*-*-*-* TEACHER : Balgobin, give me a sentence starting with "I". BALGOBIN : I is... TEACHER : No, Balgobin. Always say, "I am." BALGOBIN : All right... "I am the ninth letter of the alphabet
READ MORE - have a laugh Nice Joke

have a laugh Nice Joke

Niceeeeeeeeee Jokessssssssss


TEACHER : Why are you late? BALGOBIN : Because of the sign. TEACHER : What sign? BALGOBIN : The one that says, "School Ahead, Go Slow." *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, why are you doing your math sums on the floor? BALGOBIN : You told me to do it without using tables! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, how do you spell "crocodile"? BALGOBIN : "K-R-O-K-O-D-A-I-L" TEACHER : No, that's wrong BALGOBIN : Maybe it's wrong, but you asked me how I spell it! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : What is the chemical formula for water? BALGOBIN : "HIJKLMNO"!! TEACHER : What are you talking about? BALGOBIN : Yesterday you said it's H to O! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, go to the map and find North America . BALGOBIN : Here it is! TEACHER : Correct. Now, class, who discovered America ? CLASS : Balgobin! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, name one important thing we have today that we didn't have ten years ago. BALGOBIN : Me! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, why do you always get so dirty? BALGOBIN : Well, I'm a lot closer to the ground than you are. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* BALGOBIN : Dad, can you write in the dark? FATHER : I think so. What do you want me to write? BALGOBIN : Your name on this report card.*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : How can you prevent diseases caused by biting insects? BALGOBIN : Don't bite any. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-**-*-*-*-* TEACHER : Balgobin, give me a sentence starting with "I". BALGOBIN : I is... TEACHER : No, Balgobin. Always say, "I am." BALGOBIN : All right... "I am the ninth letter of the alphabet
READ MORE - have a laugh Nice Joke

have a laugh Nice Joke

Niceeeeeeeeee Jokessssssssss


TEACHER : Why are you late? BALGOBIN : Because of the sign. TEACHER : What sign? BALGOBIN : The one that says, "School Ahead, Go Slow." *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, why are you doing your math sums on the floor? BALGOBIN : You told me to do it without using tables! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, how do you spell "crocodile"? BALGOBIN : "K-R-O-K-O-D-A-I-L" TEACHER : No, that's wrong BALGOBIN : Maybe it's wrong, but you asked me how I spell it! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : What is the chemical formula for water? BALGOBIN : "HIJKLMNO"!! TEACHER : What are you talking about? BALGOBIN : Yesterday you said it's H to O! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, go to the map and find North America . BALGOBIN : Here it is! TEACHER : Correct. Now, class, who discovered America ? CLASS : Balgobin! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, name one important thing we have today that we didn't have ten years ago. BALGOBIN : Me! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, why do you always get so dirty? BALGOBIN : Well, I'm a lot closer to the ground than you are. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* BALGOBIN : Dad, can you write in the dark? FATHER : I think so. What do you want me to write? BALGOBIN : Your name on this report card.*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : How can you prevent diseases caused by biting insects? BALGOBIN : Don't bite any. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-**-*-*-*-* TEACHER : Balgobin, give me a sentence starting with "I". BALGOBIN : I is... TEACHER : No, Balgobin. Always say, "I am." BALGOBIN : All right... "I am the ninth letter of the alphabet
READ MORE - have a laugh Nice Joke

have a laugh Nice Joke

Niceeeeeeeeee Jokessssssssss


TEACHER : Why are you late? BALGOBIN : Because of the sign. TEACHER : What sign? BALGOBIN : The one that says, "School Ahead, Go Slow." *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, why are you doing your math sums on the floor? BALGOBIN : You told me to do it without using tables! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, how do you spell "crocodile"? BALGOBIN : "K-R-O-K-O-D-A-I-L" TEACHER : No, that's wrong BALGOBIN : Maybe it's wrong, but you asked me how I spell it! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : What is the chemical formula for water? BALGOBIN : "HIJKLMNO"!! TEACHER : What are you talking about? BALGOBIN : Yesterday you said it's H to O! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, go to the map and find North America . BALGOBIN : Here it is! TEACHER : Correct. Now, class, who discovered America ? CLASS : Balgobin! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, name one important thing we have today that we didn't have ten years ago. BALGOBIN : Me! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : Balgobin, why do you always get so dirty? BALGOBIN : Well, I'm a lot closer to the ground than you are. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* BALGOBIN : Dad, can you write in the dark? FATHER : I think so. What do you want me to write? BALGOBIN : Your name on this report card.*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* TEACHER : How can you prevent diseases caused by biting insects? BALGOBIN : Don't bite any. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-**-*-*-*-* TEACHER : Balgobin, give me a sentence starting with "I". BALGOBIN : I is... TEACHER : No, Balgobin. Always say, "I am." BALGOBIN : All right... "I am the ninth letter of the alphabet
READ MORE - have a laugh Nice Joke

10 Online Publishers That Want To Pay You to Write

The Internet
has made it possible for ordinary people like yourself to write and make money from the very thing that you already enjoy doing. Webmasters are consistently on the lookout to partner with eager writers that desire to share their passions with other people around the world. Most smart webmasters have already learned that in order to attract and maintain a healthy population of amazing authors is to share the ad revenue or just pay them well for their services.
Personally, I have always enjoyed writing and have equally enjoyed helping my fellow writers locate the very best writing opportunities available online and offline. By working together we all can achieve some measure of success and readership for our works. This is exactly the main reason for writing these types of articles for me. I just enjoy watching people succeed.
Some of the following opportunities I have personal, first-hand experience writing for or dealing with and I have included a mention regarding the programs that I am currently involve with and/or have written for or dealt with in the past. Honestly, I only have a finite amount of time to write and for me, writing for no more than a couple of services in all I can manage effectively.
If you would like to learn about other writing opportunities that I have written about in the past, then check out Five Fantastic Freelance Websites for Writers Earning an Income honest living doing exactly what makes you happy.
Bukisa (http://www.bukisa.com/join/2633)
Writers serious about earning some extra cash from their written word will discover some satisfaction when choosing to write and publish with Bukisa. This online publisher offers writers currently $3.95 per 1000 unique page views that their published content earns on an individual basis for as long as the content is published on the website. So, the more that a writer writes, then the better the long-term royalty residuals will be month after month.
Additionally, Bukisa offers all of its members an unique opportunity to generate an extra stream of income by simply referring their family and friends to join Bukisa to publish their writings, photography, slides, audio or videos on the publisher's website. Be sure to read Bukisa's terms and policies, before joining, so to be certain that this publishing opportunity is the right program for you to join.
Triond (http://www.triond.com)
I can personally testify that Triond has one of the very best writing programs on the Internet, today. Writers can write about practically anything subject under-the-sun within the boundaries of common sense. Triond rewards their writers 50% of the ad revenues that is generated from the author's published articles. I have never had any problems getting paid and in my personal experience, I have been paid very well.
StoryMash (http://www.storymash.com)
This is a relatively new website to me, but after visiting and checking things out I can see the potential in participating in this program. StoryMash is a community of like-minded writers that write and publish stories one chapter at a time. Once the writer's chapter is published, and then other writers can write the next chapter in any way that they choose to write it. So, the stories at StoryMash start with the first chapter written by you, and then after that the story may have five second chapter and so on. You get paid at least 50% of all third party ad revenue. You must have a Google Adsense Account, so that you can earn money in the StoryMash program.
Xomba (http://www.xomba.com)
Write Xombytes for Xomba and earn real cash monies from the ad revenue earned from the things that you write. Xomba members must have a Google Adsense Account, so that they can earn money in the program. Xomba pays 50% of the ad revenue generated from the articles and blogs that you write.
ReviewParty (http://www.reviewparty.com)
If you are writer that enjoys sharing your opinion about the movies that you watch or the music that you listen to or about the commercial products that you normally purchase, then ReviewParty is a program that you should seriously consider. It is very simple, just write reviews about the products that you currently use and get paid for sharing your opinions. ReviewParty pays 50% of the ad revenue that your review(s) generate through Google Adsense, but you must have a Google Adsense Account to participate in the program.
Daytipper (http://www.daytipper.com)
Earn $1.00 for earn insightful tip that you write and is accepted by Daytipper and published. Share what you know with people who want to know what you know.
CREAMaid (http://www.creamaid.com)
This service lets you meet other bloggers with similar interests as you, and make money while doing it. Write an interesting blog about anything that you are interest in as long as they abide in accordance to the CREAMaid writing guidelines and rules. It is not clear how much of the ad revenue is shared in part of the royalty program, but by writing a couple of blogs I am sure you will learn what it is exactly.
LetterRep (http://www.letterrep.com)
The LetterRep program pays writers to write letters that are designed to sell to companies or individuals who are in need of professionally written letters to be used as possible mail outs or other marketing needs. Writers are paid every time a LetterRep client purchases or request one of the letters that you have had published through LetterRep. The payouts vary depending on the type of request that you receive.
ReviewStream (http://www.reviewstream.com)
ReviewStream is consistently seeking writers to write comprehensive and professionally written product reviews. Writers can write about any commercial product that they choose to write about, but it is always best to have actually used the products before writing a review about it. Writers can earn up to $2.00 per accepted review and an additional 10 cents for every vote that their review receives from actual visitors. There are some writing guidelines to consider before beginning the program, so be sure to take time to read them carefully. I have personal experience writing for this company and I know first hand that you can potentially earn a nice second income, if you work at it long enough.
MatrixMails (http://www.matrixmails.com)
Now, I find this program really quite interesting as there are many ways to earn money through this website. However, this article is strictly about writing opportunities where eager writers can earn money from the things that they write, so here is what I know about this program. Writers get paid to write articles in the English language and can earn additional bonuses for the accumulate clickthru received through your membership. Like I have already mentioned this is not the only way to start making money in this program, so you may want to check them all out once you have some extra free time to spare.
READ MORE - 10 Online Publishers That Want To Pay You to Write

 
 
 

Popular Posts