Coming in on the tail end of this :)
-----Original Message-----
From: Roger Marquis [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 15, 2000 16:03
To: [EMAIL PROTECTED]
Subject: Re: Workgroups through firewall
Reckhard, Tobias [mailto:[EMAIL PROTECTED]] wrote:
>Isn't the use of a WINS server the solution here? If so, you could use
>Samba instead of Windows NT.
Samba is almost always a better choice that NT because of its reliability
and remote administration capabilities. I say "almost always" since there
are a couple of pre-requisites to running a Samba server: 1) you should
have someone available, either on staff or a consultant, who knows how to
setup and manage both Unix and Samba and, 2) the server should be securely
configured. They're typically not optimally configured out of the box (or
CD).
SAMBA can't handle the workload NT/W2K can though, at least in our
environment. We pull over 4GB of data a day of a SAMBA share at work, every
day. SAMBA crashes, once every 1-2 days. We moved the data to a less powered
W2K box. Not only does it not crash, it is measurably faster. The Unix guys
have explained the problem as having something to do with how Solaris/SAMBA
cache file system reads, or something to that degree (I am not a Unix fellow
:))
>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
Not too sure how you are defining collision domains, but WINS resolves layer
3 addresses, which sit well above collision domains. You don't need a WINS
server for every collision domain. If you did, you would need a WINS server
on every single switch port (since switch ports tend to define where
collision domains are)!! For that matter, you don't need a WINS server for
every broadcast domain either. Most companies I know of are collapsing down
to 2-10 WINS servers worldwide, due to the problems related to over
implementation of WINS in an enterprise.
Small correction for the newbies reading this list: Samba doesn't "run
Linux". Samba is an application. Linux is an OS. Samba runs on just
about every Unix OS including Linux. Also, Samba is just as easy setup
and manage under Solaris and FreeBSD as it is under Linux. The best OS
for your environment is probably the one your sysadmins or consultants are
most familiar with.
YMMV,
--
Roger Marquis
Roble Systems Consulting
http://www.roble.com/
-
[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.]
