From: Larson, Chris (Contractor) (Chris.Larson@xxxxxx)
Date: Mon Jan 07 2002 - 14:05:38 GMT-3
I have 2 workstations running IPX with the IPX client. So when I click the
nethood I can see the other machine.
If you look at the configs I posted I believe type 20 propogation is enabled
on the interfaces.
Anyway, I seem to remember back in the day when I worked a lot more on the
lan and server side that if you have NWlink and netbui installed on a
Microsoft box that netbui will be carried in IPX anyway so that type 20
really isn't needed on the routers as the netbios names are carried inside
IPX. Similiar to the fact that if you only run IP on a Windows box you can
still attatch to a shared drive on a peer across the wan (with name
resolution) as the Netbui is carried inside the packet and netbui is what is
used to open the session, connect to the share etc. etc. The same holds
true for IPX if your running IPX on yer windows and the IPX file sharing.
At any rate, blocking IPX corrected the issue and that is all I wanted so I
could be sure my netbios filters through DLSW were working.
-----Original Message-----
From: tom cheung [mailto:tkc9789@hotmail.com]
Sent: Monday, January 07, 2002 11:29 AM
To: Chris.Larson@ed.gov; labccie@yahoo.com; clarson52@home.com;
ccielab@groupstudy.com
Subject: RE: DLSW netbios CCBOOT 3
But IPX does not transport Netbios by default. I wonder how do you see
Netbios hosts with IPX only?
>From: "Larson, Chris (Contractor)" <Chris.Larson@ed.gov>
>To: 'CCIE Lab' <labccie@yahoo.com>, Chris Larson <clarson52@home.com>, tom
>cheung <tkc9789@hotmail.com>, ccielab@groupstudy.com
>Subject: RE: DLSW netbios CCBOOT 3
>Date: Mon, 7 Jan 2002 11:16:34 -0500
>
>No, I was running IPX on the same interfaces that I was running dlsw and on
>the machines so even though dlsw was blocking, IPX was was still routing
>from one machine through the lab to the other. If you run 2 protocols on an
>interface like IPX and IP they run independant of each other. So even if I
>took IP and dlsw off these interfaces I would still route IPX between the
>machines.
>
>
>
>
>-----Original Message-----
>From: CCIE Lab [mailto:labccie@yahoo.com]
>Sent: Monday, January 07, 2002 2:34 AM
>To: Chris Larson; tom cheung; ccielab@groupstudy.com
>Subject: Re: DLSW netbios CCBOOT 3
>
>
>IPX shouldn't transport across over DLSw+, should it?
>
>--- Chris Larson <clarson52@home.com> wrote:
> > ooops.
> > I think I found the problem. It was still finding
> > the netbios machines
> > through IPX. I filtered IPX and it is working
> > properly now.
> >
> > Thank you.
> >
> >
> >
> > ----- Original Message -----
> > From: "tom cheung" <tkc9789@hotmail.com>
> > To: <clarson52@home.com>; <ccielab@groupstudy.com>
> > Sent: Sunday, January 06, 2002 1:44 PM
> > Subject: Re: DLSW netbios CCBOOT 3
> >
> >
> > > This is normal. You'll still see the netbios name
> > in the reachability
> > cache
> > > but it will be filtered when a connection is
> > attempted. You should be able
> > > to observe this with dlsw debug turned on.
> > >
> > >
> > > >From: "Chris Larson" <clarson52@home.com>
> > > >Reply-To: "Chris Larson" <clarson52@home.com>
> > > >To: <ccielab@groupstudy.com>
> > > >Subject: DLSW netbios CCBOOT 3
> > > >Date: Sun, 6 Jan 2002 13:10:10 -0500
> > > >
> > > >I am working off the ccboot lab 3. I have setup
> > my netbios access-list
> > > >excpet
> > > >I am using LAB1 instead of CCIELAB as I have a
> > real station called lab 1
> > > >off
> > > >of R3 ethernet. (My r3 is ethernet instead of
> > Token and my R4 is token
> > > >instead
> > > >of ether).
> > > >I have gone as far as creating a netbios access
> > list that is a deny * on
> > > >BOTH
> > > >routers but my netbios names stil show up ???.
> > The config is posted
> > below.
> > > >Can
> > > >someone enlighten me??
> > > >
> > > >Osing ios 12.07t Etnerprise IPSEC 56
> > > >
> > > >
> > > >
> > > >hostname R3
> > > >!
> > > >netbios access-list host r3 deny LAB1
> > > >netbios access-list host r3 deny *
> > > >!
> > > >memory-size iomem 20
> > > >clock timezone eastern -5
> > > >ip subnet-zero
> > > >no ip domain-lookup
> > > >!
> > > >ipx routing 0003.0003.0003
> > > >!
> > > >dlsw local-peer peer-id 137.20.13.3
> > > >dlsw remote-peer 0 tcp 137.20.20.1
> > host-netbios-out r3
> > > >dlsw remote-peer 0 tcp 137.20.23.4
> > lsap-output-list 201 host-netbios-out
> > r3
> > > >dlsw bridge-group 1
> > > >!
> > > >
> > > >interface FastEthernet0/0
> > > > ip address 137.20.13.3 255.255.255.0
> > > > no ip directed-broadcast
> > > > ipx network 310
> > > > ipx type-20-propagation
> > > > bridge-group 1
> > > >
> > > >
> > > >hostname R4
> > > >!
> > > >netbios access-list host r4 deny *
> > > >!
> > > >ip subnet-zero
> > > >no ip domain-lookup
> > > >ipx routing 0004.0004.0004
> > > >!
> > > >!
> > > >!
> > > >source-bridge ring-group 2000
> > > >dlsw local-peer peer-id 137.20.23.4
> > > >dlsw remote-peer 0 tcp 137.20.20.1
> > host-netbios-out r4
> > > >dlsw remote-peer 0 tcp 137.20.13.3
> > lsap-output-list 201 host-netbios-out
> > r4
> > > >!
> > > >interface TokenRing0
> > > > ip address 137.20.23.4 255.255.255.0
> > > > no ip directed-broadcast
> > > > ipx network 400
> > > > ipx type-20-propagation
> > > > ring-speed 16
> > > > source-bridge 1 1 2000
> > > > source-bridge spanning
> > > >!
> > >
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:18 GMT-3