Re: SAMBA problems on Debian 8.8

[Frank Miles]

On Sat, 15 Jul 2017 17:10:03 +0200, Jason Wittlin-Cohen wrote:

> You are running an out-of-date version of samba (2:4.2.14+dfsg-0+deb8u6
>  vs. 4.2.14+dfsg-0+deb8u7+b1).  In addition, you seem to be missing
> samba-common-bin,  samba-dsdb-modules, and python-samba, all of which are
> dependencies of samba.
> 
> Try 'sudo apt-get install --reinstall samba'
> 

Thanks, Jason - I had reinstalled samba-libs but not some other apparently
critical part of samba.  The --reinstall fixed it!

   -F

(Not the OP, just another still-running-jessie guy)

Re: SAMBA problems on Debian 8.8

[Marc Shapiro]

On 07/15/2017 08:09 AM, Jason Wittlin-Cohen wrote:
You are running an out-of-date version of samba 
(2:4.2.14+dfsg-0+deb8u6  vs. 4.2.14+dfsg-0+deb8u7+b1).  In addition, 
you seem to be missing samba-common-bin,  samba-dsdb-modules, and 
python-samba, all of which are dependencies of samba.


Try 'sudo apt-get install --reinstall samba'

If that doesn't include install the removed packages, run, 'sudo 
apt-get install samba-common-bin samba-dsdb-modules python-samba'


I, too, have been having problems that seem to point to samba.  Note 
that I am still running Jessie.


If I run 'sudo aptitude update' followed by 'sudo aptitude upgrade' I 
get the following:


-

The following packages will be upgraded:
  python-samba
The following partially installed packages will be configured:
  samba samba-common-bin
1 packages upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 0 B/1,016 kB of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?] y
Traceback (most recent call last):
  File "/usr/bin/apt-listchanges", line 29, in 
import anydbm
ImportError: No module named 'anydbm'
(Reading database ... 336173 files and directories currently installed.)
Preparing to unpack 
.../python-samba_2%3a4.2.14+dfsg-0+deb8u7+b1_amd64.deb ...

  File "/usr/bin/pyclean", line 63
except (IOError, OSError), e:
 ^
SyntaxError: invalid syntax
dpkg: warning: subprocess old pre-removal script returned error exit 
status 1

dpkg: trying script from the new package instead ...
  File "/usr/bin/pyclean", line 63
except (IOError, OSError), e:
 ^
SyntaxError: invalid syntax
dpkg: error processing archive 
/var/cache/apt/archives/python-samba_2%3a4.2.14+dfsg-0+deb8u7+b1_amd64.deb 
(--unpack):

 subprocess new pre-removal script returned error exit status 1
Traceback (most recent call last):
  File "/usr/bin/pycompile", line 35, in 
from debpython.version import SUPPORTED, debsorted, vrepr, \
  File "/usr/share/python/debpython/version.py", line 24, in 
from ConfigParser import SafeConfigParser
ImportError: No module named 'ConfigParser'
dpkg: error while cleaning up:
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/python-samba_2%3a4.2.14+dfsg-0+deb8u7+b1_amd64.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package.  Trying to recover:
dpkg: dependency problems prevent configuration of python-samba:
 python-samba depends on samba-libs (= 2:4.2.14+dfsg-0+deb8u6); however:
  Version of samba-libs:amd64 on system is 2:4.2.14+dfsg-0+deb8u7+b1.

dpkg: error processing package python-samba (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of samba:
 samba depends on python-samba; however:
  Package python-samba is not configured yet.

dpkg: error processing package samba (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of samba-common-bin:
 samba-common-bin depends on python-samba; however:
  Package python-samba is not configured yet.

dpkg: error processing package samba-common-bin (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 python-samba
 samba
 samba-common-bin

-

So far as I can tell, samba only exists on my system because smbclient 
is suggested by CUPS and since my wife sometime prints from her Windows 
laptop I want to leave it installed (is this correct?).


Trying to reinstall, or update any of the samba packages just gives me 
more of the same.  How do I resolve this?


At some point I will want to upgrade from Jessie to Stretch, but I need 
a clean system before I can attempt that.


Marc

[SOLVED (mostly)] Re: SAMBA problems on Debian 8.8

[Hans Kraus]

Thanks a lot to all who have helped and/or contemplated my problem.

After:
---
apt-get install --reinstall samba
apt-get install samba-dbg samba-doc
---
and installing the suggested packages too I see:

dpkg -l | grep samba
---
ii  libcrypt-smbhash-perl   0.12-4 
all  generate LM/NT hash of a 
password for samba
ii  python-samba 
2:4.2.14+dfsg-0+deb8u7+b1amd64Python bindings for Samba
ii  samba 
2:4.2.14+dfsg-0+deb8u7+b1amd64SMB/CIFS file, print, 
and login server for Unix
ii  samba-common 
2:4.2.14+dfsg-0+deb8u7   all  common files used by 
both the Samba server and client
ii  samba-common-bin 
2:4.2.14+dfsg-0+deb8u7+b1amd64Samba common files 
used by both the server and the client
ii  samba-dbg 
2:4.2.14+dfsg-0+deb8u7+b1amd64Samba debugging symbols
ii  samba-doc 
2:4.2.14+dfsg-0+deb8u7   all  Samba documentation
ii  samba-dsdb-modules 
2:4.2.14+dfsg-0+deb8u7+b1amd64Samba Directory 
Services Database
ii  samba-libs:amd64 
2:4.2.14+dfsg-0+deb8u7+b1amd64Samba core libraries
ii  samba-vfs-modules 
2:4.2.14+dfsg-0+deb8u7+b1amd64Samba Virtual 
FileSystem plugins
ii  vlc-plugin-samba 
2.2.6-1~deb8u1   amd64Samba plugin for VLC

---

systemctl status smbd.service:
---
root@robbe:/etc/samba# systemctl status smbd.service
● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd)
   Loaded: loaded (/etc/init.d/smbd)
   Active: active (running) since Sat 2017-07-15 17:45:27 CEST; 35min ago
  Process: 1906 ExecStop=/etc/init.d/smbd stop (code=exited, 
status=0/SUCCESS)
  Process: 1911 ExecStart=/etc/init.d/smbd start (code=exited, 
status=0/SUCCESS)

   CGroup: /system.slice/smbd.service
   ├─1920 /usr/sbin/smbd -D
   ├─1923 /usr/sbin/smbd -D
   └─3101 /usr/sbin/smbd -D

Jul 15 17:45:27 robbe smbd[1911]: Starting SMB/CIFS daemon: smbd.
Jul 15 17:45:27 robbe systemd[1]: Started LSB: start Samba SMB/CIFS 
daemon (smbd).
Jul 15 17:51:19 robbe smbd[2533]: pam_unix(samba:session): session 
opened for user kraush by (uid=0)
Jul 15 17:51:56 robbe smbd[2533]: pam_unix(samba:session): session 
closed for user kraush
Jul 15 17:53:57 robbe smbd[2568]: pam_unix(samba:session): session 
opened for user kraush by (uid=0)
Jul 15 17:54:19 robbe smbd[2568]: pam_unix(samba:session): session 
closed for user kraush
Jul 15 17:54:30 robbe smbd[2573]: pam_unix(samba:session): session 
opened for user kraush by (uid=0)
Jul 15 17:54:41 robbe smbd[2573]: pam_unix(samba:session): session 
closed for user kraush
Jul 15 17:55:51 robbe smbd[3101]: pam_unix(samba:session): session 
opened for user kraush by (uid=0)
Jul 15 18:07:30 robbe smbd[3101]: pam_unix(samba:session): session 
closed for user kraush
Jul 15 18:07:30 robbe smbd[3101]: pam_unix(samba:session): session 
opened for user kraush by (uid=0)

---

I can now again connect to the shares via the "Connect Network Drive"
window, choosing a drive letter and entering:
\\\.

I still do not see the Shares (on Windows 8.1) in the "Connect Network
Drive" window in the "Search" part.

Kind regards,
Hans

Am 15.07.2017 um 17:10 schrieb Jason Wittlin-Cohen:

BTW, here is what I see when I run dpkg -l | grep samba:

jason@storage-server:~$ dpkg -l | grep samba
ii  python-samba  2:4.2.14+dfsg-0+deb8u7+b1 
   amd64Python bindings for Samba
ii  samba 2:4.2.14+dfsg-0+deb8u7+b1 
   amd64SMB/CIFS file, print, and login server for Unix
ii  samba-common  2:4.2.14+dfsg-0+deb8u7 
  all  common files used by both the Samba server and client
ii  samba-common-bin  2:4.2.14+dfsg-0+deb8u7+b1 
   amd64Samba common files used by both the server and 
the client
ii  samba-dbg 2:4.2.14+dfsg-0+deb8u7+b1 
   amd64Samba debugging symbols
ii  samba-doc 2:4.2.14+dfsg-0+deb8u7 
  all  Samba documentation
ii  samba-dsdb-modules2:4.2.14+dfsg-0+deb8u7+b1 
   amd64Samba Directory Services Database
ii  samba-libs:amd64  2:4.2.14+dfsg-0+deb8u7+b1 
   amd64Samba core libraries
ii  samba-vfs-modules 2:4.2.14+dfsg-0+deb8u7+b1 
  

Re: SAMBA problems on Debian 8.8

[Jason Wittlin-Cohen]

BTW, here is what I see when I run dpkg -l | grep samba:

jason@storage-server:~$ dpkg -l | grep samba
ii  python-samba  2:4.2.14+dfsg-0+deb8u7+b1
  amd64Python bindings for Samba
ii  samba 2:4.2.14+dfsg-0+deb8u7+b1
  amd64SMB/CIFS file, print, and login server for Unix
ii  samba-common  2:4.2.14+dfsg-0+deb8u7
   all  common files used by both the Samba server and client
ii  samba-common-bin  2:4.2.14+dfsg-0+deb8u7+b1
  amd64Samba common files used by both the server and the client
ii  samba-dbg 2:4.2.14+dfsg-0+deb8u7+b1
  amd64Samba debugging symbols
ii  samba-doc 2:4.2.14+dfsg-0+deb8u7
   all  Samba documentation
ii  samba-dsdb-modules2:4.2.14+dfsg-0+deb8u7+b1
  amd64Samba Directory Services Database
ii  samba-libs:amd64  2:4.2.14+dfsg-0+deb8u7+b1
  amd64Samba core libraries
ii  samba-vfs-modules 2:4.2.14+dfsg-0+deb8u7+b1
  amd64Samba Virtual FileSystem plugins


On Sat, Jul 15, 2017 at 11:09 AM, Jason Wittlin-Cohen <
jwittlinco...@gmail.com> wrote:

> You are running an out-of-date version of samba (2:4.2.14+dfsg-0+deb8u6
>  vs. 4.2.14+dfsg-0+deb8u7+b1).  In addition, you seem to be missing
> samba-common-bin,  samba-dsdb-modules, and python-samba, all of which are
> dependencies of samba.
>
> Try 'sudo apt-get install --reinstall samba'
>
> If that doesn't include install the removed packages, run, 'sudo apt-get
> install samba-common-bin samba-dsdb-modules python-samba'
>
> On Sat, Jul 15, 2017 at 11:01 AM, Hans Kraus  wrote:
>
>> Am 15.07.2017 um 16:05 schrieb Jason Wittlin-Cohen:
>>
>>> What does 'dpkg -l | grep samba'  show?
>>>
>>> On Sat, Jul 15, 2017 at 10:01 AM, Hans Kraus >> > wrote:
>>>
>>> Am 15.07.2017 um 14:48 schrieb Jason Wittlin-Cohen:
>>>
>>> Did you run an apt-get dist-upgrade yesterday?  Debian released
>>> updated Samba packages as part of a security update.  However,
>>> the updated packages had dependency issues and were quickly
>>> replaced by new packages.  If you attempted to run a
>>> dist-upgrade with the broken packages, it would have installed
>>> samba and samba-core.  Check to see whether your samba packages
>>> are still installed.
>>>
>>> On Sat, Jul 15, 2017 at 7:56 AM, Hans Kraus >>  >>
>>> >> wrote:
>>>
>>>  Hi,
>>>
>>>  yesterday, 14. July, about 9:30 pm my SAMBA shares on
>>> Debian simply
>>>  stopped working. I did not do anything on the system.
>>>
>>>  When I now try to connect to them from Windows 8.1 I do not
>>> see them
>>>  in the "Connect Network Drive" window.
>>>
>>>  When I enter the address manually I get the error "The
>>> connection isn't
>>>  accepted from the remote device ...".
>>>
>>>  All texts are my translations from German, so the will be
>>> only
>>>  approximately correct.
>>>
>>>  Any advice for me and what debug info shall I supply?
>>>
>>>  Kind regards,
>>>  Hans
>>>
>>>
>>> No, definitely not. I do updates/upgrades rather infrequently and I
>>> issued (packed in a small script):
>>>
>>> /usr/sbin/update-smart-drivedb
>>> apt-get update
>>> apt-get -y upgrade
>>> apt-get -y autoremove
>>>
>>> only after the error occurred.
>>>
>>> Kind regards,
>>> Hans
>>>
>>
>> root@robbe:/var/log/samba# dpkg -l | grep samba
>> rc  samba 2:4.2.14+dfsg-0+deb8u6   amd64SMB/CIFS
>> file, print, and login server for Unix
>> ii  samba-common 2:4.2.14+dfsg-0+deb8u7   all  common
>> files used by both the Samba server and client
>> ii  samba-dsdb-modules 2:4.2.14+dfsg-0+deb8u7+b1amd64
>> Samba Directory Services Database
>> ii  samba-libs:amd64 2:4.2.14+dfsg-0+deb8u7+b1amd64
>> Samba core libraries
>> ii  samba-vfs-modules 2:4.2.14+dfsg-0+deb8u7+b1amd64
>> Samba Virtual FileSystem plugins
>> ii  vlc-plugin-samba 2.2.6-1~deb8u1   amd64
>> Samba plugin for VLC
>> root@robbe:/var/log/samba#
>>
>> Kind regards,
>> Hans
>>
>>
>

Re: SAMBA problems on Debian 8.8

[Jason Wittlin-Cohen]

You are running an out-of-date version of samba (2:4.2.14+dfsg-0+deb8u6
 vs. 4.2.14+dfsg-0+deb8u7+b1).  In addition, you seem to be missing
samba-common-bin,  samba-dsdb-modules, and python-samba, all of which are
dependencies of samba.

Try 'sudo apt-get install --reinstall samba'

If that doesn't include install the removed packages, run, 'sudo apt-get
install samba-common-bin samba-dsdb-modules python-samba'

On Sat, Jul 15, 2017 at 11:01 AM, Hans Kraus  wrote:

> Am 15.07.2017 um 16:05 schrieb Jason Wittlin-Cohen:
>
>> What does 'dpkg -l | grep samba'  show?
>>
>> On Sat, Jul 15, 2017 at 10:01 AM, Hans Kraus > > wrote:
>>
>> Am 15.07.2017 um 14:48 schrieb Jason Wittlin-Cohen:
>>
>> Did you run an apt-get dist-upgrade yesterday?  Debian released
>> updated Samba packages as part of a security update.  However,
>> the updated packages had dependency issues and were quickly
>> replaced by new packages.  If you attempted to run a
>> dist-upgrade with the broken packages, it would have installed
>> samba and samba-core.  Check to see whether your samba packages
>> are still installed.
>>
>> On Sat, Jul 15, 2017 at 7:56 AM, Hans Kraus >  >
>> >> wrote:
>>
>>  Hi,
>>
>>  yesterday, 14. July, about 9:30 pm my SAMBA shares on
>> Debian simply
>>  stopped working. I did not do anything on the system.
>>
>>  When I now try to connect to them from Windows 8.1 I do not
>> see them
>>  in the "Connect Network Drive" window.
>>
>>  When I enter the address manually I get the error "The
>> connection isn't
>>  accepted from the remote device ...".
>>
>>  All texts are my translations from German, so the will be
>> only
>>  approximately correct.
>>
>>  Any advice for me and what debug info shall I supply?
>>
>>  Kind regards,
>>  Hans
>>
>>
>> No, definitely not. I do updates/upgrades rather infrequently and I
>> issued (packed in a small script):
>>
>> /usr/sbin/update-smart-drivedb
>> apt-get update
>> apt-get -y upgrade
>> apt-get -y autoremove
>>
>> only after the error occurred.
>>
>> Kind regards,
>> Hans
>>
>
> root@robbe:/var/log/samba# dpkg -l | grep samba
> rc  samba 2:4.2.14+dfsg-0+deb8u6   amd64SMB/CIFS file,
> print, and login server for Unix
> ii  samba-common 2:4.2.14+dfsg-0+deb8u7   all  common
> files used by both the Samba server and client
> ii  samba-dsdb-modules 2:4.2.14+dfsg-0+deb8u7+b1amd64
> Samba Directory Services Database
> ii  samba-libs:amd64 2:4.2.14+dfsg-0+deb8u7+b1amd64
> Samba core libraries
> ii  samba-vfs-modules 2:4.2.14+dfsg-0+deb8u7+b1amd64
> Samba Virtual FileSystem plugins
> ii  vlc-plugin-samba 2.2.6-1~deb8u1   amd64
> Samba plugin for VLC
> root@robbe:/var/log/samba#
>
> Kind regards,
> Hans
>
>

Re: SAMBA problems on Debian 8.8

[Hans Kraus]

Am 15.07.2017 um 14:58 schrieb Ulf Volmer:

On 15.07.2017 13:56, Hans Kraus wrote:


yesterday, 14. July, about 9:30 pm my SAMBA shares on Debian simply
stopped working. I did not do anything on the system.


There were samba updates for jessie yesterday. First one was broken on
some systems so maybe it will help to do an upgrade again.


Any advice for me and what debug info shall I supply?


is samba running? If yes, any messages in the log?

best regards
Ulf



Hi, thanks for the help to all.
apt-get upgrade/update installed nothing. Therefore I presume that I
have the latest updates.

I tried to restart the Samba server:

root@robbe:/var/log/samba# systemctl restart smbd.service


Querying the status gives:

root@robbe:/var/log/samba# systemctl status smbd.service
● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd)
   Loaded: loaded (/etc/init.d/smbd)
   Active: active (exited) since Sat 2017-07-15 15:35:43 CEST; 6s ago
  Process: 17381 ExecStop=/etc/init.d/smbd stop (code=exited, 
status=0/SUCCESS)
  Process: 17384 ExecStart=/etc/init.d/smbd start (code=exited, 
status=0/SUCCESS)


Jul 15 15:35:43 robbe systemd[1]: Starting LSB: start Samba SMB/CIFS 
daemon (smbd)...
Jul 15 15:35:43 robbe systemd[1]: Started LSB: start Samba SMB/CIFS 
daemon (smbd).

root@robbe:/var/log/samba#


I don't find in the output of 'ps -elf' anything with samba or smb.

In '/var/log/samba' the latest files are from yesterday, around the time
the error occurred. The log files are (the bigger ones are truncated):

log.nmbd

...
[2017/07/14 20:49:01.939924,  0] 
../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail)

  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for 
