Connecting Client PCs to AIX Fast Connect for Windows

AIX Version 4.3 System Management Guide: Communications and Networks

Connecting Client PCs to AIX Fast Connect for Windows

The steps shown in the following sections are required to connect a PC client to the Fast Connect server.

TCP/IP Configuration

To access the 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.

Windows 95, Windows 98 Clients

From the Start button, select Settings->Control_Panel->Network.
On the Configuration tabbed panel (initially shown), verify that the following entries exist:
- An entry for your networking-card (hardware driver)
- TCP/IP (protocol)
- Client for Microsoft Networks (client)
If any is missing, add it from your Windows 95 disks.
Click on the TCP/IP entry and select Properties. The TCP/IP Properties dialog box has several tabbed panels. Verify the following:

IP Address panel

Configure as needed. (For initial testing, you may find it convenient to manually specify unique IP addresses for each PC.)

Bindings panel

Select Client for Microsoft Networks.

Additionally, you may wish to enable WINS support, DNS support, and/or GATEWAY support for each client. If so, configure each as needed.
TEST the client's TCP/IP configuration by ping-ing (by IP address) from the client PC's DOS prompt to the Fast Connect server, and vice versa.

Windows NT Clients

Note: You must be logged in as an Administrator.

From the Start button, select Settings->Control_Panel->Network.
On the Services tabbed panel, verify that there are entries for the following services:
- Computer Browser
- NetBIOS Interface
- Workstation
If any is missing, add it from your Windows NT CD.
On the Protocols panel, add TCP/IP (if missing), then select Properties.
The TCP/IP Properties dialog box has several tabbed panels. Verify the following:

IP Address panel

Configure as needed. (For initial testing, you may find it convenient to manually specify unique IP addresses for each PC.)

You may also want to configure DNS, WINS Address, and Routing.
Test the client's TCP/IP configuration by ping-ing (by IP address) from the client PC's DOS prompt to the Fast Connect server and vice versa.

Windows For Workgroups (Windows 3.11) Clients

From group Network (within Program Manager), run Network Setup.
Verify that the following entries exist:
- Microsoft Windows Network (version 3.11) (network)
- An entry for your LAN adapter card (device-driver)
- Microsoft TCP/IP-32 3.11b (protocol)
You may 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 Microsoft's web site 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.)
Test the client's TCP/IP configuration by ping-ing (by IP address) from the client PC's DOS prompt to the Fast Connect server and vice versa.

OS/2 Clients

Install TCP/IP and NetBIOS support during OS/2 installation.
Use the TCP/IP Configuration program to verify and configure TCP/IP.
Use the Multi-Protocol Transport Services program (MPTS) to verify and configure the following protocols for your network adapter:
- IBM OS/2 TCP/IP
- IBM OS/2 NetBIOS OVER TCP/IP
These protocols should have the same LAN adapter number, which 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.)
Test the client's TCP/IP configuration by ping-ing (by IP address) from the client PC's DOS prompt to the Fast Connect server and vice versa.

NetBIOS Name Resolution

In addition to being able to ping the Fast Connect server over TCP/IP, each client PC also needs to be able to resolve the NetBIOS name of the Fast Connect server (the Fast Connect servername) to an IP address. This can be done using UDP-Broadcast, LMHOSTS files, DNS, or WINS.

UDP-Broadcast

The simplest NetBIOS name resolution (both in terms of setup and functionality) is UDP-Broadcast. No additional setup is required on the client PC as long as the client is on the same physical network segment (Ethernet, Token Ring, ...) as the Fast Connect server. The PC client broadcasts a UDP NetBIOS query to the local network, to which the Fast Connect server will respond.

Note: This mechanism does not work across TCP/IP routers, gateways, etc. Larger networks typically use DNS or WINS.

LMHOSTS files

Windows PCs can provide local LMHOSTS files for resolving NetBIOS names. Similar to /etc/hosts on AIX, each PC can have an LMHOSTS file to statically resolve NetBIOS names to IP addresses. (This mechanism might be unsuitable for DHCP environments or networks with many PC clients, because every LMHOSTS file must change whenever the Fast Connect servers IP addresses change.)

