[c-nsp] HDLC or PPP for layer 2 encapsulation?

[Joseph Jackson]

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net 
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Larry Smith
> Sent: Thursday, March 02, 2006 10:21 AM
> To: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] HDLC or PPP for layer 2 encapsulation?
> 
> On Thursday 02 March 2006 12:01, Joseph Jackson wrote:
> > > -----Original Message-----
> > > From: cisco-nsp-bounces at puck.nether.net 
> > > [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Dave Lim
> > > Sent: Thursday, March 02, 2006 2:45 AM
> > > To: cisco-nsp at puck.nether.net
> > > Subject: [c-nsp] HDLC or PPP for layer 2 encapsulation?
> > >
> > > Bear with me guys. I am more of a PIX and switching guy 
> and have not 
> > > really done such implementation before.
> > >
> > > I am configuring 2 Cisco routers for a point to point connection.
> > > Circuit will be provided by the telco. Am wondering about the
> > > layer2 encapsulation between the 2 Cisco 1841 router with WIC-1T 
> > > module using
> > > V.35 cables.
> > >
> > >  I am wondering should I use HDLC or PPP for the layer 2 
> > > encapsulation. HDLC is the default encapsulation used by Cisco 
> > > Routers right? I understand that HDLC encapsulation 
> doesnt support 
> > > asynchronous lines which goes to say that if both circuits are 
> > > operating on different timing, the line connection will be down.
> > >
> > >  With PPP, it supports both synchronous and asynchronous 
> connection.
> > > So which means that if the timing are different, the line 
> will still 
> > > be up. And PPP supports PAP and CHAP for authentication.
> > >
> > > And on another note, how do I forward NetBIOS and WINS 
> broadcast on 
> > > cisco routers as they have a domain which is on NT 
> servers they have 
> > > to access across the point to point leased line.
> >
> > You are correct HDLC is the default.  We use PPP because it 
> is an open 
> > standard and if For any reason we have to replace a router with a 
> > non-cisco at one end we don't have to configure the other router.
> > As for the NetBIOS stuff as long as you have IP 
> connectivity between 
> > the too sites you won't have any issues With the communication of 
> > them.
> >
> 
> Hmmm, I was under the impression that pretty much all Netbios 
> communication was done as broadcast packets (ports 137, 138, 
> 139, and now 450 to the .255 network address) and that 
> broadcast packets are not transferred across 
> routers.   A wins server takes care of all this, but natively 
> I do not 
> believe that you will "see" the other network in standard 
> Windows Network without a wins server or something running 
> running that does this function???
>  

You are correct with out a domain controller or another machine acting
As a master browser you will not be able to see across subnets.  But in
any 
Domain setup the client machines will be able to see all of the other
machines within 
The domain.