Re: DLSW + NetBIOS problem

From: Rick Burts (burts@xxxxxxxxxxxxxx)
Date: Wed Sep 05 2001 - 14:07:42 GMT-3


   
Fred

It very much depends on how the PCs are configured. If the PCs are using
NBT (NetBIOS over TCP) then the traffic will not be transported by DLSw -
which is what you said (it was using routing logic to send packets).
If the PCs are configured to send NetBIOS via NetBEUI then DLSw will
transport between remote segments.

Rick

Rick Burts, CCSI CCIE 4615 burts@mentortech.com
Mentor Technologies 240-568-6500 ext 6652
133 National Business Parkway 240-568-6515 fax
Annapolis Junction, Md 20701

Chesapeake Network Solutions has now become Mentor Technologies.
Mentor Technologies is a certified Cisco Training Partner and also
a Cisco Professional Services partner.
We offer most of the Cisco training courses.
We also offer training in Checkpoint Firewall software and
Fore Systems (now Marconi) and MicroMuse.
We also provide network consulting services including
design, management, and problem solving.
We have 21 CCIEs on our staff.
We offer the breakthrough VLAB remote access technology for
access to practice configuration on real equipment.

On Wed, 5 Sep 2001, Fred Danson wrote:

> Hey Group,
>
> I'm trying to transport NetBIOS from a Windows 2000 PC to a Win98 PC through
a
> DLSW network. When I put the PCs on to the same ethernet segment, they are
> able to find eachother, but they are not able to find eachother through the
> DLSW network. Here's my setup
>
> PC1 ----- R8 --------- R7 ----- PC2
>
> PC1 is connected to R8 through ethernet.
> PC2 is connected to R7 through ethernet.
>
> R8 has an established DLSW connection to R7.
>
> r8#show dlsw peer
> Peers: state pkts_rx pkts_tx type drops ckts TCP
> uptime
> TCP 70.70.70.70 CONNECT 63 178 conf 0 0 0
> 00:30:1
>
> Here are my configs:
>
> R8-----------------------------------------------------
> dlsw local-peer peer-id 80.80.80.80 promiscuous
> dlsw remote-peer 0 tcp 70.70.70.70
> dlsw bridge-group 1
> !
> interface Ethernet0
> bridge-group 1
> !
> bridge 1 protocol ieee
>
> r8#show dlsw reach
> DLSw Local MAC address reachability cache list
> Mac Addr status Loc. port rif
> 0006.3a43.8ace FOUND LOCAL TBridge-001 --no rif--
>
> DLSw Remote MAC address reachability cache list
> Mac Addr status Loc. peer
> 0006.3a2f.8ab8 FOUND REMOTE 70.70.70.70(2065)
>
> DLSw Local NetBIOS Name reachability cache list
> NetBIOS Name status Loc. port rif
>
> DLSw Remote NetBIOS Name reachability cache list
> NetBIOS Name status Loc. peer
>
> R7---------------------------------------------------
> dlsw local-peer peer-id 70.70.70.70 promiscuous
> dlsw remote-peer 0 tcp 80.80.80.80
> dlsw bridge-group 1
> !
> interface FastEthernet0/0
> bridge-group 1
> !
> bridge 1 protocol ieee
>
> r7#show dlsw reach
> DLSw Local MAC address reachability cache list
> Mac Addr status Loc. port rif
> 0006.3a2f.8ab8 FOUND LOCAL TBridge-001 --no rif--
>
> DLSw Remote MAC address reachability cache list
> Mac Addr status Loc. peer
> 0006.3a43.8ace FOUND REMOTE 80.80.80.80(2065)
>
> DLSw Local NetBIOS Name reachability cache list
> NetBIOS Name status Loc. port rif
>
> DLSw Remote NetBIOS Name reachability cache list
> NetBIOS Name status Loc. peer
>
>
>
> I'm thinking that the NetBIOS traffic isn't being transported because it's
> being run over TCP/IP instead of NetBEUI. Has anyone else encountered this
> problem? Any Ideas?
>
> Fred
> **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:32:14 GMT-3