All of lore.kernel.org
 help / color / mirror / Atom feed
From: "glynn" <glynn@itextron.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Help with gre tunneling
Date: Wed, 30 Jan 2002 08:43:22 +0000	[thread overview]
Message-ID: <marc-lartc-101237929017539@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101195228202181@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 3205 bytes --]

Do i really need to setup wins server in both sides? and if i configure one of my windows 98 pc how do make it as a push and pull replication? and how about nbt node type 8? do you think if i set up dns server it will work? what should be the best and easy way to have a name resolution on both ends of the tunnel?


Best Regards,
Glynn

----- Original Message ----- 
  From: Greg Scott 
  To: 'glynn' ; lartc@mailman.ds9a.nl 
  Sent: Friday, January 25, 2002 8:10 PM
  Subject: RE: [LARTC] Help with gre tunneling


  The short answer would be yes, but there are lots and lots of details.  

  Now that your GRE tunnel is up and running, switch your thinking to
  look at it from Windows' point of view.  From Windows' point of view,
  the GRE tunnel is really a router.  So you have LAN A connected to
  a router, across a WAN, to LAN B.  Your Windows PCs have no
  clue that there is a GRE tunnel in-between.  All they know is, their
  default gateway is the internal IP address of the firewall/router you
  set up.  Well, maybe not their default gateway, but at least they 
  have a route to the LAN on the other side of the tunnel.

  So what do we need with Windows so that PCs in LAN A can
  browse (Network Neighborhood) shares offered by computers in
  LAN B?  Assuming Windows 9x, we need a way for NetBIOS name 
  resolution that doesn't depend on broadcasts, so that means you'll 
  need a WINS server in both LAN A and LAN B.  You'll want to set 
  up the WINS servers as push/pull replication partners so they both 
  have up to date copies of which systems are where.  And you'll need
  to set up your PCs as NBT node type 8 (I think).  This is the hybrid,
  where PCs first try to resolve names by asking a WINs server and then
  try a broadcast if that doesn't work.  

  You could also use local lmhosts files for NetBIOS name resolution,
  but let's not even go there.

  If you have a Win2000 domain and all Win2000 clients, then the rules
  are different.  In this case, you'll need DNS servers instead of WINS
  servers.  

  Conceptually, the point is, you need some way to do name resolution
  on both ends of your tunnel to make this work.  

  You will want to set up some kind of Win NT or Win 2000 domain 
  structure that makes sense, or you will want some kind of 
  workgroup structure that makes sense.  So let's say the PCs in
  LAN A are all members of a workgroup named LANAWG.  If you
  make a PC in LAN B a member of the LANAWG workgroup, and
  you have name resolution that works, then that LAN B PC should
  be able to browse its Network Neighborhood and see the shares
  offered by PCs in the LANAWG workgroup, no matter which side
  of the tunnel they are on.

  This all assumes that the Windows PCs do their jobs properly.

  - Greg Scott


    -----Original Message-----
    From: glynn [mailto:glynn@itextron.com]
    Sent: Friday, January 25, 2002 4:07 AM
    To: lartc@mailman.ds9a.nl
    Subject: [LARTC] Help with gre tunneling


    Hello everyone. is it possible to browse the network neigborhood if i tunnel to a remote site ? if its possible how? 



    Best regards,
    Glynn

[-- Attachment #2: Type: text/html, Size: 10208 bytes --]

  parent reply	other threads:[~2002-01-30  8:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25  9:51 [LARTC] Help with gre tunneling glynn
2002-01-25 11:59 ` Greg Scott
2002-01-30  8:43 ` glynn [this message]
2002-01-30 12:20 ` Greg Scott
2002-02-13  2:25 ` [LARTC] Help with GRE Tunneling Glynn S. Condez
2002-02-13  7:59 ` bert hubert
2002-02-14  1:20 ` Glynn S. Condez

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-101237929017539@msgid-missing \
    --to=glynn@itextron.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.