From: Kyle Galusha (kgalusha@xxxxxxxxx)
Date: Fri Sep 15 2000 - 20:12:57 GMT-3
Looks right to me. Did you doublecheck case of the hostname TOKEN2. What doe
s "sho dlsw reach" on the 2600 with PC1. My experience is that reachability of
host is exchanged during the capabilities exchange (after the peer sessions ar
e set up), but the host will not be reachable from PC1 if you actually try to g
et into files on PC2 because of your netbios host filter. Did you try looking
at files on PC2 (after setting up file sharing. Can anyone else confirm my e
xperience.
Thanks,
Kyle
At 05:50 PM 9/15/2000 +0000, you wrote:
>I'm having a little trouble filtering netbios traffic in a DLSW environment,
>or maybe my understanding of how it works is incorrect...Here's the
>scenario:
>
>PC1---TokenRing---2600---Ethernet----2600----TokenRing-----PC@
>
>PC1 has the netebios name "TOKEN1" and PC2 is "TOKEN2"
>On the 2600 that shares a ring with PC1, my configuration is as follows:
>
>
>netbios access-list host ccie deny TOKEN2
>netbios access-list host ccie permit *
>source-bridge ring-group 10
>dlsw local-peer peer-id 10.1.1.1
>dlsw remote-peer 0 tcp 10.1.1.2 host-netbios-out ccie
>
>interface tokenring 0/0
> source-bridge spanning
> source-bridge 1 1 10
>
>My understanding is that this should prevent the PCs from finding each other
>via netbios, although my understanding could be the flaw in this scenario.
>But, when I look in network neighborhood, TOKEN2 shows up on TOKEN1. Any
>help with this would be greatly appreciated....Jack Heney
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:56 GMT-3