MORE INFORMATION
IBM's LAN Server is based on the core Microsoft LAN Manager code,
using the same data communications protocol (NetBEUI) and the same
file and print sharing protocol (server message block--SMB). This
similarity makes it easy for LAN Manager/WfW clients to interoperate
with IBM LAN Servers.
LAN Server uses aliases and the domain controller in ways that require
you to maintain accounts on both the LAN Manager/WfW environment and
LAN Server, and to add sharenames to LAN Server resources. Once you
have done this you can access LAN Server resources.
METHOD 1
To access LAN Server 1.3 shared resources, follow these steps:
- One or more WfW machines on your LAN must select the LAN Server
domain for WORKGROUP Name. This may sound odd but it has to do
with the VBROWSE service WfW implements, which is sophisticated
but not fully compatible with LAN Server 1.3.
- You must configure WfW for LAN Manager access and logon to a LAN
domain (as though you are running LAN Manager, which of course
is what LAN Server 1.3 is based upon): in the CONTROL PANEL
select NETWORK, and make the configuration change in the
Networks--LAN Manager dialog box.
- These two steps allow you to LOGON to the LAN Server. To have
access to LAN Server shared resources you first must create a
sharename. In the IBM LAN Server environment an alias equals
what we in a LAN Manager/WfW environment call a sharename.
For example: in a LAN Server environment you may type in
NET USE H: PCHOME, but in a LAN Manager/WfW environment you must
type in the full resource name--NET USE H: \\SERVER1\PCHOME.
Aliases are usually created by default on the LAN Server
machine, but sharenames must be added manually.
After completing these steps, reboot. You now should be able to
logon and link to any resources.
By default, clicking on the domain name from a file manager screen
(that is, from a graphical user interface net connection) does NOT
expand into the file servers. To get a list of the sharenames you can
connect to, type \\SRVNAME in the path box (in the example below,
\\SERVER1) but remember that being able to connect does not mean you
have access rights for the files. Use the access control lists on the
server to see which files you have rights to.
Once you are connected, set up your links. Here is an example:
H: \\SERVER1\PCHOME
O: \\SERVER1\OS2APPS
P: \\SERVER1\DOSAPPS
T: \\SERVER1\TEMPDATA
LPT1 \\PSERVER1\QMS
LPT2 \\PSERVER1\LJETSI
\\SNASRV\IPC$ (for comms server)
Once they are set up, WfW automatically reestablishes them (and logs
on) during startup.
If you have the same userid on two servers, you can access resources
just as if you were logged onto both. The user in the example above
could be using resources on SNASRV, such as its DCA/MS communications
server for the session, and linked to a local home drive on \\SERVER1.
Remember: if you have accounts on several machines, you must
synchronize your passwords to avoid security problems.
If the WfW password and LAN Server password are not the same, you
may be prompted to store the LAN Server password in the WfW
password list. This is due to some of the original authors'
proprietary software/hardware.
METHOD 2
An alternate method for achieving communication between WfW and LAN
Server 1.3 is to install the IBM LAN Support drivers (the DXM*.*
drivers) on the WfW client and perform a NET START FULL before
starting Windows.
This uses the real mode redirector, which has different capabilities
(less available memory, etc.), but it is useful in environments where
3270 emulation is required, because the IBM LAN Support Program
drivers also support the DLC protocol, which is often used to support
3270 emulators such as IBM Personal Communications 3270, Attachmate,
etc.