similar to: Discard datagram messages

Hello All, I am having a problem trying to ger Samba wot work again. It was working a few days ago and now it has stopped. My OpenVPN is working just fine but Samba does not seem to find the names. I was also trying to set it up so that the users could browse to our PeoplesQuest workgroup after which they could login to their account. ----------------------------------------- [2005/08/21

Here's the sitch: I have a RH 6 machine and an NT 4.0 SP3 machine that I want to use Samba to make the Linux box space available to the NT client. There is no DNS, and there is no Internet connection. Each of the two machines has a "dummy IP", specifically 192.168.255.253 (NT) and 192.168.255.254 (Linux). Trying to browse on the NT box results in either a "Cannot obtain list of

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

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

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]

Greetings All, Can some one please tell me what causes this: --------------------------------------- [2005/08/19 01:45:07, 0] nmbd/nmbd_nameregister.c:register_name_response(130) register_name_response: WINS server at IP 172.16.0.1 rejected our name registration of PEOPLESQUEST<00> IP 172.16.0.1 with error code 5. [2005/08/19 01:45:07, 0] nmbd/nmbd_workgroupdb.c:fail_register(228)

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

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 ! >> " >

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

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

greetings All, I have been reading over the Tinc manual and have become very interested in the "4.2 Multiple Networks" section of the manual. In particular, I am wondering if I read this correctly in that by using: `-n, --net=netname' Use configuration for net netname. then I can have multiple daemons running on the same machine. If I have 3 machines A, B, and C with A being

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

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

Ensure that the size filled in by userland in the datagram header matches the size of the buffer passed down in the IOCTL. Note that we account for the size of the header itself in the check. Acked-by: Jorgen Hansen <jhansen at vmware.com> Acked-by: Aditya Sarwade <asarwade at vmware.com> Signed-off-by: Andy King <acking at vmware.com> Reported-by: David Ramos <daramos at

Ensure that the size filled in by userland in the datagram header matches the size of the buffer passed down in the IOCTL. Note that we account for the size of the header itself in the check. Acked-by: Jorgen Hansen <jhansen at vmware.com> Acked-by: Aditya Sarwade <asarwade at vmware.com> Signed-off-by: Andy King <acking at vmware.com> Reported-by: David Ramos <daramos at

Signed-off-by: George Zhang <georgezhang at vmware.com> --- drivers/misc/vmw_vmci/vmci_datagram.c | 583 +++++++++++++++++++++++++++++++++ drivers/misc/vmw_vmci/vmci_datagram.h | 55 +++ 2 files changed, 638 insertions(+), 0 deletions(-) create mode 100644 drivers/misc/vmw_vmci/vmci_datagram.c create mode 100644 drivers/misc/vmw_vmci/vmci_datagram.h diff --git