Hi Rich,
 RW> Maybe you can point me in the right direction..
 RW> I'm working on the same basic thing as Don.  I have a 
 RW> WFWG machine I have to get a large number of files off 
 RW> of.  I have MS's TCP/IP loaded on it.  I can ping back 
 RW> and forth between 4 machines (WFWG, NT, W95, OS/2 4.0), 
 RW> they all seem to be talking to each other that way, so 
 RW> I figure I'm close.  But no machines can see the WFWG 
 RW> machine (or connect to it) and the WFWG cant see or 
 RW> connect to the others.
It sounds like you have the Network cards, their drivers and TCP/IP 
configured on all platforms ok, if each machine can PING all the others... To 
get WFWG talking, you need to have the SMB (Server Message Block) technology 
environments configured to handle this the same on all systems. 
SMB technology is the basis behind things like WORKGROUPS and OS/2 PEER 
networking, both of these use SMB as their main transport service. There are 
differences in the 2 methodologies, but they have the same origins and are so 
similar the differences are not relevant here.
 RW> There all on the same domain (turtil) and the machine 
 RW> name refer's to the op system, so there shouldnt be a 
 RW> conflict..
In your situation, because you have 2 communications protocols running that 
each use the term DOMAIN NAME, you need to ensure that all machines have them 
set up appropriately for each communications methodology they are using. 
The TCP/IP DOMAIN NAME, and the SMB DOMAIN NAME are actually totally 
different things, although they are used in a fairly similar manner. The 
TCP/IP DOMAIN NAME is something that looks like -
        www.ibm.com
and the SMB DOMAIN name is something like
        IBMPEERS        (OS/2 default one)
The default SMB DOMAIN name for Windows environments is different to the OS/2 
one, check that these names are the same on BOTH machines........pk.
--- Maximus/2 3.01
---------------