password pb

Discussion in 'Active Directory' started by vhoward, Apr 21, 2006.

  1. vhoward

    vhoward Guest

    hi,

    i use windows server 2003 and active directory

    later i was on NT4, stations are on XP

    when i reset a password using AD the user obtain the following message when
    he tries to log with a new password :
    domain server is actually UNDISPONIBLE ... (translated from french)

    with news stations i don't have the problem

    could you help me
    thanks in advance
     
    vhoward, Apr 21, 2006
    #1
    1. Advertisements

  2. vhoward

    Jmnts Guest

    Hi

    Can you ping the FQDN of the Domain controller (ping server.domain.com)?
    Check clients dns settings (should be pointing to your DC Dns ip address)
     
    Jmnts, Apr 21, 2006
    #2
    1. Advertisements

  3. vhoward

    vhoward Guest

    thanks for your help

    yes i have a positive result with nslookup

    the pb remains

    may be the diagnostic would be more simple with this phenomen : when i press
    ctrl+alt+sup and try to change the pass, i have the message "server not
    disponible"
    unless i have opened a session
     
    vhoward, Apr 24, 2006
    #3
  4. vhoward

    Jmnts Guest

    Hi
    server not disponible = server not available


    This only happens for a especific user, does this user can change his pw on
    another computer?
    Can you change the pw for other users in this pc?

    Could you please post the results for:
    ipconfig /all
    dcdiag /test:registerindns /dnsdomain:domain.com
    netdiag /test:dsgetdc /v
    nltest /dsgetdc:domain.com




    --
    I Hop that helps

    Best Regards
    Systems Administrator
    MCSA + Exchange
     
    Jmnts, Apr 25, 2006
    #4
  5. vhoward

    vhoward Guest

    hi,

    sorry to respond so later, was not a the office for some days

    This only happens for a especific user = > happens for some users
    does this user can change his pw on another computer => yes, users can
    change their password on another computer

    IPCONFIG /ALL on the server
    =====================
    Configuration IP de Windows

    Nom de l'hôte . . . . . . . . . . : BHHOLDING
    Suffixe DNS principal . . . . . . : KLEBER
    Type de noud . . . . . . . . . . : Inconnu
    Routage IP activé . . . . . . . . : Non
    Proxy WINS activé . . . . . . . . : Non
    Liste de recherche du suffixe DNS.: KLEBER

    Carte Ethernet Connexion au réseau local :

    Suffixe DNS propre à la connexion :
    Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
    Connection
    Adresse physique . . . . . . . . . : 00-11-43-27-00-B7
    DHCP activé. . . . . . . . . . . . : Non
    Adresse IP. . . . . . . . . . . . : 197.30.30.200
    Masque de sous-réseau . . . . . . : 255.255.255.0
    Passerelle par défaut . . . . . . : 197.30.30.2
    Serveurs DNS . . . . . . . . . . : 193.252.19.3
    193.252.19.4

    dcdiag /test:registerindns /dnsdomain:domain.com on the server
    =================================
    Starting test: RegisterInDNS
    DNS configuration is sufficient to allow this domain controller to
    dynamically register the domain controller Locator records in DNS.

    DnsUpdateTest returned 9017. The A record test is thus inconclusive.

    ......................... BHHOLDING passed test RegisterInDNS


    netdiag => not working, dll problem DNSAPI.dll

    nltest => not working, dll problem NETAPI32.dll


    thanks in advance
     
    vhoward, Apr 27, 2006
    #5
  6. vhoward

    Jmnts Guest

    sorry to respond so later, was not a the office for some days
    Assuming that this server is DNS server:
    THE DNS SETTINGS ARE WRONG, the DNS should point to itself (197.30.30.200),
    if the 193.252.19.3 and the 193.252.19.4 are the Dns Servers that resolve
    internet addresses you have to place them on Forwarders tab under Dns server
    properties. ALL CLIENTS should have Dns address to 197.30.30.200


    As you can see your DC can't find sifficient information to register in dns.



    Start by resoolving this problem:

    1 - POINT DC dns settings to itself under TCP/IP prooerties, the Dns should
    have the 197.30.30.200
    2 - Go to the DNS console and right click the DNS server and choose
    properties then goto the forwarders tab and place both DNS settings
    193.252.19.3 and the 193.252.19.4.
    3 - MAKE SURE that your clients have their DNS settings pointing to the DC
    Address (197.30.30.200) and nothing more.


    Let me know if it worked.




    --
    I Hop that helps

    Best Regards
    Systems Administrator
    MCSA + Exchange
     
    Jmnts, Apr 28, 2006
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.