Message-Id: <200511291950.jATJoh8w013574@smtp-vbr15.xs4all.nl>
In-Reply-To: <15647-70261@sneakemail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Date:  Tue, 29 Nov 2005 20:50:37 +0100 (CET)
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  "Frank Vos" <os2-wireless_users@2rosenthals.com>
To:  "os2-wireless_users@2rosenthals.com" <os2-wireless_users@2rosenthals.com>
Subject: [OS2Wireless] anyone have GenMac and NETBIOS/TCPIP working?

Hello Bob,
On Mon, 28 Nov 2005 21:22:08 -0800, Bob wrote:

>** Reply to message from "Chris Clayton clayton@ieee.org" on Sun, 27 Nov 2005
>21:05:35 -0700 (MST)
>
>> O.K. this is the problem I give a quick fix to below.  NetBIOS is a
>> broadcast protocol that polls the network to see who is on line and
>> what is available.  This was ok until networks with 100s of computers
>> were established.  This NetBIOS poling really slowed things down.  So
>> an extension was created called NetBIOS over TCP/IP that included an
>> NetBIOS name server to handle connection requests and a non broadcast
>> mode was established and, this is the biggie, connection caching was
>> included.  But to maintain compatibility, broadcast mode was included
>> as an option.  The NetBIOS over TCP/IP we use defaults to a
>> quasi-broadcast mode with caching enabled (In the M$ world this is
>> known as Microsoft Networking)  This is great for us small users since
>> we do not need to set up a NetBIOS name server.  However, the caching
>> part remember NetBIOS name and the associated mac address.  The problem
>> comes when a computer changes mac cards (i.e. goes from a wired nic to
>> a wifi nic ) but not NetBIOS names.  Unless told otherwise, the cache
>> is used first to resolve names, so when you look for a computer, the
>> system cryptically responds that your not there because your name
>> doesn't correspond to your mac address.
>
>Still trying to get "net use" to work.
>
>My original configuration was:
>
>IBM Gigabit Ethernet Adapter (OS/2).......
>   IBM TCP/IP
>   IBM OS/2 NETBIOS
>Generic PRISM Driver for PCMCIA/PLX cards.......
>   IBM TCP/IP
>   IBM OS/2 NETBIOS
>GenMac Wrapper Intel 2100 Wlan [8086:1043}.......
>   IBM TCP/IP
>   IBM OS/2 NETBIOS
>
>I changed all the IBM OS/2 NETBIOS to IBM OS/2 NETBIOS OVER TCP/IP.
>
>On the re-boot I got the message
>
>SYS1719: The file C:\IBMLAN\NETPROG\NETWKSTA.200 specified in the IFS statement
>on line 61 of the CONFIG.SYS file does not contain a valid device driver or
>file system driver.  Line 61 is ignored.
>
>Of course "net use" does not work because it requires NETWKSTA.200.
Looks like the two configuration files, IBMLAN.INI and PROTOCOL.INI, are not in sync. 
The problem with MPTN is that changes to the adapters and the protocols bound to them
are only made to PROTOCOL.INI and not in IBMLAN.INI. This is why you get the SYS1719
error.

To prevent this from happening after this kind of changes is to run PROTOFIX.CMD, 
this program included in eCS (CD1) checks both files and changes IBMLAN.INI if something
is wrong.

Kind regards,
Frank

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

To unsubscribe from this list, send a message to
steward@2rosenthals.com with the command
"unsubscribe os2-wireless_users" in the body
(omit the quotes).

For help with other commands, send a message
to steward@2rosenthals.com with the command
"help" in the body (omit the quotes).

This list is hosted by Rosenthal & Rosenthal
P.O. Box 281, Deer Park, NY 11729-0281. Non-
electronic communications related to content
contained in these messages should be directed
to the above address. (CAN-SPAM Act of 2003)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=