Looking back at your original question - Have you
considered using a tiered WINS server set up??
This scenario divides up your WINS infrastructure into
levels with the top tier pushing down to the lower tier. The top tier
is where you have the DC's and "important Enterprise servers" registered while
the lower tier(s) are where you register the clients and the "organizationally
distinct" servers. The top tier servers do a push only replication to
the lower tier servers instead of a
push-pull.
It looks something like this:
Tier
1->
Enterprise WINS
/
\
/
\
Tier 2-> Company A
WINS Company B WINS
The advantage of using this setup is that Company A clients
see all of the Enterprise WINS records and the Company A records but not
any of the Company B records.
The disadvantage is that this is more complex, more
servers/services, and you are relying on WINS replication to get the
critical WINS DC records down to the Tier 2 servers.
_Stuart Fuller
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Monday, May 02, 2005 12:42 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Cross WINS Pollination
Consider the methodology of a large organization, a step
which is manual in nature could be overlooked by a single support person which
is what is to be avoided. But again, in the header of my mail, I did not
want to go into all of the reasons but rather if it could be
done.
-Jon
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Al Mulnick
Sent: Monday, May 02, 2005 2:41 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Cross WINS PollinationCertainly good feedback, but how often are you removing and updating records? This amounts to a filtered sync in my mind. I understand why you want to do it now, but I'm not sure I agree with the approach to make it semi-automatic. At least, I don't think I understand the amount of updates and number of possible records. I'm asking if it's worth it to even automate it vs. just manually doing this due to infrequent changes (this is just for dc and servers).And the conversation is academic. I'm just trying to figure out where to file this type of usage later.Al
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe
Sent: Monday, May 02, 2005 12:43 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Cross WINS PollinationIf you have a large WINS architecture you are pushing the records into I would prefer the dynamic insert than the static insert myself. Static records can be a pain to remove from a large WINS architecture or at least they were in the past the few times I tried to clean some up.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Al Mulnick
Sent: Monday, May 02, 2005 11:54 AM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Cross WINS PollinationHmm.... I see what you're after, but that's a funky place to be to say the least.I would *think* that your DC's and servers would be static enough that you *could* manually enter those records into the WINS systems on the respective sites. I would also *hope* that WINS is not required for that, but if it is, you would have to either script that manual version as Joe described (you could build a list of serrvers and DC's since it's not highly volatile right?) and run this on a regular basis, or you could read the db in the target domain and push that to others. There are permissions issues as Joe mentioned, but shouldn't be too terribly difficult to workaround that.Thanks for assuaging my curiousity and good luck with that :)Al
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Monday, May 02, 2005 10:43 AM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Cross WINS PollinationIf you had two distinct organizations and did not want to replicate each other's WINS database information that would be first reason. However, what if both organizations wanted to use a 'shared domain' model. You can accomplish this by having one set of DC's and Servers register to one set of WINS via normal processes and then create a static entry on the second set of WINS servers. The problem with this model is it isn't autonomous to changes. So if I decided to add a new server or DC, one side will automatically get the updates, but the other has to manually be changed. What would be nice if I could run a command on all servers to refresh a entries at a timed interval against the disjointed WINS server(s).
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Al Mulnick
Sent: Monday, May 02, 2005 10:08 AM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Cross WINS PollinationJust for fun, why would you want to do that?? I know you didn't want to get into specifics, but I'm trying to rationalize or otherwise apply that concept in a real-world situation and I am having some troubles thinking of reasons why I would want to do such a thing.Just curious mostly.Al
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe
Sent: Friday, April 29, 2005 1:26 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Cross WINS PollinationYou would most likely do this netsh using the wins portion and doing an add name specifying a rectype=1.That will require admin rights.An alternate method would be to write an app that does NBN registrations and you could make this a service that runs on any machines you need to do this from and it wouldn't require any special permissions at all, in fact, you don't even need to be authenticated. Everything you need to do that you can find in the SAMBA source or by following the RFCs for NBN.joe
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Friday, April 29, 2005 12:18 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Cross WINS Pollination
Without getting to the specifics we have a need to register WINS entries to a non listed WINS server.
For example, if I have Domain Controller or Server A with the following IP stack info:
168.120.2.10 - Host
168.140.140.30 - WINS1
168.140.140.31 - WINS2
140.110.12.20 - DNS1
140.110.12.21 - DNS2By performing an NBTSTAT -RR, I will trigger a registration to the two WINS servers above.
What if I wanted to register to an alternate WINS server? Let's say I need to create x00,x03,x20 host info to a different WINS server called WINS3, which is not listed in the above NIC bindings - e.g. 220.166.121.2.
How can I recreate a 00,03,20 and a 1b,1c record (domain) if I :
A- DO NOT want to use this WINS3 server in the replication topology of WINS1 and 2
B- DO NOT use it for look ups on that hosting server
C- DO NOT want static addresses in WINS3This would effectively allow another group of clients to find information in a disjoined structure.
Many thanks
Jon
