Re: Correct DNS / WINS configuration for Domain members


"DustWolf" <jure.sah@xxxxxx> wrote in message
news:1169467192.100773.193600@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Herb Martin je napisal:
I am thinking this is a client / server configuration problem.

Well, it is either a client or a server configuration problem, unless
there is an intermediary firewall causing the problems.

Small network. Cca 50 computers. One firewall / gateway for the whole
network.

The current configuration on the clients is all
defaults (e.g. nothing checked in the DNS area and all set to DHCP).

You might want the DHCP to do the registration for the DHCP
serviced clients.

Meaning?

Meaning set the DHCP server to register your client machines - use
the DNS tab of the DHCP server properties.

What exactly is WINS?

WINS is a "NetBIOS to IP resolution server", similar to DNS but
WINS is for NetBIOS names while DNS is for "Internet" (technically
"DNS") names.

But workstations use both anyway. Using anything that isn't strictly
Microsoft to find a computer will result in a DNS lookup, including our
AV managment, security checking software and remote desktop. In other
words, we don't give a damn if NetBIOS doesn't work... It might even be
considered a security feature if it doesn't. </sarcasm>

You really don't want browsing to work? (Or any of the other things still
dependent on NetBIOS?)

The resoution fail over to DNS is NOT sufficient for such things. They
require the special NetBIOS record types.

Chances are you sarcasm is misplaced and originates in from lack of
knowledge.

Is it optional or should it always be configured?

NetBIOS is TECHNICALLY optional but practically necessary* for
most real world Windows networks -- no matter what you may have
heard about the 'death of NetBIOS.

WINS is a PRACTICAL necessity for routed networks, i.e., having
mulitiple broadcast domains, that use NetBIOS.

Ours is a switched networks and most of the switches only support IP
(e.g. no native NetBIOS). Regardless, I'll take the advice.

ALL of your internal machines MUST use STRICTLY the DNS
server set which resolve this dynamic zone supporting your AD,
i.e. they must not mix another DNS server such as the ISP in on
the NIC->IP properties (nor from DHCP.)

They do. All have default configuration and all get their information
from the DHCP (except exceptions where the DNS servers are specified
manually and those are correctly configured as well).

You asked what was correct.

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)


.

Relevant Pages

  • Re: Never Saw Something This Weird
    ... NetBIOS name "OLD". ... The most common reasons for redefining UPN suffixes are ... it's DNS name. ... I'm told was the domain that was created on the 2000 server when AD ...
    (microsoft.public.win2000.active_directory)
  • Re: A g;lobal catalog cannot be located to retrieve the icons from the member list
    ... Please post your Netbios domain name, the AD domain name and the DNS ... Server has eveng logging set to no events, and I am unable to change ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)
  • Re: Browsing Subnets
    ... Another server at the 2nd site also provides the DNS. ... Name resolution possibly (although inefficiently for NetBIOS names) ...
    (microsoft.public.win2000.dns)
  • Re: WHY WINS
    ... uses Netbios names. ... This is not really about DNS and WINS servers, ... does Network Neighborhood depend on the computer browser service ... WINS server must exist fot the DNS server to integrate with (which is why ...
    (microsoft.public.windows.server.networking)
  • Re: Browsing Subnets
    ... [phone number on web site] ... Another server at the 2nd site also provides the DNS. ... Name resolution possibly (although inefficiently for NetBIOS names) ...
    (microsoft.public.win2000.dns)