the workgroup KRAUS_ZUHAUSE.

  Unable to sync browse lists in this workgroup.
[2017/07/14 20:49:01.940054,  0] 
../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail)

  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for 
the workgroup KRAUS_ZUHAUSE.

  Unable to sync browse lists in this workgroup.
[2017/07/14 21:04:01.949910,  0] 
../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail)

  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for 
the workgroup KRAUS_ZUHAUSE.

  Unable to sync browse lists in this workgroup.
[2017/07/14 21:04:01.950037,  0] 
../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail)

  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for 
the workgroup KRAUS_ZUHAUSE.

  Unable to sync browse lists in this workgroup.
[2017/07/14 21:19:01.963122,  0] 
../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail)

  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for 
the workgroup KRAUS_ZUHAUSE.

  Unable to sync browse lists in this workgroup.
[2017/07/14 21:19:01.963239,  0] 
../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail)

  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for 
the workgroup KRAUS_ZUHAUSE.

  Unable to sync browse lists in this workgroup.
[2017/07/14 21:34:01.964702,  0] 
../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail)

  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for 
the workgroup KRAUS_ZUHAUSE.

  Unable to sync browse lists in this workgroup.
[2017/07/14 21:34:01.964832,  0] 
../source3/nmbd/nmbd_browsesync.c:354(find_domain_master_name_query_fail)

  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name KRAUS_ZUHAUSE<1b> for 
the workgroup KRAUS_ZUHAUSE.

  Unable to sync browse lists in this workgroup.
[2017/07/14 21:40:44.998819,  0] ../source3/nmbd/nmbd.c:58(terminate)
  Got SIGTERM: going down...


log.smbd

[2017/07/14 21:40:46.136827,  0] ../lib/util/pidfile.c:153(pidfile_unlink)
  Failed to delete pidfile /var/run/samba/smbd.pid. Error was No such 
file or directory



log.wb-BUILTIN

[2017/06/23 11:38:12.736446,  0] 
../source3/winbindd/winbindd.c:266(winbindd_sig_term_handler)

  Got sig[15] terminate (is_parent=0)

Re: SAMBA problems on Debian 8.8

[Hans Kraus]

Am 15.07.2017 um 16:05 schrieb Jason Wittlin-Cohen:

What does 'dpkg -l | grep samba'  show?

On Sat, Jul 15, 2017 at 10:01 AM, Hans Kraus > wrote:


Am 15.07.2017 um 14:48 schrieb Jason Wittlin-Cohen:

Did you run an apt-get dist-upgrade yesterday?  Debian released
updated Samba packages as part of a security update.  However,
the updated packages had dependency issues and were quickly
replaced by new packages.  If you attempted to run a
dist-upgrade with the broken packages, it would have installed
samba and samba-core.  Check to see whether your samba packages
are still installed.

On Sat, Jul 15, 2017 at 7:56 AM, Hans Kraus  >> wrote:

 Hi,

 yesterday, 14. July, about 9:30 pm my SAMBA shares on
Debian simply
 stopped working. I did not do anything on the system.

 When I now try to connect to them from Windows 8.1 I do not
see them
 in the "Connect Network Drive" window.

 When I enter the address manually I get the error "The
connection isn't
 accepted from the remote device ...".

 All texts are my translations from German, so the will be only
 approximately correct.

 Any advice for me and what debug info shall I supply?

 Kind regards,
 Hans


No, definitely not. I do updates/upgrades rather infrequently and I
issued (packed in a small script):

/usr/sbin/update-smart-drivedb
apt-get update
apt-get -y upgrade
apt-get -y autoremove

only after the error occurred.

Kind regards,
Hans


root@robbe:/var/log/samba# dpkg -l | grep samba
rc  samba 2:4.2.14+dfsg-0+deb8u6   amd64SMB/CIFS 
file, print, and login server for Unix
ii  samba-common 2:4.2.14+dfsg-0+deb8u7   all 
common files used by both the Samba server and client
ii  samba-dsdb-modules 2:4.2.14+dfsg-0+deb8u7+b1amd64 
Samba Directory Services Database
ii  samba-libs:amd64 2:4.2.14+dfsg-0+deb8u7+b1amd64 
Samba core libraries
ii  samba-vfs-modules 2:4.2.14+dfsg-0+deb8u7+b1amd64 
Samba Virtual FileSystem plugins
ii  vlc-plugin-samba 2.2.6-1~deb8u1   amd64 
Samba plugin for VLC

root@robbe:/var/log/samba#

