TIP: Click on subject to list as thread! ANSI
echo: os2
to: ALL
from: Mike_Luther@f3001.n117.z1
date: 2006-01-07 20:25:55
subject: Networking issue

Path: number1.nntp.dca.giganews.com!local01.nntp.dca.giganews.com!nntp.adelphia.com!news.adelphia.com.POSTED!not-for-mail
NNTP-Posting-Date: Sat, 07 Jan 2006 20:25:55 -0600
Newsgroups: fidonet.os2
From: Mike_Luther@f3001.n117.z1
Date: Thu, 05 Jan 2006 03:01:16 -0500
Subject: Networking issue
Message-ID: 
Organization: Ziplog Public Port
 143/2
Lines: 108
NNTP-Posting-Host: 24.54.66.112
 properly
Xref: number1.nntp.dca.giganews.com fidonet.os2:45

Can help Alan..

 AH> How did you uninstall the Netbios over Tcp/Ip protocol?  *adh*


Note that it is INSTALLED by your choice in OS/2, but as the drunken rhino
crosses the Safari in a WIN world, shfarashino it's both default and totally
needed in the WIN world as an auto install when the master install is done.  Thus
it won't be there in an OS/2 system open to all the world with standard server
installed and default passwords like the WIN world game unless the installer of
your system hand installed it. Nice OS/2 - Thank you.

  1.) Open the OS/2 System folder.

  2.) Open the System Setup folder.

  3.) Depending on what OS/2 version you have you'll either open the
      Adapters and Protocol Services folder or the MPTN folder.  The
      MCP2 current OS/2 platform is the Adapters and Protocol Services
      folder.

  4.) Click on the Configure button in the user option pane.

  5.) The default user option choice next is the LAN adapters and
      protocl buttom with Configure highlighted.  Choose it.

  6.) You get to define your LAN adapter here.  To a given LAN adapter
      in use you get to define what protocol should be available to it.

  7.) Shfarashino the default is No Network Adapter installed.  At one
      point or another during the LAN installation phase of OS/2 or
      at a later point, the installer person has to choose the LAN
      adapter of choice.  Which means there must be a driver of some
      kind available to OS/2 which works for your version of LAN game
      in your version of OS/2. The two OS/2 ThinkPads I have here as
      well as the stack of Intel 915GAV motherboard desktop boxes are
      all using Intel PRO/100 Network Connection compatible LAN chip
      sets.  That's part of the reason I went this way to keep things
      simpler.  But you chose or choose a supported LAN adapter by
      scrolling down the Network Adapter choices to a compatible one.
      You ADD the one you need, or select Other adapters and chunk in
      the sloppy diskette or CD-ROM with the drivers on it for OS/2
      to suck the drivers on to the hard disk to use.  Or you can
      put the new drivers on the hard disk by hand if you know how.

  8.) You then go to the Protocols pane and ADD a protocol to the
      selected adapter.  For OS/2 purposes the only two normally
      'needed' are:

       a.) IBM OS/2 NETBIOS
       b.) IBM TCP/IP

      Notice that as you scroll the pane down, you see another one:

      IBM OS/2 NETBIOS OVER TCP/IP

      That's the little wolf cub which has to be there, shfarashino, to
      enable communication between OS/2 and WIN boxes on shared LAN
      stuff.  And that's a way how the path to destruction can be opened
      to the WIN world to allow a foreign WIN working box to get access
      to your shared drives for read or write, if so enabled, to let
      a foreign WIN box stuff files on your OS/2 hard disk and create
      new directories and subdirectories on them even though NOT doing
      this with native OS/2 on your system.

      BIOS = Base input output system?  Base inout output system over
      LAN.  Network base input output system over LAN.  From afar.
      Right?  Even without coffee in your Java cup, right?  From
      corrupt WIN systems, right?  Which we COULD write for OS/2 if
      one wanted to really get nasty but then having such a hated
      hand configured system is really a plus in some ways, is not?

      ;)

      If this protocol has been enabled on your OS/2 LAN and you do not
      want it, you may do the following.

  9.) Go down to the lower pane of the options.  Select that protocol
      for the LAN adapter you see it installed upon.  Highlight that
      IBM OS/2 NETBIOS OVER TCP/IP and then click to REMOVE it.  You
      confirm everything and bye-bye.  Shfarshiono your beast now can
      cross the LAN divide without such WIN world boxes able to mangle
      at least your LAN with that protocol.  Even though the files
      they want to next execute won't work.  Duhh .. unless they were
      DOS or early WIN 95/98 stuff and maybe even added a line or
      two to your CONFIG.SYS or AUTOEXEC.BAT as 'needed'.  Think
      about that o pious one(s).  Anyway.

 10.) Close down the whole show.  You'll get told to reboot your box.
      OS/2 needs to have a clean CONFIG.SYS that matches all this to
      get the choices for the LAN work straight and all the stuff in
      the PROTOCOL.INI file right with the system.


Major note.  If you are using the INJOY firewall or another firewall which
works the same way with protecting you, you must DISABLE or UNINSTALL that
firewall service before you attempt to configure the MPTN operations.  You can
then ENABLE or RE-INSTALL the firewall after you make the changes in the MPTN
files and interface to your system.


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001

SOURCE: echoes via archive.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.