TIP: Click on subject to list as thread! ANSI
echo: os2lan
to: DON GUY
from: PETER KNAPPER
date: 1998-04-04 10:02:00
subject: Sharing a WFWG printer...

Hi Don,
 PK> 1. Use NETBIOS or NETBEUI as the protocol on ALL machines,
 DG> This is where I appear to have run into a snag of sorts--
 DG> Trying to find a plain NetBIOS protocol driver for the 
 DG> WFWG machine on the 'net tried my patience more than 
 DG> anything else.
Both WFWG and OS/2 come with all the required PROTOCOL S/W for this type of 
connectivity, you should not need to add ANYTHING as far as the PROTOCOL is 
concerned. The only item you will probably need to find is the correct CARD 
driver for the OS/2 machine.
Lets just the check NETWORKING layers that you will need on each machine, 
most (if not all) of these you probably already have -
  1. You need Ethernet cards for both machine. The cards do NOT 
     need to be the same type in each machine, however let us
     assume you are using the most common card, the NE2000.
  2. You then need the CARD driver for each machine. The driver 
     is specific to the Operating System you are using and the CARD
     itself. IE the WFWG machine MUST have the appropriate WFWG 
     NE2000 driver, and on OS/2 you require the OS/2 NE2000 one.
     On the OS/2 machine, if the card did NOT come with an OS/2
     specific CARD driver, then you will need to locate one for 
     YOUR card. In the case of the NE2000 card, locate the file
     NS2000.ZIP and use that. Warning: thereis a file called 
     NE2000WC.ZIP that contains a driver for NE2000 cards, but like
     the OS/2 suplied NE2000 driver it is card specific. NS2000.ZIP 
     contains a generic NE2000 clone driver and seems to work with 
     most NE2000 cards. The standard NE2000 driver included with 
     Warp only works with one specific BRAND of NE2000 card (there 
     are several different NE2000 card manufacturers, and some have 
     added improvements to the original design that requires a 
     specific driver to get them working. These modified drivers 
     will NOT work with the original NE2000 card.)
  3. You then need to install the PROTOCOL or TRANPORT layer that 
     you wish to use between machines. Examples here are NETBIOS, 
     TCP/IP, IPX, etc... For Workgroups style connectivity, you 
     need NETBIOS to be loaded. NETBIOS is also called NETBEUI, and 
     in the WFWG, WIN95, WIN NT and OS/2 worlds either name means 
     the same thing. 
  4. Lastly, you will need the user interface. These are the Worgroups 
     functionalities that are added to the original Windows 
     environment and allow drive mappings, Logon/Logoff, etc, or
     the "Peer Networking" (Connecting and Sharing folder) support 
     that is part of OS/2. The only warning here is that under OS/2 
     you should perform a PEER logon, not a DOMAIN logon, unless one 
     of your NT boxes is NT Server and is configured as a Primary 
     Domain Controller (PDC) and you wish OS/2 to use NT's DOMAIN 
     control functions. 
Ok, so you may need to pick up the CARD DRIVERS for the network cards. What 
type of Network Card and what driver are you using for it on the OS/2 
machine? Is it the SAME type of card on all machines or are some different?
 DG> IBM Peer won't install, 'cause it can't 
 DG> see the network (allows only NetBIOS, or NetBIOS over 
 DG> TCP/IP as protocols).
I am not quite sure what you mean here by 'IBM Peer wont install'. Are you 
trying to install OS/2 "OVER the network", IE from an OS/2 CDROM in a CDROm 
drive that is loacted on another machine, and does the total install fail 
because it cant communicate with the machine with the CD? Or do you mean the 
PEER functionality within OS/2 itself?
 DG> Looking through what's available through MPTS, NetBEUI 
 DG> doesn't seem to be there. Do you know if there are 
 DG> "external" NetBEUI protocol drivers available for Warp 
 DG> Connect?
In MPTS the protocol to use is called 'IBM OS/2 NETBIOS', you do not need an 
external driver here, this one works fine... NETBEUI is just another name for 
a slightly extended NETBIOS flavour, and the IBM standard NETBIOS protocol 
can communicate with NETBIOS or NETBEUI enviroments anyway. I haven't touched 
a WFWG machine myself for many years so I can't remember the EXACT name that 
uses, but it is likely to include NETBIOS or NETBEUI in the title. The 
supplied NETBIOS drivers for each environment should work fine, once the CARD 
drivers are operating...
Hope this helps........pk.
--- Maximus/2 3.01
---------------
* Origin: Another Good Point About OS/2 (3:772/1.10)

SOURCE: echomail via exec-pc

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™.