DNS slow logons for XP not 2k pro

Discussion in 'Network Infrastructure' started by itdaddy, Sep 15, 2006.

  1. itdaddy

    itdaddy Byte Poster

    116
    0
    14
    hey gurus

    scenario:

    we have been having slow logons with XP pro only
    none of our 2k pro machines sit at Applying Computer Settings
    for 3-5 minutes. They are random times, users, and PCs.

    we have been also having network issues with cracking of our phone lines and slow network movement; users tell me
    that their applications are running slow( the applications using the network).

    no event erros leading to believe it is DNS? wtf! guys!

    had to reboot all 3 network(site) routers the other day to
    refresh the network again and it worked. all three routers
    were stalling..wtf is going on with the routers all stalling.
    not responding and all. what causes this?
    do you think DNS plays a role or maybe when we change the DNS configuration on our DNS servers the routers didnt get the updated DNS information and maybe routing tables in the routers are jacked???? what you guysthink

    thanks
    :eek:

    i have sqeezed performance out of GPO and each PC with all the tricks but nothing! and nothing in event logs on clients and DCs????

    DNS and routers/tables is what I think help!
    thanks
     
  2. GmanUK

    GmanUK Byte Poster

    154
    5
    32
    Hi

    May sound mad, and it is an initial thought without looking too deeply but you haven't got any of the machines running NetBeui have you? I'm thinking broadcasts slowing the network and killing the routers? As I said..thinking out load :blink
     
    Certifications: CompTIA N+, Server+, CCSN, ITILv3 (f)
    WIP: MCITP Security
  3. Bluerinse
    Honorary Member

    Bluerinse Exabyte Poster

    8,878
    181
    256
    Did the problem start when you changed the DNS settings?

    Are you using roaming profiles?

    How is your network set up?
     
    Certifications: C&G Electronics - MCSA (W2K) MCSE (W2K)
  4. itdaddy

    itdaddy Byte Poster

    116
    0
    14
    for example:
    (not really exact IPs but same concept)

    4 remote sites
    1 domain
    Active Directory Integrated

    192.168.1.1 SRV1 (server 1) DNS/DC/Print Server (2000)
    DNS:
    p 1.1
    s 2.1
    clients: 1.1, 2.1
    192.168.2.1 SRV2 " DNS/DC/Print Server (2000)
    DNS:
    p 1.1
    s 2.1
    clients 2.1, 1.1

    192.168.3.1 SRV3 " DNS/DC/Print Server (2000)
    DNS
    p1.1
    s2.1
    clients 3.1, 1.1

    192.168.4.1 SRV4 " DNS/DC/Print Server (2003)
    DNS
    p1.1
    s2.1

    clients 4.1, 1.1

    --------------------------------
    i have read once the SRV record is established put
    each DC back to pointing to self as primary DNS.
    we never had issues until he changed this.
    but it happened say a few weeks or so after this reconfig
    of DNS.

    thanks
     
  5. itdaddy

    itdaddy Byte Poster

    116
    0
    14
    it all started say 3-4 weeks after tech reconfig our DNS servers
    :eek:
     
  6. Bluerinse
    Honorary Member

    Bluerinse Exabyte Poster

    8,878
    181
    256
    Thinking more about this issue, I don't believe it to be a DNS issue as such or your W2K clients would be suffering too.

    So I did a bit of googling and came up with this, which may be worth a try..

    The source
     
    Certifications: C&G Electronics - MCSA (W2K) MCSE (W2K)
  7. itdaddy

    itdaddy Byte Poster

    116
    0
    14
    bluerinse..
    i found same article and tried this...


    thanks check this out:
    butokay i am not sure but what you think

    we have th 4 domain controllers
    all SYSVOL are the same size on each DC

    but on three servers DC1, DC2, DC3 the ntds.dit file is
    34,833KB and on DC4 it is 30, 833 KBs

    server 1 -3 are Advance server 2000
    server 4 is 2003 server added like 3 years later

    shouldnt they be the same size replicated out to each
    DC??? or less since added later??

    we have had to reboot DC1 and DC2 and DC4 once in while
    to speed up network; it has worked
    and we have had funny stuff with AD user and objects
    in groups that should not be!

    my gut is now saying AD-integration corruption due to
    faulty replications; i have found some MS tech papers
    on AD-Integ can get corrupted but the question is
    what to can i use to verify DB is corrupt and how to revive it?
    I am looking into the ntdsutil.exe tool!

    will keep you guys up to date

    thanks bluerinse!
    appreicate your research!
     
  8. Sparky
    Highly Decorated Member Award 500 Likes Award

    Sparky Zettabyte Poster Moderator

    10,718
    543
    364
    Is it possible to make some changes in AD and then push the replication manually? Then you could check the other DCs to see if the changes have replicated successfully.

    Any chance on some more info on how the network is setup? :blink
     
    Certifications: MSc MCSE MCSA:M MCSA:S MCITP:EA MCTS(x5) MS-900 AZ-900 Security+ Network+ A+
    WIP: Microsoft Certs
  9. itdaddy

    itdaddy Byte Poster

    116
    0
    14
    AD - Integrated mixed mode
    all DCs are DNS servers/file servers/print servers
    p = primary DNS
    s = second ary DSN
    2000 advance server
    dc1 192.168.1.1

    p 1.1
    s 2.1
    clienst 1.1, 2.1

    2000 windows
    dc2 2.1
    p 1.1
    s 2.1
    clients 2.1, 1.1

    2000 windows
    dc3 3.1

    1.1
    2.1
    clients 3.1, 1.1

    2003 windows GC
    dc4 4.1
    1.1
    2.1

    clients 4.1, 1.1


    shouldnt the ntds.dit file on all servers be the same size
    time stamp is the same but size on dc4 is 4000kb less.

    thanks
    is this enough

    only one domain!
    4 sites which are the Dc1 to Dc4
    :eek:
     
  10. Sparky
    Highly Decorated Member Award 500 Likes Award

    Sparky Zettabyte Poster Moderator

    10,718
    543
    364
    Have you tried the suggestion by Bluerinse?

    If so has the GP replicated ok in the SYSVOL folder? :blink

    If possible switch off the DC on your site (out of hours) and then log on. If it takes ages but you log on ok (make sure you are not using a cached profile) then it looks like secondary DNS server is being used to logon.

    Not the easiest problem to fix! :biggrin

    Edit: Forgot about this gem. Install the Windows 2003 Resource Kit here http://www.microsoft.com/downloads/...69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en
    Then at the run line line type replmon This will monitor replication and allow you to do some troubleshooting
     
    Certifications: MSc MCSE MCSA:M MCSA:S MCITP:EA MCTS(x5) MS-900 AZ-900 Security+ Network+ A+
    WIP: Microsoft Certs
  11. Bluerinse
    Honorary Member

    Bluerinse Exabyte Poster

    8,878
    181
    256
    Okay, my gut feeling is that you are barking up the wrong tree with your AD corruption theory. If it was corrupted I am sure you would see the problem in Event viewer!

    Also you should not concern yourself with the fact that the ntds.dit is not of uniform size on different DCs.

    Source

    I would focus on DNS!

    Pete
     
    Certifications: C&G Electronics - MCSA (W2K) MCSE (W2K)
  12. Sparky
    Highly Decorated Member Award 500 Likes Award

    Sparky Zettabyte Poster Moderator

    10,718
    543
    364
    Maybe the problem is DNS related after all :biggrin
     
    Certifications: MSc MCSE MCSA:M MCSA:S MCITP:EA MCTS(x5) MS-900 AZ-900 Security+ Network+ A+
    WIP: Microsoft Certs

Share This Page

Loading...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.