similar to: nmbd: Ignoring request packet with opcode 5

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

Running samba-3.5.2 I notice this in the log.nmbd file after starting samba: =============================================================== [2010/05/08 19:10:44.652249, 0] nmbd/nmbd_packets.c:738(queue_query_name) queue_query_name: interface 1 has NULL IP address ! [2010/05/08 19:10:44.652298, 0] nmbd/nmbd_packets.c:738(queue_query_name) queue_query_name: interface 1 has NULL IP address !

Hi I've got a home-made, small file server running on Samba 2.4.1.11 from Debian Wheezy backports repo. I've noticed following lines in log.nmbd file: [2014/11/17 22:54:00, 0] nmbd/nmbd.c:66(terminate) Got SIGTERM: going down... [2014/11/17 22:54:00, 0] libsmb/nmblib.c:856(send_udp) Packet send failed to 127.0.0.1(137) ERRNO=Operation not permitted [2014/11/17 22:54:00, 0]

Hi, Problem: When our network has any glitches causing a network time-out for more than a few minutes, our samba servers lose their connectivity with our WINS server even after the network is restored. This causes the WINS server to tombstone the name registration for the samba server(s), thereby causing clients to not connect through the browser. SMB connections are not affected so the

The only thing related to 'addresses' in my /etc/samba/smb.conf file is a "hosts allow": hosts allow = 192.168.3.0/24 127.1 I'm going to ignore the 'local hosts case, as if I solve the other, the localhost case may get solved by inference. I thought the 'hosts allow' would allow any host on the local 192.168.3.0/24 subnet. The hosts have no problems

Dear Sir, I want to ask that since I have installed Linux RedHat 7.1 with Samba Server inside it. I also configured it follow some books , however, my problem now is that . I can brower the linux computer through other computer in the same domain. However, when I try to access it, then it will said network problem and can't access it. I have tried ping to both computer name and ip address

Hello everyone, I have a curious problem that seemingly came out of nowhere. After searching through the archives, I see that I am not the first to discover this problem, but so far, no solution has been found. In June 99, Mark Drummond mentioned a similar problem. Recently, I started seeing nmbd errors on the console. A little poking around revealed a log file full of these errors. Below is a

Hi there, I just got a new machine with Redhat Enterprise Workstation and samba 3.0.0-14 pre-installed. I am trying to connect it to my existing network which has a redhat v8 samba v2 PDC controlling 16 or so win2k and winxp machines. In the nmbd log I get this error 3 times every 5 seconds or so: nmbd/nmbd_packets.c:process_nmb_request(1448) process_nmb_request: Multihomed registration

When using the global options: ================================ interfaces = eth0, lo bind interfaces only = Yes hosts allow = 192.168.1. 127. ================================ and a secondary loopback address: ================================ ~ # ip addr show dev lo 3: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet

Looking for a solution to this problem. I have Googled all over the place but haven't found a definitive answer. I have a Samba Server that ONCE was on a network where there was SECOND Samba Server with IP Address 192.168.20.3. Today, the FIRST server is on a network with an address range 10.0.0.0/255.255.255.0 and it has no way of finding that SECOND Server 192.168.20.3. However,

On 25 May 2018 at 17:09, Rowland Penny via samba <samba at lists.samba.org> wrote: > On Fri, 25 May 2018 16:39:22 +0200 > Henry Jensen <hjensen at mailbox.org> wrote: > > > > > OK, maybe this is something which should be mentioned in the wiki. The > > reason I got to this was that I wanted to try sysvol replication. The > > wiki mentions at > >

Hi All, On my first internal NIC, Samba is working perfectly. On my new, second internal NIC, I am getting the following in my messages log: libsmb/nmblib.c:send_udp(793) Packet send failed to 192.168.254.255(138) ERRNO=Operation not permitted nmbd/nmbd_packets.c:send_netbios_packet(163) send_netbios_packet: send_packet() to IP 192.168.254.255 port 137 failed I though .255 was a reserved

My Linux/Samba setup was working beautifully, until I was moved to a different net. Now the Linux box is not visible to any of the Win boxes. My investigations show the following problems: 1. 'netstat -a' shows thousand of messages in the udp/rcv queue for ports 137/138 2. the log.nmb file has lots of 'socket read error 111' messages 3. nmblookup -B own-address does not return my

Found nmbd down with this in the log; [2001/02/27 19:21:36, 0] libsmb/nmblib.c:send_udp(755) Packet send failed to 192.168.113.255(138) ERRNO=Network is unreachable [2001/02/27 19:21:36, 0] libsmb/nmblib.c:send_udp(755) Packet send failed to 192.168.22.255(138) ERRNO=Network is unreachable [2001/02/27 19:22:18, 0] libsmb/nmblib.c:send_udp(755) Packet send failed to 192.168.3.1(137) ERRNO=Network

I get the following errors on the console of my newly installed 2.0.4b server on a Sun E4000: nmbd/nmbd_packets.c: (1412) find_subnet_for_nmb_packet: response record not found for response id <num>. nmbd/nmbd_responserecordsdb.c: (240) find_response_record: response packet id <num> received with no matching record I don't know the internals well enough to decipher these, can

On Sat, 9 Jun 2018 22:58:11 +0200 Henry Jensen <hjensen at mailbox.org> wrote: > Hi Mark, > > Am Sat, 09 Jun 2018 16:22:09 -0400 > schrieb Mark Foley <mfoley at ohprs.org>: > > > I've downloaded the Samba 4.8.2 package from the Slackware64 current > > repository. I am preparing to install the package (after a full > > backup). Are there any

I made the observation that I'm able to make a call with my SIP client (kphone) even when I'm not registered/authenticated. Of course, when I'm not registered at asterisk, people can't call me, but it's still a huge security hole, that unregistered Clients can make calls. Is there a way to tell asterisk to only allow registered clients making calls? I know about the

On Thu, 07 Jun 2018 08:54:51 +0200 Henry Jensen wrote: > > Am 6. Juni 2018 19:55:52 MESZ schrieb Mark Foley via samba <samba at lists.samba.org>: > >I am running Samba 4.4.16 on Slackware64 14.2. I have a domain member > >Windows 7 workstation. I > >upgraded the hardware on this computer a couple of weeks ago. I deleted > >the computer from > >the domain,

On Fri, 25 May 2018 15:07:57 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > > running "samba-tool ntacl sysvolcheck" doesn't fix this. > > Well it wouldn't, they are both borked. > > Just do administration from Windows OK, maybe this is something which should be mentioned in the wiki. The reason I got to this was that I wanted to

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