similar to: nmblookup failing

Hi, I'm just installing Samba for the first time and have a problem with name resolution on my test client. Samba 3.0.8 is installed on a RHES system named 'fileserver1 (.our.xxx.edu)'. The clients are Windows 2000 and XP systems. This is a subnet that is part of a larger campus network. There is no Domain, just a workgroup called 'our_adm'. I have a very simple smb.conf file

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

When I setup Samba4 I already had a master and slave bind9 server so I copied the relevant dns information to my master server however I don't know how to make my existing server authoritative for the zone. It will send notifies to the slave and allow ddns updates but the slave shows this error: "slave-server named[1187]: client 1.1.1.1#22792: received notify for zone

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

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

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

On Thu, Jan 05, 2023 at 01:28:55PM -0500, Nick Couchman via samba wrote: >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

Running samba version 3.2 on AIX 6.1. Mapping share on windows 7 workstation. I can map the share using \\<ip<file:///\\%3cip> address>\testarea. If I attempt to map using using \\servername\testarea<file:///\\servername\testarea> I receive an error. smbclient -L //<servername>/testarea on the unix box is successful When I run a net view command I receive the

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

On 15/02/16 17:22, Fernando Favero wrote: > 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 >

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, we are operating the IT of a small non-profit organization with a Samba server (2.2.5) and roughly 15 Win2k workstations. Everything works fine so far but one single issue: Printing messages from Outlook Express: only the header of the mail is printed, no single line of the body. All the domain users are standard-users (I'm not sure about the correct English wording, may be someone

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

Hi! Any Ideia ? Sorry to send again, as I sent on Sunday :-D Regards; On 05-08-2018 14:12, Carlos wrote: > > 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 >