Kind regards,
Hans

PS: Sorry for the personal mails.

Re: SAMBA problems on Debian 8.8

[Ulf Volmer]

On 15.07.2017 13:56, Hans Kraus wrote:

> yesterday, 14. July, about 9:30 pm my SAMBA shares on Debian simply
> stopped working. I did not do anything on the system.

There were samba updates for jessie yesterday. First one was broken on
some systems so maybe it will help to do an upgrade again.

> Any advice for me and what debug info shall I supply?

is samba running? If yes, any messages in the log?

best regards
Ulf

Re: SAMBA problems on Debian 8.8

[Dejan Jocic]

On 15-07-17, Hans Kraus wrote:
> Hi,
> 
> yesterday, 14. July, about 9:30 pm my SAMBA shares on Debian simply
> stopped working. I did not do anything on the system.
> 
> When I now try to connect to them from Windows 8.1 I do not see them
> in the "Connect Network Drive" window.
> 
> When I enter the address manually I get the error "The connection isn't
> accepted from the remote device ...".
> 
> All texts are my translations from German, so the will be only
> approximately correct.
> 
> Any advice for me and what debug info shall I supply?
> 
> Kind regards,
> Hans
> 

Samba had 2 security updates, first one had messed up dependencies and
second one solved that. Perhaps you just updated first one and need to
do update/upgrade again to catch up second one?

SAMBA problems on Debian 8.8

[Hans Kraus]

Hi,

yesterday, 14. July, about 9:30 pm my SAMBA shares on Debian simply
stopped working. I did not do anything on the system.

When I now try to connect to them from Windows 8.1 I do not see them
in the "Connect Network Drive" window.

When I enter the address manually I get the error "The connection isn't
accepted from the remote device ...".

All texts are my translations from German, so the will be only
approximately correct.

Any advice for me and what debug info shall I supply?

Kind regards,
Hans

Samba problems

[Charles Chambers]

I'm having a problem getting Samba set up on one computer, and any
pointers would be appreciated.

I have two computers, identical except that one has an 80 gig drive and
the other has a 250 gig drive.  Both have an external USB drive, which
is the drive I'm trying to share out across a home network.  Both have
the standard Debian Samba (2.3.5.6) installed on them.  One works
perfectly.  When the USB drive is present, it's shared; when it's
disconnected from it's computer, obviously, it's not available, but when
I connect it back up - BOOM - it's there.  My Windows 7 computer loves
it for a network drive.  The other one works not at all.

I've followed the setup as described at howtoforge.com for setting up
Samba, and my windows 7 computer just won't browse to it.

It's probably something careless on my part, but I can't figure it out.

Someone have time to start walking me through it?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50a65baa.2010...@gmail.com

Re: SAMBA problems

[Paul Johnson]

On Fri, 2008-09-19 at 09:31 +0100, Gerard Hooton wrote: 
 Hello All,
 We are using Samba to provide a windows Domain login 
 The problem is that some of the users that I create (using smbpasswd -a
 are not working when I do a login from the windows machines(RPC errors)
 and some work fine.

Is it failing on Vista machines but working on other Windows machines?

-- 
Paul Johnson
[EMAIL PROTECTED]


signature.asc
Description: This is a digitally signed message part

SAMBA problems

[Gerard Hooton]

Hello All,
We are using Samba to provide a windows Domain login 
The problem is that some of the users that I create (using smbpasswd -a
are not working when I do a login from the windows machines(RPC errors)
and some work fine.
Q: Are there restrictions on what user names I can use such as the
minimum number of characters. If so where are those restriction defined?

Thanks.
-- 
Gerard Hooton.
Department of Microelectronic Engineering U.C.C.
Butler Building,
Enterprise Centre,
North Mall.
Cork.

Tel: +353 21 4904576
Fax: +353 21 4904573
http://www.ue.ucc.ie/




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Woody-Sarge Upgrade w/ Samba Problems

[Brian Kimsey-Hickman]

On 8/2/05, Brian Kimsey-Hickman [EMAIL PROTECTED] wrote:
 Just upgraded a Debian box to Sarge and my Samba shares don't seem to
 work quite the same.  This box should be using Domain Authentication
 and I successfully rejoined the domain with a net join command but the
 only people that can open share are ones that have user account on the
 device and on the domain.  Anybody have any ideas?
 
 Here is the config:
 
 # Global parameters
 [global]
 
panic action = /usr/share/samba/panic-action %d
 workgroup = OCC
 netbios name = COMPT-CD
 server string = CDROM Server
 security = DOMAIN
 encrypt passwords = true
passdb backend = smbpasswd guest
 obey pam restrictions = Yes
 passwd program = /usr/bin/passwd %u
 passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
 *Retype\snew\sUNIX\spassword:* %n\n .
 syslog = 0
 log file = /var/log/samba/log.%m
 max log size = 1000
 name resolve order = wins lmhosts hosts bcast
 os level = 0
 preferred master = False
 local master = No
 domain master = False
 dns proxy = No
 wins server = 172.30.10.21
 invalid users = root
 guest ok = Yes
 
 [BC_03_07_Jul]
 comment = BCC 2003 July
 path = /iso/shares/BCC_2003_07
 guest only = Yes
 
 [BC_03_08_Aug]
 comment = BCC 2003 August
 path = /iso/shares/BCC_2003_08
 guest only = Yes
 
 [BC_03_09_Sep]
 comment = BCC 2003 September
 path = /iso/shares/BCC_2003_09
 guest only = Yes
 
 [BC_03_10_Oct]
 comment = BCC 2003 October
 path = /iso/shares/BCC_2003_10
 guest only = Yes
 
Found some addition information.  I check the event view on my PDC
emulator Domain Controller and found this error message:

Event Type: Audit Failure
Event Source:   Security
Event Category: Account Logon
Event ID:   675
Date:   8/3/2005
Time:   7:39:20 AM
User:   SYSTEM
Computer:   COM1
Description:
Pre-authentication failed:
User Name:  cpisbk3
User ID:Additional Information [GUID]:
{S-1-5-21-844678424-286055849-2661016245-1121}
Service Name:   krbtgt/OCC
Pre-Authentication Type:0x2
Failure Code:   0x18
Client Address: 172.30.5.233
 
Data:

I turned Kerberos pre-authentication off.  But, that didn't help.

Anybody have any ideas?

Thanks,

Brian

Woody-Sarge Upgrade w/ Samba Problems

[Brian Kimsey-Hickman]

Just upgraded a Debian box to Sarge and my Samba shares don't seem to
work quite the same.  This box should be using Domain Authentication
and I successfully rejoined the domain with a net join command but the
only people that can open share are ones that have user account on the
device and on the domain.  Anybody have any ideas?

Here is the config:

# Global parameters
[global]

   panic action = /usr/share/samba/panic-action %d
workgroup = OCC
netbios name = COMPT-CD
server string = CDROM Server
security = DOMAIN
encrypt passwords = true
   passdb backend = smbpasswd guest
obey pam restrictions = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
*Retype\snew\sUNIX\spassword:* %n\n .
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
name resolve order = wins lmhosts hosts bcast
os level = 0
preferred master = False
local master = No
domain master = False
dns proxy = No
wins server = 172.30.10.21
invalid users = root
guest ok = Yes

[BC_03_07_Jul]
comment = BCC 2003 July
path = /iso/shares/BCC_2003_07
guest only = Yes

[BC_03_08_Aug]
comment = BCC 2003 August
path = /iso/shares/BCC_2003_08
guest only = Yes

[BC_03_09_Sep]
comment = BCC 2003 September
path = /iso/shares/BCC_2003_09
guest only = Yes

[BC_03_10_Oct]
comment = BCC 2003 October
path = /iso/shares/BCC_2003_10
guest only = Yes

RE: Woody-Sarge Upgrade w/ Samba Problems

[Joost Kraaijeveld]

Hi Brian,

Brian Kimsey-Hickman schreef:
 Just upgraded a Debian box to Sarge and my Samba shares don't seem to
 work quite the same.  This box should be using Domain Authentication
 and I successfully rejoined the domain with a net join command but the
 only people that can open share are ones that have user account on the
 device and on the domain.  Anybody have any ideas?

Set obey pam restrictions = Yes to obey pam restrictions = No or comment it 
out.

Groeten,

Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
e-mail: [EMAIL PROTECTED]
web: www.askesis.nl

Samba problems in stable?

[Robert L. Harris]

Recently a production stable samba server started producing this:

samba-log.cpr8r:  oplock_break failed for file Share1/Files/Financial/Comms.xls (dev = 
b, inode = 151073815, file_id = 31).
samba-log.cpr8r:  oplock_break failed for file Share1/Files/Financial/Futures.xls (dev 
= b, inode = 411546895, file_id = 31).
samba-log.cpr8r:  oplock_break failed for file Share1/Files/Financial/Historical.xls 
(dev = b, inode = 402910038, file_id = 8).

etc etc for many many files.  My samba logs currently give this 580
times in the last 2 days since the server was restarted.

The closest match is on google from 1999 and there's no reply.
Samba.org doesn't even have any matches on their search page I can find.

Anyone have any ideas what could cause this?

Kernel 2.4.26-bk1
Samba 2.0.7-1
Debian Stable

The hardware is a P3-850 with 512Megs of ram.

Most of the files being accessed are nfs mounted from a hardare
appliance (SNAP).

Robert


:wq!
---
Robert L. Harris | GPG Key ID: E344DA3B
 @ x-hkp://pgp.mit.edu
DISCLAIMER:
  These are MY OPINIONS ALONE.  I speak for no-one else.

With Dreams To Be A King First One Should Be A Man
- Manowar



signature.asc
Description: Digital signature

Samba problems.

[Mike Dresser]

Any work arounds for the problems with smbmount and smbtar both missing
files when you backup?

//dumbo/cds   25213952   7384064  17829888  30% /cdrom

twiki:/cdrom# ls -alR | wc -l
  70099
twiki:/cdrom# ls -alR | wc -l
  70094
twiki:/cdrom# ls -alR | wc -l
  70098
twiki:/cdrom# ls -alR | wc -l
  70014
twiki:/cdrom# ls -alR | wc -l
  70099

Everytime I do this, I get different # of files.

As well, when I smbtar, i get differnt # of files as well.

I'm trying to mirror over about 8 gig from the NT 4.0 machine over to a
Woody machine, but right now I can't because I can't trust the backup to
have gotten all the files.

I reported this about 3 years ago, and was told to go away because
smbmount isn't supported.  I assume smbclient is the same.

Ideas?

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Samba problems.

[R. Bradley Tilley (Brad)]

AMANDA uses smbclient. In my experience with smbclient and AMANDA, it 
has never behaved in the manner that you describe smbmount and smbtar. 
Try using smbclient.


Mike Dresser wrote:

Any work arounds for the problems with smbmount and smbtar both missing
files when you backup?

//dumbo/cds   25213952   7384064  17829888  30% /cdrom

twiki:/cdrom# ls -alR | wc -l
  70099
twiki:/cdrom# ls -alR | wc -l
  70094
twiki:/cdrom# ls -alR | wc -l
  70098
twiki:/cdrom# ls -alR | wc -l
  70014
twiki:/cdrom# ls -alR | wc -l
  70099

Everytime I do this, I get different # of files.

As well, when I smbtar, i get differnt # of files as well.

I'm trying to mirror over about 8 gig from the NT 4.0 machine over to a
Woody machine, but right now I can't because I can't trust the backup to
have gotten all the files.

I reported this about 3 years ago, and was told to go away because
smbmount isn't supported.  I assume smbclient is the same.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Samba problems.

[Mike Dresser]

On Thu, 5 Sep 2002, R. Bradley Tilley (Brad) wrote:

 AMANDA uses smbclient. In my experience with smbclient and AMANDA, it
 has never behaved in the manner that you describe smbmount and smbtar.
 Try using smbclient.

smbtar merely calls smbclient though.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

samba problems ?

[Bob Koss]

Ever since I switched from RH to Debian, I've been getting errors from tar
when I try to backup samba mounted file systems. The error is, file changed
as we read it. There are many of these errors and there is nobody changing
any of the files. I rebooted the Win95 machine and didn't start any
applications and I still get these errors.

Is anybody else seeing this or can anybody offer any advice?

These errors only happen on smbfs. None of the local volumes have this
error.


Robert S. Koss, Ph.D.   | Training and Mentoring
Senior Consultant   | Object Oriented Design
Object Mentor, Inc. | C++, Java
www.objectmentor.com| Extreme Programming

Samba problems

[Alec Smith]

I'm noticing that if I copy some files from Windows NT onto my Samba
server I end up with the wrong permissions. Instead of files being owned
by alec.mp3 as I'd like, they appear to be owned by root.mp3.

  97153 drwxr-sr-x2 alec mp3  4.0k Oct  3 13:28 ./
  32385 drwxr-sr-x3 alec alec 4.0k Oct  3 13:25 ../
  97157 -rwxrw-r--1 root mp3  4.6M Jul  9 05:14 [Barry
Sadler] - Ballad of the Green Berets.mp3*
  97154 -rwxrw-r--1 root mp3  2.7M Jul  9 04:54
oldies.shelly fabres-johnny angel.mp3*

Although I used the MP3 share to copy these files, the same effect is
seen when copying a file into home directories (root.correct group
name) using the homes share. How can I go about getting Samba to place the
correct ownerships on files? My smb.conf is included below. The server is
running Potato and Samba 2.0.7 (from the .deb).

Thanks,
Alec


# Samba config file created using SWAT
# from rs229202.resnet.wright.edu (130.108.229.202)
# Date: 2000/10/03 13:31:04

# Global parameters
[global]
workgroup = SHADOWSTAR
netbios name = TWEETY
server string = %h server (Samba %v)
encrypt passwords = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
*Retype\snew\sUNIX\spa$
syslog = 0
max log size = 1000
socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=4096
SO_RCVBUF=40$
os level = 128
preferred master = Yes
domain master = Yes
dns proxy = No
wins support = Yes
invalid users = root
admin users = alec
hosts allow = 130.108.229.200, 130.108.229.201, 130.108.229.202,
130.10$
hosts deny = 130.108
printing = lprng

[homes]
comment = Home Directories
writeable = Yes   
create mask = 0700
directory mask = 0700
inherit permissions = Yes
browseable = No

[printers]
comment = All Printers
path = /tmp
create mask = 0700
printable = Yes
browseable = No

[mp3]
comment = MP3 files
path = /home/alec/mp3
valid users = alec, carl
read list = carl
write list = alec
force group = mp3
create mask = 0774
inherit permissions = Yes

Re: Samba problems (fwd)

[Alberto Pereira]

The problem is the windows system not found the printers!
I use potato with samba2.0.7-3

On Tue, 3 Oct
2000, Alec Smith wrote:

I use the default Samba printers share, and then the standard method of
mapping the network printers on my Windows machine. There's nothing
special to printing from Windows to a Samba machine. (Samba to Windows is
a little trickier) Once Windows knows which printers it has available on
the network, you can use the regular Print menu in applications.



On Tue, 3 Oct 2000, Alberto Pereira wrote:

 Sir, 
 I read your message on the list and I want to make a question to you.
 What the command you put in your client to print??
 I assume your client is windows system.
 
 Thanks so much
 
 Atenciosamente,
   .
,,$,Alberto Pereira  
   ;$'  ':  Analista de Suporte 
   $: :  
$   o_)$$$: -E ai linux, o que faremos hoje a noite?? 
;$,_/\ :' -O que fazemos todas as noites link, 
  ' /( tentaremos dominar o mundo
  \_'
 .  -DEBIAN, THE CHOICE OF NEW GNU LINUX GENERATION 
   :  
  
 
 



Atenciosamente,
  .
   ,,$,Alberto Pereira  
  ;$'  ':  Analista de Suporte 
  $: :  
   $   o_)$$$: -E ai linux, o que faremos hoje a noite?? 
   ;$,_/\ :' -O que fazemos todas as noites link, 
 ' /( tentaremos dominar o mundo
 \_'
