XP doesn't see NetBIOS/IPX over DOS Raima lock manager

[Richard H. Berman]

I have an office which has been
running an old netBIOS over IPX/SPX
using frames 802.3 network. There is
a lock manager computer running
NetBIOS v. 3.0.2 Rev.C over DOS which
handles all of the access to the
database files. I have been running
the office software since 1996 on
WIN95 and 98 with no problem. Now I
am forced to upgrade a computer to
WinXP Pro and am having a heck of a
time getting XP to see the
NetBios "lockmgr" computer. I have
installed NWLink/Netbios/IPX/SPX and
set up frames as 802.3. The XP
computer sees all the other 802.3
computers, but not the DOS lockmgr
computer. On the WIN95/98 computers
as long as I checked the "make this
the default" box in the IPX/SPX setup
and added and bound IPX/SPX and
NetBIOS to the microsoft client all
worked well. Why not on XP? ANy
solutions would be greatly appreciated.
thanks..rich berman

[John-Thomas Gaietto]

Hello,
Try this:

1) Go right click on My network Places

2) Click on properties

3) Select the properties of your Network interface

4) Check to see if you have the following protocols installed NWLink NetBios, NWLink IPX/SPX/NetBIOS Compatible Transport Protocol, TCP/IP

5) Open the TCP/IP Properties and go to Advanced

6) Then click on the Wins TAB

7) Check to enable NetBIOS over TCP/IP.

I hope this helps if so please don't forget the points Good Luck.

[Richard H. Berman]

I tried the Netbios over TCP/IP to no avail. There is something different about how XP handles IPX/SPX/Netbios vs. Win9x. Anyone have any other ideas...helpless!

[Peter Balla_1]

The problem is the LANA number that the old DOS Raima use as default.

First, disable Netbios over TCP/IP you dont need it. Add the NWLink NetBIOS protocol.

From this article: NetBIOS LANA Numbers

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/netbios/netbios_91mb.asp

Many MS-DOS ??? based applications sent all their requests to LANA 0

The NetBIOS LANA number identifies the transport driver, network interface card (NIC) driver, and adapter that will be used to send and receive NetBIOS packets. This is known as the network route.

The IBM NetBIOS 3.0 specification supports only two LANA numbers, because NetBEUI was originally the only protocol that supported NetBIOS, and a computer could contain only two network adapters at that time. Specifying LANA 0 directed a command to the first adapter, and specifying LANA 1 directed a command to the second adapter.

Windows 2000/XP: You cannot configure LANA numbers on these platforms. !!!

--

So if you have the IPX/SPX Netbios "bind" to for example to LANA 3, the Raima staff wont work.

I changed this program to figure out the living XP LANA "bindings"

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/netbios/netbios_3wtd.asp

#include
#include
#include
#include
#include

BOOL NBReset (int, int, int);

void main ()
{
printf("\nTesting LANA:\n\n");
NBReset (0, 20, 30);
NBReset (1, 20, 30);
NBReset (2, 20, 30);
NBReset (3, 20, 30);
NBReset (4, 20, 30);
NBReset (5, 20, 30);
NBReset (6, 20, 30);
NBReset (7, 20, 30);
}

BOOL NBReset (int nLana, int nSessions, int nNames)
{
NCB ncb;

memset (&ncb, 0, sizeof (ncb));
ncb.ncb_command = NCBRESET;
ncb.ncb_lsn = 0; // Allocate new lana_num resources
ncb.ncb_lana_num = nLana;
ncb.ncb_callname[0] = nSessions; // maximum sessions
ncb.ncb_callname[2] = nNames; // maximum names

Netbios (&ncb);

printf(". LANA:%d status = %d \n\n",nLana,ncb.ncb_retcode);

return (NRC_GOODRET == ncb.ncb_retcode);
}


--------------------------------

Then you have two choises.

1) Rebuild the Raima staff to use LANA 3 or be configurable.

2) Force the XP to use LANA 0. Becouse on Windows 2000/XP: You cannot configure LANA numbers, this is a problem.

But you can playing with XP add/remove protocols and enable/disable netbios until you find the IPX/SPX Netbios is using LANA 0.

C:\TEMP\LM>lana.exe
Testing LANA:

