5 replies
Greetings,
CAUSE:
This behavior can occur for any of the following reasons:
Your password list (.pwl) file is damaged.
A service or program that loads during the startup process conflicts with another service or program.
You are using user profiles.
There is a hardware conflict on your computer.
A hardware driver on your computer is missing or damaged.
If profiles are enabled, Windows may not be able to contact the primary domain controller's Netlogon share when looking for a Config.pol file. (Windows checks for a Config.pol file even if policies are not used.)
Your primary domain controller (PDC) is not local to your Windows 95/Windows 98 clients.
A single user profile is corrupted.
Your network adapter is not correctly seated.
You are using a reserved word for your user name.
(continued in comments...)
.
.
RESOLUTION
To resolve this issue, use the following methods. After each method, test to see if the issue is resolved. If the issue continues to occur, use the next method.
Damaged Password List File
To re-create your password list file, use the following steps.
NOTE: If you are using a personal certificate, you should export it before renaming your .pwl file. If you do not do so, it may be unavailable when you send e-mail messages. For more information, see the following article in the Microsoft Knowledge Base: Q190296 Unable to Use Personal Certificates in Outlook Express
Click Start, point to Find, and then click Files Or Folders.
In the Named box, type *.pwl, and then click Find Now.
Right-click the Username.pwl file, and then click Rename, where Username is the name you use to log on to Windows.
Rename the Username.pwl file to Username.old, and then press ENTER.
Restart Windows.
When your computer restarts, you are prompted for a user name and password. If you want, you can choose to create a null password. If you create a null password, you are no longer prompted to log on when Windows starts. To create a null password, leave the password box blank, click OK, and then click OK to confirm the password.
The preceeding is from Microsoft article Q178084, "Error Message: MPREXE Not Responding". Cut and paste this link to see the whole article. There are also additional links to more articles on the subject. (REMOVE SPACES from the pasted URL if they snuck in)
http://support.microsoft.com/support/kb/articles/Q178/0/84.asp
Good luck,
Maxwell
by shanghai sam
by baziite
win95/winNT/TCP_ip is a messy combination ..the best I can suggest is to upgrade to win98 if TCP/IP is a must .If you cannot upgrade to win98 then on a small non-routed network changing to NETBEUI can do the job .
Good Luck
by sknobloc
Upgrading is in progress, however, this is a very large network (6000+ users).
Thanks,
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending