Long wait after Logging on to Win 2003 std serve

Discussion in 'Server Networking' started by Burny, Apr 2, 2005.

  1. Burny

    Burny Guest

    Hi there,

    I have this very weird problem on some of my client machines.

    When the machines are made part of the domain, they take very long to log
    on, after logging on successfully, you get to the screen,"Applying your
    personal settings" and then it takes up to 2,5 minutes before you see the

    Working on the machine off the local drive is fine, however the moment you
    try and open any of the network resources you have to wait for up to 5 min.
    before you can get access to it. This gets repeated everytime you try and
    access a network resource after not accessing it for about 5 - 10 minutes.

    The thing that really baffles me is that when a machine that is not part of
    the domain access the same network resource by using a username and password
    from the domain, there is absolutely no waiting at all. For my mobile users
    it's fine not to be part of the domain, however my desktop users need to be
    part of the domain.

    I got an article from Microsoft to disable the webclient and change the
    provider order so that microsoft windows network is at the top, however that
    did not make any difference.

    One of my suppliers also run Win2003 server and they do not have the problem
    at all.

    Does anyone have an idea of what it could be, or what i could to resolve the

    Thanks in advance.

    Burny, Apr 2, 2005
    1. Advertisements

  2. Burny

    Herb Martin Guest

    Frequently this is a DNS issue.
    (It's actually an authentication issue but that is usually
    a DNS issue.)
    Because the authentication is explicit when
    done this way.
    Start here:

    DNS for AD
    1) Dynamic for the zone supporting AD
    2) All internal DNS clients NIC\IP properties must specify SOLELY
    that internal, dynamic DNS server (set.)
    3) DCs and even DNS servers are DNS clients too -- see #2
    4) If you have more than one Domain, every DNS server must
    be able to resolve ALL domains (either directly or indirectly)

    netdiag /fix

    ....or maybe:

    dcdiag /fix

    (Win2003 can do this from Support tools):
    nltest /dsregdns /server:DC-ServerNameGoesHere

    Ensure that DNS zones/domains are fully replicated to all DNS
    servers for that (internal) zone/domain.

    Also useful may be running DCDiag on each DC, sending the
    output to a text file, and searching for FAIL, ERROR, WARN.

    Single Label domain zone names are a problem Google:
    [ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
    Herb Martin, Apr 2, 2005
    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.