TIP: Click on subject to list as thread! ANSI
echo: os2lan
to: DAVID STANTON
from: PETER KNAPPER
date: 1996-09-22 12:44:00
subject: OS/2 Connect and NT Server

Hi David,
 DS> I have to get an OS/2 connect box to talk to the NT servers. The
 DS> IS people will tell me that the NT servers are running IP only, but
 DS> since we chose OS/2 for our development machine they won't support us
 DS> at all. Anyone who knows how to do this lemme know.....
Question - Are you SURE the NT box is running TCP/IP ONLY, or do your IS 
people mean you can only reach the NT environment using TCP/IP procotols 
because of a WAN/Router network that only passes TCP/IP? 
If you have any WFWG (or Win95) people accessing the same NT box, and they 
use the standard WFWG resource allocation and sharing methods, then you 
emulate that environment using Warp Connect!
If the connectivity is restricted because YOUR local LAN segment and the NT 
Server LAN segment are connected only via TCP/IP protocols, then you can 
solve the problem by using the "NETBIOS over TCP/IP" protocol (using either 
LAPS or MPTN) on the Warp machines AND the NT box, and route the TCP/IP 
protocol between the sites. I will assume this is really what you wish to do. 
If not, then please ignore the rest of this message.
I run several Warp Connect machines in one building and use NETBIOS over 
TCP/IP to connect to an NT box at a site 15 miles away, on a daily basis. and 
it works very well. Fortunately the router/WAN connection betweent the LAN 
segments is via a 2MB link so performance is not too bad.......;-) OS/2 Peer 
is happy, the NT box is happy, the routers are happy, but it DID take some 
work to get it running. 
The end result was the discovery that if you configure Warp Connect FROM 
SCRATCH to use "NETBIOS over TCP/IP" (using the default configuration for 
this protocol), it gets it right. If you UPGRADE an existing local 
LAN/NETBIOS environment to include "NETBIOS over TCP/IP", then the OS/2 
configuration program will probably get it wrong and NOT update the 
\IBMLAN\IBMLAN.INI file! I discovered this about 2 weeks after manually 
updating the files and getting things working.....;-(
If you have NETBIOS support already configured on your Warp machines, and are 
not too familiar with manually configuring the LAN protocols, then you are 
probably better off COMPLETELY removing ALL LAN connectivity/configuration 
from your OS/2 machines, and then adding it from scratch to include the 
"NETBIOS over TCP/IP" protocol. If built from an empty LAN configuration, it 
usually works fine. 
The only other trick to watch out for is to make sure your OS/2 Peer DOMAIN 
is matched to the NT DOMAIN, or that you configure MULTIPLE DOMAIN support 
(from what I have found, it only appears possible to do this by manually 
updating the IBMLAN.INI file). In my case the NT people changed the NT DOMAIN 
on me without warning and everything vanished until I discovered this minor 
detail.....;-)
If you need further details, then I can probably post my long-winded config 
instructions but they are fairly specific to our needs and some parts may not 
apply in your case.
I hope this starts you on the way to solving your problem...........pk.
--- Maximus/2 3.01
---------------
* Origin: Another Good Point About OS/2 (3:772/1.10)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.