The steps shown in the following sections are required to connect a PC client to the AIX Fast Connect server.
To access the AIX Fast Connect server, each client PC must be configured for NetBIOS over TCP/IP (RFC1001/1002). This can be accomplished for the various clients as shown in the following sections.
Additionally, you might want to enable WINS support, DNS support, and/or gateway support for each client. If so, configure each as needed.
Note: You must be logged in as an Administrator.
You might also want to configure DNS, WINS Address, and Routing.
Note: You must be logged in as an Administrator.
You might need to install the TCP/IP protocol. TCP/IP is not included on the Windows 3.11 installation media. You can download a copy of Microsoft TCP/IP-32 3.11b from the Microsoft web site at www.microsoft.com.)
To set up the TCP/IP configuration, double-click on Microsoft TCP/IP-32 3.11b. Configure the IP Address, Subnet Mask, Default Gateway, WINS Server(s), DNS, and other options as needed. (LMHOSTS and DNS enablement are available as Advanced options.)
These protocols should have the same LAN adapter number and should match your TCP/IP interface.
Note: The default installation is IBM OS/2 NetBIOS. Be sure to add IBM OS/2 NetBIOS OVER TCP/IP if not already listed.
In addition to being able to ping the AIX Fast Connect server over TCP/IP, each client PC also must be able to resolve the NetBIOS name of the AIX Fast Connect server (the AIX Fast Connect servername) to an IP address. This can be done using UDP-Broadcast, LMHOSTS files, DNS, or WINS.
Note: This mechanism does not work across TCP/IP routers, gateways, etc. Larger networks typically use DNS or WINS.
The following is an example of editing an LMHOSTS file on Windows 95, Windows 98, or Windows 3.11. From the DOS prompt:
DOS> cd \windows DOS> edit lmhosts (LMHOSTS.SAM is included with Windows as an example.)
On a Windows NT or Windows 2000 machine, do the following:
NT> cd \winnt\system32\drivers\etc NT> edit lmhosts
After editing the LMHOSTS file, run the Windows PC command nbtstat -R.
During installation, the AIX Fast Connect servername defaults to match the AIX hostname.
Additionally, use the SMIT fast path smit smbcfghatt to set the WINS Address entry and Backup WINS Server for the AIX Fast Connect server. The AIX Fast Connect server uses these IP addresses to automatically register its NetBIOS servername with the WINS servers.
You can configure one or more AIX Fast Connect servers to act as NBNS/WINS servers. For more information, see NetBIOS Name Service.
At this point, if you have LMHOSTS, DNS, or WINS correctly configured, you should be able to ping from the client PC by using the NetBIOS server name.
AIX Fast Connect supports several different types of user authentication/access mechanisms. (See Basic User Administration and Advanced Server Administration.) Each client PC should be configured to match the AIX Fast Connect user-access scheme you have chosen for your network.
For ease of use, client PCs should be in the same Windows workgroup or NT domain as the AIX Fast Connect server (or vice versa). Windows 3.11, Windows 95, and Windows NT all use WORKGROUP as a default workgroup name, and AIX Fast Connect server initializes itself to use WORKGROUP, also. If your network uses NT domain login authentication, you can configure the AIX Fast Connect server to verify AIX Fast Connect access using the NT domain authentication servers.
Whether you use Workgroups or NT domains, access to AIX Fast Connect is managed by user security. You must set up AIX user accounts for each Windows user who is accessing AIX Fast Connect. It is easiest to use if the user accounts (and passwords) on AIX match the Windows or NT domain user accounts (and passwords).
Within the SMIT panel, enter the following:
Note: Use the OS/2 command LOGON to use NetBIOS services such as network browsing, NET VIEW, and NET USE.
For security reasons, Microsoft has disabled support for nonencrypted (plain text) network passwords in all recent versions of Windows (Windows 95C, Windows 98, Windows NT 4.0 w/ Service Pack 3, Windows 2000). If you want to use plain text passwords on your network, these clients must be upgraded with the following Registry patches.
Note: Microsoft has recommended the current System Registry be saved as a backup before any manual changes are made to it. For details, see Microsoft's technet web site.
REGEDIT4 ; Registry file to allow plaintext passwords on Windows 98 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\VNETSUP] "EnablePlainTextPassword"=dword:00000001
REGEDIT4 ; Registry file to allow plaintext passwords on Windows NT 4.0 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters] EnablePlainTextPassword=dword:00000001
Note: Even with the previous patch installed, all Windows NT 4.0 clients still require the user to type his/her password every time the user first connects to the AIX Fast Connect server (by browsing, mapping drives, etc.). Once the user is successfully connected, additional browsing or drive mapping operations proceed without hindrance. The initial "Password Invalid" message occurs because Windows NT 4.0 attempts to use encrypted passwords while connecting to AIX Fast Connect server, rather than plain text passwords.
AIX Fast Connect supports browser operations such as NET VIEW and Network Neighborhood (renamed My Network Places on Windows 2000). These operations show the user a list of file and printer shares exported by each server.
Network Neighborhood can also be used as a convenient way to map drives. (Right-click on a file share name, then select Map Network Drive from the pop-up menu.)
However, note the following limitations on network browsing:
Network browsing generally works best if the client PC and the AIX Fast Connect server are in the same workgroup/domain.
Normally, PC clients must define drive mappings to use the AIX Fast Connect-exported file shares. These drive mappings can be done from Windows or from the DOS command prompt.
You can use the following mechanisms to define/undefine mappings between PC drive letters and AIX Fast Connect file shares. For the sake of the following examples, assume that the NetBIOS servername is cifs01, and that file share apps is defined.
DOS> net help (help info for DOS) DOS> net use H: \\cifs01\home (pre-defined AIX Fast Connect share) DOS> net use F: \\cifs01\apps DOS> copy F:\oldfile H:\newfile (uses the mapped drives) DOS> net use F: /delete (delete the drive-mapping)
For printing, DOS and Windows mappings are somewhat different. For the following examples, assume that AIX Fast Connect server cifs01 has print shares netprint1 and pscolor defined.
For DOS applications, the following simple device-mappings can be used:
DOS> net use LPT1: \\cifs01\netprint1 DOS> net use LPT2: \\cifs01\pscolor
To test these DOS printer-mappings, use the following:
DOS> COPY text_file LPT1: DOS> COPY Postscript_file LPT2:
Note: During print-spooling, neither DOS nor AIX Fast Connect auto-convert Postscript to text, or vice versa; however, this auto-detection/auto-convert feature can be enabled using AIX print-spooling options, if desired.
For Windows applications, a Windows printer driver needs to be installed, and mapped to the network printer, as follows:
Test Windows printer-driver functionality by printing a test-file from any Windows application (for example, Notepad), or by using the "Print Test Page" feature as follows:
For Windows 3.11, install the desired printer driver through Control Panel, and use the Connect... button to map it to the AIX Fast Connect print share.
Windows 2000 clients are now supported using CIFS/SMB protocol on NetBIOS over TCP/IP. Network Logon is not yet supported for Windows 2000 clients.
AIX Fast Connect is compatible with the Windows Terminal Server program. This program allows multiple PC clients running Windows Terminal Client software to login to the Windows Terminal Server and establish a remote console session. Any network drive (or network printer) mapping made within that console session gets forwarded by Windows Terminal Server to other NetBIOS servers, as required.
Windows Terminal Server (and other similar terminal-server programs) must accomodate multiple net-mappings by multiple usernames, coming from multiple client PCs. Windows Terminal Server (and other terminal servers) can multiplex these requests to AIX Fast Connect using the following mechanisms:
Both of these mechanisms are supported by AIX Fast Connect version 3.0 and later.
To enable Windows Terminal Server support, set multiuserlogin=1.
Refer to your Windows Terminal Server documentation for specific information about setup and use of Windows Terminal Server and Windows Terminal Client.