From: Robert_Wang@xxxxxxxxxx
Date: Tue May 09 2000 - 16:19:39 GMT-3
First of all, on all the Microsoft PCs, turn off MS NetBUIE, and leave only
TCPIP protocol with Client for MS networks service under Network property. Onc
e
it's been set, and make sure no filters is turned on against NetBIOS, such as
"dlsw icannotreach sap F0".
When the DLSW peers are connected, you should see the your PC's netbios names
shown up under "show dlsw reach" database either in the Ethernet or TR side, an
d
you may browse the PCs of the other side under "network neighborhood".
Remember, NetBIOS is encapsulated in TCPIP during DLSW exchange process (just
like SNA sessions under "show dlsw circuit"). NetBUIE is a non-routed protocol
and will be bridged across if you have NetBUIE protocol in your PCs.
- Robert -
"Erik Belz" <EBELZ@mecnet.com> on 05/08/2000 02:34:40 PM
Please respond to "Erik Belz" <EBELZ@mecnet.com>
To: ccielab@groupstudy.com
cc: (bcc: Robert Wang/Vendors/Toyota)
Subject: NetBIOS Dlsw
Ok,
I'm tying to test dlsw source-route transparent over ip cloud to ethernet
transparent.
What exactly has to be done on the microsoft side?? Will I see the NetBIOS name
s
int the reachability cache??
I have two laptops on both ends. one on token ring the other on ethernet..
any help is appreciated.
thanks,
Erik
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:28 GMT-3