Announcement

Collapse
No announcement yet.

Domain is no longer accessible to user

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Domain is no longer accessible to user

    hi Guys,


    I finally extend my schema and ran Dcpromo on my new windows 2003 server. I transferred the FSMO role to the two new servers with the global catalog. Now users can no longer log on to the domain.When user try to log on they get a error message saying log on to domain with correct user name and password.
    But i have not yet demoted my windows 2000 server yet. my Exchange is down.

    Below are some configuration from the ldap tools


    stablished connection to adbaddc1.
    Retrieving base DSA information...
    Result <0>: (null)
    Matched DNs:
    Getting 1 entries:
    >> Dn:
    1> currentTime: <ldp error <0x0>: cannot format time field;
    1> subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=agricba nk,DC=com;
    1> dsServiceName: CN=NTDS Settings,CN=ADBADDC1,CN=Servers,CN=Pegasus,CN=Site s,CN=Configuration,DC=agricbank,DC=com;
    5> namingContexts: DC=agricbank,DC=com; CN=Configuration,DC=agricbank,DC=com; CN=Schema,CN=Configuration,DC=agricbank,DC=com; DC=DomainDnsZones,DC=agricbank,DC=com; DC=ForestDnsZones,DC=agricbank,DC=com;
    1> defaultNamingContext: DC=agricbank,DC=com;
    1> schemaNamingContext: CN=Schema,CN=Configuration,DC=agricbank,DC=com;
    1> configurationNamingContext: CN=Configuration,DC=agricbank,DC=com;
    1> rootDomainNamingContext: DC=agricbank,DC=com;
    23> supportedControl: 1.2.840.113556.1.4.319; 1.2.840.113556.1.4.801; 1.2.840.113556.1.4.473; 1.2.840.113556.1.4.528; 1.2.840.113556.1.4.417; 1.2.840.113556.1.4.619; 1.2.840.113556.1.4.841; 1.2.840.113556.1.4.529; 1.2.840.113556.1.4.805; 1.2.840.113556.1.4.521; 1.2.840.113556.1.4.970; 1.2.840.113556.1.4.1338; 1.2.840.113556.1.4.474; 1.2.840.113556.1.4.1339; 1.2.840.113556.1.4.1340; 1.2.840.113556.1.4.1413; 2.16.840.1.113730.3.4.9; 2.16.840.1.113730.3.4.10; 1.2.840.113556.1.4.1504; 1.2.840.113556.1.4.1852; 1.2.840.113556.1.4.802; 1.2.840.113556.1.4.1907; 1.2.840.113556.1.4.1948;
    2> supportedLDAPVersion: 3; 2;
    12> supportedLDAPPolicies: MaxPoolThreads; MaxDatagramRecv; MaxReceiveBuffer; InitRecvTimeout; MaxConnections; MaxConnIdleTime; MaxPageSize; MaxQueryDuration; MaxTempTableSize; MaxResultSetSize; MaxNotificationPerConn; MaxValRange;
    1> highestCommittedUSN: 57476;
    4> supportedSASLMechanisms: GSSAPI; GSS-SPNEGO; EXTERNAL; DIGEST-MD5;
    1> dnsHostName: ADBADDC1.agricbank.com;
    1> ldapServiceName: agricbank.com:[email protected];
    1> serverName: CN=ADBADDC1,CN=Servers,CN=Pegasus,CN=Sites,CN=Conf iguration,DC=agricbank,DC=com;
    3> supportedCapabilities: 1.2.840.113556.1.4.800; 1.2.840.113556.1.4.1670; 1.2.840.113556.1.4.1791;
    1> isSynchronized: TRUE;
    1> isGlobalCatalogReady: FALSE;
    1> domainFunctionality: 0;
    1> forestFunctionality: 0;
    1> domainControllerFunctionality: 2;
    -----------

  • #2
    Re: Domain is no longer accessible to user

    Are there any kind of replication problems between the old DC and de new servers.
    In Active Directory Sites and Services on the Windows 2000 DC are there the new DCs listed?


    \Rems

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

    __________________

    ** Remember to give credit where credit's due **
    and leave Reputation Points for meaningful posts

    Comment

    Working...
    X