similar to: The case of the disconnecting network shares

Hi Jeremy, No, I don't mean "deadtime". I mean auto disconnect. Specifically, the command "net config server /autodisconnect:-1" was run on each client machine. If deadtime is a server configuration item perhaps you could point me in the direction of some documentation where that is covered. The documentation for smb.conf is, to put it very mildly, incomplete.

On Tue, Dec 15, 2015 at 02:48:21PM +1100, John Gardeniers wrote: > We recently completed our Samba 3 to Samba 4 transition without too > many serious problems but one rather annoying issue has cropped up > since the migration. Network shares on our file server become > disconnected overnight, whether idle or not. This was never a > problem with Samba 3 but since upgrading Samba on

Hi Jeremy, Using Samba without Windows seems rather pointless, as no other OS needs it, nor can test it to any truly useful extent. Thanks for point out the man page, which I've always taken as be referring to Samba 3, not Samba 4. I can only wonder why there's a site dedicated to Samba 4 documentation and this information isn't there. If the default deadtime = 0 and we

Hello, I stepped through the archives of this list, but could not find a thread dealing with exactly this problem we are experiencing here. Server HP-UX 10.20 Samba 2.0.6 security = domain deadtime = 500 ... that should be enough The win2k clients map a drive and everything is working fine. after a period of inactivity (about half an hour) win2k somehow disconnects the mapped drive and marks

After awhile, my connections from my PC to my samba server end up with a red "X" in them (share disappeared) if I leave my explorer window open. If I click on these, they "wake up" and continue to function (and the red X's go away). If I close my explorer window (while the red X's are there) and reopen it , they are gone. An attempt to reestablish these

I have a couple of Linux directories that are being exported via Samba running under SuSE 10.0. On the Windows side, each of them is assigned a (mapped) drive letter. In the "My Computer" list they initially show up as "Disconnected Network Drive". If I attempt to access a file within one of them, the access fails with an indication that the drive does not exist. (For

We recently moved our Linux file servers from Debian Woody to Debian Etch (v4.0r3). We use the current stable Debian Samba package which is version 3.0.24. Since moving to this Samba version from 2.2.8a-0.1 we see that Windows clients are very slow to list the 5 network drives mapped by our domain login script in Explorer or "My Computer". It can take 10 seconds or so before the drives

I am getting red crosses on the mapped drives of some win2k pro machines connecting to a samba pdc. I don't have them logging into the domain and the drives are disconnecting (it happens on win2k server too). There is a parameter for win2k server to autodisconnect the drive after 15 minutes which can be changed with: net config server /autodisconnect:TIME and there is a registry key in

Hi Robert, It doesn't break compatibility with MS, unless you're talking about the RSAT DNS tool, which is a lot more cumbersome than a text editor anyway and it's pretty much assumed that if you're using Samba you're a Linux sysadmin, so not being able to use the RSAT DNS tool should not be a problem. I haven't read Mark Andrew's comment, not being on the Bind

Maybe this has been asked many times, but I could not find it in the list archive (in this case could someone please address me to the right thread?) I've an XP professional client (SP1) connected to a 2.2.7a samba server running on a redhat 6.2 box (kernel 2.2.22). I can log on and access samba shares, but the XP box keeps losing these connections. Log file just tell me that:

Hi, Trying to be simple and direct. My last email didn't get answers. Thank you and best regards. Problem: ----------- W2K workstations remains connected do samba server at port 139, even after logoff, and this causes: false wtmp information and no possibility do control (even no fail proof) simultaneous logins. Workaround ( not acceptable )

Hi! I'm running a RedHat 7.2 server with Samba 2.2.3a - but recently I have a problem that mapped drives on Windows 2000 workstations get disconnected and have problems reconnecting (error message is something like "local device name already in use" when I try to browse the drive in Windows Explorer). Any idea what causes this problem ? Regards, /Brian

> Since you have taken the disk apart it will now be useless as within the > enclosure there could have been a vacuum or an inert gas. >From what I know gas filled disks didn't exist in the times when 3X0GB was on a 2" drive. > > You will never be able to recover any data on the disk unless you go and > pay > for a professional data recovery organisation to read the

Hi, I am using samba 2.2.5. My problem is with windows 2000, the mapped network drive share losses connection after a period of time, e.g. 30 minutes. You will see an "X" marked red in the mapped drive letters. I looked up microsoft's website for persistent connections problems but the suggestion is already set in my register keys.

Hello, Has anyone written R functions for applying self-controlled case series methods (http://statistics.open.ac.uk/sccs/). In fact only thing needed is to modify glm function to allow absorption of effect. Eg. in Poisson model individual effect is used as factor, but it is considered as nuisance term where parameter estimates are not needed. Could anyone point how absorbing individual

We're using the Sernet Samba v4.2.4 with internal DNS and I can't find the DNS logs. Where does the Samba 4 internal DNS log queries? Thanks. regards, John

On 11/4/2015 4:13 PM, John Gardeniers wrote: > Nobody? Surely somebody knows where Samba 4 logs its DNS queries, or > was this was a huge oversight and the internal DNS doesn't get logged > at all, as appears to be suggested by my utter failure to locate such > logs. > > On 28/10/15 14:28, John Gardeniers wrote: >> We're using the Sernet Samba v4.2.4 with

I have a machine running redhat 6.2 and samba 2.0.6 that does a persistent mount to my Windows 2000 machine for the purposes of serving files via FTP. The samba connection occasionally times out it seems, I get the message smb_request: result -32, setting invalid smb_retry: new pid=20679, generation=12 and it generates a new connection I've got SO_KEEPALIVE active in the socket options in my

Has anyone here managed to get sudo working with Samba 4 AD users, using either ldap or sssd, with sssd preferred? If so, can you please point me in the direction of whatever instructions you used? It seems like there are a bunch of tutorials on the subject, each with different, and sometimes conflicting, information but none of those I've tried work for me. regards, John

Hi Rowland, I Upgraded from Samba 4.4.2 and we have tried the FQDN without success. regards, John On 21/11/16 08:02, Rowland Penny via samba wrote: > On Mon, 21 Nov 2016 07:42:30 +1100 > John Gardeniers via samba <samba at lists.samba.org> wrote: > >> Hi Louis, >> >> While it wasn't spelled out, it was firmly implied in my previous >> message that