.  -DEBIAN, THE CHOICE OF NEW GNU LINUX GENERATION 
  :  
 

Re: Samba problems

[Alberto Pereira]

Yes,
the samba is rigth configured but the printer not appears in the windows 
net box!!
:(
All others folders appears in the net windows box.

On Tue, 3 Oct 2000, Alec
Smith wrote:

Can the Windows machine see other shares on the Samba machine?


On Tue, 3 Oct 2000, Alberto Pereira wrote:

 The problem is the windows system not found the printers!
 I use potato with samba2.0.7-3
 
 On Tue, 3 Oct
 2000, Alec Smith wrote:
 
 I use the default Samba printers share, and then the standard method of
 mapping the network printers on my Windows machine. There's nothing
 special to printing from Windows to a Samba machine. (Samba to Windows is
 a little trickier) Once Windows knows which printers it has available on
 the network, you can use the regular Print menu in applications.
 
 
 
 On Tue, 3 Oct 2000, Alberto Pereira wrote:
 
  Sir, 
  I read your message on the list and I want to make a question to you.
  What the command you put in your client to print??
  I assume your client is windows system.
  
  Thanks so much
  
  Atenciosamente,
.
 ,,$,Alberto Pereira  
;$'  ':  Analista de Suporte 
$: :  
 $   o_)$$$: -E ai linux, o que faremos hoje a noite?? 
 ;$,_/\ :' -O que fazemos todas as noites link, 
   ' /( tentaremos dominar o mundo
   \_'
  .  -DEBIAN, THE CHOICE OF NEW GNU LINUX GENERATION 
:  
   
  
  
 
 
 
 Atenciosamente,
   .
,,$,Alberto Pereira  
   ;$'  ':  Analista de Suporte 
   $: :  
$   o_)$$$: -E ai linux, o que faremos hoje a noite?? 
;$,_/\ :' -O que fazemos todas as noites link, 
  ' /( tentaremos dominar o mundo
  \_'
 .  -DEBIAN, THE CHOICE OF NEW GNU LINUX GENERATION 
   :  
  
 
 



Atenciosamente,
  .
   ,,$,Alberto Pereira  
  ;$'  ':  Analista de Suporte 
  $: :  
   $   o_)$$$: -E ai linux, o que faremos hoje a noite?? 
   ;$,_/\ :' -O que fazemos todas as noites link, 
 ' /( tentaremos dominar o mundo
 \_'
.  -DEBIAN, THE CHOICE OF NEW GNU LINUX GENERATION 
  :  
 

Re: Samba problems

[Alec Smith]

Your Samba machine does have a [Printers] share, right? If that share is
there, I'm not sure what's wrong. I'm by no means a Samba god... :(



On Tue, 3 Oct 2000, Alberto Pereira wrote:

 Yes,
 the samba is rigth configured but the printer not appears in the windows 
 net box!!
 :(
 All others folders appears in the net windows box.
 
 On Tue, 3 Oct 2000, Alec
 Smith wrote:
 
 Can the Windows machine see other shares on the Samba machine?
 
 
 On Tue, 3 Oct 2000, Alberto Pereira wrote:
 
  The problem is the windows system not found the printers!
  I use potato with samba2.0.7-3
  
  On Tue, 3 Oct
  2000, Alec Smith wrote:
  
  I use the default Samba printers share, and then the standard method of
  mapping the network printers on my Windows machine. There's nothing
  special to printing from Windows to a Samba machine. (Samba to Windows is
  a little trickier) Once Windows knows which printers it has available on
  the network, you can use the regular Print menu in applications.
  
  
  
  On Tue, 3 Oct 2000, Alberto Pereira wrote:
  
   Sir, 
   I read your message on the list and I want to make a question to you.
   What the command you put in your client to print??
   I assume your client is windows system.
   
   Thanks so much
   
   Atenciosamente,
 .
  ,,$,Alberto Pereira  
 ;$'  ':  Analista de Suporte 
 $: :  
  $   o_)$$$: -E ai linux, o que faremos hoje a noite?? 
  ;$,_/\ :' -O que fazemos todas as noites link, 
' /( tentaremos dominar o mundo
\_'
   .  -DEBIAN, THE CHOICE OF NEW GNU LINUX GENERATION 
 :  

   
   
  
  
  
  Atenciosamente,
.
 ,,$,Alberto Pereira  
;$'  ':  Analista de Suporte 
$: :  
 $   o_)$$$: -E ai linux, o que faremos hoje a noite?? 
 ;$,_/\ :' -O que fazemos todas as noites link, 
   ' /( tentaremos dominar o mundo
   \_'
  .  -DEBIAN, THE CHOICE OF NEW GNU LINUX GENERATION 
:  
   
  
  
 
 
 
 Atenciosamente,
   .
,,$,Alberto Pereira  
   ;$'  ':  Analista de Suporte 
   $: :  
$   o_)$$$: -E ai linux, o que faremos hoje a noite?? 
;$,_/\ :' -O que fazemos todas as noites link, 
  ' /( tentaremos dominar o mundo
  \_'
 .  -DEBIAN, THE CHOICE OF NEW GNU LINUX GENERATION 
   :  
  
 
 
 
 -- 
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null
 
 

Re: Samba problems

[Ethan Benson]

On Tue, Oct 03, 2000 at 01:39:12PM -0400, Alec Smith wrote:
 I'm noticing that if I copy some files from Windows NT onto my Samba
 server I end up with the wrong permissions. Instead of files being owned
 by alec.mp3 as I'd like, they appear to be owned by root.mp3.
 
   97153 drwxr-sr-x2 alec mp3  4.0k Oct  3 13:28 ./
   32385 drwxr-sr-x3 alec alec 4.0k Oct  3 13:25 ../
   97157 -rwxrw-r--1 root mp3  4.6M Jul  9 05:14 [Barry
 Sadler] - Ballad of the Green Berets.mp3*
   97154 -rwxrw-r--1 root mp3  2.7M Jul  9 04:54
 oldies.shelly fabres-johnny angel.mp3*
 
 Although I used the MP3 share to copy these files, the same effect is
 seen when copying a file into home directories (root.correct group
 name) using the homes share. How can I go about getting Samba to place the
 correct ownerships on files? My smb.conf is included below. The server is
 running Potato and Samba 2.0.7 (from the .deb).
 
 Thanks,
 Alec

[snip]

 invalid users = root
 admin users = alec

try removing this admin users = alec.  iirc (and i may not) this
basically gives you root privileges when you login instead of normal
privileges.  that is the only thing in your config i can see that
might cause this.  (you use security mode = users right?)

also if you set your create mode to 644/664 (no 7s) and directory mode
to 755/775, along with map archive = no you won't get those hideously
ugly 764 permissions like you have above.  

-- 
Ethan Benson
http://www.alaska.net/~erbenson/


pgpvzQZZBVW0b.pgp
Description: PGP signature

Re: Samba problems

[Alec Smith]

Doing what you suggested seems to have cleared everything up. The extra
tidbit to get the permissions more correct is also appreciated and
reflected in my updated smb.conf. Thanks for the info.

Alec


On Tue, 3 Oct 2000, Ethan Benson wrote:

 On Tue, Oct 03, 2000 at 01:39:12PM -0400, Alec Smith wrote:
  I'm noticing that if I copy some files from Windows NT onto my Samba
  server I end up with the wrong permissions. Instead of files being owned
  by alec.mp3 as I'd like, they appear to be owned by root.mp3.
  
97153 drwxr-sr-x2 alec mp3  4.0k Oct  3 13:28 ./
32385 drwxr-sr-x3 alec alec 4.0k Oct  3 13:25 ../
97157 -rwxrw-r--1 root mp3  4.6M Jul  9 05:14 [Barry
  Sadler] - Ballad of the Green Berets.mp3*
