similar to: Nmbd crash with failure to open wins.tdb

Hi Guys, Since the automatic fedora update to 23c I'm having problems with samba crashing when a share access is attempted. However, I also notice that the nmbd daemon isn't being started up properly (though its startup script, through init.d, shows it as starting up OK). The error that is being shown in the logs is: [2006/09/28 20:06:35, 0]

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 list I'm running a samba 3.0.24 with an ldap backend and as a print server. The server is also serving printer drivers for my Windows clients. If more information is needed please let me know. I have a question about tdb files. Some of my tdb files haven't been touched since my installation in december 2005 and I'm thinking if this is something I should consider critical or not.

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

Hi, please imagine the following scenario: We have 4 local samba networks consisting of multiple samba machines and Win95 and NT machines as well. They all talk to each other and all works well. We have one central (samba) WINS server for all 4 nets. These 4 nets are connected together and communicate to the outside world through a firewall. Now I want to connect to exactly one share on the

Hello together! I have an problem with the wins server, based on a Gentoo distribution with Samba 3.0.24. The problem is following: After an restart of samba everything works fine, but after an undefined time period its not possible to make an nmblookup for some other computers. The samba server is also configured as wins server. an cut from the smb.conf: ...... domain master = Yes

I've just fixed a bug (#528 in bugzilla) to do with wins hook functionality. The wins hook parameter is broken in Samba 3.0.0 but will be fixed in 3.0.1. The attached patch against the release samba-3.0.0.tar.gz file can be used to fix it. Tim. -------------- next part -------------- Index: nmbd_winsserver.c =================================================================== RCS file:

Hi @all, does anybody know, where privileges are stored? deveis # net rpc rights list 'Domain Power Users' -U root%password SeMachineAccountPrivilege SeBackupPrivilege SeRestorePrivilege SePrintOperatorPrivilege SeDiskOperatorPrivilege But: deveis # ls -l /var/lock/samba/*.tdb -rw------- 1 root root 8192 Nov 13 20:14 /var/lock/samba/account_policy.tdb -rw-r--r-- 1 root root 696 Nov

Hi guys, I realy need your help. It looks like SMBD doesn't want to talk with NMBD, but why? When I run the command: nmblookup torpc8 The result is: querying torpc8 on 10.5.255.255 Got a positive name query response from 10.5.2.27 ( 10.5.2.27 ) 10.5.2.27 torpc8<00> That is correct. When I run the command: smbclient -NL torpc8 The result is: resolve_wins: Attempting wins lookup for

Hello Have a trouble. I have mashine with two interfaces. Samba running at both with the same name of computer. In wins-servers wins.dat i see next string: "GRAND#20" 1044171787 192.168.1.1 192.168.2.1 46R It's ok. But for ALL mashines in any interfaces with any IP (192.168.1.X or 192.168.2.X) returned first IP in list: ------------------ [2003/01/30 11:03:21, 3]

Hi there...this problem has me banging my head against a wall.... Until last week I was running Samba 2.2.7a on an old Slack box. I decided to upgrade as I needed more drive space and wanted something more current. I went with Fedora Core 2 and am running 2.6.6-1.435 kernel. I was using the default Samba install that came packaged with this release of Fedora and decided to try

We're running samba 2.0.7 on an alphalinux machine (kernel 2.2.16, this is redhat-alpha 6.0, if that's important) and nmbd is crashing with an internal error. See the logs below (log.nmb at the bottom). I'd do some checking around on the samba mailing list archives, but they've been down for some time now. nmbd generates this message on startup. When I ran it from the shell

When I start winbindd (Samba v2.2.3a on Linux), I get the entries in log.winbindd shown below. What's the story on all those complaints about file "unexpected.tdb"? There is no general problem with Samba writing to that subdirectory: # ll /var/lock/samba/ total 288 -rw-r--r-- 1 root root 696 Feb 12 22:01 brlock.tdb -rw-r--r-- 1 root root 231 Feb 13

Helo , System : redhat 8 DS: netcape 4.16 Samba version : RC1. I am upgrading from samba3b3. Everything ( except changing passwd for user xp pro PC and I try to use rc1 to resolve ) seems ok in beta 3. On rc1 I Can't connect For a few second I can do : nmblookup -S l1serv2 added interface ip=172.29.160.100 bcast=172.29.167.255 nmask=255.255.248.0 querying l1serv2 on 172.29.167.255 Got

Hi all! I am using samba server at the company i work. Samba version is: 2:3.2.5-4lenny9 Some settings: os level = 255 domain logons = no wins support = yes domain master = yes local master = yes preferred master = yes i have dhcp configured witch sends wins server address (this samba servers address) to all clients. After I (re)start samba within a minute or so all computer of our network

Hi everybody I installed 2 subnets, one with a samba PDC fully functional and the other with just one linux client (called CLIENTE) with samba running a basic configuration. Subnet 1 has a samba PDC called BAR (domain FOOBAR with ip 192.168.1.1) that is also the wins server for both subnets and the domain master browser for 192.168.1.0/24 bar:/var/log/samba # smbclient

I'm having some difficulties joining a Win2k workstation to a Samba domain. This particular workstation is my work laptop (DRUMMSW01) which normally operates as a member of a standard Win2k domain called BIZ. At windows startup/logon, BIZ is specified as the domain. At home, my Samba PDC's workgroup/domain is HOME.LAN When I try to browse shares on HOME.LAN with the Win2k laptop, I

Guys, I'm running Samba 2.0.7 on a Solaris 7 box and in the log.nmb I'm getting this error when trying to get a machine to join the domain. There is a quad ethernet adapter in the client machine, however I'm not using it. Can someone explain the below error or tell me why it's showing up? Thanks, PhilY tail -f log.nmb [2001/01/02 11:50:20, 1]

Ok, after several months of pulling my hair out I finally fixed WINS and browsing at out Univesity. It ended up being an acutal bug, er bad code segment. To explain we have a large number of clients ~1000+ at any one time over 6 subnets. Browsing was spuratic at best. nmbd sucked up %70 of the proccessing power of a sparc 5. Well after serious investigation I traced it down to two lines of

Hello, I run Samba 3.0.23d on a Host with SuSE 10.2, configured as PDC with LDAP-Backend. This is working so far since some month. But one USer can't log in. Ith seems that samba does not have the permission to acces the netlogon-share, whre the profile from "Default User" is located. The folder is readable for everyone, so, I think that this is not the Problem. Here is the