System Error 1326 has occurred

[dw3284]

Can anyone offer advise on how I can resolve the error
msg. I'm getting?

Some Background:

I have a home network with a 4 systems. The main system
(we'll call this SystemX) is has all the main connections
(printer, dsl, cdrw, etc.) SystemX is running Windows XP
Professional. I'm trying to get my laptop (Let's call
this SystemY) which is running Windows 2000 Profesional
to connect to SystemX so that I can use the printer. I
was informed that I have to establish a trusted
connection and the best way to do that is to just mount a
shared drive from SystemX (TEMP) to SystemY. So, I have
been issuing the following command on SystemY:

net use * \\SystemX\TEMP * /USER:Administrator

This worked like a charm for a while, but then something
changed (don't ask me what... download of XP updates, new
software installs, etc.) and I can no longer use this
command. As a result I can no longer get to my printer on
SystemX.

The Error msg I get back is:

System Error 1326 has occurred
Logon failure: unknown user name or bad password.

However, when I go to SystemX, I can login just fine with
the specified login and password and the rights on the
TEMP directory are wide open.

Can anyone offer any insight or just point me in the
right direction to troubleshoot what is going on here?

Thanx in Advance.

--D

 

[Steven L Umbach]

Make sure that the built in ICF firewall on XP Pro did not get
enabled. Make sure that administrator password is correct from system y
[password is case sensitive] . You could also try enabling log on event
auditing on system x and then examine Event Viewer for any clues. I am not
sure what kind on network file sharing you have set up - classic or simple.
You also may need to enable the guest account if using simple file sharing
[not generally recommended way to share files though]. Another possibility
if none of the above helps is that you may need to disable smb signing on
the two computers if enabled. There are four "digitally sign communications"
security options in Local Security Policy - try disabling all on both
machines and rebooting. -- Steve

http://www.wown.com/j_helmig/winxppro.htm