Need help configuring OS/2 to talk to Linux

Need help configuring OS/2 to talk to Linux

Post by Gary R. Wal » Thu, 19 Nov 1998 04:00:00



I have two machines that I am networking together, a 486DX66 with Red Hat
Linux 5.1 and a triple boot Pentium 166 with RH 5.1, OS/2 and that other OS.
I have managed to get the two boxes to talk together happily over TCP/IP with
the Pentium booted to Linux.  I have gotten both NFS and IP forwarding to work
well (modem on the Pentium.)  
However, when I boot the Pentium box to OS/2, I can't seem to get things
configured properly.  I am using TCP/IP 4.1 and WR08610B.  The NIC seems to be
detected properly, but the following config.sys statements do not load:

DEVICE=F:\IBMCOM\PROTOCOL\NETBEUI.OS2
DEVICE=F:\IBMCOM\PROTOCOL\TCPBEUI.OS2
IFS=F:\IBMLAN\NETPROG\NETWKSTA.200 /I:F:\IBMLAN /N
DEVICE=F:\IBMCOM\PROTOCOL\NETBIOS.OS2
DEVICE=F:\IBMCOM\PROTOCOL\LANVDD.OS2

Is there a particular order that these and related statements should be listed
in the config.sys?  I am a networking newby, so if someone could give me some
pointers, I would appreciate it.


Richmond Hill, Ontario          http://www.interlog.com/~grwalsh

 
 
 

Need help configuring OS/2 to talk to Linux

Post by Gary R. Wal » Thu, 19 Nov 1998 04:00:00



Quote:(Gary R. Walsh) writes:

:>
:>I have two machines that I am networking together, a 486DX66 with Red Hat
:>Linux 5.1 and a triple boot Pentium 166 with RH 5.1, OS/2 and that other OS.
:>I have managed to get the two boxes to talk together happily over TCP/IP with
:>the Pentium booted to Linux.  I have gotten both NFS and IP forwarding to work

            ^^^^^^^^^^^^^^^^
                                                                            I
mean IP masquerading  

Quote:>well (modem on the Pentium.)  

:>However, when I boot the Pentium box to OS/2, I can't seem to get things
:>configured properly.  I am using TCP/IP 4.1 and WR08610B.  The NIC seems to be
:>detected properly, but the following config.sys statements do not load:
:>
:>DEVICE=F:\IBMCOM\PROTOCOL\NETBEUI.OS2
:>DEVICE=F:\IBMCOM\PROTOCOL\TCPBEUI.OS2
:>IFS=F:\IBMLAN\NETPROG\NETWKSTA.200 /I:F:\IBMLAN /N
:>DEVICE=F:\IBMCOM\PROTOCOL\NETBIOS.OS2
:>DEVICE=F:\IBMCOM\PROTOCOL\LANVDD.OS2
:>
:>Is there a particular order that these and related statements should be listed
:>in the config.sys?  I am a networking newby, so if someone could give me some
:>pointers, I would appreciate it.
:>

Richmond Hill, Ontario          http://www.interlog.com/~grwalsh

 
 
 

Need help configuring OS/2 to talk to Linux

Post by Todd Bordeau » Thu, 19 Nov 1998 04:00:00


Use MPTS Configuration program and set the IFType to 6.  The
configuration program will put the device statements in the order that
they should appear.

HTH...Todd

 
 
 

Need help configuring OS/2 to talk to Linux

Post by mike.lut.. » Fri, 20 Nov 1998 04:00:00



Quote:>Use MPTS Configuration program and set the IFType to 6.  The
>configuration program will put the device statements in the order that
>they should appear.

>HTH...Todd

Todd.. I've long wondered where I could read documentation on the IFType
definitions...

I'll be the first to admit that it's probably in the DOCs right under
me noes and yes, I've even printed the whole section in the OS/2 stuff
on the network..  Just may have missed it.. whatever...  I've made a lot
of errors and missed seeing lots of things in my life...

Would you be so kind to point me to where I can study this?   If it's
simple, and just something you can read into a reply here, posting it
here might do a lot of good...

Thanks if you can help...

//-----------------------------


 
 
 

Need help configuring OS/2 to talk to Linux

Post by Gary R. Wal » Fri, 20 Nov 1998 04:00:00



writes:
:>
:>Use MPTS Configuration program and set the IFType to 6.  The
:>configuration program will put the device statements in the order that
:>they should appear.

That didn't seem to do anything.


Richmond Hill, Ontario          http://www.interlog.com/~grwalsh

 
 
 

Need help configuring OS/2 to talk to Linux

Post by Gary R. Wal » Fri, 20 Nov 1998 04:00:00



writes:
:>
:>Use MPTS Configuration program and set the IFType to 6.  The
:>configuration program will put the device statements in the order that
:>they should appear.

That didn't seem to do anything.


Richmond Hill, Ontario          http://www.interlog.com/~grwalsh

 
 
 

Need help configuring OS/2 to talk to Linux

Post by James Kno » Sat, 21 Nov 1998 04:00:00





>writes:
>:>
>:>Use MPTS Configuration program and set the IFType to 6.  The
>:>configuration program will put the device statements in the order that
>:>they should appear.

