Re: Slow logon
From: Tom (oldfatjedi_at_hotmail.com)
Date: 07/29/04
- Next message: Markw911: "New NIC and DNS reporting event 414"
- Previous message: randy: "Re: duplication when setup.... ie: acme.acme.com"
- In reply to: Kevin D. Goodknecht Sr. [MVP]: "Re: Slow logon"
- Next in thread: Kevin D. Goodknecht Sr. [MVP]: "Re: Slow logon"
- Reply: Kevin D. Goodknecht Sr. [MVP]: "Re: Slow logon"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 28 Jul 2004 21:10:34 -0700
Thanks guys.
I thought I did all that but I'll find out in the morning when I'm back out
at the client.
Other than the client PC cache, are there any other DNS entries I should be
concerned with?
Thanks again,
Tom
"Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in message
news:%23LbS0vQdEHA.1000@TK2MSFTNGP12.phx.gbl...
> In news:%23SUeKKMdEHA.2376@tk2msftngp13.phx.gbl,
> Tom <oldfatjedi@hotmail.com> posted a question
> Then Kevin replied below:
> > I have an account that has an existing AD network. When
> > I first came on site I noticed that DNS had no forward
> > lookup zone and had the '.'
> > I thought that I'd come back and 'correct' that at some
> > later date.
> >
> > I had to replace the owners computer. A few days later
> > he complained that it would take minutes to access the
> > network resources. I thought NOW is the time to fix the
> > DNS so I went to the account and removed the dot and
> > created a forward lookup zone with a forwarder to the on
> > site LinkSys router (which should push traffic to the
> > ISP, right?). Everything worked fine.
> >
> > I got a call saying the problem remains for the boss's PC
> > and, this morning, the ISP went down and ALL the units
> > took 15 minutes to log in.
> >
> > I've verified that DHCP is providing the DNS / AD server
> > as the DNS server. Even with the ISP down, logging in
> > should only be local, right?
> > What did I do wrong or what can the problem be?
>
> Create a forward lookup zone with the name of the AD Domain in AD users
and
> computers, set it to allow dynamic updates. Delete the " . " forward
lookup
> zone if they want internet access.
>
> Make sure all machines use only the local DNS address for DNS, never the
> ISP's DNS in any position on the NIC. The ISP's DNS can be used only as a
> forwarder.
>
>
> --
> Best regards,
> Kevin D4 Dad Goodknecht Sr. [MVP]
> Hope This Helps
> ============================
> --
> When responding to posts, please "Reply to Group" via your
> newsreader so that others may learn and benefit from your
> issue. To respond directly to me remove the nospam. from my
> email. ==========================================
> http://www.lonestaramerica.com/
> ==========================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ==========================================
> Keep a back up of your OE settings and folders with
> OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ==========================================
>
>
- Next message: Markw911: "New NIC and DNS reporting event 414"
- Previous message: randy: "Re: duplication when setup.... ie: acme.acme.com"
- In reply to: Kevin D. Goodknecht Sr. [MVP]: "Re: Slow logon"
- Next in thread: Kevin D. Goodknecht Sr. [MVP]: "Re: Slow logon"
- Reply: Kevin D. Goodknecht Sr. [MVP]: "Re: Slow logon"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|