The following is an example of editing an LMHOSTS file on Windows 95, Windows 98, or Windows 311. From the DOS prompt:

DOS>  cd \windows
DOS>  copy lmhosts.sam lmhosts
DOS>  edit lmhosts

On a Windows NT machine, do the following:

NT> cd \winnt\system32\drivers\etc
NT>  copy lmhosts.sam lmhosts
NT>  edit lmhosts

For Windows 3.11 and Windows NT machines, you also must enable LMHOSTS under TCP/IP Properties.

Note: Edits to the LMHOSTS file may require a Shutdown/Restart of the client PC to properly take effect.

DNS

If your network has domain name service (DNS) for TCP/IP and your Fast Connect servername is registered in the DNS, then each PC-client can be configured to use DNS for NetBIOS name resolution. (This is default on Windows 95, but must be enabled for Windows NT under TCP/IP Properties.)

During installation, the Fast Connect servername defaults to match the AIX hostname.

WINS

Your Windows network may use Windows Internet Naming Service (WINS) for NetBIOS name resolution. Similar to DNS for TCP/IP, WINS allows NetBIOS service names to be resolved to IP addresses across multiple LAN segments. When this is the case, each client PC should be configured to use the WINS server(s) under TCP/IP Properties.

Additionally, use the SMIT fast path smit smbcfghatt to set the WINS Address entry and Backup WINS Server for the Fast Connect server. The Fast Connect server will use these IP addresses to automatically register its NetBIOS servername with the WINS servers.

At this point, if you have LMHOSTS, DNS, or WINS properly configured, you should be able to ping from the client PC by using the NetBIOS servername.

Workgroups, Domains, and User Accounts

For ease of use, client PCs should be in the same Windows workgroup or NT domain as the Fast Connect server (or vice versa). Windows 3.11, Windows 95, and Windows NT all use WORKGROUP as a default workgroup name, and Fast Connect server initializes itself to use WORKGROUP, also. If your network uses NT domain login authentication, you can configure the Fast Connect server to verify Fast Connect access using the NT domain authentication servers.

Whether you use Workgroups or NT domains, access to Fast Connect is managed by user security. You must set up AIX user accounts for each Windows user who is accessing 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).

On the Fast Connect server, use the SMIT fast path:
```
smit smbcfghatt
```
To use Workgroups, enter the workgroup name in the Domain Name field.
To use NT domain validation, enter the IP addresses for the NT domain authentication server(s) in the Passthrough Authentication Server and Backup Passthrough Authentication Server fields.
On PC clients running Windows 95 or Windows 98, select Start button -> Settings -> Control_Panel -> Network. On the Identification panel, enter the computer name for that PC.
To use Workgroups, enter the workgroup name in the Workgroup field.
To use NT domain validation, go to the Configuration tabbed panel, select Client for Microsoft Networks, and click on Properties. Check the NT domain checkbox, and enter the NT domain name.
On PC clients running Windows NT, make sure you are logged on as Administrator. Then:
1. Select Start button -> Settings -> Control_Panel -> Network.
2. On the Identification panel, select the Change... button.
3. Enter the Computer Name for that PC.
4. Enter the workgroup or domain name, as appropriate.
On PC clients running Windows for Workgroups, configuration for the workgroup occurs during Windows 3.11 install/setup, but can be changed in the SYSTEM.INI file, if necessary.
On PC clients running OS/2, configuration for the workgroup occurs during OS/2 installation, but can be changed in the DOMAIN parameter of IBMLAN.INI, if necessary.
Note: Use the OS/2 command LOGON to use NetBIOS services such as network browsing, NET VIEW, and NET USE.

Using Plain Text Passwords with Windows 98 or Windows NT 4.0 (Service Pack 3)

