OS/2 -> NT NETBIOS over TCPIP Boot Problem

Stan Towianski

unread,

Sep 29, 1997, 3:00:00 AM9/29/97

to

Hi,

I don't know the exact difference between NETBIOS and NETBEUI.
I think NETBEUI can do routing, and NETBIOS can only work on
one network?

Anyway, I had TCP/IP separate and NETBIOS separate in MPTS.
I could only see certain systems on the network. I could not
see basically the win NT machines that were running NETBIOS over
TCP/IP,
but were not running NETBEUI. The Win NT guy and I think I probably
have to try NETBIOS over TCPIP on my OS/2 machine.

The problem is that my system does not boot up correctly after I
took out plain NETBIOS and choose the protocol NETBIOS over TCPIP.
Boot complains about NETWKSTA.200, and if I do:
[C:\]net start
NET2102: The NETWKSTA.200 requester driver is not installed.

I see on boot up with NETBIOS over TCPIP it tries to use tcpbeui on
bootup instead of netbeui like before.

On boot up I get:
IBM OS/2 TCPBEUI 5.05.0
TCPBEUI: Using a 32-bit data segment
NET3406: An error occurred while opening network device driver NET1 =
NETBEUI$.
SYS1719: The file c:\ibmlan\netprog\netwksta.200 specified in the IFS
statement
on line 132 of the config.sys file does not contain a valid device
driver or
file system driver. Line 132 is ignored.
Press Enter to continue...

I have OS/2 4.0
with probably newest tcpip
and newest mpts wr08415

Anyone know what is wrong?
Thanks.

sta...@ibm.net

Trev Peterson

unread,

Sep 29, 1997, 3:00:00 AM9/29/97

to sta...@ibm.net

Stan Towianski wrote:
>
> Hi,
>
> I don't know the exact difference between NETBIOS and NETBEUI.
> I think NETBEUI can do routing, and NETBIOS can only work on
> one network?

The difference is Netbios is an upper layer (layer 5 OSI - I think)
protocol and it rides on Netbeui (layer 3,4 OSI - same layers as TCPIP
and IPXSPX if that helps). Netbeui is non-routable and netbios uses a
broadcast system to do name resolution so it's name resolution must be
broadcasted. What this really comes down to is it works on basically
one large segment.

It looks as though you still have netbuei configured and netbios is
trying to use it as the transport. I would remove the netbeui from the
MPTS (install and remove it if it is not currently installed). Hope
this helps.

Trev

John S. Giltner, Jr

unread,

Sep 30, 1997, 3:00:00 AM9/30/97

to sta...@ibm.net

Stan Towianski wrote:
>
> Hi,
>
> I don't know the exact difference between NETBIOS and NETBEUI.
> I think NETBEUI can do routing, and NETBIOS can only work on
> one network?
>

Hello Stan,

Windows NT also runs NETBIOS over NETBEUI, unless your NT folks removed
it. NT uses NETBIOS over NETBEUI by default, it also support NETBIOS
over IP. If NETBIOS over NETBEUI has not been disabled on NT you should
have no problems getting to the NT server, now you may not see it using
a net view command, but you can get to resources on it. But once you
get access to a resource on it you will be able to see all resources
available. You can use connection manager (CONMAN.EXE) to do this. I
have tested NETBIOS over IP and I still can not see the NT server. I
think it has to do with the way that NT has modifed the way that it
"announces" itself on the LAN. No matter what NETBIOS is going over,
NETBEUI or IP, it is still a function of NETBIOS to see servers. Your
NT guy can check to see if the network has netbeui configured. If it is
configured then NT can and is doing NETBIOS over NETBEUI. For real LANs
NETBEUI is perfered, for LANs that are really conntected by WANs NETBIOS
over IP is better.

Good Luck,
John G.

rpet...@ix.netcom.com

unread,

Oct 1, 1997, 3:00:00 AM10/1/97

to

Reconfigure File & Print sharing so it can pickup the changes you made
via MPTS.

sta...@ibm.net (Stan Towianski) wrote:

--
------------------------------------------------------------------------
Randy Petersen (OS/2 Warp warps)
rpet...@ix.netcom.com
------------------------------------------------------------------------

Jacco de Leeuw

unread,

Oct 1, 1997, 3:00:00 AM10/1/97

to

sta...@ibm.net (Stan Towianski) writes:

>On boot up I get:
>IBM OS/2 TCPBEUI 5.05.0
>TCPBEUI: Using a 32-bit data segment
>NET3406: An error occurred while opening network device driver NET1 =
>NETBEUI$.
>SYS1719: The file c:\ibmlan\netprog\netwksta.200 specified in the IFS
>statement on line 132 of the config.sys file does not contain a valid device
>driver or file system driver. Line 132 is ignored.
>Press Enter to continue...

I think this is a bug in the "MPTS.EXE" program. Check the
file \IBMLAN\IBMLAN.INI

The top of this file should be something similar to:

[networks]

net1 = NETBEUI$,0,LM10,34,100,14
net2 = TCPBEUI$,1,LM10,34,100,14

Don't worry if some of the paramaters are different. The point I want to make
is that some people (including me) had a problem where the TCPBEUI$ line
contained complete rubbish. It looked something like
net2 = TCPB@ 4%-.&@!$ *. This is clearly wrong and if you got
something like this, make the second line look similar to the first one,
except with NETBEUI$ changed to TCPBEUI$ and the adapter number (the second
parameter after the equal sign) changed from 0 to 1.

See also my webpage http://carol.wins.uva.nl/~leeuw/samba/warp.html on this.

Jacco
--
Jacco de Leeuw | Fac. Phys,Math.&Comp Sc. | mailto:le...@wins.uva.nl
J.C. van Wessemstr. 54 | University of Amsterdam | Maxer txtpager: 0660331048
1501 VM Zaandam, Holland<-Tel:+31(0)756352068| http://carol.wins.uva.nl/~leeuw/
Mir boardcomputer down again? I'm detecting a pattern! Are they running Win95?!

dshi...@direct.ca

unread,

Oct 3, 1997, 3:00:00 AM10/3/97

to

In <60t7qe$q0o$1...@adder.wins.uva.nl>, le...@wins.uva.nl (Jacco de Leeuw) writes:

>sta...@ibm.net (Stan Towianski) writes:
>I think this is a bug in the "MPTS.EXE" program. Check the
>file \IBMLAN\IBMLAN.INI

It's not... MPTS does not update the IBMLAN.INI ever.
It is up to the File/Print client (ie. LANINST.EXE) or the user to keep IBMLAN.INI up to date.
LANINST.EXE will call MPTS to reconfigure PROTOCOL.INI, then update the IBMLAN.INI to reflect changes made by MPTS, but MPTS will never touch IBMLAN.INI on its own.
I've never personally seen the bug you mention (probably cause I've done this sort of thing too many times and usually just use a text editor), but I believe it is a bug in the Warp install program, not in LANINST.EXE or MPTS.EXE.
It sounds like this fellow used MPTS to change protocols and did not update his IBMLAN.INI afterwards.
In the end the solution is the same - fix the IBMLAN.INI.

--------------------------------------------------------------
Doug Shields PowerHouse Point
dshi...@direct.ca Calgary, AB
BESTeam IBM OS/2 Warp Vancouver, BC
Server Software Specialist http://powerhouse.teleserve.ca
http://powerhouse.teleserve.ca/Doug/ (403) 264-1984
--------------------------------------------------------------

Jacco de Leeuw

unread,

Oct 6, 1997, 3:00:00 AM10/6/97

to

dshi...@direct.ca writes:

>In <60t7qe$q0o$1...@adder.wins.uva.nl>, le...@wins.uva.nl (Jacco de Leeuw) writes:
>>sta...@ibm.net (Stan Towianski) writes:
>>I think this is a bug in the "MPTS.EXE" program. Check the
>>file \IBMLAN\IBMLAN.INI

>It's not... MPTS does not update the IBMLAN.INI ever.

Ok ok, some other problem has this bug. Small technicality :-)

(BTW, I did find a problem with MPTS. Run it with 4OS/2 v2.50 [and higher?]
and it will go berzerk :-)

You have new spam.

dshi...@direct.ca

unread,

Oct 7, 1997, 3:00:00 AM10/7/97

to

In <61aogp$crc$1...@adder.wins.uva.nl>, le...@wins.uva.nl (Jacco de Leeuw) writes:

>dshi...@direct.ca writes:
>Ok ok, some other problem has this bug. Small technicality :-)

I would not normally have mentioned it, but one of the most common mistakes made by the technical people I work with (seperate from all the end-user problems) is to use MPTS to update the PROTOCOL.INI and then forgetting to update the IBMLAN.INI.

>(BTW, I did find a problem with MPTS. Run it with 4OS/2 v2.50 [and higher?]
>and it will go berzerk :-)

