From: Greg Scott <GregScott@InfraSupportEtc.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Yay!
Date: Mon, 18 Mar 2002 18:38:21 +0000 [thread overview]
Message-ID: <marc-lartc-101647540131992@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101646480629627@msgid-missing>
Now that your VPN is working, you really have two LANs separated by routers.
So the issues with browse lists etc. are the same as in any other WAN
situation and really not related to Linx Advanced Routing. (But who am I to
make that call - I'm just a skinny bald guy from Minnesota!)
NetBIOS broadcast name resolution does you no good, so you'll either need a
WINS server or local lmhosts files. That's for NetBIOS name resolution.
For DNS name resolution, you'll need a DNS server.
- Greg
-----Original Message-----
From: Patrick Dench [mailto:pat@acdisplays.com]
Sent: Monday, March 18, 2002 11:11 AM
To: lartc@mailman.ds9a.nl
Subject: [LARTC] Yay!
Looks like my GRE problems were due to ipchains. I went to IP Tables, and
it looks like it is working.
Next issue: name resolution.. Right now the only way I know my home PC is
connected is because I turned it on this morning. Is there anyway to
resolve PC names through the VPN? Specifically to make it possible to
browse another subnet via the Windoze 'network neighborhood'?
-Pat Dench
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-03-18 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 15:20 [LARTC] Yay! Patrick Dench
2002-03-18 18:38 ` Greg Scott [this message]
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=marc-lartc-101647540131992@msgid-missing \
--to=gregscott@infrasupportetc.com \
--cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.