For security reasons, Microsoft has disabled support for nonencrypted (plain text) network passwords in Windows 98 and Windows NT 4.0 (with Service Pack 3 installed). If you want to use plain text passwords on your network, these clients must be upgraded with the following Registry patches:

To install the Windows 98 Enable Plain Text Passwords patch:

Use EDIT or the NOTEPAD accessory to create the following text file, named W98plain.reg, as a local file on the Windows 98 machine:

/REGEDIT4

; Registry file to allow plaintext passwords on Windows 98

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\VNETSUP]
"EnablePlainTextPassword"=dword:00000001

Using Windows Explorer, double click on the W98plain.reg file name in the directory where you saved it. This action will update the Windows Registry for that client to allow plain text passwords.
Shutdown/Restart the Windows 98 machine. (Shutdown/Restart is required for this patch to take effect.)

To install the Windows NT 4.0 Enable Plain Text Passwords patch,

Use EDIT or the NOTEPAD accessory to create the following text file, named NT4plain.reg, as a local file on the Windows NT machine:

/REGEDIT4

; Registry file to allow plaintext passwords on Windows NT 4.0, SP3

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters]
EnablePlainTextPassword=dword:00000001

Using Windows Explorer, double click on the NT4plain.reg file name in the directory where you saved it. This action will update the Windows Registry for that client to allow plain text passwords.
Shutdown/Restart the Windows NT machine. (Shutdown/Restart is required for this patch to take effect.)

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 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 is because Windows NT 4.0 attempts to use encrypted passwords while connecting to Fast Connect server, rather than plain text passwords.

Browsing the Network

Fast Connect 1.0 for AIX supports Browser operations such as Network Neighborhood and NET VIEW. 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:

To see the Fast Connect server in Network Neighborhood, a client PC needs to be able to see the Master Brower for the workgroup or domain for which that Fast Connect server is configured. (Fast Connect does not act as a browse master itself, but any Windows 95, Windows 98 or Windows NT clients in that workgroup/domain can perform the role.)
Network browsing generally works best if the client PC and the Fast Connect server are in the same workgroup/domain.
The browse list database that is maintained by the Master Browser is not always up-to-date. The list can show Fast Connect server names for servers that are currently down, off, physically disconnected, or otherwise unreachable. The Master Browser does not delete a server from the browse list until that servername's refresh timeout has expired, which could take several days. If a user tries to access that servername, though (by browsing share names, mapping drives, etc.), a disconnected Fast Connect server will be detected as unavailable.

Mapping Drives

Normally, PC clients will need to define drive mappings to use the 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 Fast Connect file shares. For the sake of the following examples, assume that the NetBIOS servername is cifs01, and that file shares apps and pcdata are defined.

From DOS:

DOS> net help	                   (help info for DOS)
DOS> net use H: \\cifs01\home     (pre-defined Fast Connect share)
DOS> net use F: \\cifs01\apps
DOS> copy F:\oldfile H:\newfile   (uses previous drive-mappings)
DOS> net use F: /delete           (delete the drive-mapping)

From Windows:

Find the Map Network Drive dialog box.
- Select Windows Explorer -> Tools -> Map Network Drive.
  or
- Right-click on Network Neighborhood and select Map Network Drive.
Select the desired drive (for example, F:) from the Drive: drop-down list, then
- Enter in the path: (for example, \\cifs01\apps).
  or
- Use the Shared Directories (browse tree) panel to select the network share desired.

Using Fast Connect Printers

For printing, DOS and Windows mappings are somewhat different. For the following examples, assume that 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

But to support printing from Windows applications, a Windows printer driver needs to be installed, and mapped to the network printer, as follows:

Select Start -> Settings -> Printers -> Add Printer.
Select Network Printer.
Enter the Fast Connect print share name (for example, \\cifs01\netprint1) or, use the browse list to select the desired print share.
Select the proper Windows printer driver for that network printer (for example, IBM 4039 Laser Printer PS), which will be installed from your Windows installation disks.

For Windows 3.11, install the desired printer driver through Control Panel, and use the Connect... button to map it to the Fast Connect print share.