cifs client configuration problems

Lamar Coit_1 — Thu, 05 Jun 2003 19:19:13 GMT

I am new to cifs client and have read some of the posts and configure guides, but I am still unable to simply mount a windows 2000 share to our hp-ux server running 11i. I have the following questions:
- Is there any configuration that has to be done on the Win2k side, aside from creating a share and making sure I have access to that share? I assumed that cifs is ok on the win2k side or do we need to do something on that side?

- I did not install the Pam NTLM since all I want to do is connect to a share and from what I read this is optional - is that ok?

- Any other suggestions would be helpful.,ss there anything that needs to be set on the windows 2000 server side?

Any help would be greatly appreciated, thanks in advance.

Re: cifs client configuration problems

Steven E. Protter — Thu, 05 Jun 2003 19:29:04 GMT

The most important thing is to set up an account for the HP machine on the windows Primary domain controller.

This account needs to have appropriate access to the windows shares involved. You might need to log on to a windows box using that ID to validate the permissions.

There may be a doc you missed here but I don't think so.
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x698c44f56197d711abdc0090277a778c,00.html

Good Luck

3 1/2 hours till pumpkin land.

SEP

Re: cifs client configuration problems

Geoff Wild — Fri, 06 Jun 2003 02:53:25 GMT

If you have a Windows domain, and all you want to do is share files on the HP-UX box, then you don't really need to add the HP-UX box to the domain....

Just set:

security = server
encrypt passwords = Yes
preferred master = False
domain master = False
keepalive = 0
password server = YOURPDC, YOURBDC

That way your Windows domain does all the authenticating - the users need an Unix id = to their NT ID....or, set up a username.map:

username map (G)
This option allows you to specify a file containing a mapping of usernames from the clients to the server. This can be used for several purposes. The most common is to map usernames that users use on DOS or Windows machines to those that the UNIX box uses. The other is to map multiple users to a single username so that they can more easily share files.

The map file is parsed line by line. Each line should contain a single UNIX username on the left then a '=' followed by a list of usernames on the right. The list of usernames on the right may contain names of the form @group in which case they will match any UNIX username in that group. The special client name '*' is a wildcard and matches any name. Each line of the map file may be up to 1023 characters long.

The file is processed on each line by taking the supplied username and comparing it with each username on the right hand side of the '=' signs. If the supplied name matches any of the names on the right hand side then it is replaced with the name on the left. Processing then continues with the next line.

If any line begins with a '#' or a ';' then it is ignored

If any line begins with an '!' then the processing will stop after that line if a mapping was done by the line. Otherwise mapping continues with every line being processed. Using '!' is most useful when you have a wildcard mapping line later in the file.

For example to map from the name admin or administrator to the UNIX name root you would use:

root = admin administrator

Or to map anyone in the UNIX group system to the UNIX name sys you would use:

sys = @system

You can have as many mappings as you like in a username map file.

If your system supports the NIS NETGROUP option then the netgroup database is checked before the /etc/group database for matching groups.

You can map Windows usernames that have spaces in them by using double quotes around the name. For example:

tridge = "Andrew Tridgell"

would map the windows username "Andrew Tridgell" to the unix username "tridge".

The following example would map mary and fred to the unix user sys, and map the rest to guest. Note the use of the '!' to tell Samba to stop processing if it gets a match on that line.

!sys = mary fred
guest = *

Note that the remapping is applied to all occurrences of usernames. Thus if you connect to \\server\fred and fred is remapped to mary then you will actually be connecting to \\server\mary and will need to supply a password suitable for mary not fred. The only exception to this is the username passed to the password server (if you have one). The password server will receive whatever username the client supplies without modification.

Also note that no reverse mapping is done. The main effect this has is with printing. Users who have been mapped may have trouble deleting print jobs as PrintManager under WfWg will think they don't own the print job.

Default: no username map

Example: username map = /usr/local/samba/lib/users.map

Use SWAT to configure (login as root):

http:\\yourhpbox:901

Rgds...Geoff

topic Re: cifs client configuration problems in Operating System - HP-UX

cifs client configuration problems

Re: cifs client configuration problems

Re: cifs client configuration problems