Re: Client Machine cannot see Active Directory
- From: Derek Schauland <DerekSchauland@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 9 Sep 2005 11:20:02 -0700
Thanks Ace.
I looked through the DNS Zones that are set up and this pc (invoicing01)
points to xxx.xxx.1.133 anywhere in DNS that it is referenced. I also
checked the properties for TCP/IP and set the local DNS server as the only
one to be used...
I ran netdiag on invoicing01 and got a [Warning] failed to query SPN
registration on DC 'dc fqdn' might this have something to do with the problem?
Also when trying to browse the network in net neighborhood, Active Directory
doesnt appear in Entire Network.. it just shows Windows Network. And trying
to access the DFS using \\domain produces an error about being unavailable,
but if I try \\domain\dfsrootname the window pops right up...
Sounds like it is almost working but not quite... any further ideas?
thanks
Derek
"Ace Fekay [MVP]" wrote:
> In news:EE68706F-C759-4596-9D56-EDB11CC22C81@xxxxxxxxxxxxx,
> Derek Schauland <DerekSchauland@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post,
> which I then commented about below:
> > I have one client that is unable to see Active Directory or access
> > shares via \\servername for our new NAS
> >
> > but mapped drives work ok and authentication is ok.
> >
> > I can see the client using both the FQDN and the Netbios name using
> > NSLookup from any PC on the network, but from that PC I get an error
> > that the domain doesnt exist.
> >
> > I have removed the PC from the domain, cleared the DNS cache with
> > ipconfig/flushdns, deleted the computer record in AD users and
> > computers, and readded it and got the same result. I am not sure
> > what I should try next.
> >
> > I have not seen this issue with any other clients.
> >
> > Any assistance would be greatly appreciated
> >
> > thanks
> >
> > Derek
>
> Make absolutely sure all of your machines (DCs, clients and member servers)
> only use the internal DNS and not an ISP's or any other outside DNS server
> in their IP properties. Also make sure the SRV records exist under the zone.
>
> If not sure of what I mean by the above paragraph, please post the following
> information to help you out:
>
> 1. Unedited ipconfig /all of a DC and of one of your client machines.
> 2. The exact zone name spellng in DNS and whether updates are allowed on the
> zone.
> 3. The AD DNS domain name as it shows up in ADUC.
> 4. If the SRV records exist under your zone.
>
> --
> Regards,
> Ace
>
> If this post is viewed at a non-Microsoft community website, and you were to
> respond to it through that community's website, I may not see your reply.
> Therefore, please direct all replies ONLY to the Microsoft public newsgroup
> this thread originated in so all can benefit.
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft Windows MVP - Windows Server - Directory Services
> Infinite Diversities in Infinite Combinations.
> =================================
>
>
>
.
- Follow-Ups:
- Re: Client Machine cannot see Active Directory
- From: Ace Fekay [MVP]
- Re: Client Machine cannot see Active Directory
- References:
- Client Machine cannot see Active Directory
- From: Derek Schauland
- Re: Client Machine cannot see Active Directory
- From: Ace Fekay [MVP]
- Client Machine cannot see Active Directory
- Prev by Date: Re: Client Machine cannot see Active Directory
- Next by Date: Re: trouble with delegating unlock rights
- Previous by thread: Re: Client Machine cannot see Active Directory
- Next by thread: Re: Client Machine cannot see Active Directory
- Index(es):
Relevant Pages
|
