Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Chris Davis (chris.davisCOMPUTERJOBS.COM)
Date: Tue Mar 20 2001 - 12:41:40 CST
It sounds like your WINS replication might be configured to go in only one
direction (clients from domain A are added to domain B's browse list, but
not vice versa). Ensure that replication is configured for both directions.
I believe in order to do this, you must create two instances of replication.
Also, you know, Windows 2000 uses DNS to resolve names before it uses WINS,
so it might actually be a DNS issue if your clients are 2000 boxes.
Upgrade Your Future
From: Magus Ba'al [mailto:magusbaalMINDSPRING.COM]
Sent: Sunday, March 18, 2001 9:23 PM
Subject: WINS and browsing problem
I'm running into a problem with WINS and browsing Network Neighborhood. I
have 2 seperate Windows domains on either side of a WAN. Both WINS servers
are Win2K Server. They both replicate to each other just fine. The problem
is that computers on <domain-a> can't see <domain-b> in Network
Neighborhood. But the computers on <domain-b> can see <domain-a> just fine.
Firewall rules are perfectly fine. I've been beating my head for the last
few days trying to figure this problem out. Both servers are setup exactly
the same, but it's only working on one side.
Here's what I've tried so far:
Setting static entries in WINS for the other Domain Master
Importing LMHOSTS into WINS (pretty much the above step)
Making sure the box has all the latest updates
Wiping and reinstalling Win2K Server on the WINS server
None of those have seemed to worked. Although a few things I did managed to
bring up <domain-b> in Network Neighborhood...
Logging into a machine on <domain-a> with an account from <domain-b> and
<domain-b> comes up in the Network Neighborhood (login is possible because
of the 2way trust :)
Setting the Primary WINS to be the WINS on the <domain-b> side of the WAN
causes <domain-b> to pop up in Network Neighborhood.
I don't want to cause unneccesary traffic on the WAN by leaving the Primary
WINS set to the <domain-b> WINS, or leaving the other user with the ability
to login. Also this seems to be more of a temp fix than a perm fix (but
since I don't reboot <domain-a> WINS, it'll work for now). Any ideas, tips,
or pointers would be greatly appreciated.
"Failure is not an option, it comes pre-installed with your Windoze
"He who fights with monsters should look to it that he himself does not
become a monster...when you gaze long into the abyss the abyss also gazes
into you." -Friedrich Nietzsche
"Time is dead...I stabbed him in the eye with a fork." -Poxin