>That didn't seem to do anything.

Removing/reinstalling the File & Print client often clears a lot of
problems.

--

_________________________________________________________________________
The above opinions are my own and not those of ISM Corp., a subsidiary of
IBM Canada Ltd.

 
 
 

Need help configuring OS/2 to talk to Linux

Post by Will Ro » Tue, 24 Nov 1998 04:00:00



: I have two machines that I am networking together, a 486DX66 with Red Hat
: Linux 5.1 and a triple boot Pentium 166 with RH 5.1, OS/2 and that other OS.
: I have managed to get the two boxes to talk together happily over TCP/IP with
: the Pentium booted to Linux.  I have gotten both NFS and IP forwarding to work
: well (modem on the Pentium.)  
: However, when I boot the Pentium box to OS/2, I can't seem to get things
: configured properly.  I am using TCP/IP 4.1 and WR08610B.  The NIC seems to be
: detected properly, but the following config.sys statements do not load:

: DEVICE=F:\IBMCOM\PROTOCOL\NETBEUI.OS2
: DEVICE=F:\IBMCOM\PROTOCOL\TCPBEUI.OS2
: IFS=F:\IBMLAN\NETPROG\NETWKSTA.200 /I:F:\IBMLAN /N
: DEVICE=F:\IBMCOM\PROTOCOL\NETBIOS.OS2
: DEVICE=F:\IBMCOM\PROTOCOL\LANVDD.OS2

: Is there a particular order that these and related statements should be listed
: in the config.sys?  I am a networking newby, so if someone could give me some
: pointers, I would appreciate it.

Below is the networking stuff in my Connect config.sys; note that I'm
using Netbios to talk to a Lanserver, and TCP/IP to talk to some Unix
boxes.  You can probably edit out about half these lines - the question
is, which half?

REM Protocol stuff
BASEDEV=DETNE2.SYS
DEVICE=D:\IBMCOM\PROTOCOL\LANPDD.OS2
DEVICE=D:\IBMCOM\PROTOCOL\LANVDD.OS2
DEVICE=D:\IBMCOM\LANMSGDD.OS2 /I:D:\IBMCOM
DEVICE=D:\IBMCOM\PROTMAN.OS2 /I:D:\IBMCOM
REM *** why is call used here?
CALL=D:\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=D:\IBMCOM\LANMSGEX.EXE
DEVICE=D:\MPTN\PROTOCOL\SOCKETS.SYS
DEVICE=D:\MPTN\PROTOCOL\AFOS2.SYS
DEVICE=D:\MPTN\PROTOCOL\AFINET.SYS
DEVICE=D:\MPTN\PROTOCOL\IFNDIS.SYS
RUN=D:\MPTN\BIN\CNTRL.EXE
CALL=D:\OS2\CMD.EXE /Q /C D:\MPTN\BIN\MPTSTART.CMD
SET ETC=D:\MPTN\ETC
REM Protocol end
REM LAN stuff
DEVICE=D:\IBMCOM\PROTOCOL\NETBEUI.OS2
DEVICE=D:\IBMLAN\NETPROG\RDRHELP.200
REM *** can this be moved? Probably not.
IFS=D:\IBMLAN\NETPROG\NETWKSTA.200 /I:D:\IBMLAN /N
DEVICE=D:\IBMCOM\PROTOCOL\NETBIOS.OS2
DEVICE=D:\IBMCOM\MACS\MACWD.OS2
REM System logging stuff
DEVICE=D:\OS2\LOG.SYS
RUN=D:\OS2\SYSTEM\LOGDAEM.EXE
RUN=D:\IBMLAN\NETPROG\LSDAEMON.EXE
REM Used by DB/2 and CM/
REM Buggy? Try detach... from startup.cmd
rem RUN=D:\OS2\EPW.EXE
rem RUN=D:\OS2\EPWROUT.EXE 1
SET NWDBPATH=D:\IBMLAN\NETPROG
SET DLSINI=D:\IBMLAN\NETPROG\NETGUI.INI
SET INIT_FILE_NAMES=NETGUI
SET INIT_FILE_RANGES=200
SET WPS_COMMUNICATION=YES
REM LAN end
REM TCP/IP stuff
DEVICE=D:\TCPIP\BIN\VDOSTCP.VDD
DEVICE=D:\TCPIP\BIN\VDOSTCP.SYS
SET USE_HOSTS_FIRST=1
rem SET LANG=ENUS437
SET TZ=PST8PDT
SET HOSTNAME=whatever
SET USER=whoever
SET TELNET.PASSWORD.ID=whichever
RUN=D:\TCPIP\BIN\VDOSCTL.EXE
REM TCP/IP end

Will

 
 
 

Need help configuring OS/2 to talk to Linux

Post by Francoi » Fri, 27 Nov 1998 04:00:00




> writes:
> :>
> :>Use MPTS Configuration program and set the IFType to 6.  The
> :>configuration program will put the device statements in the order that
> :>they should appear.

> That didn't seem to do anything.


> Richmond Hill, Ontario          http://www.interlog.com/~grwalsh

Can you help me, I whant some information about the virtual memory
management of OS/2.

Please write me back soon thanks.