Hello Rich,
Replying to a message of Rich Wonneberger to Peter Knapper:
 RW> Maybe you can point me in the right direction..
 RW> I'm working on the same basic thing as Don.  I have a WFWG machine I
 RW> have to get a large number of files off of.  I have MS's TCP/IP
 RW> loaded on it.  I can ping back and forth between 4 machines (WFWG,
 RW> NT, W95, OS/2 4.0), they all seem to be talking to each other that
 RW> way, so I figure I'm close.  But no machines can see the WFWG machine
 RW> (or connect to it) and the WFWG cant see or connect to the others.
 RW> There all on the same domain (turtil) and the machine name refer's to
 RW> the op system, so there shouldnt be a conflict..
The domain name in the TCP/IP setup has nothing to do with the domain name 
(or workgroup name) in the network settings for Netbios/Netbeui type setup.
If you want to connect from one machine to another using drive letters, you 
either have to use some sort of Netbios setup (including Netbios over TCP/IP 
- a bit more complicated).  TCP/IP will not give you that (and I will leave 
out NFS type systems for now).
The most common WFWG networking protocol is Netbeui - setup that on your WFWG 
machine.  Set up (if not already) Netbuei or Netbios on the other machines.  
Use the same domain name (this is not the TCP/IP domain name!  However, it 
can be the same name as used for TCP/IP) on all machines.  Use different 
workstation names.  Use the same logon name and password.  This should allow 
you to share drive resources easily and transfer files.  Note that the WFWG 
resources may not show up in the OS/2 browser and vice versa; use fully 
qualified UNC names on the command line such as 'NET USE X: 
\\WFWGMACH\DRIVE1'.
TCP/IP - for transferring files, you have to use FTP - and the receiving end 
has to run a FTP daemon or server.
Regards, Alec
--- FleetStreet 1.12 NR
---------------