> Problem:

 >  Can NOT write to a correctly shared Win95 drive from OS/2 on
 >  a peer network using Drag'n'Drop in the WPS.
 >  Works using the command line and WIN-OS/2 Drag and Dropping.

 >  Can NOT print to a correctly shared Win95 printer from OS/2
 >  on a peer network using Drag'n'Drop in the WPS.
 >  Can print plain text from command line, but can't create
 >  desktop object for printer. Prints fine from WIN-OS/2.

 >  Using ipx/spx with netbios enabled (or netbios disabled) and
 >  /or netbui makes no difference.

 >  OS/2 will network correctly with Win 3.11. ie write to shared
 >  drives and print to network printers.

OS/2 does not as yet claim complete compatibility with Win95 or NT; the
official level is Win3.11 with Win32s v1.25 at present. The file systems
and print routines Microsoft uses were changed with the release of Win95
and NT, and the same problems are being experienced by OS/2 clients of NT
servers as evidenced in the OS2LAN echo. Connecting Win3.11 (not WFW3.11)
to Win95 or NT would probably be just as nasty. Note that this is primarily
a problem with a Windows specification change, not a problem with OS/2 per
se.

Having issued the standard caveat :-) we proceed with a summary of the
related comments and suggestions made in the last month in OS2LAN.

First, you make no mention of which version of OS/2 you're running but
judging from the fact that you're using IPX/SPX it looks like it's probably
Warp Blue riding on SCO, Lantastic or Novell so all comments about OS/2
Server and Connect can be selectively ignored if I have this part right. 

There's also no support for IPX (only NETX) from Win/OS2, and since it
would have to be run via VLMs in a DOS box and doesn't even work properly
that way perhaps you can clarify or correct the above somehow to indicate
the _actual_ configuration. If the above is correct, I'd be *very*
interested in how you got this far.

When a connection is established does "Connecting and Sharing"
display anything in the connections panel ? If not, there might be a link
broken somewhere between network objects and the WPS, which would indicate
a reinstall of OS/2 is necessary. But read on ...

Here's the checklist:

1. Ensure the following is in config.sys on the OS/2 machine -

SET AUTOSTART = PROGRAMS,TASKLIST,FOLDERS,CONNECTIONS,LAUNCHPAD

(Connections is prolly Server or Connect specific)

2. Make sure Fixpack 22 for Warp and all current MS service packs are
applied. For plain Warp you can add PN71501 fix for TCP/IP; for Server and
Connect also add WR08210 (MPTS) and UN00067 if using TCP/IP, and finally
IP08250 which brings you up to current specs.

3. Warp Blue fails to update all necessary files when adding NETBIOS over
TCP/IP and this may also be true if your system was upgraded for network
use after the initial installation. It works fine from a new install. The
problem appears to be in \ibmlan\protocol.ini in the [peer] section. A line
"svrnets=NET1, NET2" or something similar is omitted. The
quickest fix is to uninstall all TCP/IP stuff and do a selective install,
including the protocol required for Windows (Netbeui or whatever).

4. Double check that all userids and passwords are *exactly* the same for
both systems.

If all the above fails, you may need to get the NFS pack for OS/2, which is
about $89.00 US. Please let me know if any of the above works for you, so I
can write it down as the correct fix for this seemingly common problem. I
don't run Win95 or NT here, only Win3.11, and don't plan to.

Rob

--- FMail 0.94