. LANA:0 status = 0
. LANA:1 status = 35
. LANA:2 status = 35
. LANA:3 status = 35
. LANA:4 status = 35
. LANA:5 status = 35
. LANA:6 status = 35
. LANA:7 status = 35

This state is permanent after reboot, and DOS Raima works fine :)

>>> peter

--

"No trees were killed in the sending of this message. However a large number of electrons were terribly inconvenienced."

[Peter Balla_1]

appendix:

Windows NT/Windows 2000/Windows XP enables NetBIOS to use transport protocols other than NetBEUI. Therefore, Microsoft has extended the meaning of a LANA number to indicate a specific transport protocol on a specific adapter. For example, if you have two network adapters, and have three transport protocols installed, you have six LANA numbers. The LANA numbers are not necessarily sequential.

Zero might map to IPX/SPX on the first adapter, three might map to a different protocol on a second adapter, and so on.

Windows 2000/XP: You cannot configure LANA numbers on these platforms.

-

I'v checked the USENET where many people asking, "how to config LANA numbers under XP". But it seems nobody knows a solution.

http://groups.google.com/groups?num=100&q=XP+LANA

-

I found the XP use some autoconfig algorithm to assign the LANA numbers. This add/remove and enable/disable method (maybe the order is the important thing) force the XP to go over the assignments.

And when you have NetBIOS over IPX/SPX assigned to LANA 0 then stop, and bingo.

--

"If you're not googleable, you don't exist"

[Richard H. Berman]

Peter,
I think you are on to the problem. I can do the trial and error approach, but it's been many years since I 've done any programming and I no longer recognize what language the lana.exe program is written, nor do I have any language compilers. Any chance you can email me your lana.exe program? email to dentist@netreach.net
thanks again..
rich berman

[Peter Balla_1 · Accepted solution]

Meanwhile our IT guy has figured out the correct method, to how to force the XP to using LANA 0.

here is the solution from Taki:

1. Run the regedit.
2. Find the LanaMap entries 3 or 4
3. Change the value to this:

0000 01 00 01 01 00 02 00 03
0008

4. Restart the XP.
5. Tha LANA 0 changed to the desired Netbios.

--

"Any sufficiently advanced technology is indistinguishable from magic." Arthur C. Clarke

[Peter Balla_1]

I looked around for some information about this LanaMap registry key.

In the regisry at the NetBIOS Linkage settings, where the NetBIOS
LanaMap value must contain a two-byte value (a "tuple") for each
string in the NetBIOS Bind value. For details on how to view these
values, see the second method in the "Workaround" section of this
article.

The following is an example of a single string in the Bind value:

\Device\NetBT_CPqNF31

If this is the only string in the Bind value, then the LanaMap value
must contain only one two-byte tuple for the one Bind string.

The LanaMap must contain the correct number of two-byte tuples, for
example:

1 string in the "Bind" value = 1 two-byte tuple (for example, 01
01)
2 strings in the "Bind" value = 2 two-byte tuples (for example, 01
01 01 02)


in our enviroment:
------------------

Here you can see our Bind registry key snapshot, it says we have 4
Device string in it.

\Device\NwlnkNb
\Device\NetBT_Tcpip_{61096195-EC12-4FC5-BAA6-42A1D6E0C69E}
\Device\NetBT_Tcpip_{3E06ADA6-B8FF-4AC9-A5E1-2FF196CB0750}
\Device\NetBT_Tcpip_{C67832FC-A091-4137-BA55-86B200F10298}

This means the LanaMap key must hold 8 numbers or 4 tuples. And here
it is.

01-00 01-01 00-02 00-03

I think the first tuple in each set is 01 if its enabled, the second
tuple must be the Lana number of the corresponding transport device
that NetBIOS should bind to (as listed in the Bind value)

WARNING: Using Registry Editor incorrectly can cause serious problems
that may
require you to reinstall your operating system. Note that you should
back up the registry before you edit it. If you are running Windows NT
or Windows 2000, you should also update your Emergency Repair Disk
(ERD).


>>> peter

--

"No trees were killed in the sending of this message.
However a large number of electrons were terribly inconvenienced."

[Richard H. Berman]

Peter,
You are a genius!!! It worked like a charm on XP home and XP Pro!!!
Tell everyone on the google search list as well as Microsoft/Dell/et al.
rich