:) I had so many things go berserk with 4OS/2 I finally dumped it completely. I seem to recall the MPTS readme (or perhaps it was a fixpak readme) specifically mentioning problems with 4OS/2 which did not help the cause. Many of the main non-trivial features I used in CMD.EXE were broken by 4OS/2 (major bugs in the pipe support to the point all my programs started using CMD /C <command> rather then just <command>), and the main features I used in 4OS/2 (aliases and the command history) are now present or easily done with CMD.EXE.

Keith Medcalf

unread,

Oct 12, 1997, 3:00:00 AM10/12/97

to

In <c1.01.2HqQc0$0...@dshields.direct.ca>, dshi...@direct.ca writes:

>In <61aogp$crc$1...@adder.wins.uva.nl>, le...@wins.uva.nl (Jacco de Leeuw) writes:
>>dshi...@direct.ca writes:

>>Ok ok, some other problem has this bug. Small technicality :-)

>I would not normally have mentioned it, but one of the most common
>mistakes made by the technical people I work with (seperate from all the
>end-user problems) is to use MPTS to update the PROTOCOL.INI and then
>forgetting to update the IBMLAN.INI.

>>(BTW, I did find a problem with MPTS. Run it with 4OS/2 v2.50 [and higher?]
>>and it will go berzerk :-)

I found that permitting the Graphical Useless Interface tools to execute
AT ALL is almost certainly a guaranteed way to totally fuck up a perfect
system. If I want the config.sys, startup.cmd, protocol.ini, or
ibmlan.ini files farted with, I will do it myself. The Graphical
Useless Interface programs insist on "diddling" with files that are not
related to changes you have made, and usually end up rendering the
functions performed by that file inoperable.

Hence I immediately delete all the Graphical Useless Interface smegma
immediately after installation (this includes MPTS, LAPS, TCPIP and
LANMAN configuration programs).

At this point, editing the proper files with Qedit is a very effective
configurator -- and does not result in "random hosing" of the system.

>--------------------------------------------------------------
>Doug Shields PowerHouse Point
>dshi...@direct.ca Calgary, AB
>BESTeam IBM OS/2 Warp Vancouver, BC
>Server Software Specialist http://powerhouse.teleserve.ca
>http://powerhouse.teleserve.ca/Doug/ (403) 264-1984
>--------------------------------------------------------------

-------------------------------------------------------------
Keith Medcalf (416) 410-5791 http://www.dessus.com/
IBM OS/2, LAN Server, DB2/2, TCP/IP, DOS, Windows, Windows NT
"kmedcalf" at "dessus.com" is the correct reply address
(beware the spammer foiler in return address)

Stan Towianski

unread,

Oct 16, 1997, 3:00:00 AM10/16/97

to

[C:\]dir laninst.exe /s

The volume label in drive C is OS2WARP.
The Volume Serial Number is 270E:B815.

SYS0002: The system cannot find the file specified.

[C:\]d:

[D:\netsuite]cd\

[D:\]dir laninst.exe /s

The volume label in drive D is DATA.
The Volume Serial Number is 312A:2B49.

SYS0002: The system cannot find the file specified.

[D:\]

Is laninst.exe on the OS/2 install cdrom or where?

I wanted to use netbios over IP if I remember correctly (I quit
trying),
and all I tried was using MPTS to go in and drop netbios and add
netbios over IP. I did not know anything about having to mess with
ibmlan.ini. MPTS seemed to let me do what I wanted. IBMLAN.ini looks
pretty scary to me. I do not think I would know where to start to
make changes to it. What do you suggest?

Thanks.

P.S. My thoughts are that as long as I am already running tcp/ip I
might as well run netbios over IP to connect to NT instead of bringing
in another lower level protocol like netbeui? Make sense?

(posted newsgroup reply and sent email)

sta...@ibm.net

dshi...@direct.ca

unread,

Oct 17, 1997, 3:00:00 AM10/17/97

to

In <34465...@news1.ibm.net>, sta...@ibm.net (Stan Towianski) writes:
>[C:\]dir laninst.exe /s
[...]

>Is laninst.exe on the OS/2 install cdrom or where?

I already mentioned this in e-mail, but for everyone else...
The install program for LAN Server is LANINST.EXE, however the File/Print client in Warp 4 (and probably Connect) uses \IBMLAN\INSTALL\PEERINST.EXE

dshi...@direct.ca

unread,

Oct 17, 1997, 3:00:00 AM10/17/97

to

In <c1.01.2Hts2w$0...@news.dessus.com>, kmed...@dessus.spam.com (Keith Medcalf) writes:
>I found that permitting the Graphical Useless Interface tools to execute
>AT ALL is almost certainly a guaranteed way to totally fuck up a perfect
>system. If I want the config.sys, startup.cmd, protocol.ini, or
>ibmlan.ini files farted with, I will do it myself. The Graphical

