similar to: Hanging smbd Processes

I have a problem with Samba 2.0.3 on Solaris 7. We use an multi-user NTrigue Server, based on NT3.5.1, as an application server for running windows applications on Sun workstations. All workstations are connected to an NIS-, File- and application server running under Solaris 7, host name "enterprise". When a UNIX user starts NTrigue the user logs in to the PDC server based on NT4.0, SP4.

Hello, I am currently testing my old samba configuration, 1.9.18p10, under samba 2.0.2. Everything appeard o.k. for the first few hours, but then I started receiving calls from users of our Citrix based multi user NT 3.51 servers, that some of them could not connect to the samba shares. We are using two Citrix based boxes. Windd from Tektronix and NTRIGUE. I only had one user on the Windd

Hi All: I am using NTRIGUE ( from Insignia Solutions) server which is basically WINNT3.5. I am not been able to connect from NTRIGUE to my samba server (1.9.17p1) which is running on my HPUX machine. I can easily connect from NT4.0 server machine and Win95s under same user account and password. I have set the registry setting EnablePlainTextPasswork:D_WORD=1 as documented in WinNT.txt Every

Dear Samba list, I have an issue with what seems to be group permissions, when using a stand-alone Samba file server. I have a directory where files are meant to be writable to a group of users. The permissions on Linux are: root# ls -ld /users/misc/teaching /users/misc/teaching/* drwxrws--- 2 teaching csos 4096 May 15 08:47 /users/misc/teaching -rw-rw---- 1 teaching csos 17 May 15

On Wed, 15 May 2024 17:27:53 +1000 Paul Szabo via samba <samba at lists.samba.org> wrote: > Dear Samba list, > > I have an issue with what seems to be group permissions, when using a > stand-alone Samba file server. > > I have a directory where files are meant to be writable to a group of > users. The permissions on Linux are: > > root# ls -ld

Dear Rowland, Thanks for the hint, it sounds like I should get rid of the line "acl_xattr:ignore system acls = yes" in smb.conf. I think I read that there was a change in its meaning, around version 4.5 or so. Thanks, this gives me something to experiment with. Could you please tell me what I would "lose" if I also dropped the "vfs objects = acl_xattr" line? I do

samba@samba.org wrote: > SAMBA Digest 2150 > > For information on unsubscribing see http://samba.org/listproc/ > Topics covered in this issue include: > > 1) Autoconnect on restarts doesn't work > by =?iso-8859-1?Q?Str=F6mberg_Peter?= <Peter.Stromberg@scania.com> > 2) Re: How to backup from Win to Linux using smb? >

All, Sometimes when I do an rsync, it times out and leaves on orphaned process on the remote machine. I am running rsync over ssh using public key authentication. I synchronize about twenty-five machines, and this problem only appears on one of them. It worked until recently on this machine. I don't know what changed or what is different. I run rsync with a command line like this

Hello, I'm running Samba 3.2.5 on Debian, with tdbsam backend. For the past few days, I've had trouble with starting Samba (which I do routinely once a day) but with users unable to login on Windows workstations. When this happens, the current smbd.log shows no activity (not even the "starting samba" event) and the previous day's smbd.log shows entries like these:

Hello, Is there any reason why an IP-phone would pounder on port 5060 ? My firewall blocks the public IP because it thinks the remote IP is port scanning on port 5060. I think the phone is just registering but for some reason it does this repeatedly in a very short time. Oct 28 09:01:48 astserver kernel: Firewall: *UDP_IN Blocked* IN=eth0 OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:00:00

The Samba Team are pleased to announce Samba 1.9.18p5. It may be fetched via ftp from : ftp://samba.anu.edu.au/pub/samba/samba-1.9.18p5.tar.gz This is a bugfix release, designed to address issues that users have reported with the 1.9.18p4 release. It is intended that the next Samba release will be an alpha of Samba 1.9.19, which will contain significant new functionality for integrating Samba

Hi, I have a proxy/firewall, I want to dnat requests for 193.205.140.106 on port 443 towards 10.2.15.23 and requests for 193.205.140.106 on ports 4330 and 3389 towards 10.2.15.25, these rules must apply from internet, loc and fw (some client use a proxy on fw to reach these servers) I have tried with the following rules: DNAT net dmz:10.2.15.23 tcp 443 -