Re: Drive Mapping Issues in Win2K AD, DNS related?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Ace Fekay [MVP] (PleaseSubstituteMyActualFirstName&LastNameHere_at_hotmail.com)
Date: 08/05/04 

Date: Thu, 5 Aug 2004 08:02:53 -0400

In news:e5bf79ee.0408042035.306f439f@posting.google.com,
Dan <drivie@hotmail.com> made a post then I commented below
> Kevin,
>
> Thanks for the reply. We have tried connecting via NetBIOS name and
> by IP address but not by FQDN. DNS appears to resolve the host names
> correctly by NetBIOS name but I still receive the error saying that
> "no logon servers are available..."

This can depend on a coupel things:
1. What operating system are the clients?
2. If the clients are W2k or newer, then is DNS resolving and do the SRV
records exist? You said so far it does NOT resolve by FQDN, so there's a
huge hint that DNS is not setup correctly across your mutliple subnets.

If you can post this data below for us from a client and a server from both
subnets, that can give us a start in diagnosing this:
1. Unedited ipconfig /all
2. AD DNS domain name (as it shows in ADUC):
3. Zone names that exist on both DNS server in both subnets.

> We do not have WINS setup so we
> are unable to browse one child domain from the other but that's not a
> big deal for us. Would WINS help to resolve authentication issues?

That depends on what app is trying to authenticate. Active Directory for W2k
or newer clients use Kerberos, and Kerberos uses DNS, so no, WINS won't help
with Kerberos, but YES for backward level clients, such as Win98, WinME,
NT4, or DOS, etc.

If you need this Network neighborhood functionality along with the ability
for backward level clients, then you need WINS. I would follow Kevin's
advise on how to set it up. 

-- 
Regards,
Ace
Please direct all replies ONLY to the Microsoft public newsgroups
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
Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
-- 
=================================

Relevant Pages

  • Re: DNS query basics
    ... netBIOS disabled ... I suppose in my scenario DNS should be used to resolve names. ... if i ping xp by name with a trailing dot - it responds. ... it will use DirectSMB to resolve it. ...
    (microsoft.public.windows.server.dns)
  • Re: NS and domain A record affecting AD
    ... Clients are pointing to the local dc for both WINS and DNS, ... If the remote dc's are on a slow link you may not even get your gpo's ... If local clients can not resolve AD domain name to ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS-NetBios name resolution order
    ... it could help with slow access to shares but that depends on whether there is another problem other that the default name resolution ... You could setup a zone on your local DNS server, add A records for the local hosts and then use this DNS server on home LAN. ... You can add forwarders to the DNS server so the clients can resolve names out on the internet. ... >> of XP will attempt to resolve this name using Netbios. ...
    (microsoft.public.windows.server.networking)
  • Re: VPN Client Name Resolution
    ... Yes, the vpn/ras clients get a dhcp assigned ip address, ... dns address, etc. ... internal DNS server. ... They try to resolve the name to the external ...
    (microsoft.public.win2000.ras_routing)
  • Re: Drive Mapping Issues in Win2K AD, DNS related?
    ... We have tried connecting via NetBIOS name and ... DNS appears to resolve the host names ... If the clients are W2k or newer, then is DNS resolving and do the SRV ...
    (microsoft.public.win2000.active_directory)