On 01/24/08 11:07, Jerry Backlin wrote:
> Alan,
>
> You were spot on, the /var/smb/smbpasswd file was empty. It seems the
> upgrade replaced it for some reason.
>
This looks like a bug in the SUNWsmbsr package, where upon upgrade the
smbpasswd file is blown away.
Jerry, could you file a bug (over at bugs.opensolaris.org) indicating
the fact this file is blown away upon upgrade?
Thanks
--jc
PS: if you look at the pkgmap for the SUNWsmbsr package you see that
/var/smb/smbpasswd is shown as a regular file, not as an editable file
and there is no indication it should be preserved (via the class field).
What needs to happen is this file needs to be preserved just like
/etc/passwd (see the SUNWcsr package for examples on how to fix the bug)
> Thanks a lot,
> Jerry
>
> Alan M Wright wrote:
>> Jerry Backlin wrote:
>>> Thanks Alan for your reply,
>>>
>>> I did what you suggested and it didn't change anything for me. I
>>> really appears that my solaris machine is
>>> in the workgroup (seen from Windows) but if I either try to map a
>>> drive from windows or browse the computers in the workgroup I been
>>> asked for username & password and when I enter it I been told:
>>> invalid password.
>>> Normally I should be able to at least see what shared resources are
>>> there without giving a password?
>>>
>>> I did put some additional info below but I'm not at all sure it is
>>> what you would need to understand what is going on.
>>
>> We are still working on the troubleshooting part of the admin
>> guide but there's a draft at
>>
>> http://opensolaris.org/os/project/cifs-server/docs/
>>
>> The output of 'sharectl get smb' and 'smbadm list' (which I see
>> below) are useful. Also /var/adm/messages, logs listed by
>> 'svcs -xv' and the idmap properties (svccfg -s idmap).
>>
>> Things you could try:
>>
>> Check that /var/smb/smbpasswd looks okay, i.e. has the appropriate
>> users in it. Just to be sure, ensure pam_smb_passwd.so.1 is in
>> /etc/pam.conf and set your password using the passwd command.
>> There's no reason this should have changed during an upgrade but
>> it shouldn't hurt to rule it out.
>>
>> Delete/rename the idmap database (/var/idmap/idmap.db) and restart
>> the idmap service. There was a recent database format change.
>>
>> Check the idmap properties (svccfg -s idmap) for inconsistencies
>> with the CIFS service.
>>
>> Run zpool upgrade and zfs upgrade to ensure that there are no
>> pool/fs version/feature dependency issues.
>>
>> If you experiment with the above, it is probably a good idea to
>> reboot to ensure that everything comes up consistently. The
>> SMF dependencies should force things to restart correctly but if
>> you get different results after a reboot, let us know so that we
>> can investigate.
>>
>> Alan
>>
>>> I'm working in storage marketing and converted my home server to
>>> solaris as a learning exersice for the upcoming
>>> announcements. Now you understand why my unix skills are a bit
>>> rusty....
>>>
>>> Any help is wellcome,
>>> Jerry
>>>
>>> svcadm restart smb/server
>>> # sharemgr start -P smb zfs
>>> # smbadm list
>>> security mode: workgroup
>>> workgroup name: JB-GROUP
>>> # sharemgr list -v
>>> default enabled smb nfs
>>> zfs enabled
>>> # sharemgr show -v
>>> default
>>> zfs
>>> zfs/JBpool/ZFS/W_backup
>>> backup=/zfs/W_backup
>>> zfs/JBpool/ZFS/W_kits
>>> kits=/zfs/W_kits
>>> zfs/JBpool/ZFS/W_media
>>> media=/zfs/W_media
>>> zfs/JBpool/ZFS/W_users
>>> users=/zfs/W_users
>>>
>>>
>>>
>>> Alan M Wright wrote:
>>>> There's not enough context here to be sure but this may be
>>>> the problem described in 6646629. Workaround:
>>>>
>>>> After restarting smb/server:
>>>>
>>>> sharemgr start -P smb zfs
>>>>
>>>> Alan
>>>> --
>>>>
>>>> Jerry Backlin wrote:
>>>>> I have a similar problem, where CIFS is not seen from the rest of
>>>>> the workgroup.
>>>>> It worked fine in b79 but after upgrade to b80 the shares are not
>>>>> seen anymore and when I try to mount the shares from windows I
>>>>> keep getting the login window over & over again.
>>>>> The protection of the shares is OK so that is not the problem (I
>>>>> think).
>>>>>
>>>>> # sharemgr show -vp
>>>>> default smb=() nfs=()
>>>>> zfs
>>>>> zfs/JBpool/ZFS/W_backup smb=()
>>>>> backup=/zfs/W_backup
>>>>> zfs/JBpool/ZFS/W_kits smb=()
>>>>> kits=/zfs/W_kits
>>>>> zfs/JBpool/ZFS/W_media smb=()
>>>>> media=/zfs/W_media
>>>>> zfs/JBpool/ZFS/W_users smb=()
>>>>> users=/zfs/W_users
>>>>> Should I wait for b81?
>>>>>
>>>>> Jerry
>>>>>
>>>>>
>>>>> This message posted from opensolaris.org
>>>>> _______________________________________________
>>>>> storage-discuss mailing list
>>>>> [email protected]
>>>>> http://mail.opensolaris.org/mailman/listinfo/storage-discuss
>>>>
>>>>
>>
>>
> _______________________________________________
> storage-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/storage-discuss
>
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