97154 -rwxrw-r--1 root mp3  2.7M Jul  9 04:54
  oldies.shelly fabres-johnny angel.mp3*
  
  Although I used the MP3 share to copy these files, the same effect is
  seen when copying a file into home directories (root.correct group
  name) using the homes share. How can I go about getting Samba to place the
  correct ownerships on files? My smb.conf is included below. The server is
  running Potato and Samba 2.0.7 (from the .deb).
  
  Thanks,
  Alec
 
 [snip]
 
  invalid users = root
  admin users = alec
 
 try removing this admin users = alec.  iirc (and i may not) this
 basically gives you root privileges when you login instead of normal
 privileges.  that is the only thing in your config i can see that
 might cause this.  (you use security mode = users right?)
 
 also if you set your create mode to 644/664 (no 7s) and directory mode
 to 755/775, along with map archive = no you won't get those hideously
 ugly 764 permissions like you have above.  
 
 -- 
 Ethan Benson
 http://www.alaska.net/~erbenson/
 

Re: samba problems (rather Access programmers)

[C. Falconer]

At 08:57 PM 8/31/00 -0300, you wrote:

 the stupid Access programers
 coded the path into code statically. So the program search the dbm files
 at \\SERVER\\ACCDOC and more he has to map the network drive under E:
 . But the ACCDOC is under a folder SOLTSYS. So the structure is
 Soltsys\accdoc . Here comes the problem. The Soltsys at server has to be
 seen as P: . Summarize : \\SERVER\SOLTSYS has to be mapped as P: and
 \\SERVER\SOLTSYS\ACCDOC has to be mapped as E: . The rules from our
 smb.conf are included. Please help me set up the directory structure and
 shares that the users can access the dirs with right mapped drivers...



With...
[SOLTSYS]
  comment = Soltsys
  path = /home/soltsys
  public = yes
  writeable = yes
  printable = no
  write list = @users
  create mask = 0765

[ACCDOC]
  comment = Soltsys
  path = /home/soltsys/accdoc
  public = yes
  writeable = yes
  printable = no
  write list = @users
  create mask = 0765

you get two shares in the guindoz browser; just map them to the letter
you'd like.


You forgot one detail...  shoot those access programmers

They're called DBFs for a reason  (Data Base Fsckers) :)

--
Criggie

Re: samba problems (rather Access programmers)

[Christoph Simon]

 At 08:57 PM 8/31/00 -0300, you wrote:
   seen as P: . Summarize : \\SERVER\SOLTSYS has to be mapped as P: and
   \\SERVER\SOLTSYS\ACCDOC has to be mapped as E: . The rules from our
   smb.conf are included. Please help me set up the directory structure and
   shares that the users can access the dirs with right mapped drivers...
 
 With...
 [SOLTSYS]
 
 [ACCDOC]
 
 you get two shares in the guindoz browser; just map them to the letter
 you'd like.
 
 You forgot one detail...  shoot those access programmers
 
 They're called DBFs for a reason  (Data Base Fsckers) :)

Not so much a deal. We have to be patient with the poor guys using
that brain killing stuff. They'll find out what's the better
alternative (sooner or later).

Christoph Simon
[EMAIL PROTECTED]

-- 
^X^C
q
quit
:q
^C
end
x
exit
ZZ
^D
?
help
shit
.

samba problems (rather Access programmers)

[Deim Agoston]

Hello !

I have a friend who wants to get rid of NT and change to linux+Samba but
we have minor problems. The first is : the stupid Access programers
coded the path into code statically. So the program search the dbm files
at \\SERVER\\ACCDOC and more he has to map the network drive under E:
. But the ACCDOC is under a folder SOLTSYS. So the structure is
Soltsys\accdoc . Here comes the problem. The Soltsys at server has to be
seen as P: . Summarize : \\SERVER\SOLTSYS has to be mapped as P: and
\\SERVER\SOLTSYS\ACCDOC has to be mapped as E: . The rules from our
smb.conf are included. Please help me set up the directory structure and
shares that the users can access the dirs with right mapped drivers.
Any help appriciated.
Thanks,
Ago

[global]
netbios name = SERVER
workgroup = SOLTESZ
server string = SERVER
browseable = yes
hosts allow = 192.168.1. 127.
log file = /var/log/smb.%
max log size = 150
security = user
encrypt passwords = yes
smb password file = /etc/samba/smbpasswd
unix password sync = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n \
*passwd:*all*authentication*tokens*updated*successfully*
include = /etc/samba/smb.conf.%m
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
interfaces = 192.168.1.100/255.255.255.0
local master = yes
os level = 65
domain master = yes
preferred master = yes
domain logons = yes
logon path = \\%L\Profiles\%U
name resolve order = wins lmhosts bcast
wins support = yes
dns proxy = yes

[homes]
comment = Home Directories
browseable = no
writeable = yes

[netlogon]
comment = Network Logon Service
path = /home/netlogon
guest ok = yes
writeable = no
share modes = no

[Profiles]
path= /home/profiles
browseable = no
guest ok = yes

[public]
comment = Soltsys
path = /home/soltsys
public = yes
writeable = yes
printable = no
write list = @users
create mask = 0765


-- 
Irish Linux Users' Group: [EMAIL PROTECTED]
http://www.linux.ie/mailman/listinfo/ilug for (un)subscription information.
List maintainer: [EMAIL PROTECTED]

Re: samba problems (rather Access programmers)

[Christoph Simon]

 I have a friend who wants to get rid of NT and change to linux+Samba but
 we have minor problems. The first is : the stupid Access programers
 coded the path into code statically. So the program search the dbm files
 at \\SERVER\\ACCDOC and more he has to map the network drive under E:
 . But the ACCDOC is under a folder SOLTSYS. So the structure is
 Soltsys\accdoc . Here comes the problem. The Soltsys at server has to be
 seen as P: . Summarize : \\SERVER\SOLTSYS has to be mapped as P: and
 \\SERVER\SOLTSYS\ACCDOC has to be mapped as E: . The rules from our
 smb.conf are included. Please help me set up the directory structure and
 shares that the users can access the dirs with right mapped drivers.
 Any help appriciated.
 Thanks,
 Ago

With...

[SOLTSYS]
  comment = Soltsys
  path = /home/soltsys
  public = yes
  writeable = yes
  printable = no
  write list = @users
  create mask = 0765

[ACCDOC]
  comment = Soltsys
  path = /home/soltsys/accdoc
  public = yes
  writeable = yes
  printable = no
  write list = @users
  create mask = 0765

you get two shares in the guindoz browser; just map them to the letter
you'd like.

HTH

Christoph Simon
[EMAIL PROTECTED]

-- 
^X^C
q
quit
:q
^C
end
x
exit
ZZ
^D
?
help
shit
.

samba problems

[Joseph de los Santos]

Hi,

 hoping that someone really nice can lend a helping hand...with configuring 
samba...

  1.  I always do an ifconfig eth0 192.168.0.1 netmask  255.255.255.0  
everytime I boot to configure my network interface. I want to configure the 
interface permanently so I do not have to manually specify it everytime.

2. do I need to do a 'route add -net 192.168.0 dev eth0' aside from 
specifying the ip add and netmask? how about the broadcast address? do i need 
to configure that too?

  3.when trying to test the connection with $smbclient debian\\user1 , it 
prompts me for the password, then gives the error..
Password: 
session setup failed: ERRSRV - ERRbadpw (Bad password - name/password pair in 
a Tree Connect or Session Setup are invalid.)
ah.say what?

btw,
 I run samba from inetd. nmblookup works..(i think, doesn't complain anyway)   
testparm also doesn't complains...but checking  var/log/smb shows this 
errors...when I first installed samba it asked me if i wanted to make a new 
samba passwords file...i said no, (taking the default choice) perhaps that is 
where my problem lies?

[2000/08/02 20:16:56, 1] smbd/server.c:main(641)
  smbd version 2.0.7 started.
  Copyright Andrew Tridgell 1992-1998
[2000/08/02 20:16:56, 1] smbd/files.c:file_init(216)
  file_init: Information only: requested 1 open files, 1014 are available.
[2000/08/02 20:17:11, 0] passdb/smbpass.c:startsmbfilepwent_internal(87)
  startsmbfilepwent_internal: unable to open file /etc/samba/smbpasswd. Error 
was No such file or directory
[2000/08/02 20:17:11, 0] passdb/passdb.c:iterate_getsmbpwnam(149)
  unable to open smb password database.
[2000/08/02 20:17:11, 1] smbd/password.c:pass_check_smb(500)
  Couldn't find user 'root' in smb_passwd file.
[2000/08/02 20:17:11, 0] passdb/smbpass.c:startsmbfilepwent_internal(87)
  startsmbfilepwent_internal: unable to open file /etc/samba/smbpasswd. Error 
was No such file or directory
[2000/08/02 20:17:11, 0] passdb/passdb.c:iterate_getsmbpwnam(149)
  unable to open smb password database.
[2000/08/02 20:17:11, 1] smbd/password.c:pass_check_smb(500)
  Couldn't find user 'root' in smb_passwd file.
[2000/08/02 20:17:11, 1] smbd/reply.c:reply_sesssetup_and_X(925)
  Rejecting user 'root': authentication failed



Hoping for any kind of help. 

Re: samba problems

[Phil Brutsche]

A long time ago, in a galaxy far, far way, someone said...

 Hi,
 
  hoping that someone really nice can lend a helping hand...with
 configuring samba...

Samba's not that hard.

   1.  I always do an ifconfig eth0 192.168.0.1 netmask 
 255.255.255.0 everytime I boot to configure my network interface.  I
 want to configure the interface permanently so I do not have to
 manually specify it everytime.

One of two ways:
 * /etc/init.d/network
 * /etc/network/interfaces

 2. do I need to do a 'route add -net 192.168.0 dev eth0' aside
 from specifying the ip add and netmask?

Depends; what kernel revision are you using?

 how about the broadcast address? do i need to configure that too?

Yep.  Same place as the ip number.

   3.when trying to test the connection with $smbclient
 debian\\user1, it prompts me for the password, then gives the
 error..
 Password: 
 session setup failed: ERRSRV - ERRbadpw (Bad password - name/password pair in 
 a Tree Connect or Session Setup are invalid.)

You entered the wrong password, obviously.  What are the contents the
[global] section in smb.conf?  According to the log below, you're missing
the smbpasswd file (the list of encrypted NT LanMan passwords).  You
really can't use samba without it...

 ah.say what?
 
 btw,
  I run samba from inetd. nmblookup works..(i think, doesn't complain
 anyway) testparm also doesn't complains...but checking var/log/smb
 shows this errors...when I first installed samba it asked me if i
 wanted to make a new samba passwords file...i said no, (taking the
 default choice) perhaps that is where my problem lies?

Yes that's the problem.

 
 [2000/08/02 20:16:56, 1] smbd/server.c:main(641)
   smbd version 2.0.7 started.
   Copyright Andrew Tridgell 1992-1998
 [2000/08/02 20:16:56, 1] smbd/files.c:file_init(216)
   file_init: Information only: requested 1 open files, 1014 are available.
 [2000/08/02 20:17:11, 0] passdb/smbpass.c:startsmbfilepwent_internal(87)
   startsmbfilepwent_internal: unable to open file /etc/samba/smbpasswd. Error 
 was No such file or directory
 [2000/08/02 20:17:11, 0] passdb/passdb.c:iterate_getsmbpwnam(149)
   unable to open smb password database.
 [2000/08/02 20:17:11, 1] smbd/password.c:pass_check_smb(500)
   Couldn't find user 'root' in smb_passwd file.
 [2000/08/02 20:17:11, 0] passdb/smbpass.c:startsmbfilepwent_internal(87)
   startsmbfilepwent_internal: unable to open file /etc/samba/smbpasswd. Error 
 was No such file or directory
 [2000/08/02 20:17:11, 0] passdb/passdb.c:iterate_getsmbpwnam(149)
   unable to open smb password database.
 [2000/08/02 20:17:11, 1] smbd/password.c:pass_check_smb(500)
   Couldn't find user 'root' in smb_passwd file.
 [2000/08/02 20:17:11, 1] smbd/reply.c:reply_sesssetup_and_X(925)
   Rejecting user 'root': authentication failed

-- 
--
Phil Brutsche   [EMAIL PROTECTED]

There are two things that are infinite; Human stupidity and the
universe. And I'm not sure about the universe. - Albert Einstien

RE: samba problems

[CHEONG, Shu Yang \[Patrick\]]

OK here goes

cd to /etc/network and ls to see whether you already have a file there
named interfaces. If not, use you favourite editor (mine's ae, BTW as it
is so ealy to use for simple editing) and create this file with the
following contents:-

# The loopback device
iface lo inet loopback

# The eth0 device (replace the ip with the appropriate address)
iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.255
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.10# If this box is not the gateway, otherwise,
this can be commented out

Note that if you specified a gateway, ips meant for other networks will be
routed via the gateway.
(Someone correct me if I am wrong!)

As for Samba, have your included your username and password to the
smbpasswd...ooopsss you did mention that you skipped that pasrt when
askedwell, to create the said file, I suggest you use Samba Web
Administration Tool or SWAT for short...

From thereon, you should be able to smbclient //debian/user1 ...and make
sure you key in the correct password

Hope that helped


Patrick Cheong
Information Systems Assurance
Measat Broadcast Network Systems
E-mail: [EMAIL PROTECTED]
Visit us at: http://www.astro.com.my

 -Original Message-
 From: Joseph de los Santos [SMTP:[EMAIL PROTECTED]
 Sent: Thursday, August 03, 2000 5:19 AM
 To:   debian-user@lists.debian.org
 Subject:  samba problems
 
 Hi,
 
  hoping that someone really nice can lend a helping hand...with
 configuring 
 samba...
 
   1.  I always do an ifconfig eth0 192.168.0.1 netmask 
 255.255.255.0  
 everytime I boot to configure my network interface. I want to configure
 the 
 interface permanently so I do not have to manually specify it everytime.
 
 2. do I need to do a 'route add -net 192.168.0 dev eth0' aside from 
 specifying the ip add and netmask? how about the broadcast address? do i
 need 
 to configure that too?
 
   3.when trying to test the connection with $smbclient debian\\user1 ,
 it 
 prompts me for the password, then gives the error..
 Password: 
 session setup failed: ERRSRV - ERRbadpw (Bad password - name/password pair
 in 
 a Tree Connect or Session Setup are invalid.)
 ah.say what?
 
 btw,
  I run samba from inetd. nmblookup works..(i think, doesn't complain
 anyway)   
 testparm also doesn't complains...but checking  var/log/smb shows this 
 errors...when I first installed samba it asked me if i wanted to make a
 new 
 samba passwords file...i said no, (taking the default choice) perhaps that
 is 
 where my problem lies?
 
 [2000/08/02 20:16:56, 1] smbd/server.c:main(641)
   smbd version 2.0.7 started.
   Copyright Andrew Tridgell 1992-1998
 [2000/08/02 20:16:56, 1] smbd/files.c:file_init(216)
   file_init: Information only: requested 1 open files, 1014 are
 available.
 [2000/08/02 20:17:11, 0] passdb/smbpass.c:startsmbfilepwent_internal(87)
   startsmbfilepwent_internal: unable to open file /etc/samba/smbpasswd.
 Error 
 was No such file or directory
 [2000/08/02 20:17:11, 0] passdb/passdb.c:iterate_getsmbpwnam(149)
   unable to open smb password database.
 [2000/08/02 20:17:11, 1] smbd/password.c:pass_check_smb(500)
   Couldn't find user 'root' in smb_passwd file.
 [2000/08/02 20:17:11, 0] passdb/smbpass.c:startsmbfilepwent_internal(87)
   startsmbfilepwent_internal: unable to open file /etc/samba/smbpasswd.
 Error 
 was No such file or directory
 [2000/08/02 20:17:11, 0] passdb/passdb.c:iterate_getsmbpwnam(149)
   unable to open smb password database.
 [2000/08/02 20:17:11, 1] smbd/password.c:pass_check_smb(500)
   Couldn't find user 'root' in smb_passwd file.
 [2000/08/02 20:17:11, 1] smbd/reply.c:reply_sesssetup_and_X(925)
   Rejecting user 'root': authentication failed
 
 
 
 Hoping for any kind of help. 
 
 
 
 
 -- 
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] 
 /dev/null

Re: samba problems (was: Re: Serial conn. to WIN (success!) - thanks)

[Keith G. Murphy]

Stephan Hachinger wrote:
 
 Hello!
 
 Now, the further problems: I hope perhaps someone can send me some
 suggestions about this 'cause I have read the smb.conf manpage thoroughly
 and don't know what to do (although I said I was probably able to solve
 this).
 
 I'm using a ip connection over slip (serial cable direct) from a WIN 95b box
 to slink. I can also mount my win services (smbmount), no problem. And I can
 use the samba supplied services on the win box. But, the problem is that win
 doesn't find any computer in the Network Neighbourhood and claims it can't
 be browsed. If I Run //computername/resource in win, I can see the
 resource, and then, if I press the change to upper dir button (don't know
 what it's called in English WIN vers), I get, after some time connected,
 the workgroup in the window, and then, after a second click I reach the
 network neighbourhood and then --- the computername is shown
 CORRECTLY!!!
 
 I really don't know what causes this behaviour, and so I'm sending you the
 smb.conf as well as the dialup.dun file with this mail. I'm using Samba
 2.0.5 or so.
 
 Sometimes it also says that the groupname workgroup cannot be found,
 although I've configured both boxes to be in that group.
 
I've run into this a fair number of times.  I think the problem is that
when Windows networking looks for other computers in the neighborhood,
all it can do through TCP/IP is broadcast to local machines.  It needs
WINS to be able to resolve names over a PPP or (I assume) SLIP link. 
(Why, I'm not quite sure; maybe someone can fill me in on this).  Try
setting up My Computer/Control Panel/Network on your Win machine to use
WINS, and point it to the IP address of your Linux box in the DUN TCP/IP
settings.  (pppd has a way to provide the WINS IP address from the
server, so you wouldn't have to set it on the Win machine, but I don't
know if SLIP has this).

In smb.conf on your Linux box, make sure to set:

wins support

I also set:

os level=65
domain master=yes
local master=yes
preferred master=yes

That way, browsing is all done through the Linux box and doesn't drift
around.

One more thing: make sure those workgroup names match on your Win box
and in smb.conf!

samba problems (was: Re: Serial conn. to WIN (success!) - thanks)

[Stephan Hachinger]

Hello!

Now, the further problems: I hope perhaps someone can send me some
suggestions about this 'cause I have read the smb.conf manpage thoroughly
and don't know what to do (although I said I was probably able to solve
this).

I'm using a ip connection over slip (serial cable direct) from a WIN 95b box
to slink. I can also mount my win services (smbmount), no problem. And I can
use the samba supplied services on the win box. But, the problem is that win
doesn't find any computer in the Network Neighbourhood and claims it can't
be browsed. If I Run //computername/resource in win, I can see the
resource, and then, if I press the change to upper dir button (don't know
what it's called in English WIN vers), I get, after some time connected,
the workgroup in the window, and then, after a second click I reach the
network neighbourhood and then --- the computername is shown
CORRECTLY!!!

I really don't know what causes this behaviour, and so I'm sending you the
smb.conf as well as the dialup.dun file with this mail. I'm using Samba
2.0.5 or so.

Sometimes it also says that the groupname workgroup cannot be found,
although I've configured both boxes to be in that group.


Thanks for any help,
Kind Regards,


Stephan Hachinger


 This was my last mail...

  Hello!
 
  Thanks a lot for all your help. Now, I have finally succeeded and I'm
  running samba as server and client.
 
  I've only still got some minor problems, but I think I'll be able solve
  them.
 
  Thanks again to all who helped, and especially to Phil.
 
 
  Kind Regards,
 
  Stephan Hachinger


smb.conf
Description: Binary data


dialup.dun
Description: Binary data

samba problems - more infos - please help

[Stephan Hachinger]

Hello!

I've got some more infos now...

I'm loggin in to the linux box over ttyS1 (getty in inittab with options -L
/dev/ttyS1 115200 network) with the windows dialup. The dialup networking
uses a modem emulation inf (see attachment) for the serial line.

Now, the problem seems to be that the workgroup doesn't appear. I can get to
all other net places (see below) but not to the workgroup in the network
neighbourhood. But, if I rerun smbd -D and nmbd -D, and then logoff at the
win box and log back on (I'm using diplogini), there is a very good chance
that I see the workgroup properly than. That were only the results from some
experiments. Maybe this helps finding my configuration problem.

Kind Regards,

Stephan Hachinger


- Original Message -
From: Stephan Hachinger [EMAIL PROTECTED]
To: Debian User debian-user@lists.debian.org
Sent: Wednesday, October 06, 1999 11:13 PM
Subject: samba problems (was: Re: Serial conn. to WIN (success!) - thanks)


 Hello!

 Now, the further problems: I hope perhaps someone can send me some
 suggestions about this 'cause I have read the smb.conf manpage thoroughly
 and don't know what to do (although I said I was probably able to solve
 this).

 I'm using a ip connection over slip (serial cable direct) from a WIN 95b
box
 to slink. I can also mount my win services (smbmount), no problem. And I
can
 use the samba supplied services on the win box. But, the problem is that
win
 doesn't find any computer in the Network Neighbourhood and claims it can't
 be browsed. If I Run //computername/resource in win, I can see the
 resource, and then, if I press the change to upper dir button (don't
know
 what it's called in English WIN vers), I get, after some time connected,
 the workgroup in the window, and then, after a second click I reach the
 network neighbourhood and then --- the computername is shown
 CORRECTLY!!!

 I really don't know what causes this behaviour, and so I'm sending you the
 smb.conf as well as the dialup.dun file with this mail. I'm using Samba
 2.0.5 or so.

 Sometimes it also says that the groupname workgroup cannot be found,
 although I've configured both boxes to be in that group.


 Thanks for any help,
 Kind Regards,


 Stephan Hachinger


  This was my last mail...
 
   Hello!
  
   Thanks a lot for all your help. Now, I have finally succeeded and I'm
   running samba as server and client.
  
   I've only still got some minor problems, but I think I'll be able
solve
   them.
  
   Thanks again to all who helped, and especially to Phil.
  
  
   Kind Regards,
  
   Stephan Hachinger



mdmcbx4.inf
Description: Binary data

Samba Problems

[Chris Hoover]

I've had samba working on my network, allowing my nt box to see my unix home 
directories.  However, I had to reorganize my NT box (server) and ended up 
reinstalling to free up a hd.  When I did this, I changed the domain from 
PRI_NT_DOMAIN to WINDOWS.  I changed the appropriate line in the /etc/smb.conf, 
but I'm unable to connect from winnt.  I get the following error when I try: 
\\Debian2 is not accessible.  Network path not found.

Does anyone know how to fix this, and/or what it means?  It seems to make no 
since since debian2 is showing up in the neighorhood network.  

Thanks,

chris

Re: Samba Problems

[Haymo Meran]

 I've had samba working on my network, allowing my nt box to see my unix home 
 directories.  However, I had to reorganize my NT box (server) and ended up 
 reinstalling to free up a hd.  When I did this, I changed the domain from 
 PRI_NT_DOMAIN to WINDOWS.  I changed the appropriate line in the 
 /etc/smb.conf, but I'm unable to connect from winnt.  I get the following 
 error when I try: \\Debian2 is not accessible.  Network path not found.

 Does anyone know how to fix this, and/or what it means?  It seems to make no 
 since since debian2 is showing up in the neighorhood network.

Had the same prob But I had to change in the smb.conf

security = server

Don't know what your smb.conf looks like... but the very much saing M$ errormsg 
was the same...

bye haymo

Re: samba problems

[Mario Olimpio de Menezes]

Hi,

Maybe I didn't explain very well (poor english mine!). As I said,
I have three NIC's (the linux is a masq machine). The tcp/ip part is
working ok, since all my internal machines can reach internet
(http,telnet,etc). 
In the smb.conf I added the correct ip's for all interfaces. I
even can connect to winnt machines with smbclient. Better, I can connect
to machines in all three networks (192.168.9.0, 192.168.10.0 and
200.136.52.0) from the linux server. The problem is with the winnt
machines trying to connect to my linux box thru the valid ip. (one of my
nic's have a valid ip). 


192.168.9.0
eth0-|
 | 
192.168.10.0 |
eth1-| |---winnt/win95---
 | |
 |valid ip |
 |---eth2--|-winnt-
linux box


I thought  MacAddr was the problem because it was the only
strange thing I could notice from the winnt machines outside my dept.
Wins is based in MacAddr, isn't it?
Should I put the  linux box IP in the lmhosts of the wins
server?  Could this help? 
Thanks,

On Thu, 24 Sep 1998, Jens B. Jorgensen wrote:

 Ok, first of all it isn't the MacAddr that's needed, it's your IP. Now,
 the machines that can't reach your box, are they on the same physical
 network (for at least one of your ethernet cards)? samba usually only
 sets up one interface and that's the one that corresponds to the IP
 address which matches the host name (at last with the default smb.conf).
 You probably need to edit smb.conf and add an 'interfaces = XXX XXX'
 line. 
 
 Mario Olimpio de Menezes wrote:
 
  Hi,
 
  I can't get the correct MacAddr of my Linux box when I run nbtstat
  in a Windows box.
  Are there some parameters to set in order to have this work
  properly?
  I guess I having problems with the wins server (nt) because it
  can't get the correct MacAddr of my card. FYI, the card is ok. All values
  are correctly reported by ifconfig.
  I have 3 3Com vortex cards, working ok. From the internal dept
  machines I can connect to my linux samba server without problems. Only
  machines from other dept's can't connect to my server.
  TIA.
 
 
 --
 Jens B. Jorgensen
 [EMAIL PROTECTED]
 
 

[]s,
Mario O.de Menezes | Many are the plans in a man's heart, but
IPEN-CNEN/SP   | is the Lord's purpose that prevails Prov. 19.21
Then you'll know the truth, and the truth will set you free John 8.32
'Then you'll know the code, and the code will set you free' Linux

Re: samba problems

[Jens B. Jorgensen]

WINS maps NetBIOS names to IP addresses. When it comes time to send a packet the
MAC Address is gotten through arp. NetBEUI does sit right on top of ethernet 
(and
thus uses MAC Addresses) but this is not the same thing and Linux doesn't 
support
NetBEUI. To complicate things, a NetBT (NetBIOS over TCP/IP, the proper name for
this type of windows networking, described in internet RFCs 1001 and 1002) node
may operate in different modes. A node may be either a B node, P node, M node,
or H node. The difference is mainly how names are resolved (and claimed, etc.). 
In
short, B nodes use broadcast only to resolve names, P nodes only use a specific
WINS server(s), and M  H nodes use combinations thereof. I believe WinNT 
machines
default to operating as Hybrid. This means that first an NT machine will 
broadcast
and if that doesn't work it will contact the WINS servers it's using. That's 
why I
asked about the 'interfaces' line since this controls what addresses nmbd (the
daemon responsible for NetBT Name Service) responds to. You may want to use
'tcpdump' to see what packets are shooting around that ethernet. Also, do you 
have
WINS servers set up? Do you have your samba configured to register with them?

Mario Olimpio de Menezes wrote:

 Hi,

 Maybe I didn't explain very well (poor english mine!). As I said,
 I have three NIC's (the linux is a masq machine). The tcp/ip part is
 working ok, since all my internal machines can reach internet
 (http,telnet,etc).
 In the smb.conf I added the correct ip's for all interfaces. I
 even can connect to winnt machines with smbclient. Better, I can connect
 to machines in all three networks (192.168.9.0, 192.168.10.0 and
 200.136.52.0) from the linux server. The problem is with the winnt
 machines trying to connect to my linux box thru the valid ip. (one of my
 nic's have a valid ip).

 192.168.9.0
 eth0-|
  |
 192.168.10.0 |
 eth1-| |---winnt/win95---
  | |
  |valid ip |
  |---eth2--|-winnt-
 linux box

 I thought  MacAddr was the problem because it was the only
 strange thing I could notice from the winnt machines outside my dept.
 Wins is based in MacAddr, isn't it?
 Should I put the  linux box IP in the lmhosts of the wins
 server?  Could this help?
 Thanks,

 On Thu, 24 Sep 1998, Jens B. Jorgensen wrote:

  Ok, first of all it isn't the MacAddr that's needed, it's your IP. Now,
  the machines that can't reach your box, are they on the same physical
  network (for at least one of your ethernet cards)? samba usually only
  sets up one interface and that's the one that corresponds to the IP
  address which matches the host name (at last with the default smb.conf).
  You probably need to edit smb.conf and add an 'interfaces = XXX XXX'
  line.
 
  Mario Olimpio de Menezes wrote:
 
   Hi,
  
   I can't get the correct MacAddr of my Linux box when I run nbtstat
   in a Windows box.
   Are there some parameters to set in order to have this work
   properly?
   I guess I having problems with the wins server (nt) because it
   can't get the correct MacAddr of my card. FYI, the card is ok. All values
   are correctly reported by ifconfig.
   I have 3 3Com vortex cards, working ok. From the internal dept
   machines I can connect to my linux samba server without problems. Only
   machines from other dept's can't connect to my server.
   TIA.
  
 
  --
  Jens B. Jorgensen
  [EMAIL PROTECTED]
 
 

 []s,
 Mario O.de Menezes | Many are the plans in a man's heart, but
 IPEN-CNEN/SP   | is the Lord's purpose that prevails Prov. 19.21
 Then you'll know the truth, and the truth will set you free John 8.32
 'Then you'll know the code, and the code will set you free' Linux

--
Jens B. Jorgensen
[EMAIL PROTECTED]

samba problems

[Mario Olimpio de Menezes]

Hi,

I can't get the correct MacAddr of my Linux box when I run nbtstat
in a Windows box. 
Are there some parameters to set in order to have this work
properly? 
I guess I having problems with the wins server (nt) because it
can't get the correct MacAddr of my card. FYI, the card is ok. All values
are correctly reported by ifconfig. 
I have 3 3Com vortex cards, working ok. From the internal dept
machines I can connect to my linux samba server without problems. Only
machines from other dept's can't connect to my server.
TIA.

[]s,
Mario O.de Menezes | Many are the plans in a man's heart, but
IPEN-CNEN/SP   | is the Lord's purpose that prevails Prov. 19.21
Then you'll know the truth, and the truth will set you free John 8.32
'Then you'll know the code, and the code will set you free' Linux

Re: samba problems

[Jens B. Jorgensen]

Ok, first of all it isn't the MacAddr that's needed, it's your IP. Now, the 
machines
that can't reach your box, are they on the same physical network (for at least 
one of
your ethernet cards)? samba usually only sets up one interface and that's the 
one
that corresponds to the IP address which matches the host name (at last with the
default smb.conf). You probably need to edit smb.conf and add an 'interfaces = 
XXX
XXX' line.

Mario Olimpio de Menezes wrote:

 Hi,

 I can't get the correct MacAddr of my Linux box when I run nbtstat
 in a Windows box.
 Are there some parameters to set in order to have this work
 properly?
 I guess I having problems with the wins server (nt) because it
 can't get the correct MacAddr of my card. FYI, the card is ok. All values
 are correctly reported by ifconfig.
 I have 3 3Com vortex cards, working ok. From the internal dept
 machines I can connect to my linux samba server without problems. Only
 machines from other dept's can't connect to my server.
 TIA.

 []s,
 Mario O.de Menezes | Many are the plans in a man's heart, but
 IPEN-CNEN/SP   | is the Lord's purpose that prevails Prov. 19.21
 Then you'll know the truth, and the truth will set you free John 8.32
 'Then you'll know the code, and the code will set you free' Linux

 --
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null

--
Jens B. Jorgensen
[EMAIL PROTECTED]

Re: samba problems

[Hamish Moffatt]

On Tue, Aug 11, 1998 at 04:11:37PM +, [EMAIL PROTECTED] wrote:
 Hamish Moffatt [EMAIL PROTECTED] wrote:
 
  However, now 95 users have to supply their network password once,
  which is undesirable. Once entered it seems happy enough, but I would
  prefer that those users didn't have to enter a password.
  
  Any suggestions for a solution?
 
 And what about setting the password for those users in /etc/smbpasswd
 to be blank? Does that work?

It works (I'm using that now) but my system is internet connected
as well, so it's not very secure. I have set allow hosts = to limit
connections but do want to allow some outside access; unfortunately
it does not seem to be possible to set this on a host + username basis.
Still, I think I might be able to use auto-logon in Win95 to have a password
for those machines and not prompt for it. I will try this later.


thanks

Hamish
-- 
Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5
CCs of replies from mailing lists are welcome.   http://hamish.home.ml.org

Re: samba problems

[Hamish Moffatt]

On Wed, Aug 12, 1998 at 12:42:40AM -0700, George Bonser wrote:
 On Wed, 12 Aug 1998, Hamish Moffatt wrote:
 
  It works (I'm using that now) but my system is internet connected
  as well, so it's not very secure. I have set allow hosts = to limit
  connections but do want to allow some outside access; unfortunately
  it does not seem to be possible to set this on a host + username basis.
  Still, I think I might be able to use auto-logon in Win95 to have a password
  for those machines and not prompt for it. I will try this later.
 
 Can you use ipfwadm to block traffic on the netbios port to/from undesired
 locations?

Alas, the one user I do want to allow access to outside the network
has a dynamic IP. Setting passwords for everyone will make it secure
enough for my liking anyway.


Hamish
-- 
Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5
CCs of replies from mailing lists are welcome.   http://hamish.home.ml.org

Re: samba problems

[peloy]

Hamish Moffatt [EMAIL PROTECTED] wrote:

 However, now 95 users have to supply their network password once,
 which is undesirable. Once entered it seems happy enough, but I would
 prefer that those users didn't have to enter a password.
 
 Any suggestions for a solution?

And what about setting the password for those users in /etc/smbpasswd
to be blank? Does that work?

I have just checked smb.conf's man page and it looks like you have to
add:

null passwords=yes

to the global section of your smb.conf, as this parameter defaults to
no.

Good luck!

Eloy.-

--

Eloy A. Paris
Information Technology Department
Rockwell Automation Venezuela
Telephone: +58-2-9432311 Fax: +58-2-9431645

samba problems

[Hamish Moffatt]

I've been running sambades on a bo box which I upgraded to hamm this evening.
The box provides file  printing services to two Win95 boxes and an NT box,
hence the need for encryption.

On hamm, I created the smbpasswd file with mksmbpasswd and set passwords
for the users. Previously I had no security = set, which defaults to
share-level, I believe. The 95 boxes would remember their passwords
and reconnect shares without prompting (desirable), while the NT box
would need to be reminded once on login then would get everything else
ok (acceptable).

Now with samba in hamm, NT requires the password re-entered for every
share, and actually doesn't bother to prompt me when trying to use
the printer, and just says it can't print. So I changed
to security = user, which makes NT happy as punch (never checks
my password with me now, because it is the same as my NT login password).

However, now 95 users have to supply their network password once,
which is undesirable. Once entered it seems happy enough, but I would
prefer that those users didn't have to enter a password.

Any suggestions for a solution?


thanks,
hamish
-- 
Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5
CCs of replies from mailing lists are welcome.   http://hamish.home.ml.org

Re: samba problems

[Eloy A. Paris]

Hi Hamish,

is this solved already or you need help with this? You sent two
messages before and in one of them you say the problem is solved, but
I don't know if it is the problem in your 1st. message or the one in
this message.

Regards,

E.-

 Hi Eloy,
 
 I just upgraded to your latest samba package. Before I was running
 an old samba without password encryption, but now I need to talk
 to it from NT+SP3 so I upgraded it. However I can't even talk
 to it from smbclient!
 
 [1:41am] [EMAIL PROTECTED]:/usr/doc/samba smbclient yodeller\\hamish
 Added interface ip=203.63.216.19 bcast=203.63.216.23 nmask=255.255.255.248
 Server time is Wed Dec 24 01:41:47 1997
 Timezone is UTC+11.0
 Password: 
 Domain=[RISING SOFTWARE] OS=[Unix] Server=[Samba 1.9.18alpha12]
 security=share
 SMBtconX failed. ERRSRV - ERRbadpw (Bad password - name/password pair in a 
 Tree Connect or Session Setup are invalid.)
 Perhaps you are using the wrong sharename, username or password?
 Some servers insist that these be in uppercase
 
 With security=user, I can't get a share listing either; same error.
 I can't get anything from NT either; it just asks me for a password
 all the time and says it was wrong. I did have shadow passwords
 disabled but just turned them on in case it would help; it hasn't.
 
 Any ideas? I have the old sambades going great on another machine.
 On that machine I can smbclient to itself just fine, but not to this
 machine with the new 1.9.18alpha12-1.
 
 thanks,
 Hamish
 


-- 

Eloy A. Paris
Information Technology Department
Rockwell Automation de Venezuela
Telephone: +58-2-9432311 Fax: +58-2-9431645


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

samba problems

[Hamish Moffatt]

Hi Eloy,

I just upgraded to your latest samba package. Before I was running
an old samba without password encryption, but now I need to talk
to it from NT+SP3 so I upgraded it. However I can't even talk
to it from smbclient!

[1:41am] [EMAIL PROTECTED]:/usr/doc/samba smbclient yodeller\\hamish
Added interface ip=203.63.216.19 bcast=203.63.216.23 nmask=255.255.255.248
Server time is Wed Dec 24 01:41:47 1997
Timezone is UTC+11.0
Password: 
Domain=[RISING SOFTWARE] OS=[Unix] Server=[Samba 1.9.18alpha12]
security=share
SMBtconX failed. ERRSRV - ERRbadpw (Bad password - name/password pair in a Tree 
Connect or Session Setup are invalid.)
Perhaps you are using the wrong sharename, username or password?
Some servers insist that these be in uppercase

With security=user, I can't get a share listing either; same error.
I can't get anything from NT either; it just asks me for a password
all the time and says it was wrong. I did have shadow passwords
disabled but just turned them on in case it would help; it hasn't.

Any ideas? I have the old sambades going great on another machine.
On that machine I can smbclient to itself just fine, but not to this
machine with the new 1.9.18alpha12-1.

thanks,
Hamish


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Samba problems.

[Niklas Höglund]

...
Allowed connection from dropzone.flf.lu (192.168.1.20) to Linux root
nobody logged in as admin user (root privileges)
08/13/97 17:04:50 dropzone (192.168.1.20) connect to service Linux root
as user nobody (uid=0,gid=0) (pid 22285)
...

dropzone.flf.lu is a winnt machine, and I log on as grewer on it, but
when I'm trying to mount the linux machine it logs on as nobody (tried
w95 too, same thing).

I'm using smbd 1.9.16p11 (old?)

--
//Regards,
 Niklas

. Email: [EMAIL PROTECTED]
. Phone: +46-707-543009
. Netmail: 2:206/137.12


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

New samba problems

[Leszek Gerwatowski]

Hallo!

I've one problem:

I used to work with samba 1.9.16alpha10 . Everything was fine except one 
thing - after some time started new samba daemons (I was running it as a 
daemon, not from inetd) and they ate my CPU  - idle was  1% and load 
average after 1-2 hours was about 3.00-4.00. So it was nice but not so 
much :-) . So when new samba (1.9.16.p9) became available I've decided to 
make upgrade to this version. But now I can't run it as a daemon!! From 
inetd it runs quite smoothly but response is much slower. I've no 
problems with new multiplicating daemons (naturally) but I've no browsing - 
when I try to search whole network from Win'95 workstation there is no 
serwer available, but when I try to mount directory from server (naturally 
writing exactly the name of the serwer) it works. When I try to use 
smbclient, it prints four or five times strange message - 
get_hostbyname() - host not found serwer1 (serwer1 is the name of my 
linux box) and refuses to work. This name is in /etc/hosts and I run also 
bind withiut any problems!


So I've one question - WHAT'S UP??


Leszek Gerwatowski
[EMAIL PROTECTED]

--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]

Re: samba problems

[Behan Webster]

   Domain=[workgroup] OS=[Unix] Server=[Samba 1.9.15p4]

 I believe two or three loop bugs were found in the earlier releases
 of SAMBA. The current release is 1.9.16p2, you should probably install
 that release. I have been running it for a few weeks (on IRIX 5.3) and
 it seems quite stable (although there are a few browsing problems).

This seems to be the case (i.e. there were bugs in version
1.9.16alpha10) as since I down graded all my hosts to using Samba
1.9.15p4 every thing is fine.  I think I will wait for the debian
package of samba 1.9.16p2 rather than installing it by hand.  I'm
in no hurry to upgrade samba as 1.6.15p4 works just fine.

I would warn others from using Samba 1.9.16alpha10 and would go so
far as to advise debian to remove 1.9.16alpha10 from rex and replace
it with 1.9.15p4 from buzz pending the debian release of samba
1.9.16p2 (yes, that is how broken 1.9.16alpha10 is).  In reading the
samba news group (which I do now) I understand that the new version
is quite stable.

I would just like to finish by saying that this is the first major
problem we have have had in the past year with an unstable version
of debian.  The completeness and robustness of the debian
distribution (even in the, IMHO misnamed, unstable version) continues
to astound me day after day.  Debian truely is the best, most
up-to-date, best supported, and easiest to use linux distribution
that I know of on the market today.

Thanks for everyone's help!


Behan

-- 
Behan Webster
[EMAIL PROTECTED]
(613) 224-7547  or page me at (613) 2~4-7547

Re: samba problems

[Hamish Moffatt]

 About 90% of my /var/log/smb* log files are the line:
 Added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0
 
 It seems that smbd prints this as it starts up.  I just don't

Possible temporary workaround: run smbd/nmbd as daemons, not from inetd.
This means it'll only start up once, and also it should respond slightly
quicker in theory, especially since you seem to be using samba
pretty heavily.


hamish

Re: samba problems

[Don Gaffney]

On Thu, 19 Sep 1996, Behan Webster wrote:

 Martin Budsj| wrote:
 
  My /var/log/nmb* log files are a mixture of the following lines:
  
  more than one master browser!
  connect error: Connection refused
  Domain=[workgroup] OS=[Unix] Server=[Samba 1.9.16alpha10]
  Domain=[workgroup] OS=[Unix] Server=[Samba 1.9.15p4]
  
  
  Looks like you are running both 1.9.15p4 AND 1.9.16alpha10. How many
  nmbd processes is there? Only one i hope...
 
 One of four machines in workgroup was sunning Samba 1.9.15p4 while the
 rest were running Samba 1.9.16alpha10.  I recently upgraded that last
 machine to run Samba 1.9.16alpha10 as well, but it didn't help.  Smbd
 processes are still chewing up tons of CPU on each samba host.
 
 There is only one nmbd process running on each host.
 
 Behan
 

I believe two or three loop bugs were found in the earlier releases
of SAMBA. The current release is 1.9.16p2, you should probably install
that release. I have been running it for a few weeks (on IRIX 5.3) and
it seems quite stable (although there are a few browsing problems).

You can fetch samba from the upstream site: ftp://nimbus.anu.edu.au/pub/
tridge/samba.
_
Don Gaffney (http://www.emba.uvm.edu/~gaffney)
Engineering, Mathematics  Business Administration Computer Facility
University of Vermont - 237 Votey Building - Burlington, VT  05405
(802) 656-8490 - Fax: (802) 656-8802

Re: samba problems

[Behan Webster]

Martin Budsj| wrote:

 My /var/log/nmb* log files are a mixture of the following lines:
 
 more than one master browser!
 connect error: Connection refused
 Domain=[workgroup] OS=[Unix] Server=[Samba 1.9.16alpha10]
 Domain=[workgroup] OS=[Unix] Server=[Samba 1.9.15p4]
 
 
 Looks like you are running both 1.9.15p4 AND 1.9.16alpha10. How many
 nmbd processes is there? Only one i hope...

One of four machines in workgroup was sunning Samba 1.9.15p4 while the
rest were running Samba 1.9.16alpha10.  I recently upgraded that last
machine to run Samba 1.9.16alpha10 as well, but it didn't help.  Smbd
processes are still chewing up tons of CPU on each samba host.

There is only one nmbd process running on each host.

Behan

-- 
Behan Webster
[EMAIL PROTECTED]
(613) 224-7547  or page me at (613) 2~4-7547

Re: samba problems

[Kevin Traas]

On Sat, 14 Sep 1996, Behan Webster wrote:

 My /var/log/nmb* log files are a mixture of the following lines:
 
 more than one master browser!
 connect error: Connection refused
 
 The first two lines about seem to be errors, but I haven't been able
 to find any documentation of what they mean.

I don't know much about Samba on Linux, but I do know quite a bit about 
Microsoft networks.  The master browser line above indicates quite a 
problem.  

Have you recently added an NT Server to your network segment?  I've no 
idea how Samba handles elections (who gets to be master/backup/etc), but 
that may be the source of this problem and the high CPU usage.  

Do you notice unusually high broadcasts on your network?  i.e. slow 
response outside of the Linux box?

Sorry I can't help more.

Kevin Traas
ValleyNet Hardware/Software Committee ChairAbby:  (604) 859-9741
Head System Administrator   Chwk:  (604) 823-4763
Central/Upper Fraser Valley, BC, Canada Miss:  (604) 859-9741
Toll Free Pager:  (604) 918-2054 
Alternate E-Mail: [EMAIL PROTECTED]

samba problems

[Behan Webster]

We've been using samba on our LAN to connect our Windows boxes to
our debian hosts for quite some time now.  Unfortunately, ever since
we've upgraded to the latest version of samba (1.9.16alpha10-1)
we've been experienced problems where smbd processes startup and
use up significant amounts of CPU (keeping the load average above 10!)
At any particular time we have between 4 and 8 smbd processes
running, not apparently doing anything (just using up tons of CPU).

About 90% of my /var/log/smb* log files are the line:

Added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0


It seems that smbd prints this as it starts up.  I just don't
understand why it's being started, as the logs don't point to anything
being done once the smbd interface is up!

My /var/log/nmb* log files are a mixture of the following lines:

more than one master browser!
connect error: Connection refused
Domain=[workgroup] OS=[Unix] Server=[Samba 1.9.16alpha10]
Domain=[workgroup] OS=[Unix] Server=[Samba 1.9.15p4]


The first two lines about seem to be errors, but I haven't been able
to find any documentation of what they mean.

btw, I have run through the samba diagnostics file in /usr/doc/samba
and everything checks out.

This problem has me stumped.  Any help would be appreciated.

Thanks,

Behan Webster

-- 
Behan Webster
[EMAIL PROTECTED]
(613) 224-7547  or page me at (613) 2~4-7547