Discussion Locked

IPC$ Password error.

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I just upgraded three of my systems with Win2K and one with Win XP. The others are Win 98SE. All systems have all the service packs installed.
This is a 6 system LAN on TCP/IP.

The problem is when I try to access the Win 2K or XP systems from the Win 98SE systems through Network Neiberhood I get a popup box that says,

Enter Network Password
You must supply a password to make this connection.
Resource \\"computer name\IPC$

I did not setup a password and can't find a way to change orfind it.

P.S. I can access the Win98SE systems from the Win2k and Win XP systems with no problems.
The Win 98SE is Fat32 and the others are NTFS format.

4 replies

by maxwell edison

You probably have a password conflict. (And a password can be blank and still have a conflict.) IPC stands for Inter-Process Communication and is how Windows systems communicate with one another. The most likely cause of this problem is that the ID you are using on the local system also exists on the system you are trying to contact, but the Passwords are different from one system to the other.

Verify that the passwords for that ID on the two systems are the same.

One very common sourceof this problem is a Win9x system that is trying to map a share on a WinNT (Win2k) system. If there is a user ID in the local user database on the WinNT system that matches the ID the user is logged into on the Win9x system, but the password is different, then this error occurs.

For example: User JOE logs onto a Win9x workstation using the ID JOE and the Password (blank). This ID and Password is validated by the PDC and the user is logged on. Then the user tries to map a share on another server named FILESERVER which is a member server of the domain. On the Local User Database of FILESERVER there is a local user ID for JOE with a Password of XYZ987. When the user tries to map the resource they get the error message listed above. The solution for this problem is to remove the user ID JOE from the Local User Database on FILESERVER or to change the password for JOE on FILESERVER to match the domain password.

This also applies to users who are on a Win9x system trying to connect to an NT system across the network, especially in the case of a Win9x user dialing into an NT system using RAS. If you log onto the Win9x system using the ID JOE and the Password (blank), then bring up a RAS connection using the ID JOE and the Password XYZ987, you will receive a prompt asking for a password for the IPC$ resource. In this case you need to log onto the Win9x system using the ID and Password that will be used in RA

by maxwell edison

.
.
Another possibility:

Recent versions of Windows won't allow connections to servers that request clear text passwords. To fix this, you need to add an entry to the registry. This can either be done by hand or by running a .reg file.

For Windows 95/98/ME:

Manual: Run regedit and locate the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\VNETSUP

Then add the following registry entry:

EnablePlainTextPassword:REG_DWORD=1
Automatic

See this link for more information and more options:

http://www.precedence.co.uk/nc/faq/client.html#clrpass

(REMOVE SPAES from the pasted URL.)

----------

Another possibility:

Under "Admintools" ==> "Local security settings" ==> "Local Policies" ==> "User rights Assignment"

there's on the right an entrance with the name "Deny acces to this computer for the network" and Guest is in that list remove Guest.

Best of luck and have a GREAT 2002!

Maxwell

by shanghai sam

Answer 1 was correct. It was that the user name on the 98SE system was not the same as the Win 2k and XP systems. The passwords were the same. This help was great! Thanks

This discussion is closed to new replies.