similar to: WINS isn't working correctly and I think somebody is trying to exploit a security hole...

Hello, I am using samba 2.0.4b on Linux 2.0.36. Since I changed some of the parameters in my smb.conf I have a very strange Problem. Everytime my Samba-Box wins the browselist election process two nmbds are started and my WinXX-Clients do not get access to samba (I could see the server but not access the shares nor login to the domain). smbclient -L server from server works fine. From another

Hello. Time after time users can not log in in domain and im see this in logs(time stamps deleted): nmbd/nmbd_logonnames.c:become_logon_server_success(124) become_logon_server_success: Samba is now a logon server for workgroup HQ on subnet 172.16.1.3 ...skipping... nmbd/nmbd_incomingrequests.c:process_name_release_request(80) process_name_release_request: unicast name release request

Hi guys, I would like you to help me with two problems we have here with samba. It works fine on almost all the situations but we're unable to connect from a win95 machine with two identities simultaneously. The situation is that: john and eric have their own account in the server (Unix running samba). They share another account (say netmen). They need access to

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

Am Do 01.02.2018 um 12:04 schrieb Martin Schwenke: > Hi Nicolas, > > On Thu, 1 Feb 2018 10:57:59 +0100, Nicolas Zuber via samba > <samba at lists.samba.org> wrote: > >> I try to update two clustered samba file servers. Right now samba 4.7.0 >> with ctdb is running on both of them. To update samba I stopped ctdb on >> one of the servers, and compiled and

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:

I am seeing a BUNCH of these type of messages in my log.nmb file. the IP address varies, with only 2 different ones showing up. process_node_status_request: status request for name *<00> from IP 206.139.7.109 on subnet REMOTE_BROADCAST_SUBNET - name not found. The other IP address is 192.68.22.214 Unfortunately, the log does not have time stamps, so I don't know when this is

Hi, I'm running Samba 2.0.4b on a Debian Linux (v2.2) PC. If I look at the "log.nmb" file there are many messages: [1999/10/25 08:39:19, 0] nmbd/nmbd_namequery.c:query_name_response(95) query_name_response: Multiple (2) responses received for a query on subnet 130.199.xxx.yyy for name WORK<1d>. This response was from IP 130.199.xxx.zzz The frequency is every 5 minutes.

SMBv1 (the anonymous thing behind network neighborhood) because of the massive security problems it caused was decprecated. Microsoft came up with network neighborhood and they've shut it down due to their bad implementation. Samba, likewise, doesn't support SMBv1 by default. On 7/12/20 10:29 PM, Michael Jones via samba wrote: > I'm trying to diagnose why my windows 10 clients

If you have 1 member server, you could enabe nmbd in that server. Or install : llmnrd on linux and/or avahi-deamon if you dont have a member. And make sure you can use "proxy dns" as in, The primary DNS domain on linux should match (see in windows) CMD: ipconfig /all The : - primay dns suffix - DNS Suffix search order Then you are able to use \\hostname or \\hostname.FQ.DN.TLD

A reasonable alternative is to run Christgau's excellent Web Service Discovery host daemon (wsdd) on the samba server and make sure the Function Discovery Provider Host and Function Discovery Resource Publication services are running on the Windows 10 machines. Get wsdd from here: https://github.com/christgau/wsdd.git You can then stop and disable the nmbd on the samba machines as it's

Hello all, This my first mail in this list. We have succesfully setup a samba server at our 1st attempt, next we go in another site and try the same things but now it seems we got it all wrong! The facts: we have a linuxbox (named enlogic) (REdHat 7, kernel 2.2.18, samba 2.0.7)and one winbox win98se (named ndemou). Our workgroup is localenlogic. No other PC (not even a Hub because we've

hello, I read this in my ./samba/var/log.nmb process_node_status_request: status request for name *<00> from IP 145.72.37.14 on subnet REMOTE_BROADCAST_SUBNET - name not found. As my subnet is 193.190.195.0, I don't understand this message. Could help me to understand? Thanks, -C. Dumont

Hello, in the last days I found some entries in nmb.log on one of my servers: process_node_status_request: status request for name *<00> from IP 195.232.44.19 0 on subnet REMOTE_BROADCAST_SUBNET - name not found. (repeated many times) The host on this ip is not exactly in my domain :-) # nslookup Default Name Server: localhost Address: 127.0.0.1 > set type=PTR > 195.232.44.190 Name

Our log.nmb file fills up very quickly with the following pattern of messages: [2000/06/19 05:10:59, 0] nmbd/nmbd_namequery.c:query_name_response(93) query_name_response: Multiple (2) responses received for a query on subnet 129.130.10.136 for name NT.CIS.KSU.EDU<1d>. This response was from IP 129.130.10.24 [2000/06/19 05:10:59, 0] nmbd/nmbd_namequery.c:query_name_response(93)

This is a repost with some new information: Our log.nmb file fills up very quickly with the following pattern of messages: [2000/06/22 11:58:25, 0] nmbd/nmbd_namequery.c:query_name_response(93) query_name_response: Multiple (2) responses received for a query on subnet 129.130.10.136 for name NT.CIS.KSU.EDU<1d>. This response was from IP 129.130.10.24 [2000/06/22 11:58:25, 0]

Thanks for the replys... Just a basic samba server...being accessed by windows 7 to the gc and tmr shares with \\10.10.171.9\gc and \\10.10.171.9\tmr This has been running for a year without any issues...till the update yesterday afternoon :-( The file server is Ubuntu 18.04 and there was an update to Ubuntu 18.04.1, which I thought would be a mild step. The current version of samba is...

Hello, Don't know what happened, but Samba stopped serving up shares. Top shows 'smbd' using 66% of the cpu and 'rpc.mountd' using 33%. The samba log on shows; [2006/01/19 16:34:54, 0] nmbd/nmbd.c:main(668) Netbios nameserver version 3.0.13-1.1-SUSE started. Copyright Andrew Tridgell and the Samba Team 1994-2004 [2006/01/19 16:40:03, 0]

I'm not sure whether this is a samba problem or not - but thought someone on the list will probably know. After quite a bit of fiddling - I think Samba is now doing what I want it to - providing file and printer sharing for my windows machines. However - my Centos 5.1 Linux box Can't browse the windows machines from the gnome/nautilus interface. I know the windows machines are

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