Technical article 100035

Windows 95 asks for a password when I try to map a drive.

OpenServer 5.0.0OpenServer 5.0.2

Written · Last revised

Problem

I am trying to map a local drive on a Windows 95 client to a drive on an AFPS server. When I choose to map the drive, I get prompted for a password; the system will not accept any password I provide.

Solution

The following steps will help in resolving the password problem.
They involve checking the system from both the Windows 95 side
and the AFPS side.  In the examples provided, the Windows 95
machine has been named "CLIENT" and the AFPS server has been
named "SERVER".  In addition, Windows 95 "CLIENT" machine has
an ip address of 132.147.209.41, and the AFPS server "SERVER"
has an ip address of 132.147.193.105:
Machine         Name           ip Address
-------         ----           ----------
Windows 95      "CLIENT"       132.147.209.41
AFPS server     "SERVER"       132.147.193.105
IMPORTANT: It is also assumed that the client login domain
           is the same as the server domain; make sure that
           this is the case.
From Windows 95 ("CLIENT"):

1. Remove the user "<username>.PWL" file in \WINDOWS directory.

In the \WINDOWS directory is a file with the format "<username>.PWL". This file stores the local user password for initial Workgroup logins. This file should be removed.

2. Make sure all logins are validated by the server.

From Windows 95, select Start-> Settings-> Control Panel-> Network. Then select "Client for Microsoft Windows" and click on "Properties". Make sure that the property "Log on to Windows NT Domain" is checked; this will make sure that the login is validated by the server.

3. (For routed IP networks only): Check client "LMHOSTS" file.

If you are using routing, make sure the \WINDOWS\LMHOSTS file has the correct information about the AFPS server:

132.147.193.105  SERVER   #DOM:<domain name>

NOTE: If the Windows client is also configured to use DNS, The LMHOSTS file must also include the following line:

132.147.193.105  "<server DOMAIN name>    \0x1c"  #PRE

The domain name must be in uppercase.

IMPORTANT: To temporarily resolve a bug in Windows 95, the number of characters in the domain name _plus_ the number of spaces before the "\0x1c" should be _exactly_ 15. For example, if the domain is "SALES", there should be 10 spaces between "SALES" and "\0x1c" because "SALES" has five characters.

4. Check the IP address and net mask.

From Windows 95, select Start-> Settings-> Control Panel-> Network. Then select the appropriate network protocol (usually TCP/IP) and choose "Properties". Make sure the IP address and net mask are correct for your system.

From the AFPS server ("SERVER"):

NOTE: If you have SCO OpenServer 5.0.0, make sure that both the rs500d and net100 supplements are installed. If you have SCO OpenServer 5.0.2 no supplements are needed.

1. Try to log in as "Administrator".

Run "net logon" on the AFPS side, and try to log in as "Administrator" by pressing <Return>. If you can log in, then there is a problem with the specific account, and you should check the user information (2). If logging in to the "Administrator" account also fails, check the routing and NetBios information (2,3) and CLIENT side information (1-3).

2. Check user information.

Run "net user <username>". You will get output similar to the following:

Username                     anita
Full Name                    Anita Nobel
Comment                      Anonymous ftp access to flight
User's comment
Country code                 000 ( System Default)
Privilege level              USER
Operator privileges          None
Account active               Yes
Account expires              Never
Password last set            06/24/96 12:48 PM
Password expires             08/05/96 12:48 PM
Password changeable          06/24/96 12:48 PM
Password required            Yes
User may change password     Yes
Workstations allowed         All
Maximum disk space           Unlimited
Logon script
Home directory
Last logon                   Never
Logon hours allowed          All
Group memberships            *Domain Users

It is important to make sure the account is active ("Account active: Yes"); if it is not then you can activate the account with the following command:

net user [user] /ACTIVE:yes

3. (For routed IP networks only): Check server "/etc/lmhosts" file.

If you are using routing, make sure the /etc/lmhosts file has correct information about the Windows 95 client:

132.147.209.41  CLIENT

If the /etc/lmhosts file must be modified then either the system must be rebooted or dlnbhosts(ADMN) must be run to update the NetBIOS host table.

4. (For NetBIOS only): Check NetBIOS configuration.

If you are using NetBIOS, check the information name (especially the host information) in the file /etc/default/nbconf to make sure it refers to your system:

NB_HOST=SERVER
NB_ADDR=132.147.193.105
NB_BROADCAST=132.147.193.255

See also

user(net), lmhosts(SFF), dlnbhosts(ADMN)

From the Xinuos technical article database, record 100035. Reproduced with permission. The original is at www.sco.com/ta/100035, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.