Alan Wright <>


>> It seems way over complicated for a home lan user.  And I suppose that
>> isn't where it is targetted either.
> Have you tried using something based on the example on that page:
>       idmap add unixuser:terrym

I wasn't much able to follow it as I said.
Where does that bit go... does it get written somewhere, is it a
cmd from the terminal prompt?

>> I get rejected sometimes on cifs shares... not at other times.
> See the comment on guest access below.

>> My working windows uid is different than solaris uid but I do have a
>> windows user on every windows machine with the same name as my solaris
>> user.  It used to be necessary to do that just to make windows
>> networking work with other windows machines.
> That was never necessary (on Windows or Solaris).  If the names don't
> match, you may have to provide an appropriate name (and password)
> that is valid on the server from which you are mapping the share.
> If an first authentication fails, you may be granted guest access,
> which will possibly result in being denied access to files based
> on the ACLs.

It may not have been absolutely necessary on windows but many many
user have found (I mean before the advent of windows 7) it necessary
to have a like named user on all the windows machines involved in
networking ... that is if you wanted to have smooth sailing and not
have to diddle around too much.

Some of the experts and semi-experts that have populated the newsgroup 
microsoft.public.windowsxp.* and its forrunners..
Have posted that as a solution to windows networking problems for yrs.


> Making the names and passwords the same on both client and server
> tends to simplify things but it is not a requirement.

I could not tell from your input if the answer to my question was yes
or what.  Whatever that input was you posted:

   idmap add winuser: [...]

Is that something that is found in a file used for mapping windows
names to unix user names? 

cifs-discuss mailing list

Reply via email to