Hi,
Sorry. My earlier reply was not entirely correct. Add to this....
For win95 at least we have to make a registry entry to correct this problem.
Hope this helps in Windows ME.
I'm attaching a txt file which explains setup for 95 and NT
Murali
----- Original Message -----
> From: Verma Amit <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, May 16, 2001 2:26 PM
> Subject: [LIH] Smaba Conf
>
>
> > DEar All,
> > I had configured samba.But when I access the
> > server through Windows ME it says
> > " Resource \\ip address\IPC$
> > password =
> > "
> > When I enters the password it will not
> > authenticated.
> > It is not asking me for the User name and password.
> > What should I do.
> > Amit
> >
> >
> > =====
> > Amy
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Auctions - buy the things you want at great prices
> > http://auctions.yahoo.com/
> >
> > _______________________________________________
> > linux-india-help mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/linux-india-help
>
!==
!== WinNT.txt for Samba release 2.0.5a 22 Jul 1999
!==
Contributors: Various
Password Section - Copyright (C) 1997 - John H Terpstra
Printing Section - Copyright (C) 1997 - Matthew Harrell
Priting Info - Copyright (C) 1997 - Frank Varnavas
Updated: October 16, 1997
Status: Current
Subject: Samba and Windows NT Password Handling
=============================================================================
There are some particular issues with Samba and Windows NT.
Passwords:
==========
One of the most annoying problems with WinNT is that NT refuses to
connect to a server that is in user level security mode and that
doesn't support password encryption unless it first prompts the user
for a password.
This means even if you have the same password on the NT box and the
Samba server you will get prompted for a password. Entering the
correct password will get you connected only if Windows NT can
communicate with Samba using a compatible mode of password security.
All versions of Windows NT prior to 4.0 Service Pack 3 could negotiate
plain text (clear text) passwords. Windows NT 4.0 Service Pack 3 changed
this default behaviour so it now will only handle encrypted passwords.
The following registry entry change will re-enable clear text password
handling:
Run regedt32.exe and locate the hive key entry:
HKEY_LOCAL_MACHINE\system\CurrentControlSet\Services\Rdr\Parameters\
Add the following value:
EnablePlainTextPassword:REG_DWORD=1
Alternatively, use the NT4_PlainPassword.reg file in this directory (either
by double clicking on it, or run regedt32.exe and select "Import Registry
File" from the "Registry" Menu).
The other major ramification of this feature of NT is that it can't
browse a user level non-encrypted server unless it already has a
connection open. This is because there is no spot for a password
prompt in the browser window. It works fine if you already have a
drive mounted (for example, one auto mounted on startup).
=====================================================================
Printing:
=========
When you mount a printer using the print manager in NT you may find
the following info from Matthew Harrell <[EMAIL PROTECTED]>
useful:
------------
I noticed in your change-log you noted that some people were
still unable to use print manager under NT. If this is the same problem
that I encountered, it's caused by the length of time it takes NT to
determine if the printer is ready.
The problem occurs when you double-click on a printer to connect it to
the NT machine. Because it's unable to determine if the printer is ready
in the short span of time it has, it assumes it isn't and gives some
strange error about not having enough resources (I forget what the error
is). A solution to this that seems to work fine for us is to click
once on the printer, look at the bottom of the window and wait until
it says it's ready, then clilck on "OK".
By the way, this problem probably occurs in our group because the
Samba server doesn't actually have the printers - it queues them to
remote printers either on other machines or using their own network
cards. Because of this "middle layer", it takes an extra amount of
time for the NT machine to get verification that the printer queue
actually exists.
I hope this helped in some way...
=====================================================================
Printing Info:
--------------
From: Frank Varnavas <[EMAIL PROTECTED]>
Subject: RE: Samba as a print server
When an NT client attempts to connect to a printer on a non-NT print
server the attempt is failed with an error, something like:
"You have insufficient access to your computer to perform the
operation because a driver needs to be installed"
This is because domain users must have 'Power User' status on the
desktop to connect to printers on a non-NT print server.
This error occurs regardless of whether the driver in question is
already installed or not. What it really means is that the server is
a non-NT server and the client does not have permission to create
printers locally. Apparently when a connection to a non-NT print
server is made the printer is defined locally. Such an action can be
performed by either a local administrator or a Power User.
Unfortunately there is no way to limit the powers of a Power User, nor
is there any way to grant the Printer Creation right to another group.
This permission policy is documented in PSS database WINNT, ID Q101874
Frank Varnavas ([EMAIL PROTECTED])
!==
!== Win95.txt for Samba release 2.0.5a 22 Jul 1999
!==
Copyright (C) 1997 - Samba-Team
Contributed Date: August 20, 1997
Last Update: August 20, 1997
Subject: Windows 95 and Samba Interoperability
===============================================================================
Password Handling:
------------------
Microsoft periodically release updates to all their operating systems. Some of
these are welcomed while others cause us to change the way we do things. Few
people like change, particularly if the change is unexpected. The best advice
always is to read the documentation provided BEFORE applying an update.
One of the recent Win95 updates (VRDRUPD.EXE) disables plain text (also called
clear text) password authentication. The effects of this updates are desirable
where MS Windows NT is providing the password authentication service. This
update is most undesirable where Samba must provide the authentication service
unless Samba has been specifically configured to use encrypted passwords _AND_
has been linked with the libdes library.
If the above conditions have not been complied with, and you are using Samba,
then Windows 95 clients will NOT be able to authenticate to a Samba server.
To re-enable plain text password capabilities AFTER applying this update
you must create a new value in the Windows 95 registry.
Either foillow the following procedure or just double click on the
file Win95_PlainPassword.reg for an easier way to do this.
Procedure:
1) Launch the Registry Editor as follows:
Click on: /Start/Run
Type "regedit" and press enter.
2) Double click on: HKEY_LOCAL_MACHINE
3) Locate the following Key:
/HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/VxD/VNETSUP
4) From the menu bar select Edit/New/DWORD Value
5) Rename the entry from "New Value #1" to:
EnablePlainTextPassword
6) Press Enter, then double click on the new entry.
A dialog box will pop up and enable you to set a value.
You must set this value to 1.
-------------------------------------------------------------------------------
Windows 95 Updates:
-------------------
When using Windows 95 OEM SR2 the following updates are recommended where Samba
is being used. Please NOTE that the above change will affect you once these
updates have been installed.
There are more updates than the ones mentioned here. You are referred to the
Microsoft Web site for all currently available updates to your specific version
of Windows 95.
Kernel Update: KRNLUPD.EXE
Ping Fix: PINGUPD.EXE
RPC Update: RPCRTUPD.EXE
TCP/IP Update: VIPUPD.EXE
Redirector Update: VRDRUPD.EXE
Also, if using MS OutLook it is desirable to install the OLEUPD.EXE fix. This
fix may stop your machine from hanging for an extended period when exiting
OutLook and you may also notice a significant speedup when accessing network
neighborhood services.
-------------------------------------------------------------------------------
The above password information was provided by: Jochen Huppertz <[EMAIL PROTECTED]>
