windows domain and samba password

[Chris]

I have a samba server that a user is trying to access. It is running
Samba 2.2. The user has two computers. I did not set these computers
up, but one is a desktop that is NOT on the domain. The other is a
laptop that IS on the domain and I believe authenticates with it. The
computer NOT on the domain (desktop) is able to connect to the samba
server just fine. However, trying to connect to the server using the
same account on the laptop (on windows domain) results in an invalid
user/password message on both the client and on the samba server.

Does the computer being on the windows domain affect its ability to
connect to file servers that are not on the domain?


Thanks,

Chris

 

[Chuck]

I have a samba server that a user is trying to access. It is running
Samba 2.2. The user has two computers. I did not set these computers
up, but one is a desktop that is NOT on the domain. The other is a
laptop that IS on the domain and I believe authenticates with it. The
computer NOT on the domain (desktop) is able to connect to the samba
server just fine. However, trying to connect to the server using the
same account on the laptop (on windows domain) results in an invalid
user/password message on both the client and on the samba server.

Does the computer being on the windows domain affect its ability to
connect to file servers that are not on the domain?


Thanks,

Chris

Chris,

In general, a computer joined to a domain has access to resources in the domain.
That doesn't prevent its accessing resources outside the domain.

And in general, a computer running Samba should work OK with Windows Networking.
Other folks here have had success using Samba anyway. Is the Samba server
joined to the domain? If so, how does the desktop computer authenticate with
it? If not, how does the laptop authenticate with it?

 

[Chris]

Hi Chuck, thanks for responding. The Samba server is *not* on the
domain. Users authenticate to it via username/password that is locally
stored on the Samba server. I had assumed what you are saying is true,
but the only difference I could find was the domain issue. I'm not
saying the domain is the root cause, but I have been suspecting it has
something to do with that. The error message I get from Samba is:
smb_pam_passcheck: PAM: smb_pam_auth failed - Rejecting User jjtoy

 

[Chuck]

Hi Chuck, thanks for responding. The Samba server is *not* on the
domain. Users authenticate to it via username/password that is locally
stored on the Samba server. I had assumed what you are saying is true,
but the only difference I could find was the domain issue. I'm not
saying the domain is the root cause, but I have been suspecting it has
something to do with that. The error message I get from Samba is:
smb_pam_passcheck: PAM: smb_pam_auth failed - Rejecting User jjtoy

Yet you have 2 computers, one a domain member and the other a workgroup member.
Both using the same account / password local account. The workgroup member
using the local account successfully, the domain member using it but not
successfully. Right? Both computers are using the same local account, with
identical, non-blank password?

 

[Malke]

Yet you have 2 computers, one a domain member and the other a
workgroup member.
Both using the same account / password local account. The workgroup
member using the local account successfully, the domain member using
it but not
successfully. Right? Both computers are using the same local
account, with identical, non-blank password?

I've been watching this thread with interest. I don't have a definitive
answer, but it feels to me like the domain user and the local user must
not appear the same to Linux. Perhaps even though they have the same
name the user ID is different. I'm just guessing.

Why not try a workaround and create a new user account in Linux and in
Samba (as you know, you have to add the user in Samba after first
creating the user in the main Linux distro) for the domain user. Call
it jjtoy-domain or the like. Then see what happens. I realize this
isn't the most wonderful solution because you'd need to create the
matching user/pwd in Windows, too.

You might want to post in a newsgroup for your distro. Or possibly the
gurus in one of the MS server newsgroups will know. I use Samba all the
time on my mixed network and have set it up many times for clients
using a Linux file server, but I've never had any experience with Samba
and a Windows domain.

If you do find out, please post the solution because I'd love to know
the answer.

Malke