similar to: automounted filesystem appears empty on first reference

Hello, we recently had a big problem with a very high load on our linux (Sles11 SP3) samba server version 3.6.3. We experienced a system load of up to 90 for 300 active samba users. The result was that hardly any user was able to really do anything (eg access a file via samba). One sympton was visible in a very high share of cpu *system* time (about 25% on each of the 10 CPUs). This system load

Regards, Sent this one before, here's another go: My sambaserver, let's call it sserv, is running Solaris 8 (latest Recommended set) or 9 (tried both) compiled with automount support. When PC client A tries to access a file in a automounted mapping from sserv, the client is freezing and Windows Explorer has to be restarted. The NFS server which the samba server automounts from is a

On Tue, 11 Jul 2017 06:50:42 -0500 John Schmerold via samba <samba at lists.samba.org> wrote: > I am trying to configure a public file share on \\fs1\vol1 > > From a Windows 7 command prompt, I enter: dir \\fs1\vol1 > Windows says: Logon failure: unknown user name or bad password. > > Where am I going wrong? > > Error log says: " SPNEGO login failed:

This is just a minor annoyance, but I wondered if anyone has any insights. When I first boot the system and log in to Gnome, and then plug in e.g. a USB stick or compact flash card, I get an icon for it on the desktop. I can right-click on this icon to "eject" the filesystem, etc. Eventually, though, for no obvious reason, this stops working and I no longer get an icon when I insert a

A setup on howto improve your samba network and simplify it. This is how i setup, sure looks dificult but its all about DNS setup and what you add to it. For AD-DC.s ( AD, TIME, NS, LDAP ) Hostname.FQDN.TLD : max 63chars, incl the .'s allowed chars: a-Z 0-9 - Hostname : sam-dc1.internal.domain.tld IP : what you need/want. ( example 192.168.1.11 ) PTR : 11.0.168.192.in-addr.arpa

hello, I have samba 3.0.21c on an aix 5.2.0.7 server configured to use active directory authentication. However, I need to do something a little funky: The server with samba I will call: sambaserver A server with a user's home directory that is automounted on a few other servers: homeserver The user has on homeserver his files that he works on that he conveniently has automounted on

Background on setup Here is some basic background of my setup I have 3 domains setup running over a IPSEC tunnel over the Internet with one PDC BDC and some file servers at each location all running samba (I am sorry I do not have the version number in front of me for samba) from SUSE enterprise 10 using the LDAP backend. There is a trust setup between all the domains and the IPSEC tunnels is

Regards, Samba 3.0.14a, running on Solaris 8 or Sgi IRIX 6.5.27. Scenario: 1. User has a symlink on his homeshare to a directory, let's call it dir1, which is automounted to the samba server (tried both Solaris samba server and Sgi, same result). 2. In a subdirectory under dir1 there's another directory (dir2) which contains a file (filename.wrl). 3. When the user directs Windows

I'm testing Dovecot as a possible replacement for UW. In my environment the home directories are automounted via NFS from a NetApp. In general this works fine, but Dovecot isn't picking up the automounted directories. Consider the case of Arthur Dent, test user: May 12 10:30:24 testbed dovecot: [ID 107833 mail.info] imap-login: Login: user=<adent>, method=PLAIN,

On Tue, 7 Nov 2017 07:13:19 -0500 Bernard Fay <bernard.fay at gmail.com> wrote: > Yes, our Samba servers are configured as standalone. Windows clients > and Xenservers for storage repositories are connecting to these > shares. > > What does that change for the Unix users as they have to be in the > passdb.tdb file anyway??? > > OK, you asked ;-) Lets say that

I am trying to configure a public file share on \\fs1\vol1 From a Windows 7 command prompt, I enter: dir \\fs1\vol1 Windows says: Logon failure: unknown user name or bad password. Where am I going wrong? Error log says: " SPNEGO login failed: NT_STATUS_NO_SUCH_USER" - that must have something to do with this, but I thought that was the point of "map to guest = Bad User"

Hello I''ve got nested ZFS filesystems exported via NFS. They are mounted on the clients using automount (from a NIS map). But: only the root exported filesystem shows any contents on the clients. Any sub-directories it has are fine, but any sub-filesystems are empty. ie. NIS map auto.stuff contains "stuff server:/stuff/images" server% zfs get sharenfs stuff/images

On Wed, Feb 26, 2020 at 10:09 AM Philippe LeCavalier < support at plecavalier.com> wrote: > On Thu, Feb 20, 2020 at 10:56 AM L.P.H. van Belle via samba < > samba at lists.samba.org> wrote: > >> >> A setup on howto improve your samba network and simplify it. >> This is how i setup, sure looks dificult but its all about DNS setup and >> what you add to

Hello, This is user MichaelConvey. I would like to add a section under TipsAndTricks/Filesystem Tips called "Configuring Automount in Gnome for USB Drives". The content will include something like the following: 1) yum install gconf-editor 2) In gnome, go to Applications/System Tools/Configuration Editor 3) In the graphical editor, in the left window, go to

Additionally to the problems I reported earlier, I'Ve discovered another problem with my server/client setup. find reports find: WARNING: Hard link count is wrong for ./foo: this may be a bug in your filesystem driver. Automatically turning on find's -noleaf option. Earlier results may have failed to include directories that should have been searched. in one directory and if I

I want to use --min-size to copy just large files (and their necessary parent directories), but everything I've tried copies *all* the source directories, and creates them empty on the destination even if they don't have any big files in them. I only want the minimal directory hierarchies that contain the big files. This doesn't work: $ rm -rf /tmp/foo $ rsync -ai --min-size

Hello, I believe that I have found a bug in the 2.0.5a configure process. If the source tarball is extracted to an automounted directory, and you run configure, it will fail the fcntl_lock test, resulting in this message at the end of the configure process: WARNING: No locking available. Running Samba would be unsafe To verify that the automounted directory is the problem, I put an "exit

Using Samba 2.2.7a on FreeBSD 4.7-STABLE. #uname -a FreeBSD fileserver1.smartrafficenter.net 4.7-STABLE FreeBSD 4.7-STABLE #0: Mon Dec 16 19:41:03 EST 2002 toor@fileserver1.smartrafficenter.net:/usr/obj/usr/src/sys/FILESERVER1 i386 All day long, constantly, I get the following messages in syslog: Jan 14 13:37:55 fileserver1 smbd[57969]: [2003/01/14 13:37:55, 0]

Using Samba 2.2.7a on FreeBSD 4.7-STABLE. #uname -a FreeBSD fileserver1.smartrafficenter.net 4.7-STABLE FreeBSD 4.7-STABLE #0: Mon Dec 16 19:41:03 EST 2002 +toor@fileserver1.smartrafficenter.net:/usr/obj/usr/src/sys/FILESERVER1 i386 All day long, constantly, I get the following messages in syslog: Jan 14 13:37:55 fileserver1 smbd[57969]: [2003/01/14 13:37:55, 0]

My syslog is constantly bombarded with these messages: Mar 27 07:15:35 fileserver1 smbd[70359]: [2003/03/27 07:15:35, 0] lib/util_sock.c:get_socket_addr(1012) Mar 27 07:15:35 fileserver1 smbd[70359]: getpeername failed. Error was Socket is not connected Mar 27 07:15:35 fileserver1 smbd[70359]: [2003/03/27 07:15:35, 0] lib/util_sock.c:write_socket_data(499) Mar 27 07:15:35 fileserver1