Re: Created users can't immediately login

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Yes I do have sites setup. The two domain controllers at the corporate
office are in the default first site. I then created sites for each of the
remote servers, and included the subnets for each server in subnets.

"Paul Bergson" <pbergson@xxxxxxxxxx> wrote in message
news:O1CCuaMDGHA.208@xxxxxxxxxxxxxxxxxxxxxxx
> You are correct on the response time, but do you have sites set up so that
> only the two corporate dc's are defined for this user to be authenticated
> against?
>
> --
>
>
> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> "msteinhoff" <msteinhoff@xxxxxxxxxxxxxxxxx> wrote in message
> news:%23YinGGKDGHA.2820@xxxxxxxxxxxxxxxxxxxxxxx
>> Environment:
>> Server 2003
>> Domain Func Level: Windows Server 2003
>> Forest Func Level: Windows Server 2003
>> The environment consists of corporate office(2 domain controllers) and 12
>> remote offices(1 domain controller/office).
>>
>> Problem:
>> If I create a user in the corporate office, and then try to log that user
>> on in the corporate office, I get an error message stating that the user
>> does not exist. Yet, if I look in my ADUaC on the two domain controllers
>> in the corporate office, the user is there. Do I have to wait for the
>> user to replicate throughout the entire AD structure before they can
>> login?
>>
>> Now, if I created a user on the corporate DC's and then tried to login
>> that user at a remote location I could see having to wait for
>> replication, but that is not the case.
>>
>> Thoughts...
>>
>>
>> Thanks
>>
>> Mike
>>
>
>


.

Relevant Pages

  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... You should check the dirctory services event log and the system event logs for errors and warning in addition to running the dcdiag /c /v command. ... This event can occur if the domain controllers ... Directory Server Diagnosis ... Verifying that the local machine ALPHA, ...
    (microsoft.public.windows.server.sbs)
  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... You should check the dirctory services event log and the system event logs for errors and warning in addition to running the dcdiag /c /v command. ... This event can occur if the domain controllers ... Directory Server Diagnosis ... Verifying that the local machine ALPHA, ...
    (microsoft.public.windows.server.sbs)
  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... test network connectivity to local domain controllers. ... Directory Server Diagnosis ... Verifying that the local machine ALPHA, ... The File Replication Service Event log test ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Migration to Server 2003 STANDARD
    ... so this is what the IT health scan looks like on the new Server 2008 ... Active Directory is connected to all domain controllers ... Active Directory Subnet Configuration Completed ... Check was skipped due to data collection errors ...
    (microsoft.public.windows.server.sbs)
  • Re: Net logon error event id:3096
    ... Verifying that the local machine yblrtgswip1, ... Connecting to directory service on server yblrtgswip1. ... No record of File Replication System, ... interval between domain controllers. ...
    (microsoft.public.win2000.active_directory)