CONNECTING OS/2 WITH WFWG/WINDOWS95

One of the many queries I see on OS/2 is the Peer connections between Warp
Connect/4.0 and Windows for Workgroups/Windows95.  I think (partly) that
the reasons for this is that when you setup the peer connections, most of
the work is done for you and the u ser does not need to know more than
what is done for him.  The problem arises when these peer connections are
between IBM's OS/2 and Microsoft's Windows.  If you try and read up on
this, not much is being said by either company about connecting to the
opposition's network.  I have spent some time reading up the
documentation on OS/2 Peer and the Windows Resource kits and managed to
put the following information together.  Please note that although my
examples uses Warp Connect, setting up Warp 4.0 is the same or very
similar.  I find most differences only applies to some naming conventions
like "Properties" as to "Settings", etc.

Please feel free to distribute this information as it can only benefit the
cause for OS/2.

Let me expand a bit on how to set up the WFWG PC so that Connect and WFWG
can see each other.  The first step is to make sure that they are in the
same domain (or Workgroup - using M$'s naming convention).  The Connect PC
will default to IBMPEER and the WFW G will default to WORKGROUP - so
change one of them so that they are the same.

To allow WFWG PCs to browse the Connect PCs, there must be at least one
WFWG PC on the network that sets the "workgroup= " entry in the [network]
section of SYSTEM.INI file to the name of the Connect PC's domain (like
IBMPEER - if that is how you have the Connect PC set up).  The "network= "
entry can be changed from the Networks option in the Windows Control
Panel.  Once a WFWG workstation is a member of the Connect's domain, this
workstation will distribute the names of all the OS/2 Connect PCs to other
WFWG workstations on the network.

By default, a WFWG workstation running in 386 enhanced mode won't announce
its presence to Connect PCs (M$ claims that they do it to reduce the
amount of broadcast traffic on the network).  If the WFWG PC is setup this
way, you can see it using Net View bu t not with the GUI network browser -
Sharing And Connecting.  So the next step is to change this "default."
How the WFWG workstation announces its presence is defined by the
"LMAnnounce= " entry in the [network] section of SYSTEM.INI.  By using
"LMAnnounce= yes", the WFWG workstation running in 386 enhanced mode will
announce its presence to Connect PCs.

Windows95 conforms to the same specifications as WfW with regard to LAN
Manager resources.  Windows95 see OS/2 Warp Connect as a LAN Manager
server.  In Control Panel/Network make sure you have the Client for
Microsoft Networks loaded and that you add the NetBEUI protocol to this

To allow Windows95 PC's to see LAN Manager or IBM Peer or IBM LANServer
Resources

In order for Windows95 machines to see Warp Connect resources, one
Windows95 PC must have their WORKGROUP set to the PRIMARY domain of a Warp
Connect PC.  This will enable the Windows95 machine to broadcast the names
of the Warp Connect servers to other Windows95 PC's This needs to be
duplicated for each Warp Connect Domain.

To allow IBM Peer or IBM LANServer to see Windows95 Resource

By default Windows95 does not announce itself to LAN Manager or IBM Peer
servers To configure Windows95 to announce to Control Panel /Settings
/Network/Microsoft File and Print Services/LMAnnounce = Yes.

 Regards
 Phill Erasmus
 CIS - 100075,340
 'Net - erasmusp@iafrica.com