similar to: Two Machines and Samba

Hello. I'm running RH 7.1, with Samba 2.2.2. VERY often I get a SIGHUP to smbd and it'll dump the workgroups. I also get a "Discarding datagram from IP 216.202.200.103. Source name ROUTER<00> is one of our names" all the time also. This line FILLS my logs. I don't understand this one, because I have the interfaces line specified in smb.conf to use only the local

Hello All, I have recently switched back over from using the MySQL backend to the standard smbpasswd file in an effort to make our implementation of Samba better.\ I am still having a great problem with getting messages from the nmbd daemon saying that ------------------------ [2005/09/10 14:53:43, 0] nmbd/nmbd_packets.c:process_browse_packet(1050) process_browse_packet: Discarding

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

I am having trouble with one of my samba PDC's. It does not recognize itself as the domain master browser even though it is set to be so. I can not add machines to this domain and I suspect this is why. Has anybody seen this or know what causes it? Notice this: DOMAIN_ALBANY(3) current master browser = ALBANY_PDC DOMAIN_NYC(2) current master browser = NYC_PDC

I've been messing around with running samba 3.4.14 inside a freebsd jail over the last couple of days, and am running into an odd problem where wbinfo -u and wbinfo -g succeed, but getent passwd fails (insofar that it shows only local users, but none of the domain users). Here's my smb.conf: [global] interfaces =192.168.0.16/32 bind interfaces only =yes security

Hello, I'm running redhat 3 enterprise server as. I installed samba during the install, and it's been running for about a week now. I looked in the LogWatch, and noticed this bit: --------------------- samba Begin ------------------------ **Unmatched Entries** auth/auth_domain.c:check_ntdomain_security(289) check_ntdomain_security: could not fetch trust account password for domain

Aug 6 11:21:44 linux nmbd[2193]: [2014/08/06 11:21:44.614859, 0] ../source3/nmbd/nmbd_packets.c:1174(process_lanman_packet) Aug 6 11:21:44 linux nmbd[2193]: process_lanman_packet: Discarding datagram from IP 192.168.1.6. Source name LINUX<00> is one of our names ! Aug 6 11:22:50 linux nmbd[2193]: [2014/08/06 11:22:50.279516, 0]

Hi I have a bunch of FreeNAS servers and a TrueNAS HA server all spamming the logs with these messages every minute about their own source name (examples below). These boxes are on two physically separate networks, and I find it unlikely both networks should have some sort of undetected loop. Any ideas on how to debug this? Samba version is 4.1.18. FreeNAS box on network A " Jan 5

On Tue, Jan 05, 2016 at 11:48:32PM +0100, Torkil Svensgaard wrote: > Hi > > I have a bunch of FreeNAS servers and a TrueNAS HA server all > spamming the logs with these messages every minute about their own > source name (examples below). > > These boxes are on two physically separate networks, and I find it > unlikely both networks should have some sort of undetected

Hi team, I'm dealing with AS/U as a member server on a Samba 3.0.20 PDC. Jonction seems ok, and from the member server I can see PDC's shares (with net view) and authenticate user (with net logon user passwd /domain:domainname). On the other side, I fell into timeout when running smbclient -L member from the PDC. Here is a log.nmbd loglevel 10 from PDC as there is no other log

Hi all, We have a weird problem, Samba is providing an outdated IP address for a client (XP Pro) machine. This means that the client machine is not contactable by the other machines on the network. The IP is that which was previously used when connecting via the company VPN, although the machine has/is now plugged onto the company network and had has new IP via DHCP. This problem continues

Hi, after quite some testing I do now have my Samba4 setup in production use. The setup mainly consists of an AD-Controller and an AD Member Server which provides file shares to about 20 Windows 7 clients. Everything is working well so far except for two somewhat 'special' clients. For these I observe the following: 1) On the AD Member Server periodically (every hour) appears a message in

On 01/06/2016 01:23 AM, Jeremy Allison wrote: >> Jan 5 23:17:32 storage4 nmbd[34068]: [2016/01/05 23:17:32.086480, >> 0] ../source3/nmbd/nmbd_packets.c:1174(process_lanman_packet) >> Jan 5 23:17:32 storage4 nmbd[34068]: process_lanman_packet: >> Discarding datagram from IP 172.21.140.17. Source name STORAGE4<00> >> is one of our names ! >> " >

Hi Denis, Thanks for taking the time to answer. Yes, I may have been wrong with --forced-sync and --full-sync since the start but in fact I wanted to make sure to force replication between the servers. Here is what I have noticed: - replication works from dc00 -> dc00 but not from dc01 -> dc00: [root at dc00 ~]# samba-tool drs replicate DC01 DC00 dc=ad,dc=lasthome,dc=solace,dc=krynn

Hello Dear Fellows, I'm trying to join my vbox windows xp sp3 machine, to my samba server. When I inform my administrator user: "root", and his password XP says: "Erro durante a tentativa de ingresso no dom?nio "CORP_TRIARIUS": O dom?nio especificado n?o existe ou n?o p?de ser contatado." What in english means somthing like: "An error occurs when try to

HI ! I have a problem with nmbd, i can't logon on a WinXP machine (wfassi-PC ,everything was alright until at a moment user coudnt connect anymore) , here is log.nmbd : [2013/07/15 16:39:26, 5] libsmb/nmblib.c:797(read_packet) Received a packet of len 50 from (192.168.0.89) port 137 [2013/07/15 16:39:26, 4] libsmb/nmblib.c:106(debug_nmb_packet) nmb packet from 192.168.0.89(137)

I had a problem similar to my current one a week or so ago, and I was encouraged to upgrade from Samba 2.2.9 to 3.0.7, which I did. Now that I've completed that nightmare, the problem I initially set out to fix is still there, just different. Namely: I am trying to set up Samba 3.0.7 on a SuSE 9.1 box as an LDAP PDC whose only job will be authentication. Our LDAP server is on a separate

On 21/08/2020 22:08, Rowland penny via samba wrote: > On 21/08/2020 21:40, vincent at cojot.name wrote: >> On Fri, 21 Aug 2020, Rowland penny via samba wrote: >> >>> This works for me: >>> >>> rowland at devstation:~$ sudo ldapsearch -H >>> ldaps://dc01.samdom.example.com -D 'SAMDOM\Administrator' -w >>> 'xxxxxxxxxx' -b

Hi Andrew, Hi Rowland, I just spent close to one hour debugging this with one OpenShift specialist from RedHat. What we figured was: 1) both of my configs work (auth and group-sync) and are in fact correct. 2) OCP group sync does not sync the groups that have no explicit 'member' Attribute or groups that are 'default' groups (E.g: 'Domain Users') where membership is

On 21/08/2020 21:40, vincent at cojot.name wrote: > On Fri, 21 Aug 2020, Rowland penny via samba wrote: > >> This works for me: >> >> rowland at devstation:~$ sudo ldapsearch -H >> ldaps://dc01.samdom.example.com -D 'SAMDOM\Administrator' -w >> 'xxxxxxxxxx' -b 'dc=samdom,dc=example,dc=com' >>