Debug or trace Celerra --> NIS server user authentication queries
Hello,
I have set up our NS80 to use a nearby NIS server for CIFS user authentication but
get a 'Sorry, you entered an invalid username or password.' popup on my MacOS X
desktop when trying to connect to a CIFS server on the Celerra.
Is there a way (ypcat, ypmatch, ...) of making the Data Mover report on success or
failure of NIS queries, including the arguments provided ?
The system is not in production yet so I can enable debug level diagnostics if needed.
I set up the NIS parameters (domainname, server address) in the Celerra GUI, modified
the nsswitch.conf on the Data Mover to "passwd: nis files" and made for "Retrieve NIS user
and group names without a domain association" (page 28 of "Configuring EMC Celerra
User Mapping")
$ server_nis server_2 -status
returns the expected information : service running, server IP address OK, domainname OK.
I should add there is a second CIFS server on this Celerra but this ooperates in a VDM, coupled with an external AD controller. This runs on a separate IP address.
Could there be interference ?
When setting up quotas for my account using the Celerra GUI, my correct Unix uid was
retrieved, so something correct must be getting back from the NIS server.
I am wondering what query is actually done for authenticating users.
The Celerra doesnt use NIS (or hosts file) for CIFS authentication - as in user/password
we either need an AD domain controller or use a standalone CIFS server with local Celerra user accounts (Windows not NIS/hosts) for that
The way CIFS works you cant do SMB with the password encryption and UIDs that Unix provides. If you were to do that you would have to drop to an old WfW era dialect that doesnt support files larger than 4GB, ACLs, VDMs, CAVA, .. And you would have to configure your clients to allow clear-test passwords see UNIX or SHARE authenticifcation mode and its restrictions in the Celerra Manuals on more why you dont want to use that
in the CIFS context NIS is only used for user mapping but not for authentication
Thank you for helping us A LOT further on this issue.
Your statement that CIFS is a User Mapping and no Authentication mechanism was an absolute eye-opener.
It looks like "local files" is the next best method in our environment, requiring pushing a 50,000 entry file to the Data Mover.
I know how to do this using 'server_file -put" from a Control Station CLI session, but since the (periodically regenerated) file resides on another system, can we automatically (rcp,scp) that file to the Control Station and 'rsh/ssh' the 'server_file -put' without providing password ?
Yesterday I tried installed a ssh public key in .ssh/authorized_keys but that was clearly not enough. Guess the sshd config must be modified too and sshd on the CS restarted. How ?
But then you could just use NIS - both require UNIX CIFS authenication mode
I would suggest to really look at all the restrictions that has and see if there isnt any other way. See the "Configuring CIFS on Celerra" manual - esp. pages 13/14 For example no Unicode most probably means you cant use non-ASCII characers Plus the UNIX and SHARE auth is very old code - I wouldnt count on it being supported forever
I think it would be best to talk to an EMC NAS NAS expert in your area about how your environment looks like and what the requirements are.
Other option would be to use NFS
Or some third party software that bridges between a domain controller and LDAP
bottom line - for modern SMB to work it requires pass-through authentification - i.e the client connects to the Celerra and sends its user/domain info plus the encrypted password the Celerra then in turns sends it to the responsible Windows domain controller, who checks it and gives us the users credentials (SIDs and so on) So the Celerra (or any other modern CIFS server) needs a domain controller since the Unix password enryption is one-way and different from the Windows way we cant just take the Unix encrypted one, find the cleartext and encrypt it again to send it to the Windows DC as well as other reasons
Using NIS for user validation (UNIX user authentication mode) would be mimicking the current setup and I would already be happy with that.
Current setup = a Sun Solaris 9 server attaching Veritas volumes from STK SAN and making those available via NFS (very limited number of clients) and Samba (thousands of desktops).
Consultancy with a regional EMC NAS expert is planned for next week.
I tried to switch CIFS user authentication from the default NT to UNIX but
Would the following elements intervene with my attempts to switch user authentication mode to UNIX ?
- another CIFS server, fully integrated in a Windows AD, running in a VDM ?
- "I18N mode = UNICODE" on my standalone CIFS server ? (how to change this ???)
page 25 of "Configuring and Managing CIFS on EMC Celerra", p/n 300-007-526 has some notes on the link between internationalization and NT user authentication
I did not come across a 'internationalization' option while create the file systems (which are still empty save for test data, so they can be re-made without much trouble)
Rainer_EMC
6 Operator
•
8645 Posts
366
0
Posted July 9th, 2009 06:00
we either need an AD domain controller or use a standalone CIFS server with local Celerra user accounts (Windows not NIS/hosts) for that
The way CIFS works you cant do SMB with the password encryption and UIDs that Unix provides.
If you were to do that you would have to drop to an old WfW era dialect that doesnt support files larger than 4GB, ACLs, VDMs, CAVA, ..
And you would have to configure your clients to allow clear-test passwords
see UNIX or SHARE authenticifcation mode and its restrictions in the Celerra Manuals on more why you dont want to use that
in the CIFS context NIS is only used for user mapping but not for authentication
hope that helps
Rainer