similar to: Samba binding to two IPs, even when specified not 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

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

I admit theres a LOT about the windows networking I dont understand - and even though this may NOT be a SAMBA issue per se, I thought I'd post it here. Have a 400gb samba server thats been working well (am upgrading to current patches today, btw). I've got 3 Win2k workstations, on two subnets, that have drives mapped, and connect every morning on startup just fine. All the machines

Clients using W2k Sp2 are randomly no longer connecting to my Samba PDC server running 2.2.5 so i thought to upgrading to 2.2.6 but the problem still remains. What can be appened? Just a few days ago all was running very very fine!! THE ERROR IS: THE DOMAIN IS NOT DISPOSABLE AT THE MOMENT! =============================================================== I only have activated Bind9 and DHCP but I

Hello All, I have recently switched back over from using the MySQL backend to the standard smbpasswd file in an effort to make our implementation of Samba better.\ I am still having a great problem with getting messages from the nmbd daemon saying that ------------------------ [2005/09/10 14:53:43, 0] nmbd/nmbd_packets.c:process_browse_packet(1050) process_browse_packet: Discarding

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'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

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

Hello Dear Fellows, I'm trying to join my vbox windows xp sp3 machine, to my samba server. When I inform my administrator user: "root", and his password XP says: "Erro durante a tentativa de ingresso no dom?nio "CORP_TRIARIUS": O dom?nio especificado n?o existe ou n?o p?de ser contatado." What in english means somthing like: "An error occurs when try to

Hello, I'm new to the list and pretty much a newbie to linux and samba. I'm quick learner though. I have been losing my samba share upon ocasion recently, below is a portion of the syslog from the time period that I think is when the share goes down. A reboot of the server or a restart of the smbd fixes the problem (....until it happens again) I don't know what SIGUP is or why

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

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

Hallo all, Last week I am trying to solve strange problem. Suddenly without no system config change the samba stops work properly. Symptoms: - it hangs after few days or hours (a worse case), there are many processes (from hundreds to thousands of smbd processes) - no new connection can be established - it happend regardless of samba package version, I've tried all available versions

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. I got this email-address from BUGS.txt file of the samba distribution. I read it carefully. I got configured and working samba, I work with samba above one year. I still have a problem, and, according to the samba log output, I think it's probably a bug. When I try to use the shares with audit support, I have my Far disconnected and telling me that something is wrong. I have that

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]

Platform: RedHat 7.0 Samba version: 2.2.7a Client platforms Windows 2000 Pro SP3 Number of clients: 7 This is my SAMBA configuration file # Samba config file created using SWAT # from localhost.localdomain (127.0.0.1) # Creation Date: 2002/10/21 15:26:01 # Global parameters [global] workgroup = SABER netbios name = SHADOW server string = SAMBA-PDC interfaces = eth0 192.168.1.13 encrypt

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