As root, install the samba RPM (neither the common nor client are necessary)

rpm -Uvh .... to do the install

Have a look at /etc/services.  Check that swat is listed at the end.

Edit the inetd.conf file and enable swat by uncommenting the swat line (probably at the end of the file)

Restart the inet deamon (inetd).  Get the pid of inetd using ps ax | grep inet.  Then kill -HUP <pid>

Then open a browser on localhost:901.  You are now looking at SWAT!

Configure SAMBA and start the services

========================================
Windows NT SP3 and 98 Client SAMBA Problem
    (Original here)

So; you have been a good person, and applied the Windows NT Service Pack 3 and now you can no longer connect to your SAMBA
server.

     The account is not authorized to login from this station

... and that's all you get now...

How to fix it Microsoft's (and the easy) way...

Well, Microsoft have decided that it will now ONLY send the password to the SMB server (SAMBA in our case) in encrypted form.
Unfortunately, SAMBA wants to see the password in plain text format. Fortunately, they did provide a fix for this, but you will have to
modify your registry on NT to get around the problem.

From the README.TXT that comes with NT Service Pack 3:

     3.6 Unencrypted Passwords No Longer Sent by Default
     ---------------------------------------------------
     Connecting to SMB servers (such as Samba and LAN Manager for UNIX)
     with an unencrypted (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 unencrypted passwords differently than
     previous versions of Windows NT. Beginning with Service Pack 3, the
     SMB redirector will not send an unencrypted password unless you add
     a registry entry to enable unencrypted passwords. For information
     on how to modify the registry, search the Microsoft Knowledge Base
     at http://www.microsoft.com/kb/ for the following article: Q166730.
     This article also contains information on how to change the
     Service Pack setup process so that unencrypted passwords are
     enabled after the Service Pack is installed.

Everything you need to know as to how to fix this evil little problem is described in their document called With Unencrypted Password
SP3 Fails to Connect to SMB Server .
 

Update for Windows 98

On the Windows 98 CD under \tools\mtsutil there is a file called "Ptxt_on.inf". Right mouse click on it and choose install. Reboot your
box, and you should be good to go!

Thanks to Oscar Miranda for this hint.
 

How to fix it the right way

With later releases of SAMBA, there is a file called docs/ENCRYPTION.txt that explains how to get SAMBA to work with the
encrypted passwords. I have done this and it works fine. Click here to download the latest version of SAMBA if you have to re-install it.
In older versions you had to also download the libdes libraries, but this is no longer needed according to the docs/ENCRYPTION.txt file.
Just remember to use the "encrypt passwords = yes" in the [global] section.
 

The Results

I have now got things working again after my installation of SP3, but not as well as it was before. Before SP3 I was prompted for my
password on the SAMBA server just the once for my 4 mounts; but now it asks for the password for each mount.

Fixed: a bit...

I have been running a Netware 32 Client (for my Novell mounts here at work) and found that if the NT name of my PC is the same as my
Netware logon id, then I had this problem. Now I am prompted only the once for my SAMBA password (even though it IS the same as
my Netware password.

I also found that by changing the name of the PC to be different to my Netware login name, I also got rid of those banner pages on my
Netware printouts that I was previously unable to remove.

Return to my Home page or sign my Guest Book if you found this helpful.
 

RESOLUTION

   Check with the vendor of the SMB server product to see if there is a way to support encrypted
   password authentication, or if there is a newer version of the product that adds this support.

   Alternatively, to enable unencrypted (plain text) passwords for the SMB client on Windows NT 4.0
   Service Pack 3 and newer systems, modify the registry in the following way:

   WARNING: Enabling this will allow unencrypted (plain text) passwords to be sent across the network
   when authenticating to an SMB server that requests this option. This can lessen the overall security
   of an environment and should only be done after careful consideration of the consequences of plain
   text passwords in your specific environment.

   WARNING: Using the registry editor incorrectly can cause serious, system- wide problems that may
   require you to reinstall Windows NT. Microsoft cannot guarantee that any problems resulting from
   the use of the registry editor can be solved. Use this tool at your own risk.

      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 NT.