Hi Steve,
SS> Does anyone use MSLANMAN for OS/2 successfully, and if so, how can I get
SS> it working?
I have never seen MSLANMAN so I can't comment about that.
SS> Does anyone have any other ideas for a networking client that will allow
SS> OS/2 to logon to a Windows NT server?
I use this type of connectivity daily, and its easy. OS/2 Warp Connect can do
that out of the box, the most difficult part will probably be making sure
that the DOMAIN NAME for the OS/2 PEER configuration matches the NT DOMAIN
NAME, otherwise it will not be easy to see the NT resources on the OS/2
system.
There are 2 ways to solve this problem -
1. The Easy way is to change the defaut setting for OS/2 in the
OS/2 PEER configuration from IBMPEERS (the default value) to
whatever DOMAIN NAME is used on the NT system.
2. OS/2 can be a member of up to 4 DOMAINS at a time, however you
cannot set more than 1 via the standard configuration utilities.
You can leave the default name of IBMPEERS, and add an extra
DOMAIN NAME manually by modifying the file \IBMLAN\IBMLAN.INI
(on your OS/2 partition). In the [requestor] section of that
file you will find a line -
DOMAIN = IBMPEERS
Add a NEW line after that one that reads -
OTHDOMAINS = XXXX, YYYY
where XXXX is the NT DOMAIN NAME you need to reach. Extra DOMAINS
can also be reached by adding , YYYY ...
At work I use Warp and connect to other OS/2, Win311, Win95, Win NT, IBM MVS
Hosts and various flavours of *nix (SCO, Linux, Sun) boxes, using TCP/IP no
problems. For those platforms that require SMB (Server Message Block) support
(such as Workgroups style resource sharing), I use NETBIOS over TCP/IP to
reach them. This means I can share resources on machines at the other of the
country (or world) over our corporate router links.
I hope this helps............pk.
--- Maximus/2 3.01
---------------
* Origin: Another Good Point About OS/2 (3:772/1.10)
|