Announcement

Collapse
No announcement yet.

Extremely long/slow client logons

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

  • Extremely long/slow client logons

    Small network with single W2K sp4 server with 8 W2K client workstations.

    Takes clients 15 - 20 minutes to log on.
    Is the long client workstation logon problem because the client workstations are pointed to ISP's nameserver and that their is no configured DNS server on the local network that does resolving on the lan?

    Server Settings:

    Host Name: server1
    Primary DNS suffix: bchmed.com
    Node Type: Broadcast
    IP Routing Enabled: Yes
    Wins Proxy: No
    DNS Suffix Search List: bchmed.com

    DHCP Enabled: No
    IP Address: 192.168.5.10
    SN Mask: 255.255.255.0
    Default Gateway: 192.168.50.1
    DNS Servers: 207.191.50.10 206.222.97.82
    ------------------------------------------------------
    First Server Event Log error messages:
    Computer: Server1
    Source: Netlogon
    Type: Warning
    Category: None
    EventID: 5781

    Description:
    Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available.
    --------------------------------------------------
    Second Server Event Log error messages:
    Computer: Server1
    Source: DnsAPI
    Type: Warning
    Category: None
    EventID: 11151

    Description:
    The system failed to register network adapter with settings:
    Host Name: server1
    Adapter-specfic Domain Suffix: bchmed.com
    DNS server list:
    207.191.50.10, 206.222.97.82
    Sent update to server: None
    IP Adress(es):
    192.168.50.10

    The cause of this DNS registration failure was because of DNS server failure.
    -------------------------------------------------
    Workstations are DHCP clients that get their ip addresses from the ISP's onsite router that provides the ISP's DNS servers IP address information as well for connecting to the internet.

    First Client Workstation Event Log
    Computer: WS2K7
    Source: DnsAPI
    Type: Warning
    Category: None
    EventID: 11151

    Description:
    The system failed to register network adapter with settings:
    Host Name: WS2K7
    Adapter-specfic Domain Suffix: bchmed.com
    DNS server list:
    207.191.50.10, 206.222.97.82
    Sent update to server: None
    IP Adress(es):
    192.168.50.26

    The cause of this DNS registration failure was because of DNS server failure.
    ----------------------------------------------------

    Second Client Workstation Event Log
    Computer: WS2K7
    Source: Userenv
    Type: Warning
    Category: None
    EventID: 1000

    Description:
    Windows cannot determine the user or computer name. Return value (1722).


    ------------------------------------------------------

    Is the long client workstation logon problem because the client workstations are pointed to ISP's nameserver and that their is no configured DNS server on the local network that does resolving on the lan?

  • #2
    Long question, short answer: Yes.

    Configure your local DNS to forward queries to your ISP, and have all computers use the local DNS.
    Cheers,

    Daniel Petri
    Microsoft Most Valuable Professional - Active Directory Directory Services
    MCSA/E, MCTS, MCITP, MCT

    Comment


    • #3
      I don't see the DNS management console in start, programs administrative tools.

      I don't think DNS is installed. When I look at AD users and computers the server shows up as a DC but there is no DNS.

      Can AD exist without DNS installed?

      Thank you.

      Comment


      • #4
        no, maybe are you just missing the shortcut..

        find the snapin using the mmc Concole (start --> run --> mmc --> ok)
        Marcel
        Technical Consultant
        Netherlands
        http://www.phetios.com
        http://blog.nessus.nl

        MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
        "No matter how secure, there is always the human factor."

        "Enjoy life today, tomorrow may never come."
        "If you're going through hell, keep going. ~Winston Churchill"

        Comment


        • #5
          Originally posted by brew
          I don't see the DNS management console in start, programs administrative tools.

          I don't think DNS is installed. When I look at AD users and computers the server shows up as a DC but there is no DNS.

          Can AD exist without DNS installed?
          No, it cannot. This means that you're in big trouble, and without fixing your DNS issues you're going to have some rough time.

          See my site for AD and DNS issues.
          Cheers,

          Daniel Petri
          Microsoft Most Valuable Professional - Active Directory Directory Services
          MCSA/E, MCTS, MCITP, MCT

          Comment

          Working...
          X