You definitely DO NOT need a WINS server in every collision domain. I've
seen networks wherein there were 8 international sites connected with WAN
links, and all using a single WINS server at one of the sites, without
forwarding NetBios broadcasts. WINS is a direct TCP/IP service, not a
broadcast service. It is what you use if you DON'T want to have to rely on
broadcasts. When it comes to using multiple WINS servers, I'd only use one
per site, regardless of how many subnetworks there are at the site. For
clients that can't normally register with WINS (MACs and nix clients without
addons), a WINS proxy agent can be installed on any NT system in a subnet,
even a workstation, to communicate with WINS as a proxy for the non M$
client.

As long as the arrangements are kept fairly simple, it's hard to go wrong
with WINS.

Dave Shackelford
Teacher, writer, engineer

-----Original Message-----
From: Reckhard, Tobias [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 14, 2000 10:56 PM
To: '[EMAIL PROTECTED]'
Cc: '[EMAIL PROTECTED]'
Subject: RE: Workgroups through firewall


Network neighborhood in a workgroup environment is going to work on
broadcasts, so unless you forward those, you can't do it in a
workgroup environment. If you set up a domain and put an NT server on
each subnet, you can do it.

Isn't the use of a WINS server the solution here? If so, you could use Samba
instead of Windows NT. AFAIK you need a WINS server on every collision
domain if you don't forward (NetBIOS) broadcasts. By putting a WINS server
onto the gateway (the IPChains box), you could probably achieve this with
only one physical machine. Since it runs Linux, Samba seems to be the most
logical choice to me, but then again, I've never tried to get it to work
across subnets. I do know that our NT4 WINS servers cause us headaches quite
often, though... we'll be reinstalling our local machine as soon as we can
and see if that cures it..

HTH
Tobias


-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]

Reply via email to