That's nice. Now if you would not mind doing it for all the other people in the world that do not know where the configurations files are kept, which configuration files/options belong to which layer in the stack, or what the options mean, let alone know how to configure them properly... all the configuration problems of the world will be fixed.
Personally I have never had any problem using the GUI tools in the years that I have used them (I hate building 802.2 configuration blocks by hand), though I generally avoid them and head straight for TEDIT simply for speed reasons. Everytime I have had to fix a busted configuration in this area it was from something the user told the GUI to do (or more often than not, failed to tell the GUI to do).

rr

unread,

Oct 26, 1997, 2:00:00 AM10/26/97

to sta...@ibm.net

rr wrote:

>
> Stan Towianski wrote:
> >
> > [C:\]dir laninst.exe /s
> >
> > The volume label in drive C is OS2WARP.
> > The Volume Serial Number is 270E:B815.
> >
> > SYS0002: The system cannot find the file specified.
> >
> > [C:\]d:
> >
> > [D:\netsuite]cd\
> >
> > [D:\]dir laninst.exe /s
> >
> > The volume label in drive D is DATA.
> > The Volume Serial Number is 312A:2B49.
> >
> > SYS0002: The system cannot find the file specified.
> >
> > [D:\]
> >

> > Is laninst.exe on the OS/2 install cdrom or where?
> >

> > I wanted to use netbios over IP if I remember correctly (I quit
> > trying),
> > and all I tried was using MPTS to go in and drop netbios and add
> > netbios over IP. I did not know anything about having to mess with
> > ibmlan.ini. MPTS seemed to let me do what I wanted. IBMLAN.ini looks
> > pretty scary to me. I do not think I would know where to start to
> > make changes to it. What do you suggest?
> >
> > Thanks.
> >
> > P.S. My thoughts are that as long as I am already running tcp/ip I
> > might as well run netbios over IP to connect to NT instead of bringing
> > in another lower level protocol like netbeui? Make sense?
> >
> > (posted newsgroup reply and sent email)
> >
> > sta...@ibm.net

> I have been currently working on doing the same and consider myself done
> except that I have not been able to test my setup. If you would like I
> can share my information on how to set up the file and print sharing
> capabilities in OS/2 through NEtbios over tcpip and maybe we can test
> our setup over the internet. I have had success in dialing into my
> machine using the ppp program and the Win95 ppp dialup prog and sharing
> my resources with a win 95 machine but have yet to test it over the
> internet.
>
> Email lle...@ibm.net
> name Richard Reyes
You need to have Netbios installed. Run MPTN and under no lan adapter or
,a lan adapter if one is configured, install the following protocals
TCPIP, NetBios, NetBios over TCPIP. You will need to change the logical
adapter number for Netbios over TCPIP to something other than the one
used by NetBios ie.

0----NetBios
1----NetBios over TCPIP

After this is done just accept the changes and close MPTN

ReBoot

Then insert the OS/2 installation CDRoM and look under the IBMINST
directory for a program called peerinst.exe this will go about setting
up the peer networking software for file and print sharing.

Reboot

When your finished you should have a peer networking folder on your
desktop you can open this folder and log on to your peer workstation
(Your computer). after you have done this you can then determin what you
would like to share by RMB clicking on the folder or printer yopu want
to share.

To Connect to another computer they have to be configured in a names
list located in the ibmcom directory this file is called
RFCNAMES.LST you need to specify the workstation name and the ipaddress
(You should be able to provide a Name style address if the individual
you will connect to is using a dynamic domain service such as ml.org)

Then Run the program under ibmcom called RFCADDR.exe this should update
your system connections

This last part is what I need to test over the internet

PS - The TCPIP used in WIndows is actually TCPBEUI tested it and it
turned out to be true. Dont know why the pretend to call it just
TCPIP???

rr

unread,

Oct 26, 1997, 2:00:00 AM10/26/97

to sta...@ibm.net

Charles Turner

unread,

Oct 29, 1997, 3:00:00 AM10/29/97

to

In <345402...@home.org>, rr <rr> writes:

>Then insert the OS/2 installation CDRoM and look under the IBMINST
>directory for a program called peerinst.exe this will go about setting
>up the peer networking software for file and print sharing.

My peerinst runs for a while but then gets to a point where it wants me to
insert peer diskette-4. I don't have any peer diskettes!

Thoughts, suggestions? Thanks.