similar to: keepalive not working?

Samba-4.0.10 in AD mode. I need to have an account with an empty password. After checking the smb.conf manpage (and also smbpasswd manpage), I added to the smb.conf file: null passwords = Yes The result is a warning from commands like smbstatus: WARNING: The "null passwords" option is deprecated I cannot find the new option to achieve this. How is it supposed to be configured

I have attached a patch which adds null packet keepalive functionality to the client. This patch is made against the current CVS tree as of 3/14/01. Please consider this patch for inclusion in the OpenSSH main tree. This patch is based upon and includes code from the Chris Lightfoot (chris at ex-parrot.com) patch posted 2/23. The original patch from Chris is at:

Greetings, I don't know how common an issue this is as I haven't found much in the list archives that was helpful to me, so I'm hoping for some pointers. FYI, we have samba 2.3.3a-6 running on the 2.4.18-10 kernel. There seems to be an issue with smbfs mounts at times where connectivity may be lost (e.g. Win share becomes unavailable) causing local processes such as lsof or ps,

Dear All, we are experiencing severe problems with Samba 2.2.0 (with quota support) running on a dual processor (400MHz) Sun E450 running Solaris 2.7. This is used as a central file server for student diskspace, accessed by approx 1200 PCs running NT 4. Up until recently we experienced some, what we assume to be, loading issues with connections during the middle of the day being slow.

Hi, I had a linux server installed with samba 3.0.9-2.6 (SuSE 9.1) and a samba shared folder among 12 PC under WinXP/Win7. The linux server has been replaced by a new one a week ago. The new machine runs samba 3.5.4-5.1.2x86-64 with the same shared folder and the same smb.conf file. Till then, when the PCs try to connect to the samba share via explorer a window opens with the message "Num?ro

I have a very small Samba4 system that supports my W7 clients. So small, in fact, that I have only one DC (right now.) My DC is a 32-bit Pentium4 processor (512Mb RAM, 60Gb hdd), small form factor case, I got lucky and found for cheap$$. My member server is a Intel DuoCore PC with RAID 1 (mdadm) hard drives mirrored running on Debian 7.8.0. And my backup machine is a seperate (does only backup)

Hi, We've been experiencing this same problem, however, with Samba 3.0.7-1.3E.1 running on RedHat ES 3.0. We've also experienced this on 2.2.7x on RedHat 9. The problem has been intermittently happening over the last several weeks, (I've posted list about it). This message, along with the others in the thread, describes the symptoms that we're seeing, however, I haven't

Hi, I am running a Panther Server as a domain controller with a Mac Tiger Server (all latest patches) as the location of home folders and group shares. I have one group of users who keep losing connection to the server (both home and group folders). The can only reconnect to the server if they logoff the XP client and login again. I have loads of other XP users and Mac clients who do not have

Hello, I'm using Samba 4.0.5 in Debian Wheezy as a member server of a DC (in Debian Wheezy too with Samba 4.0.5) and the clients are Windows7 Pro. The users use shares in the member server. Sometimes, after the logoff of the users in the Win7 clients, there are connections with the member server whiches never stop. I can see it with the "smbstatus" command which point PID out to me

Hi, I would be extremely grateful if you could cast your eye over my problem with getting Windows 7 PC back onto on a Samba domain? I have the current version from lenny-backports: 2:3.4.8~dfsg-2~bpo50+1, the client is windows 7 Ultimate. logins and profiles and nelogon scripts all seemed to work back in Feb 2010 using the instructions here: http://wiki.samba.org/index.php/Windows7 However

Hi all Thanks to David Collier-Brown for the mail on Friday - we are looking into it right now. Our setup is: RedHat 6.1, Samba 2.0.5a, on a HP LH3 NetServer - 256 MB, 5x9GB RAID 5, also running Apache and the Intranet. Cisco Catalyst 2900 (24 port) switch, and a mix of HP and NetGear hubs. PCs are connected to the hubs and then upload to the switch, the servers are straight onto the switch.

We have recently upgraded to Samba 2.05a on HPUX 10.20 and 11.0 from version 1.9 & 2.0. Since this upgrade, we have experienced the following issues and problems: 1) Lost connections to samba drives from Win95 pcs. 2) Failure to authenticate mounted drives from NT machines. 3) Using smbstatus, getting "semaphores not started by root" errors 4) Several inexplicable error messages.

A couple weeks ago I upgraded my servers from 3.0.14a to 3.0.24. My main server generally has about 800 to 1200 people connected to it at any given time. Its a Solaris 8/Sparc system, samba is configured as security = domain . Everything seems to be functioning fine, I haven't noticed any odd behavior, haven't had any complaints. But, a few weird errors have got me concerned. 1) I

I mentioned this problem in a previous post (in November). This time I'm including a patch. Version: OpenSSH_2.3.0p1 Keywords: setsockopt keepalive hang masquerade interactive Symptom: For protocol 2, socket options (especially keepalive) are not being properly set for OpenSSH_2.3.0p1, even when request in the config files. Furthermore (for either protocol), keepalive is only set for

My expectations are probably wrong, but I had to manually kill a process to unlock a file when I think it should have killed itself. I have deadtime set to 15 and keepalive at default (300). I opened a file on my server in Excel, then shut down the machine. Hours later someone tells me the file is locked. Shouldn't keepalive have detected that the machine was off in 5 minutes?

I have set /etc/ssh/sshd_config with: KeepAlive yes ClientAliveInterval 3 However, no KeepAlive type messages seem to be sent. I've verified this by looking at the network lights, which don't flicker every 3 seconds. I am attempting to keep interactive ssh sessions alive longer. If don't type anything for about 2 minutes, the sessions close. If I run a "idle"

On Tue, Nov 01, 2016 at 05:09:34PM -0700, Jeremy Allison via samba wrote: > On Tue, Nov 01, 2016 at 05:16:47PM -0500, Ed Siefker via samba wrote: > > My expectations are probably wrong, but I had to manually kill a process > > to unlock a file when I think it should have killed itself. > > > > I have deadtime set to 15 and keepalive at default (300). I opened a file on

as I monitor that one installation from the other thread "GID range full!" I see sessions in smbstatus that use the LinkLocal-range of IPv6: ipv6:fe80:: nice, why not .. Interesting for me: the same 2 PCs using these IPv6 sessions also run a smbd-process via IPv4. 2 connections in parallel. I have no problems with dual stack and don't want to turn off IPv6 or so. I just wonder

Hi, I hope some of you have been in a similar situation and can shed some light on this: I have a VPN connection to a Samba 4.1.4 server and when I use Word 2010 on a W7 client to open an existing file I often get the following error: "document.docx has been locked for editing by another user." I should clarify that the document is not in use by anyone (confirmed by smbstatus), and

Hi, I started with provisioning samba 4.0.9 then upgraded to 4.0.10 Can anyone please tell me if this is a feature ? Using I get the following results, samba -V Version 4.0.10 smbstatus Samba version 4.0.10 Windows 7 x64 SP1, Open Active Directory Users and Computer, Domain Controllers, I select my DC Click properties and chose Operating System I get Name: Samba Version: 4.0.9 Thanks Les