/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */
----- Original Message -----
From: Jesper Jensen <[EMAIL PROTECTED]>
To: Jose M. Sanchez <[EMAIL PROTECTED]>
Sent: Saturday, October 23, 1999 8:44 AM
Subject: Re: [Masq] Printing from behind a masq machine? Yes it works.
> >> Has any one ever gotten a windows machine to find a network printer
from
> >> behind a masquerading linux box? That is : the windows machine is
being
> >> masq-ed, not the printer. Windows can ping the printer, and I know the
> >> printer works. Linux prints to it just fine (which should surprise no
> >> one..), but windows can't find the printer in it's "network
> neighborhood",
> >> even if I explicitly state the printers IP.
> >>
> >This is normal.
> >
> >On local networks a machine is elected to be a "master browser" under
> >windows. This machine (Microshaft prefers NT boxes, duh) contains a list
> of
> >share which are available on you "LOCAL" lan.
> >
> >When two network "segments" are directly connected, your Winblows
machines
> >on your segment will only see your local computers in network
> neighborhood.
> >
> >In order to "see" those on the "other side" a multi-homed machine must be
> >set up as a WINS server.
>
A WINS server is ONLY used to allow two interconnected segments to see each
other...
If you have a setup like this...
LAN(a) ---------- [ Linux / WINS ] ------ LAN(b)
Then if Linux is set up as a WINS server then LAN(A) can see the shares on
LAN(B).
If you are going thru the internet... forget it. WINS, and MS Networking is
NOT designed to display SMB shares over the internet directly...
You CAN however let WINS know about another remote WINS machine.
So if you are running SAMBA at both ends (even NT does this) and designate
both to be WINS servers, it is possible to allow the two WINS servers to
exchange shares information to each other, about their respective local
machines... This permits the two to let Windows machines on each end see the
other end.
Like this...
LAN(a) ---- [Linux/Wins] --- [Router] --- Internet ---- [Router] ----
[Linux/Wins] ---- LAN(b).
Effectively the two WINS machines talk to each other and exchange info about
their local lans.
For this to work, samba would have to be installed at each end, and it must
be the browse master for the local lan.
Access also must be enabled for the IP's for "both sides" and they should be
able to authenticate against one another...
Ideally it would also be the local domain controller.
> Ok, nice, but which machine is it that has to be WINS server, the
> linux/firewall-machine? If so, how?
>
How: Samba.
> PS. Nice mail, not sent to me, but just what I needed.
>
-JMS
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES
UNSUBSCRIBING!
or email to [EMAIL PROTECTED]
PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
Please keep general linux/unix/pc/internet questions off the list.
