Re: WINS/DNS Migration
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Wed, 17 Jan 2007 16:52:01 -0600
"SLongxyzzy earthlink net>" <slr64<atdot> wrote in message
news:%23wjXqrmOHHA.3212@xxxxxxxxxxxxxxxxxxxxxxx
Need pointers. Not new to WINS/DNS in concept, but always held positions
where the Unix group took care of it.
Trying to decommission or old NT4 domain. Manager states there are still
things that rely on WINS for resolution so we need to migrate it to our
2003 AD, which currently only runs DNS. (2003 forest/domain functional
level).
Manager is correct. If you needed WINS under NT 4 you still do.
Browsing, Exchange, Clustering, (external) trusts all either require or may
require NetBIOS sometimes -- other minor things too.
When you need NetBIOS resolution across routers (multiple subnets) you
have a practical need for WINS Server(s).
EVERY machine -- especially DCs and other servers -- must also be set
as a "WINS client".
I plan to add WINS to our server where DNS is configured, and then migrate
the WINS info from the old NT4 domain.
Good plan.
Any tips and gotcha's I should be aware of.
If you have more than one WINS Server you need to manually set them
to replicate with at least one other WINS Server so there are no
disconnected
sets (of WINS Servers).
EVERY machine -- especially DCs and other servers -- must also be set
as a "WINS client". This isn't hard but must be done (use the WINS MMC.)
Also, I contend that we should do away with WINS and use DNS exclusively,
or
You are almost certainly wrong.
at least use WINS only for the services that explicitly require it.
You can't really do it "for some services" without making it available to
ALL MACHINES. (Similar to DNS except that ANY machine can
end up being Master Browser for a particular subnet etc.)
I don't want to migrate the entire WINS database to our new environment if
not necessary, but with my limited knowledge of it, and this company and
it's infrastructure being relatively new to me, this is what I plan to do
to be on the safe side.
Migration is probably not critical if you are willing to reboot or
re-register
each machine in the new database. BUT WinNT and Windows Server
WINS can replicate.
Many of the WINS entries were statically assigned, and
UGH. One of the big advantages of WINS has always been that it is
dynamic for registration by default.
BUT ALSO, this might imply YOUR company is running (MORE)
custom apps that use NetBIOS and therefore needed to register specific
manual records.
also don't clean themselves out, so I have no hope of knowing which ones
are necessary.
And this might mean moving all of the manual records you cannot identify.
I've gone the last ten years without using WINS, so I find it hard to
comprehend why we can't do without it here.
There is a practical need for NetBIOS resolution in all Windows networks.
You need WINS when you wish to resolve NetBIOS across routers.
Perhaps you ran single subnet networks or used LMHosts files?
(or you might have foregone browsing and other features.)
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
.
- Follow-Ups:
- Re: WINS/DNS Migration
- From: SLongxyzzy
- Re: WINS/DNS Migration
- From: SLongxyzzy
- Re: WINS/DNS Migration
- References:
- WINS/DNS Migration
- From: SLongxyzzy
- WINS/DNS Migration
- Prev by Date: Re: Another question on recursive queries
- Next by Date: Re: Basci question on iterative vs recursive queries
- Previous by thread: WINS/DNS Migration
- Next by thread: Re: WINS/DNS Migration
- Index(es):
Relevant Pages
|
