Re: WINS and DNS issue



--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

"Sambo" <Sambo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:158143B9-9C6C-4EA8-91B3-D706567EF9E7@xxxxxxxxxxxxxxxx
> Herb,
>
> Thanks for the reply.
>
> A few things: -
>
> Do they have their DNS name configured in the SYSTEM CONTROL
>> panel? (Don't depend on trying to override this on the NIC, but rather
>> set the System computer name properties.)
>>
>> Make sure they use ONLY the INTERNAL DNS (don't try to mix
>> the ISPs DNS server.)
>
> They do have their names configured int he system control panel, the
> settings on the NIC are untouched (as you say they are configured
> correctly
> for most instances by default). What I failed to mention earlier was
> that
> we also have a single label domain name which really confounds our
> miseries
> further!!

Yes, and especially with DYNANIC registration.

Single Label domain zone names are a problem, Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]

> I have thought about tackling this and have downloaded MS KBs on
> the subject of domain renaming but wouldnt fancy trying it without some
> consultation on the likelyhood of it screwing up our network completely.
> Have you got first hand experience of attempting this?

You cannot rename a Win2000 domain (and can only rename a Win2003
under certain special cases.)

>> Fine. Maybe not best use of your time. Is there just one WINS
>> Server? Usually the entries only get left (after cleanup) if you have
>> more than one WINS server (or had one that disappeared.)
>
> There used to be a different WINS server on the network before a new DC
> was
> installed 2 years ago. The old DC was demoted and is now a member server.
> WINS is no longer configured on this server.

A missing WINS server may "Own" some of the records which will
therefore never be scavenged (the owning server does that) so you
can continue to take ownership and delete the abandoned entries manually.

For newer entries the automatic expiration and scavenging of records may
be adjusted but then should JUST WORK.

> Replication of anything (can you
> replicate WINS like DNS?) does not take place on our network, are we being
> niave thinking that if DNS isnt functioning properly then we dont really
> need
> to have a back up system in place?

"isn't functioning properly" you NEED a backup system in place.

If you care about your network you will have at least 2 DCs, 2 DNS
servers, 2 WINS servers (they might all be on the same pair of machines.)

WINS servers can (and should) replicate but must be setup manually to do
this
(by the admins).

DNS must also (except for AD DNS) but the creation of the ZONES on
the DNS server pretty much forces you to do that (walks you through the
process of having Secondaries pull from MASTER.)

> I dont live in the US, im here in sunny Britain but I would like to take
> you
> up on your offer, your obviously very enthusiastic about your work so your
> knowledge will be invaluable to me. Many thanks for the offer
>
> Upon further investigation, it seems that only 2000 clients are
> registering
> in DNS, XP clients down seem to (see example below)
>
> Netdiag on the DC: -

RUNNING DCDIAG on DCs is BETTER. Us NETDiag mainly for NON-DCs

But you have at least one issue with DNS there:

> DNS test . . . . . . . . . . . . . : Passed
> [WARNING] Cannot find a primary authoritative DNS server for the
> name
> 'BQR1.rougemont.'. [RCODE_SERVER_FAILURE]
> The name 'BQR1.rougemont.' may not be registered in DNS.

Chances are you DCs are not all properly registered with DNS.

Deal with the KB articles about single lable DNS.

Make sure the DNS zone is DYNAMIC.

Then run DCDiag /fix

The following was in one or more of my earlier messages (along
with the info about single label DNS):

--
DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)

netdiag /fix

....or maybe:

dcdiag /fix

(Win2003 can do this from Support tools):
nltest /dsregdns /server:DC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.


.

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: How to rebuild a single AD... Please Help...
    ... Replicate from IRDC01 and Replciate to IRDC01 ... The kerberos client received a KRB_AP_ERR_MODIFIED error from the server ... I have added a new dc now, made it a gc and dns and have transferred the ... Bot DCs will be used by all machines, make sure that the machines have ...
    (microsoft.public.windows.server.active_directory)
Loading