Re: netbios equiv. of ipxripd
On Wed, 2 Jul 1997, Mario Olimpio de Menezes wrote:
> I've a Debian box configured (at least I think) as a server for 2
> subnets (it has 3 ether cards). The subnets are assigned reserved
> number (I've IP-masquerading working). Also, my DOS/Win3.x machines
> can access the Novell server transparently with ipxripd.
>
> Is there some similar daemon for netbios, so my win3.x machines can
> access a NT server in the backbone (connected with the 3rd card)?
> I can't also connect 2 machines on different subnets, because the
> netbios protocol isn't propagated to all cards.
> ---Win3.x-----Win3.x---------|
> | eth1 eth2
> Linux/Samba --------Internet------------
> | eth0 |
> ---Win3.x----Win3.x----------| |---NT server
> |
> |
> |--Novell servers
> |
first of all, i'd suggest (unless you really need your NT and Novell
servers to be accessible from the net) that you should put your servers
behind your linux firewall immediately, especially the NT server. There
are many well-known holes in NT which can be used to either gain access or
kill the machine. see http://ntsecurity.com/ and many other sites (do a
search on yahoo for "NT security" to get started)
Rule of thumb: if it doesn't need to be directly on the net, hide it
behind your firewall.
This may involve putting another ethernet card in your linux machine,
"eth3", which has only Linux machine and your router, (e.g. isdn router
box if you have one). If it's just a modem link, and/or the linux box is
your internet router then change the addresses on eth2 so that it is also
using a private (192.168, etc) network.
IMO, the only excuse for putting an NT box live on the internet is that it
is running a web server and has no other use, and no other data (including
login & passwords for other machines in the registry). Even then I think
that you'd be better off with a linux box as a web server - it'll run
faster, and be more capable....apache is infinitely better than IIS.
There's nothing that an NT web server can do that a Linux machine can't do
faster, safer, and better.
But to answer your question, you don't really need a routing daemon for
SMB. Just make sure that the LMHOSTS file contains the IP address of your
NT server and Win3.x clients or just setup the Linux machine as the browse
master (see man page and docs for nmbd). Then configure the Win3 and NT
machines to use the Linux machine as WINS server.
Craig
--
craig sanders
networking consultant Available for casual or contract
temporary autonomous zone system administration tasks.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: