On 17 Oct 2002 09:20:36 -0600
Kathy Vaughan <[EMAIL PROTECTED]> wrote:
> I apologize in advance if this question has already been asked. I've
> done some poking around in various HOW-TOs and archives, but I
> cannot find the exact answer to my question.
>
> I am trying to configure SAMBA 2.25 in Webmin 1.020 in RedHat 8.0.
> Here is the situation:
>
> - Computer A is a Windows 2000 computer that is trying to connect to
> Computer B, which is running RedHat 8.0/SAMBA 2.25. The SAMBA server
> is running on Computer B. Computer B has one share, "Drive_F", which
> is mapped to the mount point /mnt/Drive_F (which is /dev/hdb7).
> /dev/hdb7 is mounted and is browseable on Computer B. Both computers
> belong to the workgroup named "WORKGROUP". Computer A has "NetBIOS
> over TCP/IP" enabled.
>
> - Computer B has two users defined for SAMBA: user1 (me) and user2
> (the user for Computer A). No other users exist in the SAMBA user
> list in Webmin. Computer B has Lokkit running at "Low" security.
> Authentication is set to "User Level". Guest access is disabled.
>
> What is happening so far:
>
> - Computer A can see Computer B in Network Neighbourhood; however,
> if the user tries to view the shares for Computer B, the following
> message occurs:
>
> "\\ComputerB is not accessible. The network path was not found"
>
> - If Computer A tries to map to \\ComputerB\Drive_F and provide the
> SAMBA username and password, the following error occurs:
>
> "The network folder specified is currently mapped using a different
> username and password. To connect using a different username and
> password, first disconnect any existing mappings to this network
> share."
>
> Followed by:
>
> "The mapped network drive could not be created because the following
> error has occured:
> The credentials supplied conflict with an existing set of
> credentials."
>
> Note that the share was not mapped to begin with on Computer A.
>
> I have tried the following:
>
> - Changing the password for user2 so that it matches the user's
> password in Windows 2000.
> - Mapping the user's Linux username to his Windows username.
> - Enabling guest access.
> - Setting it so that no password is required for user2.
> - Setting user2's account to "Workstation Trust Account".
> - Adding user2 and user2's group to "Valid Users" and "Valid
> Groups", respectively, for the share "Drive_F".
>
> The SAMBA server was restarted after implementing each of these
> changes. In every case the same errors mentioned above occured.
> Except for the addition of the user and group to the share, all the
> changes made above were discarded after the errors occured.
>
> If Computer B reboots into Windows 2000, both computers can connect
> to eachother and browse eachother's shares.
>
> I would appreciate any suggestions on how to get Computer A to
> connect to the share on Computer B. While I have read the man pages
> for SAMBA and looked through the troubleshooting sections on their
> website, I cannot seem to solve this problem. I am unfortunately
> very new to Linux, so I apologize if this is "old hat" to the people
> on this list.
>
> Thank you in advance for any help the list can provide.
>
>
>
>
Make sure that your user login names in Win2000 and RedHat are the
same, and that the Win2000 login password is the same as the RedHat
Samba password if you are using the login names as basis for access to
the shares.. Also, check that the Samba users ID number in RedHat's
/etc/passwd file match those in the /etc/samba/smbpasswd file ( or it
could be just /etcsmbpasswd.)
I have had instances where the regular Rehat /etc/passwd UID of user
"Bob" and Samba's /etc/samba/smbpasswd UID for user "Bob" did not
match; keeping that user "Bob" from mapping shares ( kept getting
"wrong password" messages on the MS Windows machine.)
There is good troubleshooting read for Samaba in
/usr/share/doc/samba<version>/docs/textdocs/DIAGNOSTICS.txt
Best,
Tom
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
