BH>> When the OS/2 box boots, it reports that NetBIOS is loaded, yet, 
 BH>> I don't see the OS/2 box in the Win95's network neighborhood.  
 BH>> Is there something on the OS/2 box that should be set to the 
 BH>> Win95's workgroup name?
 AH>> Yes - the domain name on the OS/2 box should be set to the same 
 AH>> name as the workgroup name on the Win95 box.  [...]
 BH> I'm missing something somewhere.  In tcp/ip configuration, the OS/2
 BH> box has a hostname of 'mt1' and a domain name of 
 BH> 'medtechnet.com'. [...]
You're missing the fact that there are two completely separate "domain name"s 
on a typical OS/2 Warp 3.0 Connect or OS/2 Warp 4.0 installation, and that 
you have the wrong one.  The "domain name" that Alec is talking about is the 
domain name for OS/2 File and Print Client (a.k.a. OS/2 Peer a.k.a. OS/2 LAN 
Requester), which is configured when you installed OS/2, and can be altered 
(in OS/2 Warp 4.0) using the first page of the "Sharing and Connecting" 
notebook in your LAN Services folder.
The "domain name" that you configure with the TCP/IP settings notebook is 
something completely separate, and in this case is the wrong one if you are 
looking for the OS/2 equivalent to what Windows 95 calls a "workgroup".
Incidentally, you appear to be using the same string for your NetBIOS domain 
("workgroup") name as for your TCP/IP domain.  This is probably not a good 
idea, for the simple reason that TCP/IP domain names do not necessarily 
follow the same rules as NetBIOS names.  They have dots in them, and tend to 
be rather long.  As Alec said, a NetBIOS domain name should be 1 to 8 
alphanumeric characters.
 ¯ JdeBP ®
--- FleetStreet 1.19 NR
---------------