What flavour of windows? (95/98/nt)
I had a 'similar' problem but while trying to connect to a smb share from
NT. So I went hunting at www.microsoft.com. Here is what I found out:
With Unencrypted Password SP3 Fails to Connect to SMB Server Last
reviewed: May 29, 1998 Article ID: Q166730
The information in this article applies to: Microsoft Windows NT
Workstation version 4.0 with Service Pack 3 Microsoft Windows NT Server
version 4.0 with Service Pack 3 SYMPTOMS After upgrading your Windows NT
4.0 computer to Service Pack 3 (SP3), you are unable to connect to certain
non-Microsoft Server Message Block (SMB) servers and you may receive the
following error message: System error 1240 has occurred. The
account is not authorized to login from this station.
CAUSE Some
non-Microsoft SMB servers only support unencrypted (plain text) password
exchanges during authentication. The SMB client redirector in Windows NT
4.0 Service Pack 3 and later handles unencrypted passwords differently
than previous versions of Windows NT. Beginning with Windows NT 4.0
Service Pack 3, the SMB redirector does not send an unencrypted password
during authentication to an SMB server unless you add a specific registry
entry. In previous versions, the client would automatically negotiate
downward to unencrypted (plain text) authentication if requested from the
server.
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. Run Registry Editor (Regedt32.exe). From the HKEY_LOCAL_MACHINE
subtree, go to the following key:
\SYSTEM\CurrentControlSet\Services\Rdr\Parameters Click Add Value on the
Edit menu. Add the following: Value Name: EnablePlainTextPassword
Data Type: REG_DWORD Data: 1 Click OK and then quit Registry Editor.
Shut down and restart Windows NT. To enable unencrypted (plain text)
passwords in an automated setup, modify the registry in the following way:
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. Add the following
line to the Product.Add.Reg section of the Update.inf file:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters,
"EnablePlainTextPassword", 0x10001, 1
Last reviewed: May 29, 1998
1998 Microsoft Corporation. All rights reserved. Terms of Use.
I can now connect to the smb shares on my linux box, but using plain text
passwords. Hope this sheds some light on your situation.
-Ajay
On Sun, 20 Sep 1998, Gabe Harriman wrote:
Anytime I try to access a personal smb share on my linux box it asks me for
a password. I type the correct password in every time, and windows gives me
a "Password is incorrect" error. When I check my smb.log it says:
WARNING: You probably have a broken set of glibc2 include files - disabling
sysv shared memory
for each time I try to access one of those personal shares. Has anyone ever
experienced this problem or have any advice for me to fix this? Thanks you.
Gabe
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
