similar to: process_node_status_request and nmbd log file

One of my samba Domain controlers is trying to reach two IP addresses of 192.168.221.1 and 192.168.91.1. The samba server is not even on a 192.168 subnet. It is currnetly on a 172.16.12.x subnet. How can I trace this down? Why would the server look to access a 192.168 subnet? Can someone just point me in the right direction? Thanks for any info Here is a snipit from the nmbd log. If you

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

I manage a Samba server that has been working nicely for a couple of months (after it replace the old Samba server which worked happily for years). We use LDAP for accounts, but don't use domain logons or anything fancy. All users have their home dir on Samba mapped to drive 'M:'. In their home, there are symbolic links to various directories they're entitled to access. Links

Hello list, I don't know what is breaking my samba box but I am really very worried and confused !! My samba server has no problem with linux client. "smbclient -L <samba IP> -U <samba user>" runs well. No problem at all. But whenever I try to access the shares from Win-XP it reports that "path not found". And after repeatedly trying the same Win-XP

Hi all Im pretty new to Samba. I would like to use Samba as a PDC, for some funny reason I cant browse the network. I cant find other machines on the network. The server says its a PDC, but my win clients (win2000) says its not. [2005/09/29 19:36:09, 1] nmbd/nmbd_incomingrequests.c:process_node_status_request(328) process_node_status_request: status request for name DYNACHEM<00> from

Hi, I cant find any wins options in your smb.conf. I think you?ll need Wins for proper Network browsing. Maybe this Link would help you: http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/NetworkBrowsing.html ________________________________ Von: samba-bounces+benjamin.oeltze=fujitsu-siemens.com@lists.samba.org im Auftrag von bclark@eccotours.dyndns.org Gesendet: Do 29.09.2005 19:48

Hi, here is a client computer and a server computer (Debian Wheezy, armel, samba Version 3.6.6, IP address: 192.168.1.2, Name: xyz). Problem: wins doesn't answer nmblookups by the client on the broadcast address: client$ nmblookup -S xyz querying xyz on 192.168.1.255 name_query failed to find name xyz Why is that so? How to fix this? When I specify the the server IP I do get an answer:

Pardon the long log file but I'm fairly new to WINS servers and probably don't know what I'm doing. We've have two subnets (lets call them xxx.xxx.xxx.??? and yyy.yyy.yyy.??) I have one samba/linux server on both networks xxx.xxx.xxx.2 and yyy.yyy.yyy.2. xxx.xxx.xxx.2 is set up to be a domain master and yyy.yyy.yyy.2 is setup to be a local master with xxx.xxx.xxx.2 as its master.

I would like to understand how to make my samba-3.0.0 (-15, from Fedora Core 1) a PDC and how to make a XP/Pro box member of that domain and to add a domain user account, and eventually to ad a few more linux boxen as domain members into that domain. This is the output of the PDC box testparm (the PDC box has two eth interfaces, only eth1 (192.168.1.* and 127.0.0.1 should access the PDC):

As part of our deployment of FC updates we have upgraded our office server from 3.0.24-3 to 3.0.24.4. We got some strange results. Shares that have the same name as the users home directory and/or the same name as their users id became inaccessible. For example, my user id is kens, my home directory is in /home/kens and there was a share of it called kens. There is also a common share

Pardon me for resending the message, I am not sure whether the original message was posted at all. Mapping Samba shares from this particular server is either getting slow or rarely getting denied. Occasional error messages in log.smbd [2005/07/24 08:40:39, 1] auth/auth_server.c:(363) password server PASS_SERVER rejected the password I have configured a virtual server here, not using the real

Hello, I'd be grateful for any hints or insight into the following messages which are being written to the log.nmbd file on my samba server "samba2000". samba2000 is running Samba version 2.2.8a. Sincerely, Derek Moran [2003/06/10 15:40:17, 0] nmbd/nmbd.c:main(795) Netbios nameserver version 2.2.8a started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2003/06/10

Hello all, I'm in the process of moving over my Samba server (using LDAP). I believe everything is functioning correctly, except for this error I get when nmbd starts. Looking back at my old server, it was apparently doing this as well... so it may not even affect needed functionality. Still, I'd like to figure out why it's happening! If anyone has an idea, please let me

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

On Wed, Dec 11, 2019 at 11:03:07AM -0500, Michael S. Tsirkin wrote: > On Fri, Dec 06, 2019 at 03:39:12PM +0100, Stefano Garzarella wrote: > > When we receive a new packet from the guest, we check if the > > src_cid is correct, but we forgot to check the dst_cid. > > > > The host should accept only packets where dst_cid is > > equal to the host CID. > > >

On Wed, Dec 11, 2019 at 11:03:07AM -0500, Michael S. Tsirkin wrote: > On Fri, Dec 06, 2019 at 03:39:12PM +0100, Stefano Garzarella wrote: > > When we receive a new packet from the guest, we check if the > > src_cid is correct, but we forgot to check the dst_cid. > > > > The host should accept only packets where dst_cid is > > equal to the host CID. > > >

On Thu, Dec 12, 2019 at 07:56:26AM -0500, Michael S. Tsirkin wrote: > On Thu, Dec 12, 2019 at 01:36:24PM +0100, Stefano Garzarella wrote: > > On Wed, Dec 11, 2019 at 11:03:07AM -0500, Michael S. Tsirkin wrote: > > > On Fri, Dec 06, 2019 at 03:39:12PM +0100, Stefano Garzarella wrote: > > > > When we receive a new packet from the guest, we check if the > > >

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

On Mon, Aug 19, 2019 at 11:38 AM Hans Verkuil <hverkuil-cisco at xs4all.nl> wrote: > > Hi all, > Hi Hans. > The patches in this series can be applied independently from each other. > > If you maintain one of these drivers and you want to merge it for v5.4 > yourself, then please do so and let me know. If you prefer I commit it > to drm-misc, then please review and

On Thu, Dec 12, 2019 at 01:36:24PM +0100, Stefano Garzarella wrote: > On Wed, Dec 11, 2019 at 11:03:07AM -0500, Michael S. Tsirkin wrote: > > On Fri, Dec 06, 2019 at 03:39:12PM +0100, Stefano Garzarella wrote: > > > When we receive a new packet from the guest, we check if the > > > src_cid is correct, but we forgot to check the dst_cid. > > > > > > The