[indiana-discuss] Are there known headaches with cifs connections

[Harry Putnam]

Haik Aftandilian <haik.aftandilian at sun.com>
writes:

>> Or any of the other share names shown above results
>> in a password prompt  but the passwd fails.
>
> Is the password you're entering longer than eight characters? I was
> helping someone with a similar problem which ended up being caused
> by password length.

No, its 7 characters.

And after wiping the slate and starting over something really
different is now happening.

The cifs server doesn't appear in the network places on windows but if
I type the server like \\host in the location box on windows explorer,
the shares are then displayed and my windows user is allowed access
with NO passwd prompt.

I don't think that should happen.  

There is a windows user with the same name as the owner of the shares.

Windows client user can create new files/directories but cannot remove
files already on the share. Or files added now from the osol side by
owner of share (user reader)

Two things wrong... Not prompted for passwd and user does not have
full access to create/delete.

I can't help but feel that after hours of reading and days of messing
with getting cifs shares operational, something is wrong for this to
seem so complicated.  Seems to constantly be some little jot or tittle
that needs fixing.

Apparently there is yet some more settings that need to be made for
windows client user to have same rights as osol user.

And to make a passwd required.

Why is my Windows client user allowed to write to the share without
being prompted for a passwd?  How is it that Windows client user can
read/write but not delete files put there by osol user.  But osol user
can delete files put there by windows client.

I guess I'm getting a bit aggravated with this...Even when I seem to
make some progress, something more turns up to sink yet more time
into.