From: "Andrew J. Meader" <ameader@corp.lcom.net>
To: Y Makki <bugzilla@sympatico.ca>
Cc: netfilter@lists.netfilter.org
Subject: Re: Windows file sharing over different subnets
Date: Thu, 27 Mar 2003 13:40:40 -0600 [thread overview]
Message-ID: <3E8353B8.5020502@corp.lcom.net> (raw)
In-Reply-To: 1048794050.1021.31.camel@psyche
If you don't want to run wins on your nt2k box then you should work with
the lmhosts file. lmhosts.sam is a good reference for what you are
trying to do. You can use Samba to do some netbios forwarding but for
what you are doing that might be overkill. Read lmhosts.sam (on one of
the windows boxes.)
Andy
Y Makki wrote:
>Hi,
>
>I don't really need a wins server on the eth1 segment since there are no
>windows machines here except the file server, the eth2 segment has no
>servers at all.
>
>For testing I have set the FORWARD default policy to ACCEPT, and allow
>all incoming traffic from both eth1 and eth2.
>I also tried earlier to DNAT any 135:139 traffic coming from eth2 to the
>fileserver, which did not help. Ping works from segment to segment.
>
>Maybe there is a client or relay agent of some sort I could install on
>the linux gateway, I don't know.
>
next prev parent reply other threads:[~2003-03-27 19:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 19:08 Windows file sharing over different subnets Y Makki
2003-03-27 19:17 ` Andrew J. Meader
2003-03-27 19:40 ` Y Makki
2003-03-27 19:40 ` Andrew J. Meader [this message]
2003-03-27 21:25 ` Richard Doyle
-- strict thread matches above, loose matches on Subject: below --
2003-03-27 20:15 Daniel Chemko
2003-03-27 22:29 ` ymakki
[not found] <7C9884991ADAE0479C14F10C858BCDF5122DA7@alderaan.smgtec.com>
2003-03-29 7:31 ` Y Makki
2003-03-29 7:50 ` Raymond Leach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E8353B8.5020502@corp.lcom.net \
--to=ameader@corp.lcom.net \
--cc=bugzilla@sympatico.ca \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox