Re: XP Pro - Logging on to Domain issues
- From: "Bobby" <bobby@xxxxxxxxxxx>
- Date: Mon, 29 Aug 2005 10:27:32 -0400
Hi there,
I'm sorry I haven't responded sooner to those who were anxious to hear what
the result was. We're still trying a combination of things and taking into
consideration what was recommended. I will update you guys on the progress
and hopefully we get this sorted out since it's a new week.
Thanks for the help.
Regards,
Bobby
"Ron Lowe" <ron-msng@{d.e.l.e.t.e}lowe-family.me.uk> wrote in message
news:e7PZZWOqFHA.1024@xxxxxxxxxxxxxxxxxxxxxxx
> "Bobby" <bobby@xxxxxxxxxxx> wrote in message
> news:%23g7IN0LqFHA.712@xxxxxxxxxxxxxxxxxxxxxxx
> > Another thing discovered is when a different user tries to log on to
that
> > computer (that has access to the domain and can log on to any of the
other
> > computers already on the domain Win2K or not) it says the following
> > message
> > now "The system cannot log you on now because the domain DOMAIN is not
> > available."
> >
> > This makes it seem that XP Pro isn't seeing the domain??
> >
>
>
> As others have indicated, this is almost certainly a DNS configuration
> problem.
> Here's my usual lecture on the topic:
>
> XP differs from previous versions of windows in that it uses
> DNS as it's primary name resolution method for finding domain
> controllers:
>
>
> How Domain Controllers Are Located in Windows XP
> http://support.microsoft.com/default.aspx?scid=kb;en-us;314861
>
>
> If DNS is misconfigured, XP will spend a lot of time waiting for it to
> timeout before it tries using legacy NT4 sytle NetBIOS.
> ( Which may or may not work. )
>
>
> 1) Ensure that the XP clients are all configured to point to the local
> DNS server which hosts the AD domain. That will probably be the
> win2k server itself.
> They should NOT be pointing an an ISP's DNS server.
> An 'ipconfig /all' on the XP box should reveal ONLY the domain's
> DNS server.
>
>
> ( you should use the DHCP server to push out the local DNS server
> address. )
>
>
> 2) Ensure DNS server on win2k is configured to permit dynamic updates.
>
>
> 3) Ensure the win2k server points to itself as a DNS server.
>
>
> 4) For external ( internet ) name resolution, specify your ISP's DNS
server
> not on the clients, but in the 'forwarders' tab of the local win2k DNS
> server.
>
>
> On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints'
> tabs because they are greyed out, that is because there is a root zone
(".")
> present on the DNS server. You MUST delete this root zone to permit the
> server to forward unresolved queries to yout ISP or the root servers.
> Accept any nags etc, and let it delete any corresponding reverse lookuop
> zones if it asks.
>
>
> The following articles may assist you in setting up DNS correctly:
>
>
> Setting Up the Domain Name System for Active Directory
> http://support.microsoft.com/default.aspx?scid=kb;en-us;237675
> HOW TO: Configure DNS for Internet Access in Windows 2000
> http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
>
>
>
>
> --
> Best Regards
> Ron Lowe
> MVP - Windows Networking
>
>
.
- References:
- XP Pro - Logging on to Domain issues
- From: Bobby
- Re: XP Pro - Logging on to Domain issues
- From: Doug Sherman [MVP]
- Re: XP Pro - Logging on to Domain issues
- From: Bobby
- Re: XP Pro - Logging on to Domain issues
- From: Bobby
- Re: XP Pro - Logging on to Domain issues
- From: Ron Lowe
- XP Pro - Logging on to Domain issues
- Prev by Date: Re: Only the first line of the batch files executes, then ALL pcs
- Next by Date: Can access home network but not internet
- Previous by thread: Re: XP Pro - Logging on to Domain issues
- Next by thread: Network Cable Unplugged
- Index(es):
Relevant Pages
|
