Sponsored Content
Full Discussion: Samba authentication issue
Operating Systems Solaris Samba authentication issue Post 302774115 by batas on Friday 1st of March 2013 07:54:11 AM
Old 03-01-2013
Samba authentication issue

Hi guys we have a running samba server and it works ok, issue came when our windows samba clients were upgraded to win7... some users cant login and some needs to enter their password 7x before they can login.

the net advise to set NTLVMv2 on the win7 security options it works on the users who cant login but to other users they have to enter their password 7x before they can login... is there any other solution to this

Upgrading our samba is however not an option Smilie we are using version 3
 

10 More Discussions You Might Find Interesting

1. AIX

LDAP user authentication issue

Hello everyone, hoping you can provide some incite with a little problem I'm having.. I have the LDAP client configured and running on my AIX 5.3 server, which is authenticating against an eDirectory LDAP server. I can login via LDAP no problems on the AIX server with newly created users,... (4 Replies)
Discussion started by: j_aix
4 Replies

2. SCO

Authentication problems with Active Directory/Samba/Winbind/Pam

Hi all. I'm having real trouble authenticating users against active directory for my SCO UnixWare 7.1.4 box running samba 3.0.24 (installed via Maintenance pack 4). I can list AD users/groups (after overcoming several hiccups) with wbinfo -g / wbinfo -u. I can use id to get a view an ad user ie:... (0 Replies)
Discussion started by: silk600
0 Replies

3. Red Hat

samba authentication

Hi friends, I have a requirement is to authenticate samba users seperately. 1. Linux samba server 2. Linux Client 3. Need to mount samba share on linux client permanently without providing credentials. 4. when user is accessing that mount point need to be prompted for credentials. ... (1 Reply)
Discussion started by: arumon
1 Replies

4. Solaris

SAMBA config / vintala Authentication

could someone Please post step-by step samba config on solaris 10 we use vintala as a authentication tool dont know how to config with vintala Thank You (0 Replies)
Discussion started by: Xterm2121
0 Replies

5. Solaris

solaris samba configuration without wins service from authentication window server/Active directory

Hi All, We are using solaris samba server for our company project to provide access to code to our development team.Recently our ICT has disabled wins service on Active directory due which user are not able to connect to samba share and they are getting error "No logon server available" as samba... (2 Replies)
Discussion started by: sahil_shine
2 Replies

6. Solaris

samba issue: one samba share without password prompting and the others with.

Hi All, I've been trying to configure samba on Solaris 10 to allow me to have one share that is open and writable to all users and have the rest of my shares password protected by a generic account. If I set my security to user, my secured shares work just fine and prompt accordingly, but when... (0 Replies)
Discussion started by: ideal2545
0 Replies

7. UNIX and Linux Applications

Samba authentication issue

Hi guys we have a running samba server and it works ok, issue came when our windows samba clients were upgraded to win7... some users cant login and some needs to enter their password 7x before they can login. the net advise to set NTLVMv2 on the win7 security options it works on the users who... (0 Replies)
Discussion started by: batas
0 Replies

8. HP-UX

SSH Authentication issue.

When I am trying to connect to a sever using ssh, I happen to see the following statements in the server side logs: none for user User rejected because it is unavailable password for user User accepted I am able to connect to the server, but I am getting that "rejected" message in logs. ... (16 Replies)
Discussion started by: chacko193
16 Replies

9. Red Hat

Samba share assess w/no authentication

RH 6.4 Samba 3.5.10. Joined a Windows AD (net rpc) I'm trying to create a public read-only share but regardless of the options I've tried users get prompted for a user/password. Can someone tell me whats wrong with my setup? I'm trying to make a whole filesystem that will contain installation... (0 Replies)
Discussion started by: dignarn
0 Replies

10. AIX

Samba 3.6 on AIX 7.1 - Windows 10 Access to AIX file shares using Active Directory authentication

I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users. The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies
d_passwd(4)							   File Formats 						       d_passwd(4)

NAME
d_passwd - dial-up password file SYNOPSIS
/etc/d_passwd DESCRIPTION
A dial-up password is an additional password required of users who access the computer through a modem or dial-up port. The correct pass- word must be entered before the user is granted access to the computer. d_passwd is an ASCII file which contains a list of executable programs (typically shells) that require a dial-up password and the associ- ated encrypted passwords. When a user attempts to log in on any of the ports listed in the dialups file (see dialups(4)), the login program looks at the user's login entry stored in the passwd file (see passwd(4)), and compares the login shell field to the entries in d_passwd. These entries determine whether the user will be required to supply a dial-up password. Each entry in d_passwd is a single line of the form: login-shell:password: where login-shell The name of the login program that will require an additional dial-up password. password An encrypted password. Users accessing the computer through a dial-up port or modem using login-shell will be required to enter this password before gaining access to the computer. d_passwd should be owned by the root user and the root group. The file should have read and write permissions for the owner (root) only. If the user's login program in the passwd file is not found in d_passwd or if the login shell field in passwd is empty, the user must sup- ply the default password. The default password is the entry for /usr/bin/sh. If d_passwd has no entry for /usr/bin/sh, then those users whose login shell field in passwd is empty or does not match any entry in d_passwd will not be prompted for a dial-up password. Dial-up logins are disabled if d_passwd has only the following entry: /usr/bin/sh:*: EXAMPLES
Example 1 Sample d_passwd file. Here is a sample d_passwd file: /usr/lib/uucp/uucico:q.mJzTnu8icF0: /usr/bin/csh:6k/7KCFRPNVXg: /usr/bin/ksh:9df/FDf.4jkRt: /usr/bin/sh:41FuGVzGcDJlw: Generating An Encrypted Password The passwd (see passwd(1)) utility can be used to generate the encrypted password for each login program. passwd generates encrypted pass- words for users and places the password in the shadow (see shadow(4)) file. Passwords for the d_passwd file will need to be generated by first adding a temporary user id using useradd (see useradd(1M)), and then using passwd(1) to generate the desired password in the shadow file. Once the encrypted version of the password has been created, it can be copied to the d_passwd file. For example: 1. Type useradd tempuser and press Return. This creates a user named tempuser. 2. Type passwd tempuser and press Return. This creates an encrypted password for tempuser and places it in the shadow file. 3. Find the entry for tempuser in the shadow file and copy the encrypted password to the desired entry in the d_passwd file. 4. Type userdel tempuser and press Return to delete tempuser. These steps must be executed as the root user. FILES
/etc/d_passwd dial-up password file /etc/dialups list of dial-up ports requiring dial-up passwords /etc/passwd password file /etc/shadow shadow password file SEE ALSO
passwd(1), useradd(1M), dialups(4), passwd(4), shadow(4) WARNINGS
When creating a new dial-up password, be sure to remain logged in on at least one terminal while testing the new password. This ensures that there is an available terminal from which you can correct any mistakes that were made when the new password was added. SunOS 5.11 2 Sep 2004 d_passwd(4)
All times are GMT -4. The time now is 11:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy