similar to: Authoritative DNS Server

Hello, everyone, I'm seeing some inconsistent behavior across SMB clients when configuring shares using the "msdfs proxy" parameter, and was hoping to get some advice from the community on this. My issue is that various SMB clients seem to behave differently when this parameter is pointed as a path that includes a sub-folder under the root share. So, given the following share

Hi, I already posted this to smb-clients, but I believe that is a very low volume list. We have a very complicated dfs root. Now I'm not positive that this is how we should have done things, but it works very well with Windows clients, so it hasn't been thought about here. This does not work with smbclient or smbmount. I'm using freshly built smbclient from Samba 3.0.21a.

Hi, I have a question again about my test environment. I have dc1, dc2, fileserver1, and dc3. dc3 is on an another site, and is functioning as fileserver too. As I read in the documentation, I cannot (shouldn't) use idmap config parameters in the smb.conf on my dc3. Unfortunately, first I copied that parameters too from fileserver1 (I use rid backend on fileserver1). So, I removed the idmap

Hi! I have two server samba member domain. Version 4.8.3(Compilated) Running in Ubuntu LTS 16.04 With GlusterFS(Replicated) and Heartbeat(for HA) IP A: 192.168.200.1 (DNS: Fileserver1) -> Master IP B: 192.168.200.2 (DNS: FIleserve2) -> Slave IP C:192.168.200.10 -> (DNS: Fileserve) -> Heartbeat -> IP that stays with master server , when UP, if down IP "junp" for

My smb.conf files. The OS is a CentOS 7 DC Server 1 ------------------------------- [global] workgroup = EXAMPLE.COM realm = campus.example.com netbios name = DC-SERVER1 server role = active directory domain controller idmap_ldb:use rfc2307 = yes dns forwarder = 8.8.8.8 dsdb:schema update allowed = true winbind max clients = 2000

Hi, environment: new Centos 6 installation out of the box. somebody has an idea what causes this error mail to be sent? ---8<--- Subject: Cron <root at fileserver1> /usr/local/asc/bin/ascservicemonitor 2>&1 >/dev/null Content-Type: text/plain; charset=UTF-8 Auto-Submitted: auto-generated X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/root> X-Cron-Env:

Hi, Following DNS configuration of multiple DCs recommended on the wiki https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Di rectory#DNS_Configuration_on_Domain_Controllers , clients are unable to open windows shares based on the server IP, for example \\133.1.1.24 . However they work fine opening either the netbios name or the DNS name, for example \\FILESERVER1 or

Hi List! I have a share on an samba3 domain member (fileserver). The PDC is samba3 also. If i look on the file permissions with the explorer for shares on the PDC the owner is like MYDOMAIN/user. But if i look on the shares from my samba domain member (fileserver) they will be FILESERVER1/user. How can i change this to MYDOMAIN/user automatically for every share. this seems important for

On 27.06.2018 15:17, Rowland Penny via samba wrote: > What is in /etc/krb5.conf ? > > Rowland > I think there is a Problem with krb5.conf Fileserver1 root at srv-031:~# cat /etc/krb5.conf [libdefaults] default_realm = DOM.EXAMPLE.COM dns_lookup_realm = false dns_lookup_kdc = true root at srv-031:~# Fileserver with login Error root at srv-007:/var/log/samba# cat

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

I have an odd automount problem. The first time I look in an automounted filesystem (when the mount is requested), it is empty; the second time it is not. Moreover, I only see this behavior on Centos 4.x systems, but not on Centos 5.0 systems going to the same fileserver. Here's an example, with some details simplified to clarify. In this example, fileserver1 is exporting fs1.

All, first off thanks for any advice on this issue. Last night, my fileserver crashed on me. When i came in this morning, here is what the syslog was filled up with: May 20 21:54:26 fileserver1 nmbd[15324]: [2004/05/20 21:54:26, 0] nmbd/nmbd_packets.c:process_browse_packet(1063) May 20 21:54:26 fileserver1 nmbd[15324]: process_browse_packet: Discarding datagram from IP 192.168.1.6. Source name

hi everyone i am hoping for a bit of direction here, i've tried everything i can find that even closely relates to this. i have a samba server that has shares that can be accessed from windows by simply typing \\192.168.1.1 in windows file explorer, its name has just been changed to fileserver1 and is in dns as fileserver1. it is also in the dns as fserver1. before the name change everything

Hi, I can't get "net view \\<servername>" to work from my Windows test client. It fails with "The network path was not found". I followed some of the online debugging guides and have found that a couple of the test nmblookups on the server are failing. The server is named 'fileserver1' and its IP address is 155.2.196.251 for the purpose of this email.

Hi, This is slightly offtopic, but I have been trying to resolve that problem for two days now without much success. It looks like this may be something that works with CENTOS5, but not with CENTOS6! I have two machines, fileserver1 and server5. fileserver1 runs on CENTOS6 (virtualized, if this is important), server5 runs on Centos5. Both are running with the most recent updates. Server5 is a

On Mon, 6 Aug 2018 10:18:41 -0300 Carlos via samba <samba at lists.samba.org> wrote: > Hi! > > Thanks for anwser! > > Well, GlusterFS  just replicating(it is ok). > > Problem is access second server with specific name..... Yes, but what specific name ? is it the machines short hostname (netbios name) or what ? > > Popup appears requesting domain

Hello, We are using Samba only for file sharing. Because we are missing space in the first Samba server, we need to add a second Samba server. While building this new server i came up with the questioning about sharing the passdb.tdb file among different Samba servers? Would this be feasible? The idea is that all users should be able to access any file servers according with theirs needs. Or

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