Installing POWERLan 3.22 in Win95, Win98 and WinNT environments.

General Information

For POWERfusion customers, we strongly recommend using Microsoft Networking on the PC instead of POWERLan and migrating from POWERfusion to Fusion95 on UNIX. Windows98, Windows95 and NT users gain features and functionallity by moving from POWERfusion to Fusion95.

Obtaining POWERLan 3.22

To obtain version 3.22 of POWERLan, go to ftp://ftp.perftech.com or ftp://ftp.april.se and download the latest version of POWERLan. Follow the instructions and create the installation diskettes.

Pre-installation procedures

Do NOT try to install any of the downloaded software until you have performed the following steps.

• Uninstall all eventual earlier versions of POWERLan, remove all references to POWERLan from the AUTOEXEC.BAT.
• Let W95 or NT find your network board and install the Microsoft Networking. Windows typically installs all the necessary drivers, protocols and the Client for Microsoft Networks using NetBEUI and/or TCP/IP. At this point you just want to verify that Windows finds your network adapter and that it works correctly. You should now be able to verify and make sure that your board driver is an Enhanced Mode 32-bit NDIS version 3 driver.
• If you have problems at this stage, don't try installing POWERLan, it requires a working 32-bit NDIS driver to function correctly. If you have two Win95 or NT machines on your network they should now see each other. Use the Windows Explorer to see the other machine.
• If you have an old Network Adapter, Windows may not be able to use it and neither will POWERLan. Check with your board vendor to supply the correct NDIS drivers for your board.

Once you have verified that the boards and drivers work, you can proceed installing POWERLan.

Installation of POWERLan

You have now two choices, just install the 32-bit POWERLan NetBIOS for Win95 or NT to gain access to your POWERLan servers, or make a complete POWERLan installation to get the POWERLan logon services etc. In either case you should start with the installation of the POWERLan NetBIOS as follows:

• Insert diskette 1.
• In control panel ADD PROTOCOL, click HAVE DISK and let the PTNETBIOS install. Make sure it binds properly. The first diskette contains everything needed for Win95 and NT.
• Sometimes you will find that the PTNETBIOS binds to the dial-up adapter, in this case remove the dial-up connection and reinstall. Once POWERLan has been successfully installed, the dial-up services can be reinstalled.
• Restart your machine.

At this point you should be able to access your POWERLan servers using the Client for Microsoft Networks.

• In Windows Explorer, click TOOLS and MAP NETWORK DRIVE.
• Enter the server and resource names as usual, i.e. \\servername\resource. Note that the browsing does not work at this stage. To be able to browse your POWERLan resources you will have to proceed and make a complete installation of POWERLan.

Also at this stage you can connect to POWERLan servers running POWERLan as well as Win95 or NT servers running NetBEUI or TCP/IP. You can also connect to POWERfusion machines running the PT NetBIOS as well as Fusion95 machines running TCP/IP.

If you want to use the POWERLan logon and browsing facilities you should now install the rest of POWERLan:

• Insert diskette 1.
• Run INSTALL.EXE
• Follow the instructions. This is the same as installing on a Windows 3.1 machine.

Special information for POWERfusion users.

POWERfusion users should be aware of the possibilities to migrate into TCP/IP networking using Fusion95. This provides a UNIX server fully compatible with Windows95 and NT and the Microsoft CIFS specification. It includes support for such features as long filenames. Fusion95 includes the full featured AniTa terminal for telnet connection.

Using Fusion95 in parallel with POWERfusion provides a simple way to make a smooth transition into the TCP/IP networking world. Look for more info at http://www.april.se and contact april@april.se for information regarding special pricing for migration packages.

Accessing your POWERfusion host using AniTa.

AniTa may have difficulties finding the POWERfusion host due to the fact that the PTNETBIOS may be bound to any LAN Adapter number. The number is a little unpredictable and you may have to try all the available numbers. Use the AniTa General Settings menu and try different adapter numbers.

The following Microsoft clients have a default configuration that requires the server to support encrypted passwords over the LAN.

• Windows NT 4.0 with SP3
• Windows 95 with VREDIR update (VRDRUPD.EXE)
• Windows 98

POWERfusion version 3 does not support Windows password encryption (it only supports UNIX password encryption) and thus requires plain text passwords to be enabled in these Windows platforms. The next three sections describe how to enable plain text passwords in each of these clients.

Connecting to SMB/CIFS servers (such as POWERfusion and LAN Manager for UNIX) with a plain text password fails after upgrading to Windows NT 4.0 Service Pack 3.

This is because the SMB redirector in Service Pack 3 handles passwords differently than previous versions of Windows NT. Beginning with Service Pack 3, the SMB redirector will not send a plain text password unless you add a registry entry to enable unencrypted passwords.

This applies to both NT Server and NT Workstation.

This will cause an error such as:
SYSTEM ERROR 1240: The account is not authorized to logon from this station

Resolution

To enable plain text passwords, modify the registry in the following way:

WARNING: Make sure you know how to run the registry editor correctly. Using it incorrectly can cause serious problems.

1. Run Registry Editor (REGEDT32.EXE).
2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:
   \system\currentcontrolset\services\rdr\parameters
3. Click Add Value on the Edit menu.
4. Add the following:
   Value Name: EnablePlainTextPassword
   Data Type: REG_DWORD
   Data: 1
   
5. Click OK and then quit Registry Editor.
6. Shut down and restart Windows.

More Information

For more information see the Microsoft Knowledge Base article: Q166730.

For more information about Window NT, Service Pack 3 and The Registry see the relevent Microsoft documentation.

Connecting to SMB/CIFS servers (such as POWERfusion and LAN Manager for UNIX) with a plain text password fails after upgrading Windows95 with Microsoft's VRDRUPD.EXE update.

This is because the new SMB redirector handles passwords differently. With this update, the SMB redirector will not send a plain text password unless you add a registry entry to enable unencrypted passwords.

Resolution

To enable plain text passwords, modify the registry in the following way:

WARNING: Make sure you know how to run the registry editor correctly. Using it incorrectly can cause serious problems.

1. Run Registry Editor (REGEDIT.EXE).
2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:
   /HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/VxD/VNETSUP
3. From the Edit menu, select:
   New - DWORD
4. Rename the entry to:
   EnablePlainTextPassword
5. Set its value to:
   1
6. Click OK and then quit Registry Editor.
7. Shut down and restart Windows.

Connecting to SMB/CIFS servers (such as POWERfusion and LAN Manager for UNIX) with a plain text password fails from Windows98.

This is because the SMB redirector, by default, requires passwords to be encrypted. With this version of Windows, the SMB redirector will not send a plain text password unless you add a registry entry to enable unencrypted passwords.

Resolution

To enable plain text passwords, modify the registry in the following way:

WARNING: Make sure you know how to run the registry editor correctly. Using it incorrectly can cause serious problems.

1. Run Registry Editor (REGEDIT.EXE).
2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:
   /HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/VxD/VNETSUP
3. From the Edit menu, select:
   New - DWORD
4. Rename the entry to:
   EnablePlainTextPassword
5. Set its value to:
   1
6. Click OK and then quit Registry Editor.
7. Shut down and restart Windows.

Back to April's Home Page

Webmaster: keith@april.se