On Mon, Sep 03, 2001 at 01:46:01PM +0100, John P. Looney came forth with:
> On Fri, Aug 31, 2001 at 06:23:39PM +0100, Martin Feeney mentioned:
> > On Fri, 31 Aug 2001 17:57:03 John P. Looney wrote:
> > > Now, if I want to NAT say filesharing etc. - what ports do I need ? What
> > > are the others there for ?
> > Ports 137-139 should be enough. You probably don't even need all three as
> > one of them is probably broadcast only, so won't leave your subnet anyway.
>> I still don't see the NATted boxes in "network neighbourhood". Now, if
> the external IP on the NAT box is on my local network, will the broadcast
> be sent through anyway ? Or would I need to be doing proxy arp messing to
> see broadcasts propagated through the NAT box (so, make a network bridge,
> rather than NAT) ?
>you are a freak.
you can't send broadcast over nat... NAT by definition requires routing from
one subnet to another...
What you want is WINS, or for 2K, Active Directory.
Set all the windows machines to have one WINS server, and then you'll be
able to see them...
you should also run FreeS/WAN between the networks you want to connect, as
it makes things a lot easier and safer..
dBP dBBBBb | If you're looking at me to be an accountant
dBP | Then you will look but you will never see
dBP dBBBK' | If you're looking at me to start having babies
dBP dB' db | Then you can wish because I'm not here to fool around
dBBBBP dBBBBP' | Belle & Sebastian (Family Tree)
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!